Integrations
CRM and customer records
Keep your system of record current without manual data entry.
3 min read
Keep your system of record current without manual data entry. A connection is only useful in service of a workflow, so decide what you want Operator to carry first, then grant the access that motion needs.
What Operator can use it for
Access is granted per workspace and tied to the workflows that use it. With this connection in place, Operator can:
- read account and deal context before preparing work
- prepare record updates after a meeting or conversation
- flag accounts where a pattern changed
Common workflows
- lead response
- meeting follow-up
- customer health and renewals
What context is relevant
- contact, account and deal records relevant to the workflow
- activity history
Permissions and access
Access is scoped to the workflow you enabled and can be revoked at any time. Connect the narrowest access that lets the workflow work, not the broadest access the tool offers.
Good to know
Exact permission names differ per provider. Grant only the access the workflow requires and review it periodically.
Where approval happens
- changes to commercial terms
- deletion or bulk changes to records
Human checkpoint
If an action would be awkward to undo, keep it behind an approval.
Disconnecting access
A connection can be removed at any time. Once removed, Operator no longer has access to that system and the workflows depending on it stop until the connection is restored.
The same connect, scope and revoke model applies to every system. How integrations work
Continue learning
Lead response
Respond to inbound interest quickly without losing human control over customer-facing communication.
5 min read
Customer health and renewals
Watch the signals around an account before a renewal quietly slips.
4 min read
How integrations work
Scoped access, connected per workflow and revocable at any time.
4 min read