@Jaroslav Záveský Totally understand your concern regarding DPAs and EU regulations—that’s a critical priority when dealing with European businesses. To clear up the confusion on both points: 1. ElevenLabs CAN run on a phone number directly: ElevenLabs Conversational AI has native telephony support. You don’t need an external platform just to get a phone number working. You can plug in an existing SIP trunk (from Telnyx or a local Czech provider) directly into the ElevenLabs dashboard without writing code. Where ElevenLabs is limited compared to dedicated telecom platforms is advanced call routing (like warm transfers to an office desk phone or complex IVR trees), but for a standard inbound receptionist that answers questions and logs bookings, ElevenLabs’ built-in telephony is more than capable. 2. What "telephony platforms" mean: They are the carriers and aggregators that connect internet AI audio to real phone lines (PSTN)—think Twilio, Telnyx, or orchestrators like Retell/Vapi. 3. The DPA / EU Compliance Reality: Platforms like Retell and Vapi actually do provide standard DPAs with EU Standard Contractual Clauses (SCCs). However, European businesses often scrutinize where the audio packets and transcripts travel. Since you don't want to manage code, your best and cleanest path is actually using ElevenLabs directly: - Build the agent inside ElevenLabs Conversational AI. - Connect it to a compliant SIP trunk provider (like Telnyx with EU data anchoring, or a registered Czech VoIP carrier). - Sign a Data Processing Agreement with ElevenLabs and your SIP carrier. That keeps your stack 100% no-code, handles the legal paperwork cleanly, and avoids building a custom server. If you run into any snags configuring the SIP trunk, prompt tuning the Czech conversational flow, or hooking up the booking calendar, give me a shout. I handle these technical voice builds regularly and can easily jump in to help set it up for your client so it runs smoothly.

hi