Voice AI16 min read

Agentforce Voice Alternative UK: The Org Readiness Test

Dilr Voice is an enterprise voice AI platform from DILR.AI that answers and makes business phone calls beside Salesforce rather than inside it. This guide tests Agentforce Voice for UK teams: the editions, add-ons and telephony it needs first, its documented limits, and when staying on Salesforce is the better choice.

On this page 11 sections
Agentforce Voice Alternative UK: The Org Readiness Test DILR VOICE Agentforce Voice Alternative UK: The Org Readiness Test 01 Count the prerequisites 02 Choose the telephony 03 Test the limits 04 Map the processors dilr.ai/blog

Salesforce now sells a voice agent that lives inside the CRM. Its UK page for Agentforce Voice says it brings natural, context-aware conversations to every phone call, app and chat window, built on the CRM data that powers the business. For a UK service or sales operations lead whose customer records already sit in Salesforce, that is a serious proposition, and it deserves a serious test rather than a feature grid.

This guide runs one test: what Agentforce Voice assumes your Salesforce org already has, and what it constrains once it is switched on. Every requirement and limit below is read from Salesforce's own help pages and product pages on 21 November 2026, so you can check each one against your own org. The guide deliberately cedes three neighbouring questions to posts that already answer them. The general case for a native contact-centre agent against a separate platform belongs to our Five9 alternative guide. How call data gets written back into a CRM during lead qualification belongs to the Aircall comparison. What a team assembles to run AI agents on Amazon's contact centre belongs to the Amazon Connect build guide.

This guide is shipped by the team behind Dilr Voice, a multi-agent voice AI platform that names Salesforce among its live integrations. Or see DATS, our five-stage AI consulting system, for teams that want the placement decision made before any build starts.

What is Agentforce Voice, and what does it inherit from your Salesforce org?

Agentforce Voice is Salesforce's voice layer for its Agentforce AI agents. Salesforce describes it as native to the Salesforce platform: a voice-enabled agent uses the same subagents, actions and data that already power an organisation's text agents, so it can read customer history and update records in real time. Its value therefore depends on how much useful work your Salesforce org already does, because the voice agent inherits that work rather than replacing it.

That inheritance is the whole proposition. Salesforce's product page lists phone calls, click-to-talk on a website and voice inside a mobile app as channels, plus voice messages inside WhatsApp. The same page says the agent can update records, create cases, trigger workflows and call APIs during the conversation. Salesforce's own Agentforce Voice guide makes the argument directly: many enterprises approach voice AI as a separate procurement, with a new vendor, a second AI stack, two sets of guardrails and a seam that customers feel when they switch channels.

The argument is strongest for a team that has already built text agents in Agentforce and grounded them in Salesforce Knowledge. It is weakest for a team whose Salesforce org is a sales pipeline and little else, because there is little for the voice agent to inherit. Read the rest of this guide with one question in mind: is the work your callers need done already inside Salesforce, or does it live somewhere else? Our enterprise voice AI agents guide sets out the wider buying decision if you are earlier than that.

What must already be in place before Agentforce Voice answers a UK call?

Agentforce Voice has a set of prerequisites that Salesforce lists in its help documentation. The org needs Enterprise, Unlimited or Developer Edition with Foundations or Agentforce 1 Editions, plus Salesforce Voice add-ons. The agent is built from the Agentforce Service agent template, Voice with Telephony Providers must be turned on, Enhanced Omni-Channel must be enabled, and a partner telephony provider must be confirmed as supported.

Salesforce's Complete the Prerequisites page is short, and every line on it is a dependency you can check this week. Two lines matter more than they look. First, Salesforce tells customers to ask their Salesforce account executive to verify that Agentforce Voice supports their partner telephony or contact-centre provider, and to ask an unsupported provider to work with Salesforce to become a supported partner. If your UK numbers sit with a carrier that is not on that list, the project has a dependency outside your control before it has a design. Second, a team that is not already a Voice with Telephony Providers customer has to turn that on and create a fallback queue for the Omni-Channel flow that transfers inbound calls to a person.

