REST API with OAuth 2.0
A dedicated Connected App, scoped to the agreed objects only. No shared passwords, and the token can be revoked at any time.
Integration · CRM
Official WhatsApp + Salesforce.
brisk4 carries the WhatsApp conversation into Salesforce and brings CRM context back to the agent. The integration uses the Salesforce REST API with OAuth 2.0, plus Platform Events to react to CRM changes in real time.
What syncs
Salesforce objects inside the conversation.
| Salesforce object | Direction | Trigger |
|---|---|---|
| Lead | brisk4 → Salesforce | First WhatsApp contact creates the lead with source, channel and the AI qualification transcript. |
| Opportunity | brisk4 ↔ Salesforce | A qualified lead becomes an opportunity; a stage change in the CRM fires a follow-up message. |
| Contact and Account | brisk4 ↔ Salesforce | Customer identified by phone or email; contact and account updated on both sides. |
| Case | brisk4 → Salesforce | A support request in the conversation opens the case in Service Cloud, with attachments and history. |
| Task and Activity | brisk4 → Salesforce | Every conversation logs the activity on the contact timeline, with no manual typing. |
Ready-made flows
What goes live first.
- Qualified leads straight into the funnelAI runs the conversation, applies your funnel criteria and only then creates the lead in Salesforce, already scored, sourced and with the transcript attached. Cold leads never pollute the CRM.
- Cases opened without a formThe customer describes the problem on WhatsApp; brisk4 identifies the account, classifies the subject and opens the case in Service Cloud with the full history.
- Follow-up fired by the CRMAn opportunity stage change emits a Platform Event, and brisk4 sends the right message over official WhatsApp, using an approved template.
How we connect
Method and prerequisites.
Platform Events
To react in real time to CRM changes: opportunity stage, case status, account updates.
Field mapping
Custom fields in your org are mapped during rollout, including picklists and validation rules.
- Covered products
- Salesforce Sales Cloud and Service Cloud
- Required access
- Connected App with a dedicated integration profile
- Authentication
- OAuth 2.0 with refresh token
- API limits
- Usage within the daily limit of your Salesforce edition
- Fields
- Custom field mapping defined during rollout
- Staging
- Salesforce sandbox before production
Frequently asked questions
Salesforce and brisk4: questions.
Does brisk4 replace Salesforce?
No, and that is not the intent. Companies that already run Salesforce keep the CRM as the commercial source of truth and use brisk4 as a service and automation layer on top of it. Companies without a CRM can use brisk4 own CRM and pipeline module.
How does the integration avoid polluting the CRM with cold leads?
AI qualifies before creating the record. Only contacts that meet the criteria you define become leads in Salesforce. The rest stay in the service history, available for lookup, without clogging the funnel.
Can the agent see Salesforce data during the conversation?
Yes. The brisk4 panel shows the account, open opportunities, cases and the contact latest activities, read from the CRM in real time, with no screen switching.
Does the integration consume Salesforce API limits?
It does, like any integration. The volume is sized during the assessment based on your edition and conversation count, and we cache where it makes sense to reduce calls.
Connect your Salesforce.
In the free assessment we map the objects and fields in your org and which funnel automation pays off first.