Helvaro and WinCar.
Customer history is the difference between an agent that asks questions and an agent that already knows the customer. This integration is on the list and has not been built yet.
Where this sits in your business.
Helvaro does not replace your package. It stands in front of it, in the spot where nobody stands today.
What the integration is going to do.
History as context
What was done last time, what mileage it was on and what was noted then. That makes every message more concrete.
Service intervals
The basis for the service reminders, so they run on your intervals and not on a standard schedule.
Vehicle file
Everything belonging to a car in one place, so the conversation does not have to start there again.
No second database
One customer base stays one customer base. In the long run that matters more than any feature.
Not started yet. It is on the list because customer history makes the servicing and reactivation workflows considerably sharper, but there is nothing to see today.
- Working with the data you supply yourself, for example via an export
- Appointments in Google Calendar
- Read back and export every conversation
- Reading customer history live
- Pulling service intervals
- Writing back to the vehicle file
A one-off export of your customer records is often enough to start. That is not an integration, but it does work today.
Short and honest.
Can it also be done with an export?
Yes. For the reminder workflows an export of registrations, customer details and last visit is often enough to start.
What happens to that data?
They are processed within the EU and used only for the workflows you switch on. Details are in the privacy policy.
Do we have to switch?
No. We build towards packages, not away from them.
When is this coming?
When a garage that works with it joins the pilot. Only then do we know which fields actually matter.
Do you work in this package?
Tell us which package you work in. We will say honestly whether it can be done today, or when it can.
Book a demo