Voice AI RFP Template: 40 Questions for UAE Financial Institutions

A voice AI RFP template gives UAE banks a structured way to compare conversational-AI vendors on the criteria that matter locally: CBUAE compliance, Arabic and English fluency, data residency, and integration with core systems. Use the 40 questions below to score outbound collections, inbound service and verification vendors on an equal footing.

Buying a voice AI platform in the UAE is not the same as buying one anywhere else. Your callers are a majority-expat customer base who switch between Arabic and English mid-sentence; your collections scripts must respect the CBUAE Consumer Protection Regulation's ban on coercive pressure; and any autonomous decisioning has to sit inside the governance expectations the Central Bank of the UAE set out in its February 2026 guidance on AI and machine learning. A generic vendor questionnaire misses all of this. The template below front-loads the questions that separate a platform built for a UAE financial institution from one that merely demos well.

How should a UAE bank structure a voice AI RFP?

Group your questions by risk area, not by feature list. A vendor can wax lyrical about "natural conversations" while quietly hosting data outside the UAE or lacking a Gulf-Arabic model. Structuring the RFP around compliance, language, security, integration, capability, and commercials forces every bidder to answer the same hard questions in the same place, which makes scoring far easier. The six categories below map to the 40 questions.

Regulatory and compliance questions (1–8)

These decide whether the platform can even go live inside a licensed FI.

1. How does your platform support the governance, explainability and human-oversight expectations in the CBUAE February 2026 guidance on the use of AI and ML by licensed financial institutions?
2. Can outbound collections scripts be configured to comply with the CBUAE Consumer Protection Regulation — no coercive pressure, clear disclosure, defined contact windows?
3. How do you evidence that a human remains accountable for any automated decision or action the voice agent takes?
4. What controls prevent the agent from making commitments (settlements, waivers) it is not authorised to make?
5. How are call recordings, consent and opt-outs captured for regulatory audit?
6. Does the platform align with the UAE PDPL (Federal Decree-Law 45/2021) for processing personal data, including lawful basis and data-subject rights?
7. For entities in the DIFC or ADGM, how do you support the additional data-protection obligations, including DIFC autonomous-decision rules?
8. Can you produce a model-risk and third-party-AI-risk pack for our internal compliance and CBUAE examiners?

Language and localisation questions (9–15)

The UAE's bilingual, code-switching caller base is where most global vendors fall down.

1. Does the platform understand and speak Gulf/Emirati-accented Arabic, not only Modern Standard Arabic?
2. Can the agent handle mid-conversation code-switching between Arabic and English without dropping context?
3. How does it cope with the range of English accents across the UAE's expat population?
4. Are agent voices available in both male and female Arabic and English options?
5. Is the customer-facing interface, including any fallback SMS or WhatsApp handoff, right-to-left aware for Arabic?
6. How are UAE-specific terms — Emirates ID, salary transfer letter, WPS, AECB — recognised and pronounced correctly?
7. Can scripts be authored and version-controlled bilingually so compliance can review both languages?

Data residency and security questions (16–22)

1. Can customer data and call recordings be hosted within the UAE?
2. What is your sub-processor list, and where is each sub-processor located?
3. How is data encrypted in transit and at rest, and who holds the keys?
4. What certifications do you hold (for example ISO/IEC 27001, SOC 2, ISO/IEC 42001 for AI management)?
5. How do you segregate our data from other tenants?
6. What is your data-retention and secure-deletion policy, and can we configure it?
7. How quickly can you produce a full audit trail for a single customer interaction?

Integration questions (23–28)

1. What pre-built connectors exist for our core banking and collections systems?
2. Can the agent read and write to case-management and CRM records in real time?
3. How do you integrate telephony — SIP trunks, local numbering, call masking?
4. Can outcomes and consent flow back into our AECB reporting and reconciliation processes?
5. How do you consume salary-transfer and WPS-linked data where a customer has authorised it?
6. What is the typical time-to-integrate for a UAE bank of our size?

Conversational capability questions (29–34)

1. How does the agent handle interruptions and barge-in mid-sentence?
2. What happens when the caller is upset or the conversation goes off-script?
3. How and when does the agent escalate to a human, and how is context passed across?
4. Can the agent complete verification and simple self-service tasks end to end?
5. How do you measure and improve containment without degrading customer experience?
6. Can we A/B test scripts and voices safely in production?

Reporting, SLA and commercial questions (35–40)

1. What real-time dashboards and post-call analytics are included?
2. What uptime SLA do you commit to, and what are the service credits?
3. Is pricing per minute, per conversation, per seat or per outcome — and what is included?
4. Are professional-services and change-request costs fixed or time-and-materials?
5. What are the data-portability and exit terms if we leave?
6. Can you provide UAE banking references we may contact?

How AI helps

Once the vendor is chosen, this is where a purpose-built platform earns its keep. YuVoice runs outbound and inbound voice agents that speak Arabic and English natively, code-switch the way UAE callers actually do, and keep collections conversations inside the conduct boundaries the CBUAE expects. The practical outcome for a UAE bank is broader early-stage collections and verification coverage — reaching a materially larger share of accounts each cycle — without adding coercive pressure or headcount, while every interaction is logged for audit. Score your shortlist against the 40 questions above, then run a live pilot before you sign.

Building your UAE voice AI shortlist? Start at the YuVerse UAE hub.

Frequently asked questions

What should be in a voice AI RFP for a UAE bank? Cover six areas: CBUAE and PDPL compliance, Arabic/English localisation, in-country data residency, integration with core and collections systems, conversational capability, and commercial terms. The 40 questions above give you a scorable structure across all six.

Does a voice AI vendor need to comply with CBUAE rules? If you are a licensed financial institution, yes. The platform must fit the governance and human-oversight expectations in the CBUAE February 2026 AI guidance, and any collections use must respect the Consumer Protection Regulation. Ask vendors to evidence both.

Why is Arabic and English code-switching a specific RFP question? Because the UAE's majority-expat caller base routinely switches languages mid-call. A vendor that only offers Modern Standard Arabic, or that loses context when a caller switches, will underperform on real UAE conversations. Test it in the pilot.

Can call recordings and customer data stay inside the UAE? Many buyers require it. Ask directly about in-country hosting, the full sub-processor list and their locations, encryption and retention — and confirm alignment with the UAE PDPL (Federal Decree-Law 45/2021).

How many vendors should we shortlist? Three to five is typical. Send all of them the same 40-question RFP, score the written answers, then run a live pilot with the top two on your own Arabic and English scripts before deciding.

References

• Central Bank of the UAE — CBUAE Rulebook (Consumer Protection Regulation; guidance on the use of AI and ML by licensed financial institutions): https://rulebook.centralbank.ae/
• Central Bank of the UAE — Regulations Regarding Bank Loans, Article (3) Important Ratios (DBR): https://rulebook.centralbank.ae/en/rulebook/article-3-important-ratios
• UAE Government — UAE Personal Data Protection Law (Federal Decree-Law 45/2021): https://u.ae/