The work that runs your store does not live in any one system. It lives in the gaps between them. The Workflow AI Agent lets your desk manager compose multi-step automations across DMS, CRM, scheduler, and equity. Define the trigger. Define the steps. The agent runs them, every time, signed under the protocol.
Every dealer principal has the same list. The 60-day equity outreach. The post-sale service handoff. The recall + maintenance combine. The lost-deal follow-up. Each one is a workflow that crosses three systems and four people, and each one only runs when someone remembers to run it. The list is the operating manual. It is also the graveyard.
The SOP lives in a binder, a Google Doc, a manager's head. Execution depends on the BDC pulling the right list at the right time, the desk manager checking the right report, the service writer remembering the recall. Most months, half the workflow runs. Some months, none of it does.
The desk manager sketches the trigger, the condition, and the steps in a visual composer. The Workflow Agent fills in the routing, the timing, the agent-to-agent handoff. From that point forward it runs on its own schedule, signs every step, and surfaces only the exceptions a human needs to see.
The composer is a canvas, not a form. Drop a trigger (DMS sync, lead in, calendar event, CRM tag). Drop conditions (equity position, days since last contact, vehicle age, customer tier). Drop actions (route to Head Hunter, draft SMS, book in DealerSocket, hand off to Follow-Up). The agent infers the connections you did not draw and asks before assuming.
The agent subscribes to signed events from your DMS, CRM, scheduler, inventory, and lender systems. A vehicle hits 36 months. A new lead enters the funnel. A service customer crosses a mileage threshold. A deal stalls at the desk for 48 hours. Every trigger is observed in real time. The right workflow fires the moment the condition is met.
The agent routes each step to the right system or the right specialist agent. Read from DMS. Write to CRM. Hand the customer to Head Hunter for equity outreach, to Sales for the appointment, to Follow-Up when the cadence belongs to a different beat. Every read and write is signed under ACP. Every run produces an audit trail a GM can open in one click.
This is 36mo_equity_outreach: the workflow that lit up the wall above. Sketched by Coastline Auto's desk manager during a slow Tuesday. Has run 1,284 times since.
Below is the exact trace of run #1,284. Every read, every write, every handoff between agents: signed and time-stamped. This is what your GM opens when they want to know what actually happened.
The agent reads from your DMS (CDK, Reynolds, DealerSocket), your CRM (DealerSocket, VinSolutions, eLead), and your scheduler (xtime, myKaarma). It needs the customer file, the deal log, and the appointment book. The connection is direct, signed, and reversible.
Our deployment team sits with your desk manager and sketches the three workflows that move the most revenue at your store: a service handoff, an equity outreach, a lost-deal revive, or whatever your shop has been trying to run by hand. Shadow mode means the agent does everything except the final write. Your GM sees every step that would have happened.
Day 14: the first three workflows go live with GM approval. From there, your team composes new workflows directly in the canvas. By month two, most stores are running between ten and twenty workflows. By month six, the workflow library is the operating manual.
The Workflow Agent runs on ACP, our protocol layer that connects dealership systems to AI agents. Same protocol powers Sales, Service, Follow-Up, and Head Hunter, which is what makes cross-agent workflows possible.
Read the ACP briefNo replacement. No data migration. The agent reads from the systems your store already uses, takes inbound voice and SMS through Twilio, writes back through ACP. Your existing systems remain the source of truth. The Workflow Agent is a reader, a writer, and an orchestrator, not a new database.
Trailing 90 days, anonymized aggregate across active Workflow Agent deployments. ACP-signed and verifiable in customer audit logs.
Run rate on composed workflows. Once a workflow is composed and approved, it runs on its schedule. Forever. The number that used to be 40% is now 100%.
ev.workflow.run.closed · cohortAverage time from kickoff to first workflow live. Three workflows composed and shadowed in week one. Live the morning of day fourteen.
deployment.cohort · trailing 90dMedian number of workflows running by day sixty per rooftop. The composed library becomes the store's operating manual.
workflows.active · p50For sales managers, desk managers, and GMs who know the deal is on their lot and want to stop waiting for the customer to walk in. Answers indexable by Google AI Overviews, Perplexity, and ChatGPT.
A 30-minute demo on your live data. Custom ROI for your store. No procurement gauntlet.