Your Salesforce org is set up the way your business works. Lead statuses, owners, sharing rules, the reports leadership reads. The last thing you want is a tool that writes over it.
If you’re the Salesforce admin or the CRM owner, this page is for you. It covers exactly what moves between Salesforce and Intend, the rules Intend keeps in your org, and the three things you do to switch it on.
In short, Intend works on top of Salesforce. It reads new leads in every few minutes, answers and books them, and writes the stage, call notes and site visits back to the Lead.
What moves between Salesforce and Intend
| From Salesforce to Intend | From Intend to Salesforce |
|---|---|
| New Leads, read every few minutes | Lead Status, when a buyer moves forward |
| The stage each Status stands for, as you map it | Each call or message, as a Task |
| Do-not-contact fields, so those buyers are left alone | Site visits, as Events, kept up to date |
| Call recordings linked on Tasks, for coaching | Opt-outs, when you switch it on |
Rules Intend follows in your Salesforce org
- It never moves a Lead backwards and never touches a won Lead.
- It never changes the Lead owner.
- It never deletes anything.
- Writing back is switched on per client, once you have checked the mapping.
What your Salesforce admin does
- Creates an integration user with only the access Intend needs.
- Pastes the connection keys into a one-time link we send. No password is shared.
- Checks the stage mapping with us before anything is written back.
What stays the same on every CRM
- Your CRM stays the system of record. Intend never deletes a record in it.
- Your team keeps working in the CRM they know.
- Every call, message and site visit is also on one record per buyer in Intend.
Before you start
Have your Lead Status values to hand, and decide which one means “site visit booked”. That single mapping is most of the setup conversation.
Back to all CRMs, or see what happens to the leads on Intend for real estate developers.