# Who to hire for Bonobo on Salesforce

No Bonobo product sits in a Salesforce org. The conversation insight you can buy today is Einstein Conversation Insights, and the hire is built around its recording provider.

**Published:** 2026-09-17
**Canonical:** https://synconai.com/hire-bonobo-ai-salesforce-partner
**Author:** SynconAI Architecture Team

## In short

Hire for Einstein Conversation Insights, not for Bonobo. Salesforce acquired Bonobo in 2019, and no product of that name sits in a Salesforce org today. The working feature records nothing itself, needs a connected recording provider, and is available in Performance and Unlimited Editions or at extra cost in Enterprise. Look for Platform Administrator and Agentforce Sales Consultant credentials plus a reference on your provider.

## Sources

- **Salesforce acquires Tel Aviv-based conversational AI startup Bonobo** (retrieved 2019-05-06)
  https://tech.eu/2019/05/06/salesforce-acquires-tel-aviv-based-conversational-ai-startup-bonobo-for-a-reported-50-million/
  > Bonobo develops conversational AI technology designed to extract insights from online customer interactions.
- **Einstein Conversation Insights Implementation Guide, Winter '27** (retrieved 2026-10-13)
  https://resources.docs.salesforce.com/latest/latest/en-us/sfdc/pdf/eci_impl_guide.pdf
  > Conversation Insights doesn't record your calls.
- **Einstein Conversation Insights Implementation Guide, Winter '27 (consent)** (retrieved 2026-10-13)
  https://resources.docs.salesforce.com/latest/latest/en-us/sfdc/pdf/eci_impl_guide.pdf
  > It's a customer's responsibility to manage consent and comply with local privacy requirements in the way calls are recorded.
- **Einstein Conversation Insights Implementation Guide, Winter '27 (permission sets)** (retrieved 2026-10-13)
  https://resources.docs.salesforce.com/latest/latest/en-us/sfdc/pdf/eci_impl_guide.pdf
  > Calls placed before users are assigned ECI permission sets are not processed, and the recordings are not available on voice and video call records.
- **Einstein Conversation Insights Implementation Guide, Winter '27 (providers)** (retrieved 2026-10-13)
  https://resources.docs.salesforce.com/latest/latest/en-us/sfdc/pdf/eci_impl_guide.pdf
  > Integration work is required from the customer to add a new recording provider.

## What to take away

- There is no Bonobo product to implement. The 2019 deal bought a team and technology, and the live feature is Einstein Conversation Insights.
- Einstein Conversation Insights records nothing. Your recording provider does, so the first hiring question is which provider and who owns the integration.
- Rollout order matters: calls placed before a user holds the right permission set are never processed, so the partner must sequence licences and permission sets before calls.
- Treat certifications as a filter. The evidence is a reference where the same provider fed call records into Salesforce, with the consent wording to prove it.

## The guide

A procurement note arrives asking for a Bonobo partner. It is a natural instinct. Salesforce bought a conversational AI company, the business wants insight from customer calls, and so the shopping list names the company. The difficulty is that nobody can open a screen called Bonobo in a Salesforce org, which means whoever you hire has to be hired for the thing that will actually be switched on when the contract is signed. This guide is about hiring for that thing, and about how to check the person across the table without leaning on a logo slide.

## What the 2019 record gives you

The report on the deal described the company plainly: "Bonobo develops conversational AI technology designed to extract insights from online customer interactions." It added that Bonobo's small team would join the group behind [Einstein Forecasting](https://tech.eu/2019/05/06/salesforce-acquires-tel-aviv-based-conversational-ai-startup-bonobo-for-a-reported-50-million/), and it carried a purchase figure attributed to an anonymous source because the terms were not disclosed. None of that is a product definition. A team joining a forecasting group is a staffing fact, and a rumoured price says nothing about what a licence costs you.

The practical consequence is that a proposal which lists Bonobo as a deliverable is describing something it cannot install. Either the author has not looked at your org, or they are selling you a name. Ask them to replace the word with the Salesforce feature that does the job. For call and meeting analysis the feature is Einstein Conversation Insights, and the rest of this page is written against Salesforce's own Winter '27 implementation guide, last updated in July 2026. The wider history sits on [What happened to Bonobo AI](/what-happened-to-bonobo-ai), and the build-side view on [Bonobo, conversation insight, and what 2019 does not sell you](/bonobo-ai-salesforce).

## What a partner actually does on Conversation Insights

Start with the sentence that surprises most buyers. Salesforce's own guide says: "Conversation Insights doesn't record your calls." The feature does not capture audio. You connect a recording system, calls are matched to Voice Call or Video Call records, and the processed transcript and insights appear on those records. That makes the integration with your telephony or meeting tool the heart of the engagement, and it is where partners differ most.

The guide lists what is supported out of the box. Anything outside that list becomes custom work, and the guide says so in terms: "Integration work is required from the customer to add a new recording provider."

