Get started

Salesforce

The Salesforce integration connects a ThunderPhone agent to approved CRM actions during a phone conversation. An agent can search and read leads, contacts, and opportunities, then use separately enabled write operations to create or update records and log activity.

That scope is intentionally specific. Connecting Salesforce does not give an agent unrestricted access to the account or make every CRM process automatic. The useful unit is a defined operation attached to a particular agent, with prompt instructions that say when to use it and what to do when a lookup is incomplete or ambiguous.

What Salesforce does on ThunderPhone

Salesforce is a direct app connection in ThunderPhone. Its documented operations fall into two groups:

  • View: search and read CRM records, including leads, contacts, and opportunities.
  • Write: create or update records and log activity.

These actions can keep the conversation and the customer record aligned. A caller does not need to repeat every detail if the agent can find an authorized record, and the sales team can receive a structured outcome instead of relying on someone to reconstruct the call later.

The agent still needs a clear verification rule. A name or phone number may match more than one record. The prompt should tell the agent which details to confirm before reading account-specific information or writing a change, and it should direct uncertain cases to a human rather than choosing a record by guesswork.

Typical call flows

Qualify a new or existing lead

An inbound caller asks about a service. The agent collects the agreed qualification fields, searches Salesforce for an existing lead, and confirms the right record when a match is available. It can then create or update the record and log the call outcome. If the caller is ready for the next step, the agent can record that status for the sales team to handle.

Follow up on an opportunity

For an outbound follow-up, the agent can read the relevant opportunity context before asking the approved questions. It records the caller's response and logs the activity. The prompt should limit the agent to confirmed facts and avoid changing an opportunity stage unless that exact action is part of the approved workflow.

Capture a callback request

When a caller needs a specialist, the agent can identify the contact, collect the reason and preferred follow-up details, and write the result to the CRM. A human receives a usable record even when the call itself should not be resolved automatically.

Setup outline

  1. Create a Salesforce app connection in ThunderPhone and complete the account authorization flow.
  2. Attach that connection to the agent that needs it.
  3. Enable only the view and write operations required for that call flow.
  4. Add prompt instructions for record matching, identity confirmation, required fields, allowed updates, and failure handling.
  5. Test lookups and write-backs against controlled records. Confirm that a failed or ambiguous search produces a safe response.
  6. Deploy the agent change after the draft behaves as expected.

Start with one bounded workflow, such as lead qualification or callback capture. Review both the call result and the Salesforce record during testing. That makes field-mapping mistakes and duplicate-record behavior visible before the integration handles production calls.

Related workflows and terms