Get Started
Connect your CRM
How Sarj reads from and writes to your CRM during a conversation, and what to prepare before your deployment team connects it.
Sarj is most useful when it can act, not just answer. Connecting your CRM lets the agent recognise who it is talking to, look up their history, and record the outcome of every conversation as it happens.
What the connection does
Reads
During a conversation, Sarj can look up the caller's record, open cases, orders, appointments or balances, whatever your use case needs, so it answers with the customer's own details rather than general information.
Writes
When the conversation ends, the CRM is already up to date: the outcome, the details the customer gave, any promise to pay or follow-up, and a link to the transcript. Nobody re-keys a call after it ends.
Supported systems
Sarj works with the systems enterprises in the region already run, including Salesforce, SAP and Oracle, as well as core banking platforms. Other systems connect through their APIs. Your Sarj deployment team confirms the right approach for your environment during discovery.
Before your team connects it
Choose the records and fields
List the objects the agent needs to read and the fields it should write. Starting narrow makes review and approval faster.
Create a dedicated integration user
Give Sarj its own account with only the permissions the use case requires. Every change it makes is then attributable and easy to audit.
Agree on identity checks
Decide how a caller is verified before the agent reveals or changes anything, for example by matching a registered phone number plus a second detail.
Next steps
See CRM & ERP Actions for the kinds of actions Sarj can take once connected.