The Setup Costs Nobody Quotes You: Telephony, SIP and CRM Integration in the UAE

Why does the quoted per-minute price rarely match the invoice?

Voice AI platforms price the part of the stack they own, which is the orchestration layer. Vapi's published pricing lists hosting at $0.05 per minute and states explicitly that this excludes model provider costs. Retell's pricing page breaks the same idea into visible components: $0.055 per minute for voice infrastructure, text-to-speech from $0.015 per minute (ElevenLabs voices listed at $0.040), plus the LLM, plus telephony.

Neither number is misleading. Both are the platform's own slice. The confusion starts when a buyer treats that figure as the all-in rate, because the remaining components are billed by different vendors on different meters, and one of them is far larger than the platform fee in this region.

What does telephony actually cost on a UAE number?

This is the line item that surprises people, and the gap is not marginal. Twilio's published UAE voice rates show what it costs to move audio in and out of the country. The figures below are taken from Twilio's own pricing pages at the time of writing.

Read the first two rows against the platform fee. A minute of outbound calling to a UAE mobile is listed at roughly six times Vapi's $0.05 hosting charge. If a proposal quotes you a platform rate and stays quiet about the carrier route, the number you were given may describe well under a fifth of the real per-minute cost of an outbound campaign.

The SIP rows are the reason serious UAE deployments care about trunking. Terminating over a SIP interface is published at $0.0040 per minute, against $0.2995 to dial a UAE mobile over the standard route. That difference is not a discount you negotiate. It comes from architecture: connecting the agent to a carrier trunk rather than paying a global provider to originate every leg. Retell's pricing page notes no charge for SIP trunking or custom telephony on its side, which puts the carrier relationship, and its cost, squarely with the business.

What is involved in getting and keeping a UAE number?

Number rental itself is minor. Twilio lists UAE numbers starting at $1.00 per month, and Retell lists its own numbers at $2.00 per month. The cost is not the rental, it is the provisioning process. UAE number allocation involves documentation, and a business that has never done it underestimates how much elapsed time sits between signing and a working line.

There is a second decision here that quotes rarely surface. Porting your existing published number to the agent preserves everything you have already built, including the number printed on your vehicles, your listings and your Google Business Profile. Standing up a new number instead is faster but starts your call volume from zero and splits your caller history across two lines. Porting takes longer and involves the losing carrier. Whichever path you choose, it belongs in the project plan, not discovered in week three.

Why is concurrency a separate line on the bill?

Concurrency is the number of calls the agent can hold simultaneously. It is invisible in testing, when one person calls at a time, and it becomes the whole story at 9am on a Sunday when the week's calls arrive at once. Both major platforms charge for it as a distinct item. Vapi includes 10 concurrent lines and lists $10 per line per month beyond that. Retell lists the first 20 concurrent calls free, then $8 per concurrency per month.

Sizing this correctly matters more than the unit price. Under-provision and callers hear a busy signal, which is precisely the failure an AI receptionist in Dubai was bought to eliminate. Over-provision and you pay a monthly fee for capacity that never gets used. The honest answer is that you cannot size it from a spreadsheet before launch. Start from your busiest hour of actual call data, add headroom, and revisit after the first month.

What does CRM integration really involve?

This is the line item most often written as "included" and most often responsible for the delay between a working demo and a working deployment. "Connects to your CRM" describes an outcome, not a scope. The work underneath it is field mapping, and field mapping is bespoke to your CRM instance rather than to your CRM brand.

A concrete example. The agent captures a caller's name, an enquiry type, a preferred callback window and a property or service of interest. Your CRM has a required owner field, a picklist for lead source that rejects unknown values, a phone format expectation, and a duplicate rule that decides whether an existing contact gets updated or a second record appears. None of that is knowable until someone opens your instance. Two clinics on the same CRM product can need materially different integration work.

• Field mapping and validation. Every value the agent captures needs a destination that will accept it, including picklists that reject values they have not seen before.
• Duplicate handling. A repeat caller should update a record, not create a second one. This rule has to be decided by the business, not guessed by the integrator.
• Calendar and availability. Booking against real availability means live reads of a working calendar, plus a decision about what the agent does when the slot disappears mid-call. This is the core of any AI appointment booking deployment.
• Failure behaviour. When the CRM is unreachable, the call must still complete and the data must be recoverable. Silent data loss during an outage is the expensive version of this going wrong.

We handle this work directly rather than handing over a webhook and a guide, because the failure mode is not visible on day one. It appears in month two as records that quietly did not sync. Our deployment services scope integration explicitly for that reason.

Which compliance settings carry their own price?

Some obligations map to billable platform features. Call recording is a good example: Twilio lists recording at $0.0025 per minute and storage at $0.0005 per minute per month. Storage accrues indefinitely, so a retention policy is a cost decision as well as a compliance one. Data handling has explicit price tags too. Vapi lists Zero Data Retention as a $1,000 per month add-on and HIPAA at $2,000 per month, and notes 14-day call history on its Build tier, which is a constraint worth checking against whatever retention period your own policy commits to.

The UAE regulatory layer sits on top of all of this. Telemarketing activity is regulated federally and enforced by the TDRA, and personal data handling falls under the UAE's data protection framework. The configuration work these require, including recording notification, consent capture and do-not-call screening on outbound, is setup labour whether or not it appears as a line on a quote. For the full picture on where budget vendors cut here, see our breakdown of what cheap AI voice agents leave out.

How should you structure the quote request?

The fastest way to make hidden costs visible is to ask for the quote in components rather than as a single monthly figure. Six questions surface almost everything discussed above.

1. What is the all-in per-minute rate, broken into platform, model, and telephony?
2. Which carrier route do outbound calls take, and at what published rate to UAE mobiles?
3. Who owns the phone number, and what happens to it if we leave?
4. How many concurrent calls are included, and what does the next block cost?
5. What is the integration scope in hours, and what happens when the CRM is unreachable?
6. What is the call recording retention period, and what does storage cost per month?

A provider who answers all six in writing is quoting the real project. One who answers only the first is quoting the platform. Comparing platform economics in more depth is worth doing before you commit, and we have written per-platform breakdowns for Vapi pricing for UAE businesses and Retell AI pricing in the UAE.

What is the practical bottom line?

Setup is engineering time, not a subscription, and the largest recurring variable in the UAE is the carrier route rather than the platform fee. A deployment that gets telephony architecture, number ownership, concurrency sizing and CRM field mapping decided before launch runs on a predictable bill. One that defers them discovers each as an unplanned invoice, usually in the month it has already committed to the numbers.

Our own installs, including the multilingual outbound agent we built for IT World Trading LLC with on-site telephony configuration, spend more calendar time on trunk setup and integration than on prompt design. That ratio surprises people. It is also the honest shape of the work.