Integrations · CRM

Every lead in your CRM, with the conversation behind it.

A lead from an AI conversation is only useful where the sales team works. Salesteq writes each verified lead, test drive and service request into the CRM the dealer already runs, with name, phone, car, the brief and a link to the conversation; keeps the owner in sync when the CRM reassigns; and exposes the data the other way through a public API with webhooks. Dealers without a CRM, or tired of theirs, use Salesteq's own.

Updated October 2026

Salesteq AI agent on a dealer website capturing a verified lead and writing it into the dealer's CRM with a brief for the salesperson

1 in 4

cars sold at the first group start with a conversation with the agent, traced in the CRM

28.6%

of WhatsApp conversations at Hyundai Saudi Arabia become a CRM lead with name, phone and car

identity: the verified phone number, so a returning customer updates the card instead of creating a duplicate

24/7

leads written as they happen, on WhatsApp, the website, Instagram and the phone

Three ways into your CRM

Route	How it works	In production
Webhook per lead	A signed JSON payload with the fields your CRM expects, mapped from the conversation (name, phone, email, model, budget, urgency, branch, language, consent flags, source), with value maps for your pick lists and bearer, basic or header auth.	Hyundai Saudi Arabia (lead dashboard), MYNAGHI marketplace
Keyloop CRM web lead	The enquiry is written into Autoline CRM through Keyloop's web-lead channel, matched to the existing contact by phone number, with origin and source so the dealer's own call lists and routing rules fire.	BMW and MINI Saudi Arabia; Ford through Keyloop's partner lead API
Connector	Salesforce and other systems through a connector; the same capture, matching and audit log.	Scoped per project

What a lead carries

01Verified phone number: a one-time code confirms it before the lead is written, so sales calls go to real buyers.
02Customer, car and intent: model, trim, new or used, budget range, financing interest, preferred branch and time.
03The brief: what to lead with, what to avoid, the next step, in the salesperson's language, plus a link to the full conversation.
04Returning customers: a new conversation within 30 days updates the existing lead and flags it as returning; after that a new lead is created, with a pointer to the previous one.
05Source and channel: WhatsApp, website, Instagram, phone menu, campaign, so attribution in the CRM is right.

Owners and statuses, both ways

When the CRM is the system of record for ownership, Salesteq follows it: a change of owner in the CRM moves the conversation to that consultant's inbox, and a consultant who picks up a conversation in Salesteq is pushed to the CRM as the owner. Every write and every pull is logged with who changed what and when, so a moved chat can always be traced to the person or API key that moved it. A closed or lost opportunity means a returning customer opens a new one instead of reviving a dead card.

The other direction: a public API and webhooks

Dealers and their IT teams read Salesteq data with keys they issue themselves in Settings: conversations with an updated-since cursor, calls by period, customers by phone, with scopes, expiry, rotation and an access log per key. Tenant webhooks deliver new conversations and calls to your endpoint as they happen, signed, so nothing has to poll. The documentation is public and readable by AI agents at agent.salesteq.com/llms.txt.

Salesteq's own CRM

Dealers without a CRM, importers in new markets, and groups retiring a legacy system use the CRM inside Salesteq. The agent writes it, the team reads it: a sales board per brand, cards with the conversation, the car and the verified phone, assignment to consultants, merge of duplicates with a change log, search by name or phone from the inbox, and the same board in the mobile app. It is the system of record for the Hyundai importer in Tajikistan and for the MYNAGHI sales team's WhatsApp leads.

Questions about CRM integration

Does Salesteq integrate with our CRM?+

Yes. Leads go in through a signed webhook with your field names and pick lists, through Keyloop's CRM web-lead channel into Autoline, or through a connector. Live with Keyloop CRM at BMW and MINI Saudi Arabia and with dealer lead systems at Hyundai Saudi Arabia and the MYNAGHI marketplace.

Is the lead verified?+

Yes. A one-time code confirms the phone number before the lead is written, and the phone number is the identity: a returning customer updates the existing lead instead of creating a duplicate.

What if our CRM reassigns the lead?+

Salesteq follows the CRM: the conversation moves to the new owner's inbox, and the change is logged with who made it.

Can our IT team pull data from Salesteq?+

Yes. A public API with keys you issue yourself gives conversations, calls and customers, and tenant webhooks push new conversations and calls to your endpoint as they happen. Documentation is public at agent.salesteq.com/llms.txt.

We have no CRM. Do we need one?+

No. Salesteq's own CRM holds the leads, the conversations and the pipeline, on the web and in the mobile app, and the agent keeps it up to date.

Which CRMs have you connected?+

Keyloop CRM (Autoline) and Keyloop's partner lead API, dealer-built lead systems through webhooks, and an open-source CRM with two-way owner sync at a Saudi dealer group. Salesforce has a connector. Anything with an HTTP endpoint works through the webhook.

See a lead land in your CRM.

We map the webhook to your fields in the demo, run a conversation and watch the lead appear on your side with the brief.

Book a demo

Or write to [email protected]

Sources

Keyloop, Keyloop DMS (integrated lead capture): keyloop.com/dms-request-demo