Integrating Bonobo AI with Salesforce

An architect finds Bonobo on a list of old acquisitions and asks for an integration. The sketch arrives the next day. A box labelled Bonobo sits between the channels where customers write and a Salesforce object where an insight is supposed to land. The box has no fields. The partner says the fields will come out in discovery. Discovery cannot name a screen this page does not have. The sketch is a connector to a product the page cannot name, which is the thing this integration must not become.

Start from the sentence you can quote, and from the refusal that follows it. Then decide whether you have a current product, on a current contract, that you are willing to name. If you do, that product gets its own design. It does not inherit the Bonobo box. If you do not, the diagram stays empty and the connector does not get built.

The bounds of what you can say about conversation insight, without inventing a screen, are on Bonobo, conversation insight, and what 2019 does not sell you. The acquisition story, without a price, is on What happened to Bonobo AI. This page is the diagram that stops the connector.

#What the cited page says

The sentence this page quotes is the report's description: "Bonobo develops conversational AI technology designed to extract insights from online customer interactions." Salesforce acquired Bonobo in 2019. The sentence is about technology and a purpose. It is not a product brochure for a screen you can open now. It does not name a Salesforce object. It does not name a field. It does not name a menu.

This page does not repeat a reported dollar figure. A figure in a headline, a recollection, or a URL is not a citation this guide will carry. Price is not a design. If a business case needs what was paid, it needs a source that states it, and then it still does not need a connector. You can know a price, or refuse to repeat one, and still have no screen. Those are separate facts. This page keeps the second fact and leaves the first alone.

"Develops" is the tense of the sentence as published in that report. It describes what the technology was for. It does not establish that a Bonobo product is on sale, in your org, or on a release you can enable. No current Bonobo screen is established. Write that in the margin of any diagram that says otherwise. If a colleague says they logged in last month, ask them to show the screen, the contract, and the admin. A memory of a logo is not a tenant. This source will not confirm the memory, and this page will not design around it.

There is no API name here, no daily cap, no connector name, and no price for a call. Do not add them so the integration guide looks like other integration guides. Looking complete is how the unnamed product gets a pipe.

#The system

The system cell cannot be filled with "Bonobo" as if that were a place. A system you integrate has an owner, a login, and a boundary. This page cannot give you those. Putting the name on the left of the picture does not create them.

Online customer interactions are not, by themselves, the system either. They happen in whatever channels you run now, on contracts you hold now. Email, a chat window, a case, a community: each of those might exist in your estate, and each has its own name. Use that name. Do not file them under Bonobo because a 2019 sentence mentioned interactions. The sentence did not hand you those channels, and it did not join them to Salesforce.

Salesforce is a system you may already operate. It does not contain a Bonobo area merely because the company was acquired. If you cannot find a screen, that absence is the finding. It is not a provisioning delay. Do not raise a ticket to "enable Bonobo" against an org that has no such switch in any document you can cite. The ticket will bounce, or worse, someone will build a placeholder so the ticket can close.

A connector needs two ends that exist. One end, Salesforce, may exist. The other end, a current Bonobo product, is not established. A connector with one end is a drawing. Do not fund the drawing as if the second end were in another team's backlog. Ask that team to produce the screen. When they cannot, stop.

#The object

The object the sentence allows you to talk about is an insight from an online customer interaction. That is a description of a purpose. It is not a Salesforce object, and it is not a payload you can map.

An insight needs a home if you intend to store it. This page will not name the home. Naming one would be designing the connector. A note, a field, a custom object, a score: each of those is a choice your org can make for a product you can open. They are not choices this page can hang on the Bonobo name. If you need a place for an insight, start from the product on your current contract and from the field that already exists. Leave Bonobo out of that sentence.

There is no object called "the Bonobo record". A mapping workshop that creates one is inventing the product in spreadsheet form. Source column, target column, sample value. The sample value is where fiction becomes test data. Do not load it. A sandbox row with no real screen behind it will be treated as a specification by the next person who sees it.