What Agentforce Voice needs before the first call
01Edition and add-onsEnterprise, Unlimited or Developer, with Foundations or Agen…02Service agentBuilt from the Agentforce Service agent template03Voice with Telephony ProvidersTurned on, with a fallback queue for transfers to people04Enhanced Omni-ChannelEnabled, with permission to update call records05Telephony partner confirmedVerified as supported by your Salesforce account executive
Read from Salesforce Help, Complete the Prerequisites and Agentforce Voice Considerations, November 2026.

None of this is unusual for a platform product, and a mature Service Cloud estate may already tick most of the boxes. The point is to count them before you count benefits. A team that would need a new edition, a new add-on and a new telephony arrangement is not extending an existing investment; it is starting a new one, and should compare it with other new options on equal terms. A placement diagnostic is one way to make that count independently of either vendor.

Which telephony route suits a UK contact centre already on Salesforce?

Agentforce Voice connects to calls in one of two ways, according to Salesforce's telephony help page. Salesforce Voice is the native option, where Salesforce manages the call from procurement to post-call analysis. The alternative integrates an existing third-party telephony provider over PSTN or SIP. Salesforce's own comparison favours the native route for setup, data continuity and single-vendor support, and the choice shapes how much of your current UK telephony survives.

Salesforce's telephony comparison is unusually candid about the third-party route. The table below summarises it in our words.

ConsiderationSalesforce Voice (native)Third-party telephony provider
DeploymentEnd-to-end setup with voice agents built inConfiguration in two platforms, with PSTN or SIP coordinated between them
Data flowOne record, full transcript from start to endData can fragment, or context can be lost, at a handover
AnalyticsCall metrics, recordings and insights in one systemCall data split across systems
SupportSalesforce supports the whole solutionTelephony support comes from a separate vendor
Usage trackingTracked inside SalesforceTracked separately on each system

Read that table from a UK operations seat. If your numbers, call recording and routing already run on a contact-centre platform you are happy with, the native route means moving them; the third-party route keeps them but accepts the seams Salesforce itself lists. Neither is wrong. The question is which seam you would rather own. Our telephony provider selection guide covers the carrier side of that decision. The same help page describes two integration patterns: an AI-first frontline where the agent answers first, and an IVR transition where voice agents appear only at specific menu branches.

What operating limits should shape a UK Agentforce Voice design?

Agentforce Voice has documented limits that belong in a UK design from the first workshop. Salesforce states that each voice agent is monolingual, listening and responding only in its default language. It sets a default of 500 concurrent calls per org, warns that spelled codes can transcribe the letter O as a zero, caps sandbox storage that call recordings fill quickly, and needs the caller's number preserved to link transferred calls.

Each limit comes from Salesforce's Agentforce Voice Considerations page, and each has a practical consequence.

One language per voice agent. Salesforce says the Allowed Languages setting applies to text-based agents only, so a voice agent operates in its default language even if more are added. British English (en_GB) is listed as supporting all available voice settings, and many other languages are listed as Beta with a warning to test carefully. A UK service line that takes calls in Welsh, Polish or Punjabi needs a routing decision before the call reaches an agent, not during it.

Spelled references. Salesforce warns that when callers spell out IDs or codes, transcription may turn the letter O into the digit 0, and it publishes sample instructions to handle this. UK policy numbers, postcodes and booking references mix letters and digits constantly, so this belongs in your test script on day one.

Capacity. The default limit is 500 concurrent calls per org, raised by contacting Salesforce Customer Support. A national retailer or utility at peak can approach that; our capacity planning guide explains how to size the peak before you ask.

Testing. Sandbox environments carry a 200-MB storage limit that call recordings can reach quickly, and Salesforce says Omni-Channel stops working when it does, blocking further voice testing. It recommends turning recording off in sandboxes or testing in a full or Partial Copy sandbox. Our go-live checklist covers the rest of pre-launch testing.

Call records. Without Salesforce Voice with Telephony Providers, Salesforce creates a voice call record for the customer-agent conversation but not for the customer-rep conversation. Linking a transferred call also relies on the original caller's number being preserved as the caller ID; Salesforce gives an Amazon Connect example where a different caller ID breaks the link.

