# Who to hire for Tenyx and Salesforce voice agents

Tenyx brought voice AI to Salesforce's service agents. A voice project has three contracts and one unforgiving user, the caller, so hire for telephony and conversation design as well as Salesforce.

**Published:** 2026-06-11
**Canonical:** https://synconai.com/hire-tenyx-salesforce-partner
**Author:** SynconAI Architecture Team

## In short

Salesforce completed the Tenyx acquisition on 13 September 2024 to add voice AI to Agentforce Service Agent. Hire a partner who has taken a voice agent live on real phone lines, who understands your telephony vendor as well as Service Cloud, and who can show recordings of calls the agent handled badly and what changed afterwards.

## Sources

- **Salesforce Signs Definitive Agreement to Acquire Tenyx** (retrieved 2024-09-13)
  https://www.salesforce.com/news/stories/salesforce-signs-definitive-agreement-to-acquire-tenyx/
  > Salesforce completed its acquisition of Tenyx on September 13, 2024.
- **Salesforce Signs Definitive Agreement to Acquire Tenyx** (retrieved 2026-10-13)
  https://www.salesforce.com/news/stories/salesforce-signs-definitive-agreement-to-acquire-tenyx/
  > Upon close of the acquisition, Tenyx will extend Salesforce’s existing autonomous agent capabilities for Agentforce Service Agent by integrating Tenyx’s innovative voice AI solutions, specifically tailored for service use cases.

## What to take away

- Tenyx completed on 13 September 2024 and was announced as voice AI for Agentforce Service Agent, so the product to scope today is Agentforce Voice.
- A voice project involves three parties: Salesforce, your telephony provider and the partner, so ask who is accountable for the whole call path.
- Credentials to check are Agentforce Specialist, Agentforce Service Consultant and Platform Integration Architect, plus your telephony vendor's own certification for the people who touch it.
- Judge a candidate on recordings of real calls, including failures, not on transcripts or a scripted demo number.

## The guide

A chat agent that misreads a question can be forgiven, because the customer reads the answer, shrugs and rephrases. A voice agent that talks over a caller, or pauses for three seconds before replying, loses the call. That asymmetry shapes the whole hiring decision. You are not looking for the firm that is best at Salesforce in general. You are looking for the one that has dealt with the physics of a phone call and the politics of the contact centre.

## What the acquisition did and did not say

Salesforce announced that it would buy Tenyx, which it described as a developer of AI-powered voice agents, and completed the deal on 13 September 2024. The key sentence for buyers reads: "Upon close of the acquisition, Tenyx will extend Salesforce’s existing autonomous agent capabilities for Agentforce Service Agent by integrating Tenyx’s innovative voice AI solutions, specifically tailored for service use cases." The announcement also said Tenyx's co-founders would join Salesforce and that the voice work would sit alongside Service Cloud. You can read the full text on the [Salesforce newsroom](https://www.salesforce.com/news/stories/salesforce-signs-definitive-agreement-to-acquire-tenyx/).

What you can buy today is described on Salesforce's [Agentforce Voice help page](https://help.salesforce.com/s/articleView?id=005226934&language=en_US&type=1). It says the product lets you build voice-enabled agents that handle conversations in real time, that it is available as an add-on to Service Cloud and may need specific licensing, and that it connects to telephony through the Salesforce Voice Partner Ecosystem, naming Amazon Connect and Genesys among the options. The page we read does not mention Tenyx, so the link between the two is a reasonable inference from the announcement, not a documented fact. This guide therefore covers hiring for Agentforce Voice, which is the product a partner would configure. If anyone tells you precisely which Tenyx components run inside it, ask for a Salesforce document that says so.

## Three contracts, one call path

A voice agent is rarely a single purchase. You will normally have a Salesforce arrangement for the agent and its voice capability, a telephony or contact-centre platform that carries the call, and a services contract with the partner. Each can be reasonable on its own and still leave a gap in the middle, such as a transfer that drops context, a recording that nobody owns, or a latency problem each vendor blames on another.

When you compare proposals, ask each firm to draw the call path from the dial tone to the human agent's screen, naming every system the audio and the data pass through. Then ask who is accountable if a caller hears silence. The right answer is a named person at the partner who coordinates with your telephony vendor, not a statement that the telephony vendor is out of scope. The [integration guide](/integrating-tenyx-with-salesforce) explains the Salesforce side of that path in more detail.

