Salesforce integration use cases
1. Lead sync from chat
When chat captures a lead via collect_lead:
- Lead score calculated (BANT).
- Above threshold → sync to Salesforce.
- Creates a Lead record with channel source, conversation transcript, score.
- Routes via Salesforce workflow to the right rep.
Typical: 5 to 15% of chat conversations sync to Salesforce.
2. Customer-context retrieval
For identity-verified visitors:
- Bot looks up Account in Salesforce.
- Pulls plan tier, last interaction, open tickets.
- Tailors responses based on customer status.
Useful for Enterprise customers: bot knows them, doesn't re-ask basics.
3. Account-aware bot replies
Visitor: "What plan am I on?"
Bot (verified visitor):
- Looks up Account from Salesforce.
- Reads
Plan__ccustom field. - Replies "You're on Enterprise Plus with 50,000 seats."
For unverified visitors: escalate to a human (no leakage).
4. Knowledge Article retrieval
Salesforce Knowledge Articles indexed via Salesforce ingest:
- Bot answers from Articles.
- Cites the Article URL in Salesforce.
- Article suggestions to agents during ticket review.
5. Case context
For inbound questions on existing cases:
- Visitor mentions case number or identity-verified visitor with open Case.
- Bot pulls Case details, history.
- Personalizes response: "Your case #C-12345 was last updated 2 days ago by Alice in Engineering."
Setup
45 minutes:
- Connect Salesforce via OAuth. See Salesforce setup.
- Approve API access scopes.
- Map field-mapping: Lead, Account, Contact, Case, Knowledge.
- Configure routing: which conversations sync.
- Configure Salesforce-side webhooks for return signals.
- Test.
Field mapping
Default mapping:
| AskVault field | Salesforce field |
|---|---|
| Visitor name | Lead.FirstName, Lead.LastName |
Lead.Email | |
| Phone | Lead.Phone |
| Company | Lead.Company |
| Channel | Lead.LeadSource |
| Lead score | Lead.AskVault_Score__c (custom) |
| BANT data | Custom properties |
Customize under Integrations > Salesforce > Field Mapping.
Webhook events
Salesforce → AskVault:
Lead.converted. AskVault updates contact's audience tag.Case.closed. AskVault resolves the linked conversation.Opportunity.stage_changed. Tags the contact accordingly.
Sandbox vs production
For testing:
- Connect Salesforce Sandbox first.
- Validate the flow end-to-end.
- Switch to production once confident.
Available on Business and above.
Plan considerations
- Free, Starter, Growth. No Salesforce.
- Business. Full integration.
- Enterprise. Custom-object support, SSO between AskVault and Salesforce.
Privacy
What AskVault sends:
- Lead data when collect_lead fires.
- Conversation transcripts as Activity history.
- Custom property values.
What AskVault reads:
- Account, Contact, Lead, Case per OAuth scope.
- Knowledge Articles indexed.
Limits
- Salesforce API calls. Per Salesforce plan limits.
- Custom field mappings. Up to 50.
- Bidirectional webhook events. Configurable.
Common pitfalls
API limit hit. Salesforce's daily API limit. Audit usage; upgrade Salesforce edition if needed.
Lead duplicates. Email matching off. Configure deduplication.
Knowledge Articles missing. OAuth scope insufficient. Re-authorize with read knowledge.
FAQ
Does this work with Salesforce Service Cloud?
Yes. Service Cloud Case integration plus Sales Cloud Lead integration.
Can I sync Opportunities from chat?
Today, Leads only auto-create. Opportunity creation via webhook to your Apex.
What's the latency on lead sync?
About 60 seconds from capture to Salesforce Lead.
Related guides
- Salesforce integration setup
- Salesforce ingest
- Collect lead skill
- SDR lead qualifier skill
- HubSpot use cases