Caller lookup before hello
Match the incoming number to a lead or contact and greet returning callers by name, with their status in context.
Botphonic + Salesforce
Botphonic looks up the caller in Salesforce before the agent answers, updates the record during the call and logs the outcome as a task your reps can see.
Start your 14-day free trial
20 free minutes · $1 card check, refunded within 48 hours · Cancel anytime
Book a 20-minute demo How custom actions work
Illustrative example. You choose which objects and fields Botphonic reads and writes.
How it works
You decide which objects and fields the agent can touch. Each step is a Botphonic action or workflow step pointed at your Salesforce org.
Create a Salesforce integration user limited to the objects you map, plus OAuth credentials for Botphonic’s requests, sent directly or through your own API layer.
A before-the-call custom action finds the caller in Salesforce by phone. Fields such as name, status and owner become variables the agent can use.
During-the-call custom actions create a lead, update a field or check an open case while the caller waits. Keep each response under two to three seconds.
Information Extractor turns the caller’s answers into clean values. A workflow API step, or a webhook to your API layer, then logs a completed call task and updates the record.
What you can automate
Everything runs through standard Salesforce objects and the REST API, so your custom fields work too.
Match the incoming number to a lead or contact and greet returning callers by name, with their status in context.
Create leads, update fields or open a case while the caller is still talking, using during-the-call custom actions.
Yes/no, single-choice and open-question extractors map straight to checkboxes, picklists and text fields, instead of leaving facts buried in a transcript.
A record-triggered Flow can add a new lead to a Botphonic segment with an HTTP callout. A workflow campaign set to auto-enroll that segment then calls them.
With Cal.com or Calendly connected, the agent offers open times and books the meeting before the call ends.
When a caller asks for a person, the agent briefs your rep before handing over, so nobody has to repeat themselves.
Use cases
Start with one flow, check the results in your Salesforce reports, then add the next.
Speed to lead
A record-triggered Flow sends each new lead to Botphonic. The agent calls, asks your qualifying questions, books a meeting if there’s interest and logs the result on the lead.
See the AI sales assistantInbound sales and support
The agent recognizes existing contacts before it speaks, answers common questions from your knowledge base, and creates a lead or a case when the caller needs follow-up.
Explore AI customer serviceRenewals and reminders
Send the contacts due for a renewal, payment or appointment reminder to a Botphonic segment through the Public API. A workflow campaign calls each one and logs the outcome back to Salesforce.
See insurance use casesField mapping
Standard objects and fields are shown. Swap in your custom fields, the ones ending in __c, wherever your org uses them.
| Botphonic data | Salesforce object | Typical fields |
|---|---|---|
| Caller’s phone number | Lead or Contact (lookup) | Phone, MobilePhone |
| Qualification answers | Lead | Status, Rating, your custom fields |
| The call itself | Task with the Call subtype | Subject, CallType, CallDurationInSeconds, CallDisposition, Description, WhoId |
| A booked meeting | Event | StartDateTime, EndDateTime, WhoId |
| A support request | Case | Subject, Description, ContactId |
CallDisposition appears as Call Result in Salesforce. Check field-level security for your integration user before you go live.
Before you start
Plan the mapping with your Salesforce admin first: which calls create records, which fields change, and who owns the follow-up.
On Enterprise plans, a solution architect helps you design and test the mapping.
Security & compliance
Botphonic only reaches the objects your integration user can see, and every request travels over TLS. Botphonic is built for regulated calls, with SOC 2 Type II readiness and regular third-party penetration tests.
Read the security overviewMore integrations
FAQ
Still deciding? We’ll walk through your setup on a short call.
Book a 20-minute demoBook a demo and we’ll sketch the lookup, the fields and the task logging for your org. Or start a free trial and build your first custom action today.
14-day free trial · 20 free minutes · $1 card check, refunded within 48 hours · Cancel anytime · See pricing