## Skills and credentials that matter

On the Salesforce side, the Salesforce Certified Agentforce Specialist and the Salesforce Certified Agentforce Service Consultant are the relevant names on Trailhead, and the Salesforce Certified Platform Integration Architect matters because voice agents call back into your systems. All three appear on Trailhead's [consultant](https://trailhead.salesforce.com/en/credentials/consultantoverview), [developer](https://trailhead.salesforce.com/en/credentials/developeroverview) and [architect](https://trailhead.salesforce.com/en/credentials/architectoverview) pages, which you can use to check any claim.

Those exams do not cover the phone network. For that half, ask which telephony platform the partner has deployed against, and whether the people on your project hold that vendor's own credential. Beyond paper, the scarce skills are conversation design for speech, which is quite different from writing chat copy, and the ability to read an audio failure. Ask whether the team includes someone who has tuned prompts for spoken delivery, handled interruptions, and set sensible rules for when an agent should stop trying and transfer.

## A first call flow worth scoping

Pick one inbound reason, not the whole line. Good candidates are order status, appointment confirmation, opening hours with a callback request, or a simple balance enquiry, because each has a clear end state. A sound first engagement includes:

- A single phone number, or a single queue, routed to the agent during agreed hours, with the rest of the time unchanged.
- Caller identification you already trust, defined step by step, and a statement of what the agent may and may not do before identification is complete.
- Two or three actions into Service Cloud or another system, each with its permissions.
- A transfer rule: after how many misunderstandings, or on which phrases, the call goes to a person, and what the person's screen shows when it arrives.
- A review process for recordings and transcripts, with a named reviewer and a weekly cadence for the first month.
- A way back: one switch that returns the number to the human queue.

The [implementation guide](/tenyx-agentforce-voice) walks through a pilot of this shape.

## Conversation design is the craft

On a chat channel, a customer can scroll back, copy a reference number and read a list of options at their own pace. On a phone they cannot. That changes how every answer is written. A confirmation number has to be read in short groups and offered again. A list of three options is about the limit before people forget the first. A question that works in text, such as "Which of the following describes your issue?", sounds like a recorded menu from 1998 when spoken aloud.

Ask the candidate who writes the spoken responses and what their background is. The strongest voice teams include someone from a contact-centre or broadcast background who has listened to hundreds of real calls, and who can tell you why an apology that reads well on screen sounds insincere in the ear. Ask how the partner handles numbers, dates, names and addresses, which are the places where speech recognition most often fails, and how the agent confirms what it heard before it acts on it. A good design repeats back a postcode or order number before it changes anything, and gives the caller a simple way to correct it.

Then ask about silence. A real agent needs to know whether the caller has stopped speaking, is thinking, or has put the phone down. Partners with experience will describe how they tuned the thresholds on a live line and what they changed after listening to the first fifty calls.

## What the first month looks like

Be sceptical of a plan that ends at launch. In a typical pilot the first week is spent listening to every call, because small faults that no test caught appear quickly: a greeting that is too long, an agent that answers a question the caller did not ask, a transfer that arrives with an empty screen. The second and third weeks are a cycle of changing instructions, retesting and releasing, ideally with a short written note of each change. By the fourth week the team should be reviewing a sample rather than every call and reporting movement in the measures you agreed.

Ask the candidate who does that listening. If the answer is "your supervisors", price their time into your own plan, because it is substantial. If the answer is the partner, check that the statement of work covers it, with a named reviewer and a stated number of review hours. Pilots that skip this step tend to look fine on a dashboard for a fortnight and then collect complaints that nobody can trace to a cause.

## Red flags specific to voice

A demo number that only works on the partner's own line. Ask to call a live system on a mobile phone from a noisy room. Real callers use cars, speakerphones and regional accents, and a demo recorded in a quiet office tells you nothing about them.

No view on delay. Ask what response time the partner considers acceptable, how they measure it, and what they do when it drifts. People tolerate a short pause with a person and almost none with a machine.

Nobody has thought about interruption. Callers talk over agents. Ask how the design copes when a customer corrects the agent mid-sentence.

A single measure of success. Containment alone rewards an agent that frustrates callers into hanging up. Ask which other measures the partner tracks, such as repeat calls within a day and transfers where the customer had already given their details.

Recording and consent treated as an afterthought. Rules on recording calls and storing voice data differ between jurisdictions. A good partner raises the issue before you do and asks who in your organisation approves the wording of the opening announcement.

