In many small businesses the same customer lives in four places: the mailbox, an Excel sheet, the accounting package and the calendar. Every change has to be made in all of them, and that is exactly where things go wrong. CRM automation therefore does not start with clever features but with one question: where are you typing something that already exists somewhere else?
This article is about recording and following up customers and enquiries. For drafting the quote itself, see automating quotes from enquiry to signature.
Where double entry comes from
Double entry almost always appears where one system hands over to another. A few familiar examples:
- Installer: an enquiry comes in through the website form, someone enters the details in the schedule and later again on the invoice.
- Hair salon: a client books online, but allergies and colour formulas sit on a card or in someone’s phone.
- Recruitment agency: candidates live in a mail folder, vacancies in a spreadsheet, and the link between the two lives in one recruiter’s head.
- Garage: registration, mileage and service history are looked up and retyped for every work order.
The problem is not only time. Every time someone retypes something, a digit can slip. And when the data lives in four places, nobody knows which version is right.
One customer record as the source
The foundation of CRM automation is that every customer has exactly one record, and everything you do with that customer hangs off it: enquiries, appointments, quotes, invoices, notes and messages. Other parts of the system read from that record instead of keeping their own copy.
What belongs on the record
- Contact details: name, company, address, phone and email, entered once.
- Source: the channel the customer came through, so you know what works.
- History: earlier enquiries, appointments, quotes and payments in date order.
- Agreements: what was promised and by whom, so a colleague can take over.
- Industry data: the registration at a garage, the colour formula at a salon, the membership at a yoga studio.
That last point is where a generic CRM package often falls short. You can add extra fields, but they do not work with your scheduling or invoicing. That is why we build the customer record per industry, for example in our software for trade businesses, where the record links straight to work orders and quotes.
Follow-up that does not depend on one person
An enquiry that sits in an inbox for three days is often a lost job. Automatic follow-up makes sure there is always a next step, even when the person who read the email is ill or on holiday.
- Enquiry arrives: the form creates a customer record straight away, or adds to an existing one if the email address is already known.
- Confirmation: the customer immediately gets a message that the enquiry has arrived and when you will respond.
- Task: a task is ready for the right colleague, with a deadline.
- Reminder: if the task is not done on time, someone else gets a nudge.
- Next step: after an appointment or quote a new task appears automatically, so the thread never breaks.
Where AI helps and where it does not
An AI assistant can be useful in CRM work, especially where text is involved. Think of summarising a long email into three lines, placing details from a free-form message into the right fields, or preparing a draft reply. In Vorlyo’s software this is a module: the AI assistant makes a suggestion and a member of staff approves it.
Do not let AI overwrite customer data or send messages on its own without a check. A wrongly merged customer or a wrong address is hard to undo. How to set up that check is covered in human oversight in AI processes.
Privacy and retention periods
A CRM holds personal data, so the GDPR applies. Among other things, that means you only record what you need, you know how long you keep it, and you can handle a request for access or deletion. With one customer record that is simpler: you do not have to search four systems.
- Permissions: give staff access only to what they need for their work.
- Clean-up: set a period after which old enquiries without a job are deleted.
- Audit log: record who changed data, so you can trace mistakes.
When a standalone package no longer fits
A standard CRM package works fine while your process is simple. It becomes awkward when you copy data back and forth between CRM, scheduling and invoicing, or when integrations keep breaking. At that point, software in which customer, schedule, quote and invoice form one whole is usually calmer. That trade-off is worked out in from spreadsheet to your own software. An overview of the industries we build software for is on our software by industry page.
Frequently asked questions
Do I need a separate CRM package?
Not necessarily. If your customer data already lives in the software you use for scheduling and invoicing, a separate CRM package is often just one more place to keep up to date.
Can I move my existing customer list across?
Yes. An Excel or CSV export from your current system can be imported. It is wise to merge duplicate customers first, otherwise you bring the mess with you.
What if a customer contacts us through several channels?
The software recognises the customer by email address or phone number and attaches the message to the same record. When in doubt, you get a suggestion to merge.
Can I keep enquiries that did not lead to a job?
As long as there is a reasonable purpose and you apply a retention period. Record that period and let old enquiries be cleaned up automatically.