Who is the Salesforce integration for?
Salesforce teams usually work leads and contacts as separate records. The integration brings in either one, so a team can text new leads with one sequence and existing customers with another.
Textually is business texting built on sequences: texts go out from numbers we register for your business, each lead stays on the number that first texted them, and every reply lands in one shared inbox. Salesforce stays your record of who each person is and what happened.
How do I connect Salesforce to Textually?
Four steps, all in Settings, then Integrations. Nothing is texted during setup: an import only fills a list.
- Connect. In Textually, open Settings, then Integrations, then Salesforce, and sign in to Salesforce to approve the connection.
- Match fields. Phone, name, email and company are matched for you. Match a consent source and date too if Salesforce holds them.
- Test import. Textually reads your first 100 records and shows how many would come in, how many are ready to text, and why the rest would stay out. Nothing is saved and nobody is texted.
- Import. The records land in a list under Lists, then Integrations, then Salesforce. From there you push them into a campaign like any other list.
You choose Leads or Contacts when you connect. Name, phone, email and company come matched already, and any other field on that record type can be matched by hand.
How does consent work for Salesforce contacts?
A contact gets a consent record only when Salesforce itself holds a consent date and a consent source or a yes on an opt-in field. Textually never makes one up from the import date.
Salesforce has no standard texting opt-in field. If your team added one, match it in the field step.
Contacts without a consent record still come into the list, so you can see them, but a text step skips them, the same as a CSV import. Record consent on the list when you have it, or confirm consent for the whole campaign at launch, and they become textable. More in SMS opt-in wording.
What does Textually write back to Salesforce?
When someone texts back or opts out, Textually adds a completed task to their Salesforce record with what they said. You can also turn on a completed task when a lead finishes a sequence.
Your team answers the reply in Textually’s shared inbox, from the same number the lead already knows. Salesforce gets the history, so anyone who opens the record there sees that the lead wrote back, and that a STOP means no more texts.
Does it stay in sync with Salesforce?
Yes, if you turn on Keep in sync. Every hour Textually reads records added or changed in Salesforce since the last sync and updates the list.
- A Salesforce record already in the list is updated when its values change, never added twice.
- A new record whose phone number is already in the list is left out, so nobody gets the same text twice.
- Records with no phone number, a number outside the US and Canada, or a do-not-text mark in Salesforce stay out, and the test import tells you how many.
Disconnecting stops the reading and the completed tasks. Your list and everyone already in it stay as they are.