Last updated: October 13, 2026
Quick answer: Yes. With Kimoby on CDK, repair order, customer and appointment data sync from CDK, and CDK is currently the only DMS where a Kimoby Pay transaction writes back automatically. It marks the payment as paid on the right RO, but it doesn't close the RO. Writing approved estimate lines back to the RO is in development and not live on any DMS yet.
With Kimoby on CDK, your team gets repair order, customer and appointment data pulled straight from the DMS. CDK is 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.
Without a DMS connection, every tool your 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 use to text, inspect or take a payment. Multiply that across every call, every video and every transaction, and it's real time lost to bridging systems that don't talk to each other. The CDK connection removes that bridging step, to varying degrees depending on what you're doing.
At the Kimoby Pay terminal, the customer, RO number and amount due fill in directly from CDK. No re-typing, no toggling between two screens mid-transaction. Invoices are also delivered through CDK, so that record lives in the DMS and not only inside Kimoby.
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, because 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. For the product view, see payment write-back for CDK.
The CDK connection isn't only for payments. The rest of the service lane workflow is built on top of it.
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 estimate built from it reference the same repair order. On Service Lane OS Pro, AI drafts that estimate from the video and your advisor reviews it before it goes out. The customer's approval and the advisor's view of the RO stay in sync.
Missed calls. Kimoby Voice catches the calls your team misses, transcribes and summarizes them, and lets the caller switch to text. It doesn't book appointments yet.
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, not a separate exported list.
Not yet. If your store works out of CDK Service's grid view (a status-based RO list where jobs move between columns as they go through tech, parts, advisor and customer), a comparable view is in development inside Kimoby. Treat it as something coming, not something to plan around today. It's built for that exact workflow, not a generic list view retrofitted for CDK stores.
A DMS is the system of record. With Kimoby connected to it, your advisors turn that record into conversations, approvals and payments, working from the same CDK data they already use every day. It's not a separate tool they have to check on top of it.
Want to see it on your own CDK data? Book a demo.
RO sync also works with Tekion (pull only) and PBS, along with Reynolds & Reynolds, Keyloop Serti, Dealer Vu, Quorum and others. Payment write-back is CDK only for now. See the full integrations list.
Yes. Repair order data syncs from CDK, and CDK is currently the only DMS with automatic payment write-back through Kimoby Pay.
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.
No. The same CDK connection underlies texting, video inspections, digital estimates, missed-call handling through Kimoby Voice, loaner management through Kimoby Go, and service campaigns through Kimoby Grow. Payments is the piece with automatic write-back today, but it's one module inside the full platform.
Kimoby's Service Lane OS is one option. It connects texting, video inspections, digital estimates, loaner management, campaigns and payments to CDK, including automatic payment write-back.