# Should I migrate from Tenyx

Tenyx is voice for service. Migrate one call path onto the Case and the queue. Do not invent a product name to receive the calls.

**Published:** 2026-06-10
**Canonical:** https://synconai.com/should-i-migrate-from-tenyx
**Author:** SynconAI Architecture Team

## In short

Salesforce completed the Tenyx acquisition on 13 September 2024. Tenyx is voice for service. A Case already records the issue, including a phone origin, and a queue already holds the transfer. Migrate only a call path you can write as steps. Do not place those calls on a product name this page made up. This page states no price, no screen, and no end date.

## 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.

## What to take away

- Tenyx is voice for service. The close was 13 September 2024. This page names no generally available voice product.
- A Case already records the issue and its owner. A queue already receives a transfer.
- Migrate one call path you can write. Do not move voice onto a product name you invented.
- Alternatives sit unranked. This page invents no AppExchange listing, price, or shutdown date.

## The guide

A contact-centre lead asks which product name should sit on the migration slide. The room wants a label it can buy. This page will not print one. Tenyx is voice for service. A generally available product name, shown in an org you can open, is a different sentence. If a later page from Salesforce names a voice product and shows it, that page can carry the name. A migration plan must not invent the name in the meantime, and it must not move the calls onto a name that was coined in a workshop.

The caller cannot scroll. They cannot attach the picture a chat customer pastes. A chat topic copied onto a phone line is how a voice migration misses its first week. The only sentence this page quotes from the announcement is the completion line. "Salesforce completed its acquisition of Tenyx on September 13, 2024."

## Should you migrate

Migrate when you can write one reason people phone you, as steps a supervisor can follow. Order status is the usual candidate because the rule is boring. The caller wants a date or a place. You already know which system holds that fact. The path is identify, read, say only what may be said, and transfer. A quote that cannot say those steps is not a migration. It is a channel with no work inside it.

Do not migrate because a slide says voice for service. That phrase names a channel. It does not name the path. The cited page does not publish a shutdown date. You are not late. Stay on the number and the queue you already staff until one path is written, including what happens when the queue is closed. Five more paths are five more designs. Add them after a supervisor has listened to calls, not to a demo.

## Do not migrate onto a name you made up

The failure this page refuses is a cutover onto a product name nobody can open. "Move Tenyx to the new voice SKU" is that failure when the SKU was typed to fill a box. There is no SKU on this page. The place a call's work already lives, in Salesforce, is a Case and a queue. Migrate the path onto those, or do not migrate it. Leaving the old number in place is allowed. Inventing a destination product is not.

If someone offers a walkthrough of buttons, ask which org they opened. If the answer is a diagram, the walkthrough is a story. This page has not been shown a screen, and it will not draw one so the story has pictures.

## What the software is now

Salesforce owns Tenyx. The completion date is 13 September 2024. What the software is now, on the evidence this page will use, is voice for service. It is not a renamed product this page will announce. It is not a screen. The cited page does not publish a price. Telephony you already pay for stays on your telecom contract. This page will not choose a carrier.

People ask what Tenyx software is, hoping a category will settle the move. The category is voice agents for service. The category does not choose your identity check, your recording rule, or the queue. Those are yours. Write them, or you are not migrating voice. You are renaming it.

## The three pages

This page answers whether you should migrate, what the software is now, how a call compares with the native Case and queue, and which alternatives sit unranked. It does not price a telephony platform.

The implementation page is [Tenyx and service voice](/tenyx-agentforce-voice). Use it for one call path, the identity check, and the queue a transfer reaches. The what-happened page is [What happened to Tenyx](/what-happened-to-tenyx). Use it for ownership, the date, the blank price, and the absent end date. The integration page is [Integrating Tenyx with Salesforce](/integrating-tenyx-with-salesforce). Use it when the call must read a record and hand the note to a person. Do not ask any of the three to invent a product name.

## Versus the Case and the queue you already run

A Case already records one customer issue. It stores an origin, and phone is an origin service teams already use. It stores a status and an owner. The owner is a user or a queue. A queue already holds work for a roster, during hours you set. When the hours are closed, the queue does not become a transfer. It becomes a closed queue, and you already need a path for that: a message you approve, a callback you can actually make, or a refusal to promise either. A Knowledge article already holds words a person is allowed to say, with an owner who can change them. Those are the native objects. They already answer where the issue sits and who has it.

Only after that description does a comparison count. Tenyx is a way of speaking the path on a phone. It does not replace the Case. A call that never writes a Case, or never reaches a queue when it stops, has not arrived in the system your supervisors already run. Migrating voice means writing identify, read, speak, and transfer against those objects. It does not mean placing the calls on a product name this page made up.

What may be spoken is a disclosure decision, not a feature gap. A shipping status may be sayable. A complaint note may not. Native fields will store whatever the running user can see. The migration chooses a user whose access matches the fields you decided may be said aloud. A wide user makes a fluent call and a disclosure. Write the permission set on the paper path before anyone talks about a product name.

## What you must not move

