Salesforce, kept in step with every message.
The agent reads the lead, writes the outreach draft against the record, logs the send once a person approves it, and sorts the reply into the right stage. The CRM stays the system of record; the agent keeps it current.
- The agent reads
- Leads, contacts, accounts and opportunities in the objects you grant
- Activity history, to avoid writing to someone written to last week
- Campaign membership
- The agent writes
- Tasks and activities for every message sent or received
- Stage and status changes after a reply is classified
- Draft outreach stored on the record for approval
- A person approves
- Sending any outreach or reply
- Changing an opportunity amount or close date
- Merging or deleting records
Setting it up.
| Access | A connected app with OAuth in your org; an integration user with a permission set limited to the objects and fields the agent needs; revocable by your admin. | |
| Mapping | Field map agreed per object; custom fields for agent status and last-touch so reports can filter on them. | |
| Cap | 45 outbound a day per sender; sequences pause on any reply. | |
| Time | About 5 working days inside a sales build. | |
Builds that use it.
Questions buyers ask
Does the agent change our pipeline on its own?
- It moves a lead between stages after classifying a reply, which you can confine to a draft status if you prefer. Amounts, close dates, merges and deletions wait for a person.
Which permissions does the integration user need?
- Read on the objects it reads, create and edit on activities and the agent status fields, nothing on setup. A permission set your admin can inspect and revoke.
Can it work with HubSpot or Pipedrive instead?
- The same agents run against any CRM with an API; Salesforce is the one on the build library today. Ask about yours.
Will it email contacts who asked us to stop?
- No. Unsubscribe requests are honoured the moment they arrive and written to the record; sequences check the flag before every send.