Billing shape. Salesforce bills voice use in flex credits, either per voice action or per Agentforce Voice Minute, and minutes are rounded up, so a call of 61 seconds counts as 2 minutes. When both are enabled, minutes take precedence. Some standard actions also require a per-user add-on subscription, which Salesforce says is not technically enforced yet. Model short calls with that rounding in mind, and ask your account team which add-ons your planned actions need.

The same discipline sits behind our AI operating model consulting, which decides who owns limits like these once a voice agent is live.

What should a UK buyer confirm about speech processing and sub-processors?

Agentforce Voice uses third-party speech models, and Salesforce documents how. Its considerations page says the service typically processes data within the Salesforce trust boundary by deploying Deepgram speech-to-text and ElevenLabs and Kotoba text-to-speech models locally. If regional or availability rate limits are reached, it fails over to the provider's external infrastructure under a zero-data-retention policy. A UK controller should map both paths before go-live.

That disclosure is more specific than many vendors give, and it is the right starting point for a data protection review rather than the end of one. Under the UK GDPR, Article 28(2) says the processor shall not engage another processor without prior specific or general written authorisation of the controller, and under general authorisation the processor must tell the controller about intended changes so the controller can object. That duty binds Salesforce as your processor; your job as controller is to know what you have authorised.

Three questions follow for a UK team. Which region does the failover path use, and is a call that fails over still covered by your transfer assessment? Does the zero-data-retention policy cover audio, transcripts or both? And where do call recordings and transcripts land inside your org, given the recording settings described above? Our UK and EU voice AI compliance guide sets out the wider set of questions a controller should be able to answer. The same questions apply to any separate voice platform you compare, including ours, so put them in one procurement checklist and ask every vendor.

What does the Florida Prepaid story show, and what does it not?

Florida Prepaid is one of two customer stories on Salesforce's UK Agentforce Voice page. The story, written by staff at the Salesforce partner NeuraFlash and published on Salesforce's blog in May 2026, says Agentforce Voice is now the first point of contact for 75% of business-hours calls. It also says the agent answers only from public knowledge, with no account balances, no case history and no personal data.

The rollout itself is the most useful part for a UK planner. The Florida Prepaid story describes a deliberately narrow start and a staged increase in the share of calls the agent handled.

Florida Prepaid: Agentforce Voice rollout stages
10%Launch30%Weeks later50%After tuning75%Current
Stages as described in a vendor-published customer story, which states each on a slightly different base: share of calls, then of incoming calls, then first point of contact for business-hours calls. None is a resolution rate. Source: Salesforce blog, Florida Prepaid customer story (May 2026)

Three things limit how far it travels. Florida Prepaid serves families in Florida in the US, not UK callers, so none of the UK rules above were tested. It is vendor-published, so it is a case study rather than an independent measurement. And the starting point matters: the story says Florida Prepaid already ran Agentforce in chat, Salesforce Voice, Amazon Connect, Service Cloud and Salesforce Knowledge before it moved to voice. That is the inheritance argument from the first section at its narrowest: even a knowledge-only first phase, with no customer records in play, reused Knowledge articles the organisation already kept in Salesforce. The organisation's own chief information technology officer framed the goal this way:

"We did not approach Agentforce Voice as a call-deflection tool. We approached it as a way to redesign the service model responsibly, using AI for routine questions, preserving human capacity for higher-value conversations and building the guardrails needed to scale with trust," said Ashley Falls, chief information technology officer for Florida Prepaid.

That framing is worth borrowing whichever platform you choose. A narrow, knowledge-only first phase with a clear transfer to a person is the safest way to put any voice agent on a UK line, and if you want help running that kind of staged rollout, our AI execution office is the place to start.

When is Agentforce Voice the right choice?

Agentforce Voice is the right choice when the work callers need is already modelled inside Salesforce. A team that runs Agentforce text agents, keeps its answers in Salesforce Knowledge, holds a qualifying edition with Salesforce Voice add-ons and is willing to move telephony onto Salesforce Voice gains one record per call, one support relationship and one set of guardrails. For that team, a separate platform adds a seam it does not need.

Be honest about the strength of that case. Salesforce's own telephony comparison shows what a separate stack costs in coordination: two platforms to configure, data that can fragment at a handover, and support split between vendors. If your team has already paid to build those subagents, actions and Knowledge articles, Agentforce Voice reuses them rather than rebuilding them. A second voice AI stack would need its own prompts, its own knowledge base and its own testing, and the Genesys comparison reaches the same conclusion for teams deep inside a single contact-centre platform.