Language assumptions. Check, in writing, which languages and accents the partner has actually tested, and which the Salesforce documentation lists as supported at the time you buy.

## Ten questions to ask every candidate

1. How many voice agents have you taken live on real phone lines, and on which telephony platforms?
2. Can I phone one now, from my mobile, and hear it handle an interruption?
3. Show me recordings, with the customer's details removed, of calls the agent got wrong and what you changed.
4. What response delay do you aim for, and how do you measure it in production?
5. How does the call transfer to a human, and what context arrives with it?
6. Who is accountable when the fault might be in the telephony platform, and how have you handled that before?
7. How do you verify a caller's identity by voice, and what is the agent forbidden to do before that step?
8. Which languages and accents have you tested with real callers?
9. What measures besides containment do you report, and how do you stop them being gamed?
10. When would you advise me to take the number back to human staff?

## Evidence, references and what to put in the contract

A reference from the contact-centre manager, not the sponsor, will tell you about the first month, when supervisors listened to every call and the exceptions piled up. Ask the partner to share a sample weekly review pack. It should show call volumes, transfers, failure reasons and the changes made in response.

On commercial structure, a fixed fee for the pilot is workable if the scope fixes the number, the hours, the call reason, the actions and the success measures. Time and materials suits tuning, where each week's recordings decide the next week's work. Keep telephony usage and the Salesforce add-on out of the services quote, because both are billed elsewhere and priced differently; the [licence guide](/tenyx-salesforce-licence-cost) and the [cost guide](/tenyx-salesforce-implementation-cost) separate the lines.

| Topic | Put in the statement of work | Watch for |
| --- | --- | --- |
| Call path | A diagram naming every system and owner | "Telephony is out of scope" |
| Identity | Written steps before any account action | Voice recognition promised with no detail |
| Quality | Weekly recording review with a named reviewer | Only dashboards, no listening |
| Handoff | Context shown to the human on transfer | Cold transfers |
| Exit | One switch back to the human queue | No rollback plan |

## When a small project can skip a partner

If you already run a contact-centre platform on Salesforce, have one clear call reason and a capable admin who has completed the Agentforce Specialist path, you can reasonably trial a single line internally with your telephony vendor's support. The moment the project involves several lines, identity checks, payments or regulated advice, or when you have no one who has tuned speech, the cost of a failed launch outweighs the cost of help. Callers rarely give a second chance. For the history, the [what happened guide](/what-happened-to-tenyx) records the dates, and the [migration guide](/should-i-migrate-from-tenyx) helps if you are weighing a move from another voice platform.

## Questions

### Does Salesforce sell a product called Tenyx?

Not that we could find. Salesforce completed the acquisition on 13 September 2024 and said Tenyx would extend Agentforce Service Agent with voice AI. The product page we read, Agentforce Voice, does not mention Tenyx. Scope your project against Agentforce Voice, and ask Salesforce for a document if you need to know what came from Tenyx.

### What do I need besides a partner to run a Salesforce voice agent?

A telephony or contact-centre platform that connects through the Salesforce Voice Partner Ecosystem, with Amazon Connect and Genesys named on Salesforce's help page, and the Agentforce Voice add-on to Service Cloud, which may need specific licensing. Confirm both with your Salesforce account team before you scope services.

### Which certifications should a Tenyx-era voice partner hold?

Agentforce Specialist, Agentforce Service Consultant and Platform Integration Architect on the Salesforce side, plus the telephony vendor's own credential for the people who configure the call path. Verify each Salesforce name on Trailhead, and ask which named people on your project hold them.

### How do I test a voice partner before signing?

Call a live system they built, from your mobile in a noisy place, and interrupt it. Ask for recordings of failed calls with the changes that followed, and for a sample weekly review pack. A partner who can only offer a scripted demo has probably not run a voice agent in production.

### Should I pay a voice partner for a containment target?

Treat it cautiously. Containment can be raised by making it hard to reach a person, which damages satisfaction. If you link fees to a target, also include repeat calls, transfer quality and a customer measure, agree how each is counted, and keep the build on a fixed fee so quality is not traded away.

---

SynconAI is a Salesforce Select Partner and an OpenAI Select Partner, delivering architect-led Salesforce and AI programmes across the United States and Australia. Related service: Agentforce consulting (https://synconai.com/salesforce-agentforce-consulting).