| Recording source | Position in the Winter '27 guide | What the partner must do |
|---|---|---|
| Sales Dialer | Compatible voice provider | Switch on Dialer permission sets, confirm minutes are available |
| Amazon Connect with Service Cloud Voice | Compatible voice provider | Align the contact centre build with the Conversation Insights setup |
| Redbox, Tenfold, Fastcall | Listed as supported partners | Contact the telephony vendor about their side of the connection |
| Other telephony | Supported via API | Scope and build the integration, then test with real calls |
| Zoom Meetings, Google Meet, Microsoft Teams | Video providers | Connect at org level and again at user level for each rep |

Two thresholds are worth knowing before anyone quotes. Recorded calls are processed automatically if they run longer than ten seconds for voice and longer than one minute for video. A one-minute check-in call will therefore simply not appear, and a partner should say that out loud when you describe your call mix.

Around the connection sits a short list of configuration jobs that a good partner treats as a checklist rather than a project. Turn the feature on in Setup. Assign the right permission set to each user: Conversation Insights for Sales, Sales Engagement Conversation Insights, Einstein Conversation Insights Included, or Einstein Conversation Insights Standard, depending on what you own. Make sure the org has at least two levels of role hierarchy, because the dashboards need them. Decide whether to use Einstein Activity Capture calendar matching so call participants resolve to contacts. Define call insights, the keywords and phrases such as competitor names and product mentions that matter to your teams. Then look at the dashboards, whose dataflow runs every eight hours by default in Analytics Studio, so a rep who finished a call at lunchtime will not see it in a dashboard until later.

## The skills and credentials that matter here

Certification names change, so check them on Trailhead rather than taking them from a CV. These are the ones that map to the work above.

| Skill | Why it matters on this project | Credential or evidence to ask for |
|---|---|---|
| Permission sets, role hierarchy, Setup | Calls go unprocessed if the wrong permission set is held | Salesforce Certified Platform Administrator |
| Sales process and call-to-opportunity design | Insights only help if calls land on the right records | Salesforce Certified Agentforce Sales Consultant |
| Governing AI features | Transcripts and insights are personal data processed by AI | Salesforce Certified Agentforce Specialist |
| Non-standard recording sources | Custom providers need an API build and error handling | Salesforce Certified Platform Integration Architect, or a named integration reference |
| Who may open a call record | Calls can contain pricing and personal details | Salesforce Certified Platform Sharing and Visibility Architect, or a design walk-through |
| Analytics Studio dataflows | Dashboard refresh and field access depend on them | No certification, so ask for a live demonstration |

A credential is a filter, not proof. Plenty of certified people have never connected a recording provider, and some excellent practitioners lapsed a renewal. Use the table to decide who you interview, then use the questions below to decide who you hire.

## A realistic first engagement

For a team of a few dozen reps on one supported provider, a sensible first engagement is a pilot with a defined group and a defined end. Pick one recording provider and one team. Confirm the edition position first, because the guide describes the feature as available in Performance and Unlimited Editions and for an additional cost in Enterprise Edition, so a quote that ignores your edition is a quote that will change. Assign permission sets to the pilot users before the first recorded call, and say so in the plan, because "Calls placed before users are assigned ECI permission sets are not processed, and the recordings are not available on voice and video call records."

That one sentence should shape the schedule. A partner who switches the feature on org-wide on a Friday and asks reps to start recording on Monday has lost every call made in between. The safer pattern is permission sets first, a test call from each pilot user second, and a check that a transcript appears on the Voice Call or Video Call record third. Only then do the call insights and dashboards get built. Define success as something a manager can see: a named set of calls processed, with the competitor and product mentions you chose, on the opportunity records they belong to.

Keep the pilot honest by agreeing in advance what you will compare. A useful pilot answers three plain questions: did the calls that should have been processed actually arrive, did the matching land them on the right opportunity or contact, and did a manager find the insight worth opening. If the answer to the first is no, the fault is almost always in the provider connection or the permission sets, not in the insight definitions, and a good partner will say so rather than tuning keywords to hide it. Resist the temptation to widen the pilot until those three answers are settled.

Consent belongs in week one rather than at the end. The guide is blunt about where responsibility sits: "It's a customer's responsibility to manage consent and comply with local privacy requirements in the way calls are recorded." Someone in your organisation, usually legal or compliance, needs to approve the recording notice and the retention approach before the first call is recorded. A partner can draft the questions for that conversation. They should not answer them for you.

## Red flags specific to this work

The first is the obvious one: a statement of work that names Bonobo as a product or promises Bonobo-style insight as though it were a feature in a catalogue. The second is a partner who believes Conversation Insights records calls and who therefore has no plan for the provider. The third is a fixed price offered before anyone has asked which provider you use, because the provider decides whether the work is a checklist or an integration build.

Watch for forecast promises too. The 2019 report connected Bonobo's team to forecasting, and some partners will therefore imply that call insight lifts forecast accuracy. No source for that claim exists, so ask them to show where it is written. Be wary of a partner who has never heard of the processing thresholds, who plans a flat role hierarchy, or who has not asked who owns the recording consent. And be wary of an estimate that ignores the Enterprise Edition cost position, since the licence is part of the budget even though this page is about services.