Do not migrate every chat topic onto the phone because the words look similar. The caller cannot see a form. Do not migrate payments, address changes, or refunds onto the voice path unless a tested rule already has one outcome and a person is not required. The voice may collect inputs. It may not invent the missing input so the call continues.

Do not copy a service design from another channel onto a coined voice product "so the migration has a home". The home, if you migrate, is the Case, the queue, and the words you allow. If you cannot name the path, leave the calls where they are.

Recording and retention are part of the decision, not a footnote you attach after the calls are live. Write who may listen, how long the audio lives, and whether a transcript lands on the Case or in a store your security team has already accepted. A migration that stores audio somewhere new, because the pilot needed a place, has chosen a retention policy by accident. Languages belong on the same page. A pilot in one language your callers actually use is a scope. A promise of every language you might add is a different programme. Leave it off this move.

The running user is easy to skip because a demo uses an administrator. An administrator can see accounts the queue would never open. The caller then hears facts a person would not say. Choose a user you would give a new colleague on Monday. If you would not, do not give that user to the voice path so the pilot can finish. Write the permission set on the sheet. A blank there is a reason to wait.

## Alternatives, without a rank

People search for alternatives after the acquisition, and for an alternative on AppExchange. This page has not been shown an AppExchange listing. It will not invent a listing, a rating, or a rank, and it will not invent a voice product to rank against.

One way is to keep the phone path you already staff, with people, and treat the acquired brand as history. Another way is to move one named call path onto the Case and the queue, with a rehearsed way back to the old routing. Another way is to keep a separate voice platform you still operate and integrate only the transfer note. Another way is to evaluate a different voice tool under your own security review, outside this page.

None of these is placed first. The gate is whether the path can be written as steps, and whether the destination is a real Case rather than a name coined for the slide. If the destination is a coined name, you are not migrating. You are labelling.

## A walkthrough you can finish on paper

Write the caller's sentence. Write how you identify them, using a check they can complete by voice and your privacy owner already allows. Write the fields that may be spoken and the fields that stay unsaid. Write the queue, the hours, and the note. Write the after-hours path. Write the running user. Write the recording rule you already have. Write that no product name was added. Stop on a blank.

Take the sheet to the implementation page. Leave price and shutdown blank on the what-happened page. Take the handoff note to the integration page. If a partner adds a product name you cannot open in your org, cross it out before you read the fee.

## The first week of calls

Judge the week by listening, not by a count of contained calls. A useful transfer note says what was heard, what was read, and what was refused. "Please assist" means the caller will repeat themselves. Pull that path back to a person until the note is full. Do not add a second reason for calling while the first note is empty. Do not "finish" the week by renaming the path onto a product that still does not exist on this page.

A pack goes wrong when the title is a product name, the price cell is filled from memory, and the end date is a quarter the template required. Strip it back. One path. One Case. One queue. No invented name. No price. No end date.

::: warn
Do not migrate voice onto a product name you made up. Tenyx is voice for service, completed on 13 September 2024. The call lands on a Case and a queue you can name, or it does not migrate. This page gives no screen, no price, and no end date.
:::

| Decision | You may proceed when | Stop when |
| --- | --- | --- |
| Migrate this path | Identify, speak, and transfer are written | The brief says voice for service and stops |
| Destination | The Case and the queue already exist | A product name was coined for the slide |
| Native comparison | You have said what a Case and a queue already do | The comparison is two logos |
| Alternative | The ways sit unranked | An AppExchange listing or a rank was invented |
| Price and end date | Both cells are blank | A figure or a quarter was typed to fill a template |
| Screen | The plan has no menu | A button nobody has opened is the walkthrough |

Bring the table to the meeting. If the destination row is a name you cannot open, stop. The implementation page can price a written path. It cannot price a product this page refused to invent.

## Questions

### Should I migrate from Tenyx to Salesforce?

Migrate one call path you can write: how the caller is identified, what may be said, and which queue receives the transfer. Salesforce completed the acquisition on 13 September 2024. Tenyx is voice for service. Do not move the calls onto a product name this page does not have, and do not invent a shutdown quarter.

### What is Tenyx software now?

Tenyx is voice for service. Salesforce owns it after 13 September 2024. This page does not give that work a generally available product name, a current screen, or an end date. The cited page does not publish a price. Scope the path, not a label.

### How does Tenyx compare with native Salesforce service features?

A Case already records the issue, with an origin, a status, and an owner. A queue already holds a transfer for a roster during set hours. A published article already holds words a person may say. Voice is a way of speaking a path onto those objects. It is not a second product name.

### What are the alternatives after the Tenyx acquisition?

This page does not rank alternatives and has not been shown an AppExchange listing. Ways that sit side by side include keeping the staffed phone path, moving one named path onto the Case and queue, integrating only a transfer from a platform you still run, or evaluating another voice tool yourself.

### Can we name a new voice product as the migration target?

No. This page will not invent a generally available product name, and it will not migrate voice onto a name made up in a workshop. If you cannot write the call as steps onto a Case and a queue, leave the calls where they are.

---

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).