Keyloop messaging: what dealers can send, trigger and automate

Once Keyloop data is available to your messaging platform, the interesting question stops being technical. It becomes editorial: which events in the DMS actually deserve a message, and what should that message say.

Send too few and the integration earns nothing. Send too many and customers mute you, which costs more than the messages were ever worth.

MOT and service due

The most reliable one. The due date is already in Keyloop, so nobody needs to build a list. A message four weeks out, a second at one week if there has been no reply, and nothing after that.

Include the registration, the due date and a way to book in one tap. Do not include a price unless you can honour it, and do not send three reminders because the first two were ignored.

Vehicle health check raised

The workshop finds work, the customer needs to approve it, and the advisor spends the afternoon on voicemail. Triggering from the health check turns that into a message with the video and the itemised work attached, approved in a tap.

Timing is everything here. The message should go while the car is still on the ramp, not at five o'clock when the decision has already cost you the day.

Vehicle marked as sold

The gap between deal done and handover is where anxiety lives. Status changes in Keyloop can drive the updates: paperwork received, prep started, delivery date confirmed.

These are short, factual and genuinely welcome. They also cut the inbound calls asking whether anything has happened yet.

Finance and warranty renewal

End dates sit in the DMS and are easy to act on late. A message three months out, framed as a conversation rather than an offer, gets you into the customer's thinking before they start browsing elsewhere.

Lapsed customers

Anyone whose last visit is beyond your normal service interval. This is a campaign rather than a trigger, but the audience comes from the same live Keyloop fields, so nobody exports a spreadsheet to build it.

The best automated message reads like someone in the dealership thought of you. The worst reads like a mail merge that found you.

Rules that keep it working

1. One message per customer per event, with a single follow-up at most
2. Respect consent stored against the Keyloop record, every time, without exception
3. Send inside working hours, in the customer's time, not when the job finished
4. Always leave a route to a person, because some replies are not for a bot
5. Measure replies and bookings, not sends, so nobody optimises for volume

The discipline is the product. A group sending five well-timed messages a month gets more bookings than one sending twenty, because the first group still gets read.

See the full list of supported triggers on our Keyloop WhatsApp integration page, and how the data connection itself works in Keyloop DMS and WhatsApp.