## Ten questions to ask

1. Which recording provider do you expect us to use, and have you connected that exact one to Conversation Insights before?
2. What happens to calls made before a user holds the permission set, and how will your rollout plan avoid losing them?
3. Which of our calls will never be processed, given the duration thresholds, and how will we explain that to managers?
4. How many levels of role hierarchy does our org have, and what would you change if it is flat?
5. Who writes the recording notice, who approves it, and where is consent stored?
6. How will you decide which competitor and product phrases become call insights, and who owns the list afterwards?
7. If we need a provider outside the supported list, what does your API build involve, and how is it tested?
8. Who can open a call record once a transcript is attached, and have you checked that against our sharing model?
9. How soon after a call will a rep see the insight, given the default dashboard refresh, and what would you change?
10. What do you refuse to promise about forecast accuracy or win rates?

## Checking references without relying on logos

Ask for a reference from a customer who used the same provider, and ask that customer three things: how many calls were processed in the first week, what was lost because of rollout order, and who owns the insight definitions now. A partner who can only offer a logo or a general testimonial has not done this work enough to remember the answers. Ask for a screen share of an anonymised Voice Call record with the transcript and insights visible, which takes five minutes and cannot be faked by a slide.

Look at their own Trailhead credentials and, if they are claiming a specialist, ask which consultants will be in the room rather than which consultants the firm employs. Ask what they did when a call failed to process, because every real deployment has a story about a recording that never arrived.

## Commercial models and what to write into the statement of work

A short fixed-price discovery that ends with a named provider, a named pilot group and a written consent decision works well, followed by a build priced either as fixed scope or on a capped time-and-materials basis. For a pilot on a supported provider, fixed scope is reasonable. For a custom provider, insist on a capped estimate with a defined point at which you can stop.

Write these items into the statement of work: the recording provider and who owns its contract; the user group and the order of permission set assignment; any role hierarchy change; the call insights to be defined, as a count; the dashboards to be delivered and their refresh schedule; the consent and retention decisions and who made them; an acceptance test in which a test call from each pilot user appears with a transcript on the correct record; and a handover session for the admin who will maintain the list. Leave out forecast uplift, win-rate targets and any success fee tied to them. The licence is a separate conversation, covered on [Bonobo AI Salesforce licence cost](/bonobo-ai-salesforce-licence-cost), and the project scope sits on [Bonobo AI Salesforce implementation cost](/bonobo-ai-salesforce-implementation-cost).

## When a project is small enough to skip a partner

If you have one supported provider, an Enterprise or higher licence already in hand, a role hierarchy with at least two levels, and an admin holding the Platform Administrator credential, you can probably do this yourself. Salesforce publishes a [Trailhead module on setting up Einstein Conversation Insights for Sales](https://trailhead.salesforce.com/content/learn/modules/set-up-einstein-conversation-insights/set-up-einstein-conversation-insights-for-sales) that walks through the setup. The cases where a partner earns their fee are a provider outside the supported list, a sharing model that makes call visibility hard, a multi-region consent question, or a contact centre where Service Cloud Voice and Sales calls both need to flow into one reporting view.

Before moving to a hire, read [Should I migrate from Bonobo AI](/should-i-migrate-from-bonobo-ai) to confirm that you are not mislabelling a recording project as a migration, and [Integrating Bonobo AI with Salesforce](/integrating-bonobo-ai-with-salesforce) for the data flow in one picture.


## Questions

### Is there a Bonobo product I can hire someone to implement on Salesforce?

No. Salesforce acquired Bonobo in 2019, and the 2019 report describes conversational AI technology and a team joining Einstein Forecasting. Nothing named Bonobo is documented in Salesforce today. The feature you can implement for call insight is Einstein Conversation Insights.

### What Salesforce certifications should a Conversation Insights partner hold?

A useful starting set is Salesforce Certified Platform Administrator, Salesforce Certified Agentforce Sales Consultant and Salesforce Certified Agentforce Specialist. For custom recording sources, add Salesforce Certified Platform Integration Architect or a named integration reference. Check each credential on Trailhead before relying on it.

### Does Einstein Conversation Insights record our calls?

No. Salesforce says it does not record calls. You connect a recording provider such as Sales Dialer, Amazon Connect with Service Cloud Voice, Zoom Meetings, Google Meet or Microsoft Teams, and calls are processed from there. Consent and local privacy compliance remain your responsibility.

### Why do some calls never show insights?

Calls placed before a user was assigned the right permission set are not processed. Voice calls shorter than ten seconds and video calls shorter than one minute are also skipped. Plan permission set assignment before the first recorded call and tell managers which short calls will not appear.

### When can we skip a partner for call insight?

You can usually skip one when you have a single supported provider, a licence for the feature, at least two role hierarchy levels and an admin with Platform Administrator skills. Hire help for custom providers, tricky sharing models, multi-region consent or combined sales and service calls.

---

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