There are also cases where Salesforce is simply the safer organisational choice: a procurement team that will only add capacity to an existing enterprise agreement, or a governance board that wants one vendor accountable for the whole call. Those are legitimate reasons, and no comparison page should pretend otherwise.

How does Dilr Voice differ from Agentforce Voice for UK phone work?

Dilr Voice is a phone-first platform that sits beside a CRM rather than inside one. It chains specialised agents, such as a greeter, a qualifier and a customer care agent, into a single call, with each agent carrying its own prompt, model and tools. Telephony runs on Twilio or Vobiz, Salesforce is named as a live integration for CRM sync, and post-call automation writes CRM records and sends notifications without code.

The practical difference is where the starting line sits. Dilr Voice does not require a Salesforce edition, an add-on or a telephony partner approval to start; a team signs up at app.dilr.ai on a free trial with no credit card required. In exchange, it does not inherit your Agentforce subagents or Knowledge articles, so the agents and their knowledge base are configured in Dilr Voice itself, using uploaded documents that the agents search during live calls. Outbound campaigns also need the customer's own Twilio or Vobiz account, which matters if your telephony sits elsewhere.

Some other differences worth testing on your own calls rather than taking from either vendor's page:

  • Languages. Dilr Voice supports 30+ languages. Salesforce's voice agents are each configured for one default language. If language matters to your UK callers, run the same multilingual test call on both and compare what happens.
  • Compliance defaults. Dilr Voice ships per-country rules by default: recording consent, DNC registry checks, opt-out recognition, permitted calling hours, and an audit trail on every call. UK duties under PECR and the TPS register still rest with the calling organisation, so check how each default maps to them. Read the best AI voice agent 2026 guide for a wider view of the market.
  • Response time. Dilr Voice responds in under 500 milliseconds on DILR's own on-platform measurement. That is a vendor measurement, not a like-for-like benchmark, so time both platforms on your own calls.
  • Hosting. Dilr Voice runs on Google Cloud Platform, encrypted at rest and in transit, with dedicated tenancy and regional data residency options for enterprise.

Our CRM and telephony integration architecture guide explains how a phone-first platform and a CRM divide the work, and how DILR approaches placement explains why we start from the call, not the tool.

What is the best Agentforce Voice alternative for UK teams in 2026?

The best Agentforce Voice alternative for a UK team depends on where the call's work lives. Judge any option on four criteria: what it needs before the first call, which telephony it keeps, how many languages one call can handle, and how it treats UK consent and calling rules. Dilr Voice fits teams who want phone-first agents that write to Salesforce. Agentforce Voice wins where Salesforce already holds the work.

Applied honestly, the criteria split buyers into three groups. Teams with Agentforce text agents, Salesforce Knowledge and a willingness to adopt Salesforce Voice should start with Agentforce Voice, because the reuse is real and the Vonage AI Studio guide shows how much build ownership costs when you lack it. Teams whose contact centre runs on Genesys or Five9 should compare those platforms' native agents first, using the guides linked above. Teams whose Salesforce org is a record of customers rather than a home for service logic, or whose calls need several languages, UK outbound rules or a trial before any licence change, are the group a separate platform such as Dilr Voice suits.

Other voice AI vendors a UK team may compare include PolyAI, Cognigy, Parloa, Vapi and Retell AI. Whichever you shortlist, apply the same four criteria and the same sub-processor questions, and keep the Salesforce integration test identical across vendors.

Does Dilr Voice work with Salesforce?

Dilr Voice names Salesforce as a live CRM integration alongside HubSpot and Google Calendar. Its no-code post-call automation can write CRM records, update lead status and score, and send email, SMS and Slack notifications after each call. It runs beside Salesforce rather than inside it, so it does not reuse Agentforce subagents or actions; its agents and knowledge base are configured in Dilr Voice.

Is Agentforce Voice available in the UK?

Salesforce's UK Agentforce Voice page states that Agentforce Voice is generally available in all regions, and its help documentation lists British English among the languages that support all available voice settings. Availability is not the same as fit: a UK buyer still needs a qualifying Salesforce edition, Salesforce Voice add-ons and a supported telephony route before the first call is answered.

