An AI phone agent connected to your Salesforce org

What the agent can do in Salesforce during a call

Salesforce's hosted MCP servers are managed endpoints that expose your org's data and automation to an AI client. Daber AI connects to one, so the agent can work with your records mid-conversation. Salesforce enforces field-level security and sharing rules for the user who signed in, so the agent sees what that user sees.

• Query records: find the caller's Contact or Account and read the Case they're calling about.
• Update records: change a phone number, add a detail to a Case, or move a field your process allows.
• Run Flows: trigger automation your admin built and exposed, such as opening a callback request or routing a Case.

What happens after the call

When the call ends, Daber AI writes a completed Task in Salesforce, linked to the lead or contact, carrying the summary, sentiment and outcome. The Task can be assigned to an owner by email address, so the right rep is notified. This runs on inbound, outbound and campaign calls. A failed write never fails the call: it is recorded so it can be fixed, and the recording, transcript and summary stay in Daber AI.

What the agent can and can't do in Salesforce

What you need to connect Salesforce

Salesforce lists hosted MCP servers for Developer, Enterprise, Performance and Unlimited editions. A Salesforce admin does the setup on the Salesforce side: it needs an External Client App for OAuth, and Salesforce says Connected Apps can't be used for MCP authentication.

1. 1Ask your Salesforce admin to enable a hosted MCP server for your org and register an External Client App for it.
2. 2Decide which Salesforce user the agent works as, and give that user access only to the objects and fields it should touch.
3. 3In Daber AI, add Salesforce from the tools you can connect and sign in with that user to approve access.
4. 4Test the connection, turn Salesforce on for the agent, and choose which actions it may use.
5. 5Write in the agent's instructions when to use them, then run a test call in your browser and check the Task in Salesforce.

An example call

A policyholder calls an insurance agency to ask where their claim stands. The agent asks for their name and policy details, queries Salesforce, finds the open Case and reads the status: the adjuster's report is in and a decision is expected this week. The caller mentions a new mobile number, so the agent updates the Contact. Before hanging up, the agent runs the callback Flow the admin exposed, so the adjuster gets a request to call. A completed Task with the summary lands on the contact, assigned to the account owner.

Where it stops

These limits are worth knowing before you plan around the integration:

• Salesforce doesn't list hosted MCP servers for other editions, such as Professional. On those, the post-call webhook can still carry each call's data to your own integration.
• The agent can't see past the signed-in user's field-level security and sharing rules.
• It runs only the Flows your admin exposes, and only when its instructions say to.
• It doesn't replace your Salesforce admin: Flows, validation rules and page layouts stay theirs to build.