Inside the systems your store already runs
IDP's agents read your scheduler, DMS, CRM, lead sources and inventory before they act, write back what they did, and handle a system that's slow or down without pretending otherwise.
An AI agent that can't see your systems is a very polite answering machine. It can take a message, but it can't tell a caller when their car will be ready, offer a real appointment time, or know that the lead texting at 10 PM test-drove the same car last week.
IDP's agents work inside the systems your store already runs. They read before they speak and write back what they did, so your team keeps working in the tools they know.
What agents read
Before an agent answers a call or a message, it reads what it needs to be useful:
- The scheduler: open times, and the customer's upcoming appointments.
- The DMS: who the customer is, their vehicles, past visits and open repair orders, and later, whether a booked visit happened.
- The CRM: the customer's lead and history, so inbound and outbound conversations pick up from where your team left off, and the agent's CRM actions apply to that lead.
- Inventory: what's on the lot, with photos, prices and links, so a shopper sees real cars.
What agents write back
- Appointments into your scheduler, during the conversation.
- Notes of calls, texts and emails into your CRM, signed by whoever had the conversation: the agent, or the teammate who placed the call.
- Lead updates, such as "Appointment Set" when a sales appointment is booked, so your pipeline stays true.
Leads, from wherever they come
Leads arrive from third-party lead providers, your website and your CRM, including the standard ADF format most providers send. Leads that match a customer in your CRM are linked to them, lead-status rules apply, and a lead whose phone number is one of your store's own numbers is held for review instead of being contacted.
When a system is slow or down
Every store has a system that misbehaves now and then. IDP handles that out loud:
- If the scheduler can't answer for one customer's number, IDP tries that number less often instead of reporting the whole connection as failing.
- A booking that didn't change in the scheduler is retried once, and times are sent in the store's local time.
- A system you've disconnected no longer shows as failing.
- On a staff call or a customer call, a lookup that can't answer says so plainly, instead of guessing.
Which systems
The integrations page lists the systems IDP works with across scheduling, DMS, CRM, inventory, lead sources and phones. What a given store connects, which operations each connection allows, and how failures are handled are confirmed during solution design, because they depend on your providers, your permissions and the workflows you hand over.
See the integrations, or ask the agent on this page about the systems your store runs.
Questions about this? The agent on this page runs on IDP. Ask it anything here, or how it would work at your store.