Kimoby connects to CDK for repair order, customer, and appointment data. It's also currently the only DMS where a Kimoby Pay transaction writes back automatically.
Here's what that connection covers today, what's still in development, and how the rest of the platform, texting, video inspections, estimates, loaners, and campaigns, runs on top of it.
The problem this solves
Without a DMS connection, every tool a service department uses becomes its own island. The advisor looks up the RO in CDK, then re-enters the same customer and vehicle into whatever else they're using to text, inspect, or take a payment. Multiply that across every call, every video, every transaction, and it's real time lost to bridging systems that don't talk to each other. The CDK connection is what removes that bridging step, to varying degrees depending on what you're doing.
What syncs at the point of payment
At the Kimoby Pay terminal, customer, RO number, and amount due auto-populate directly from CDK. No re-typing, no toggling between two screens mid-transaction. Kimoby also delivers invoices through CDK, so that record lives in the DMS rather than only inside Kimoby.
What write-back actually does today
Note: some sources use "writeback" as one word. Same thing.
Once a Kimoby Pay transaction is processed on CDK, it writes back automatically and marks the payment as paid, auto-allocated to the right RO. It posts the transaction, it doesn't close the RO, your team still closes it the same way they always have. Nobody has to manually reconcile that payment at the end of the day, CDK already has it recorded.
Worth being precise about the boundary: this writes back the payment status, not the repair order line itself. A separate capability, full RO-line write-back, pushing approved estimate lines directly into the RO, is in active development. As of this writing it isn't live yet on any DMS, CDK included, so it's not something to promise on a timeline.
This is the same integration behind Honda & Toyota of Seattle's in-person payments story, which covers CDK write-back and reconciliation directly.
Beyond payments: what else runs on the same connection
The CDK connection isn't only for payments, it's what the rest of the service lane workflow is built on top of.
Texting. Every conversation ties to the open RO your advisor is already looking at in CDK, so the thread has context instead of being just a phone number.
Video inspections and estimates. A technician's walkaround video and the AI-generated estimate built from it both reference the same repair order, so the customer's approval and the advisor's view of that RO stay in sync.
Missed calls. Kimoby Voice identifies the caller against the same CDK account data, matches them to their open RO, and routes them to their own advisor instead of a generic queue.
Loaners. A loaner agreement created in Kimoby Go references the same customer and vehicle record, so it's not a separate paper trail from the repair itself.
Campaigns. Declined-service follow-up, recall outreach, and warranty-expiry campaigns through Kimoby Grow draw on the same customer and vehicle history rather than a separate exported list.
Built with CDK dealers specifically in mind
For stores used to working out of CDK Service's grid view, a status-based RO list, moving jobs between columns as they move through tech, parts, advisor, and customer, a comparable view is in development inside Kimoby. It's not live everywhere yet, so treat it as something coming rather than something to plan around today, but it's built with that exact workflow in mind rather than a generic list view retrofitted for CDK stores.
Why it matters
A DMS is the system of record. Kimoby is what turns that record into conversations, approvals, and revenue, connected to the same CDK data your advisors already work from every day, rather than a separate tool they have to check in addition to it.
Related integrations
Kimoby also connects to Tekion and PBS. See the full integrations list for CDK, Reynolds, Tekion, PBS, DealerTrack, Autosoft, and more.
FAQ
Does Kimoby integrate with CDK?
Yes. Kimoby connects to CDK for repair order data, and CDK is currently the only DMS with automatic payment write-back through Kimoby Pay.
What does payment write-back to CDK actually do?
Once a Kimoby Pay transaction is processed, it writes back to CDK and marks the payment as paid, auto-allocated to the correct repair order. It posts the transaction but doesn't close the RO. It does not write back the RO line itself, that capability is in development and isn't live yet on any DMS.
Does Kimoby only handle payments for CDK dealers?
No. The same CDK connection underlies texting, video inspections, digital estimates, missed-call handling through Kimoby Voice, loaner management, and service campaigns through Kimoby Grow. Payments is the piece with automatic write-back today, but it's one module inside the full platform.
What third-party tools integrate well with CDK?
Kimoby is one option: a Service Lane OS with texting, video inspections, digital estimates, loaner management, campaigns, and payments connected to CDK, including automatic payment write-back.