Want to see this in production? Try Dilr Voice live, compare the market in our best AI voice agent guide, see our DATS methodology, or browse more voice AI buyer guides for UK teams.

Talk to the operators

Decide where the voice agent should live.

30-min scoping call · No deck · Confidential. We will tell you whether your calls belong inside Salesforce or beside it, and what each route needs first.

Written by the Dilr.ai engineering team, practitioners who ship enterprise AI in production. Read more about Dilr.ai. Follow us on LinkedIn for shipping notes, or subscribe via the RSS feed.

  • agentforce voice alternative uk
  • salesforce agentforce voice alternative
  • agentforce voice vs dilr voice
  • agentforce voice agent uk
  • salesforce voice ai uk
  • voice ai reddit
  • best ai voice agent 2026
  • dilr voice

What does this article answer?

The questions this article answers, in short

  • Agentforce Voice is Salesforce's voice layer for its Agentforce AI agents. Salesforce describes it as native to the Salesforce platform: a voice-enabled agent uses the same subagents, actions and data that already power an organisation's text agents, so it can read customer history and update records in real time. Its value therefore depends on how much useful work your Salesforce org already does, because the voice agent inherits that work rather than replacing it.
  • Agentforce Voice has a set of prerequisites that Salesforce lists in its help documentation. The org needs Enterprise, Unlimited or Developer Edition with Foundations or Agentforce 1 Editions, plus Salesforce Voice add-ons. The agent is built from the Agentforce Service agent template, Voice with Telephony Providers must be turned on, Enhanced Omni-Channel must be enabled, and a partner telephony provider must be confirmed as supported.
  • Agentforce Voice connects to calls in one of two ways, according to Salesforce's telephony help page. Salesforce Voice is the native option, where Salesforce manages the call from procurement to post-call analysis. The alternative integrates an existing third-party telephony provider over PSTN or SIP. Salesforce's own comparison favours the native route for setup, data continuity and single-vendor support, and the choice shapes how much of your current UK telephony survives.
  • Agentforce Voice has documented limits that belong in a UK design from the first workshop. Salesforce states that each voice agent is monolingual, listening and responding only in its default language. It sets a default of 500 concurrent calls per org, warns that spelled codes can transcribe the letter O as a zero, caps sandbox storage that call recordings fill quickly, and needs the caller's number preserved to link transferred calls.
  • Agentforce Voice uses third-party speech models, and Salesforce documents how. Its considerations page says the service typically processes data within the Salesforce trust boundary by deploying Deepgram speech-to-text and ElevenLabs and Kotoba text-to-speech models locally. If regional or availability rate limits are reached, it fails over to the provider's external infrastructure under a zero-data-retention policy. A UK controller should map both paths before go-live.
  • Florida Prepaid is one of two customer stories on Salesforce's UK Agentforce Voice page. The story, written by staff at the Salesforce partner NeuraFlash and published on Salesforce's blog in May 2026, says Agentforce Voice is now the first point of contact for 75% of business-hours calls. It also says the agent answers only from public knowledge, with no account balances, no case history and no personal data.
  • Agentforce Voice is the right choice when the work callers need is already modelled inside Salesforce. A team that runs Agentforce text agents, keeps its answers in Salesforce Knowledge, holds a qualifying edition with Salesforce Voice add-ons and is willing to move telephony onto Salesforce Voice gains one record per call, one support relationship and one set of guardrails. For that team, a separate platform adds a seam it does not need.
  • Dilr Voice is a phone-first platform that sits beside a CRM rather than inside one. It chains specialised agents, such as a greeter, a qualifier and a customer care agent, into a single call, with each agent carrying its own prompt, model and tools. Telephony runs on Twilio or Vobiz, Salesforce is named as a live integration for CRM sync, and post-call automation writes CRM records and sends notifications without code.
Written by Dilr.ai EngineeringEngineering team

Who can run AI voice agents like these for me?

Dilr Voice runs AI voice agents for inbound and outbound calls

Multi-agent handoff, RAG knowledge bases and per-country call compliance in one platform, priced per minute.