I have prospects booked a meeting in the last 10 bookings; there were no shows, and I want to automate the outbound call to confirm a booking.
Do I have to have the consent from the prospect first?
Two parts here. The build is the easy bit. The consent side is the one to get right before you switch it on.
On the build: yes, you can automate it. Trigger an outbound call off your booking data (anything marked no-show or unconfirmed) and fire it through Retell’s Create Phone Call API, or Batch Call if you want to run the whole list at once. I’d wire it up in n8n so the booking event kicks off the call on its own. One gotcha: numbers you buy from Retell can only dial US destinations, so if your prospects are elsewhere you’ll need an imported number.
On consent, I’m not a lawyer and this really depends on where you and your prospects sit, so treat the below as things to check rather than legal advice. A few flags worth knowing. In the US, the FCC now treats AI-generated voices as artificial or prerecorded under TCPA, which can mean you need prior express consent depending on the call. Some regions also require you to disclose that the caller is an AI. And if you record, two-party consent areas need the prospect told up front.
The upside is these people booked with you and gave their number for that booking, so a quick call to confirm the appointment sits on much friendlier ground than cold outreach. To keep it clean I’d add a consent line to your booking form so they agree to a confirmation call, have the agent say it’s an AI assistant early, keep it strictly to confirming the booking they made, and honour any opt-out. If you’re unsure for your region, worth a quick check with someone who knows the local rules first.
Where are you and your prospects based? I can get more specific if I know the region.
Russell
amplifyautomation.ai
Hello @krittiya.clark Yes, Retell can place the outbound confirmation call — the capability is not gated by us. Whether you can lawfully place it is a consent question that sits with you as the account of record, not with Retell. A few things to keep in mind:
- US AI-voice calls fall under our TCPA addendum, which requires prior express written consent from each recipient, retained for 5 years. A prospect handing over their phone number at booking is often treated as consent for a transactional/confirmation call about that same meeting, but whether that meets the ‘written’ bar depends on your booking flow’s disclosures and checkbox language — that’s a call for your counsel, not us.
- Keep the call scope tight to confirming the booked meeting. Adding promotional or upsell content on the same call changes the consent analysis.
- Build the agent to identify itself at the top of the call (who’s calling, that it’s an AI, and the reason — confirming their meeting). This aligns with state AI-disclosure rules and our prompt best practices.
- DNC scrubbing, calling-hour limits, and AI-disclosure compliance are your responsibility under our ToS — Retell does not maintain a suppression list on your behalf. Capture opt-outs via post-call webhook or a custom function, and typically customers integrate a third-party DNC scrubbing vendor (we don’t endorse a specific one).
For the definitive ‘is our booking flow’s consent sufficient’ answer, please confirm with your compliance counsel.
Thank You
The way for this is to have a consent checkbox when they are trying to book a meeting, make sure the consent is for the call and sms.
So as long as they book a meeting it meant they already consented to be call and sms by your AI Agent
I was thinking about adding the consent checkbox too.
What do you mean by “import” the phone number for the international? Did you mean through a Twilio SIP trunk?
I am in the US and the prospects from the US/UK/EU/CA.
If I understand, the AI can call the prospect even though I didn’t check the consent checkbox, right? What about the international call?
I am in the US and the prospects are from the US/UK/EU/CA.
I will add the consent checkbox.
Yes, but you will have risk with TCPA and GDPR, it’s better to be compliant then have law problem
Hello @krittiya.clark On consent: Retell doesn’t enforce or check a consent checkbox — the platform will place whatever outbound call you configure. TCPA / prior-express-written-consent, DNC scrubbing, calling-hour limits, and AI-disclosure are on you as the caller under our ToS. A booking that collected the phone number for the meeting is often treated as consent for a transactional confirmation call about that same meeting, but whether that clears the “written” bar under US TCPA depends on your booking-flow disclosures — that’s a legal-counsel call, not ours. Keep the call scoped to confirming the meeting; adding upsell/promotional content changes the analysis.
On international: from a Retell-managed number, we currently support outbound to the countries listed here: International Calling and Fees - Retell AI . US, UK, and Canada are all supported. For the EU, only Germany, Spain, France, and Italy are on the list — other EU countries (NL, IE, SE, etc.) aren’t supported from a Retell number, and you’d need to bring your own carrier (BYOC / SIP trunk) to reach them: Connect Retell voice agents to custom telephony - Retell AI .
Regulatory layer is per-country and remains your responsibility — GDPR/ePrivacy in the EU, UK GDPR + PECR/TPS in the UK, CRTC + National DNCL in Canada. A transactional booking-confirmation call is typically lower-risk than marketing, but you’ll want your counsel to confirm for each destination and to make sure the agent’s opening line identifies you, states it’s an AI, and gives the reason for the call.
Thank You