ChatGPT
Claude
Google AI
Copilot
Platform & ArchitectureThe room usually agrees that a steering slide needs something you can buy. A contact-centre lead is building that slide and needs a product name to put under Tenyx. The announcement did not hand over a generally available name. It said Tenyx built voice agents for service, and that the capability would extend Agentforce Service Agent. A capability and a product title you can point at in a current org are different sentences. If a later Salesforce page names a voice product and shows it, that page can carry the name. A proposal should not invent it in the meantime.
That agreement is the problem. The caller cannot scroll. They cannot paste a screenshot. They have a few seconds, and a silence that feels longer than it is. A chat topic copied onto a phone line is the wrong souvenir of this acquisition. The close answers who owns the work, when it happened, and what it did not publish. The call path is a different decision.
The completion line is the sentence worth keeping in the brief, unchanged.
"Salesforce completed its acquisition of Tenyx on September 13, 2024."
What follows stops the slide inventing a title. A good answer names a person, a document, a product, or a year. A DVD, a Reddit thread, a YouTube video, a TikTok, a course, a book, or a certification is not a source for the date, the price, or a shutdown.
| Question | Who has to answer it | What a bad answer usually means |
|---|---|---|
| What is the slide allowed to name | The contact-centre lead writing the title | A capability is sold as a product title nobody can open |
| Who owns Tenyx, and who owns a call | Salesforce for the company; a named person for spoken policy and the queue | The voice is expected to arrive already configured |
| What does 13 September 2024 decide | Whoever is writing the timeline, from the announcement | The close is reused as the morning the dialler changed |
| What may be written about price | Finance, with the announcement and the order form | A containment rate is typed in to fill the blank |
| Is there a shutdown to schedule | The owner of any voice menu that still runs | A title that was never established is switched off or put on a price list |
| What would you build | The person who can listen to one path | A chat tree is renamed and called a phone design |
What is the slide allowed to name?
The question is not what to type in the title box. It is which sentence the announcement will support when someone in the room reads it back.
Salesforce bought Tenyx. Tenyx built voice agents for service. The announcement said the capability would extend Agentforce Service Agent. That is the placement. It is not a SKU. It is not a screen. It is not a containment rate. Customers were not, on the cited announcement, given a new brand to type into a contract.
What you run today is local. Some centres already have a voice menu. Some have people on a phone queue and a separate chat. Some have never turned a voice agent on. The announcement cannot hear your calls. It will not choose which of those you are. A slide that wants a title and a purchase price from the same URL is how the invented name appears.
A good answer sounds like the contact-centre lead reading the title as voice for service, extending Agentforce Service Agent, and stating that 13 September 2024 did not establish a generally available product name.
A bad answer sounds like we will call it Tenyx Voice and put it on the price list so the slide looks purchasable. The label was chosen in the room. The announcement did not choose it.
Who owns Tenyx, and who owns a call?
Salesforce owns Tenyx. Salesforce completed the Tenyx acquisition on 13 September 2024. That is not a trial, a partnership, or a rumour. Did Salesforce buy Tenyx? Yes. The announcement says the acquisition completed.
Who owns a call path is still your operation. Salesforce owning the company does not own the words callers are allowed to hear, the check you use to know who is calling, or the roster on the transfer queue. A sentence that says the voice agent will arrive configured has skipped them.
Who may change a spoken policy should be the same person who may change the article, or you have two policies. Shipping windows are the usual split. The phone says one date. The article says another. Name one owner. The brand owner is Salesforce. The policy owner is the person you can call when the window changes.
The cited announcement does not publish a headcount, a founder statement, or a jobs list. Working at Tenyx after the acquisition is not answered there. A profile is not the close. A hiring post is not a generally available product. Why Salesforce acquired Tenyx, beyond service voice on Agentforce Service Agent, is not a motive you can recover from the completion line, and why Tenyx sold is not stated there.
A good answer sounds like one named owner for the shipping window, responsible for both the article and the words the phone may say, plus a named roster on the transfer queue.
A bad answer sounds like Salesforce owns the voice, so the spoken policy will match the article on its own. The company owner changed in 2024. The policy owner did not, unless you have named them.
What does 13 September 2024 decide?
The date is 13 September 2024. Write it that way. The quoted sentence uses the month-first form from the published page. Same day. Do not add a second date called voice launch unless a release note says so, and then cite that note.
The date is the close. It is not the morning your dialler changed. It is not the day a caller first heard a new voice. It is not a contract anniversary unless your order form uses it. Open the order form for commercial dates. The announcement has the close only.
Before that day, Tenyx was a separate company building voice agents for service. On it, Salesforce completed the purchase, and the announcement placed the capability with Agentforce Service Agent. After it, there is no product rename, no price, and no end date on the announcement. A timeline that fills those gaps has become a story.
A good answer sounds like the programme lead reading 13 September 2024 from the announcement, and reading any dialler change from the contact-centre plan, labelled as a different document.
A bad answer sounds like the phones changed on 13 September 2024 because that is when voice was bought. The date is the close. It is not a launch morning.
What may be written in the price cell?
The cited announcement does not publish a price, a purchase price, or a licence fee. How much Salesforce paid, and how much Tenyx was sold for, are unanswered. Completion is not a consideration figure. If another document states a number, it is not the announcement cited here.
Your voice or service licences are a different number, on your agreement. Name the products you already pay for when the conversation becomes a call path. Leave the amounts where the agreement left them. There is no free trial on the cited announcement. Do not type zero. Zero would mean you know the deal was nothing. Do not type a containment saving either. A call that stays with a voice and leaves the caller uninformed is not a saving the announcement will support.
A good answer sounds like the finance partner leaving the acquisition cell blank, and refusing a containment percentage taken from another centre's traffic.
A bad answer sounds like we will multiply a containment rate by call volume so the slide has a return. The rate is not on the announcement, and neither is the purchase price.
Is there a shutdown to schedule?
No end date is published for the voice work. There is no sunset for the capability, and no instruction to switch a phone line off. Do not add a quarter because the template asks for an end date.
No end date does not mean a current product can be named. You cannot retire a title that was never established here, and you cannot buy a title that was never established here. Both temptations show up in the same workshop. One person wants the thing switched off. Another wants it on the price list. The announcement supports neither.
If you already run a voice menu, it keeps running until you change it. That change is an operational decision with a routing plan, not a consequence of 13 September 2024. Treat any move as a map from each menu option you keep to a path, and a sentence for each option you drop. The acquisition is not a switch-off.
On a risk register, write three lines. No end date for the voice work. No generally available product name. No published price. Then listen to a real call, or admit you have not.
A good answer sounds like the contact-centre lead stating the voice menu keeps running until the routing plan changes, and that 13 September 2024 is not that plan.
A bad answer sounds like switch the old menu off this quarter and buy the new name. Neither the name nor the quarter is on the announcement.
What would you actually build?
When the lines above are accepted, the work is one path: how you identify the caller, which fields may be spoken, when the call transfers, and which queue receives it. Identify, read, act, transfer. A partner who cannot write those four without a new brand name is not ready to price the work.
A second test is a call that touches money. The voice should transfer, with the amount and the reason in the note, unless you already have a flow that decides the money with no guess. Clarity from the caller is not authority. A pack that lets the voice refund because the caller was clear has missed the owner.
A demo, if you need one, is a call in your org or a demo Salesforce will show now. A roadmap is a Salesforce page read on the day you read it. Do not tell the chat team that their topics have become a phone tree.
A good answer sounds like one path a supervisor can listen to, with the money call set to transfer, the amount and the reason written in the note, and no new product title on the slide.
A bad answer sounds like we will point the chat topics at the phone and let the voice decide a refund when the caller is clear. That is a renamed chat tree, and it treats clarity as authority.
What to do with the answers
Read the six as a set. Specific answers mean the phone has a path and an owner. General answers mean the decision rests on a wish for a name you can purchase, which the announcement does not supply.
If the answers are specific, the next discipline is the call path, set out in Tenyx and service voice. If they are not, the useful outcome is a title line you can still delete. Keep this page for the lines a finance partner will check: owned by Salesforce, completed 13 September 2024, voice for service extending Agentforce Service Agent, price not published, no end date, no product title invented.