If your company kept exports from a tool you used in 2019, those files are your records, in your custody. This page does not establish that such files exist, and it does not tell you they are a Bonobo product you should reconnect. If you have them, the question is retention and access, on the implementation page's terms. Reconnecting them through a new connector, to a product you still cannot name, repeats the failure with old files as the excuse.

#The failure

The failure is a connector designed to a product this page cannot name. The diagram looks like progress. The statement of work looks like delivery. The first workshop discovers that nobody can log in. By then you have a credential, a queue, and a field list for an insight nobody can trace to a screen.

The failure has a few common costumes. A "thin" connector that only writes a summary. A "placeholder" connector until the product team confirms the screen. A connector named for Bonobo that actually moves data between two systems you do run, with the old name kept so the architecture stays continuous. The third costume is the most misleading. If you are integrating two systems you can name, name them. Do not borrow Bonobo as a label. A label from 2019 is not an integration pattern.

Refuse the build in writing. No screen, no connector. A partner who says discovery will produce the screen is asking you to pay for a search this source has already failed. You may still hire people for a conversation-insight problem on a product you can open. That hire should not have Bonobo in the title of the work.

Do not test the connector in a sandbox "just to see". A test that needs you to invent the payload is not a test of Bonobo. It is a test of your willingness to draw. The pass condition for this page is that the connector line is gone, not that a sample message moved.

#The diagram

A diagram that does not name the system, the object, and the failure is a poster. The usual poster is a 2019 logo, an arrow, and Salesforce. It names none of the three in a way you can build. Use this instead.

If someone fills the system cell with a login URL, ask them which contract that URL belongs to, and whether the screen is Bonobo or a different product that kept a nickname. A nickname is not a source. If they cannot show the screen, wipe the URL off. URLs are easy to remember and hard to unbuild once a credential exists.

Leave any dollar figure off the picture. This page does not repeat one. A price in the corner does not create a screen, and it makes the poster look sourced when it is not.

#What you write before anyone draws an arrow

The refusal. No current Bonobo screen is established. This programme will not design a connector to a product it cannot name. The 2019 description stays in the footnote, quoted, not expanded into a platform.

The search. Who looked for a tenant, a contract, and a screen. What they opened. A negative result is the result you record.

The current products. If you want insight from customer conversations, name the product on a contract you hold now. Name the channel. Name the field that already exists, if a person may accept a write. If you cannot name the product, you are not ready, and Bonobo is not the shortcut.

The boundary. What you will not build. A Bonobo object. A Bonobo credential. A sample payload. A guide for an admin of a screen you have not seen.

The price discipline. No reported figure copied into the business case from this episode. If finance asks what was paid, say this page does not carry that number. Do not let the question bounce into engineering as a reason to prototype.

A partner passes this page by deleting the box. A partner fails it by offering a connector with the fields "to be confirmed". Confirmed by whom, on which screen, is the only confirmation that counts. This source cannot give it.

#How the other two pages fit

This page stops the connector. It does not try to be a history, and it does not try to be a build of a product you cannot open.

What happened to Bonobo AI is the 2019 acquisition as a record. Who bought the company, and what you should not invent around that, including a figure this family of pages will not repeat. Send the corporate questions there. Do not let them return as a requirement to integrate.

Bonobo, conversation insight, and what 2019 does not sell you is the page for the limit of the report and for what to do if you still have old files. Use it when someone wants a pilot. The pilot has to name a current product. If the only name they have is Bonobo, they are still on this page, and the answer is still no connector.

#A week that deletes a box

Ask three people: the architect who drew the box, the admin who would have to log in, and the contract owner. Give them a week to produce a screen and a contract that uses the name. If they produce a different product, rename the work to that product and start a different design, with that product's own objects. If they produce nothing, delete the box, the credential request, and the mapping sheet.

Write the deletion in the decision log. System, not established. Object, not named. Failure, the connector you refused. That log is the integration deliverable. There is no feed to reconcile, because you did not build one. The absence is the result you wanted.

Anyone who returns next quarter with the same box should be shown the log, not given a new workshop. The report from 2019 will not have grown a screen in the meantime. Neither should the diagram.