The customer messages at 8:17 pm. You see it during dinner, intend to reply in the morning and then forget when the day gets busy. By lunch, the enquiry has disappeared under newer messages. If that feels familiar, start with a reliable handoff that works even on your busiest day.
Give every enquiry somewhere to go
Start with one channel, such as your website form. Send each submission into a shared queue. Record when it arrived, the customer’s preferred contact method, what they asked for, and who owns the reply. Keep the amount of information collected as small as the task allows.
Acknowledge the message and set a real expectation
Send a short receipt such as: ‘Thanks, we’ve received your enquiry. Our team checks messages from 9 am on working days and will reply by the end of the next working day.’ Choose a time your team can actually meet. Keep pricing, availability and job promises out of the automatic reply unless they come from a system that knows they are accurate.
Assign a person and make missed replies visible
Route the enquiry to a named owner and give another person responsibility when that owner is away. Flag anything still unanswered by the deadline. Keep a manual queue for incomplete messages and for cases where the automation fails. Run tests for a duplicate submission, a weekend message and an absent team member before switching the workflow on.
Measure the workflow for two weeks
Track enquiries received, the time until a person replies and the number that miss your promise. Read a handful of replies to check whether they actually answer the customer. If AI helps draft replies, have someone check unusual cases, prices and commitments before sending them. Start with the basic routing first and add AI only where it saves measurable time.
If AI will process customer information, see the ICO’s AI and data protection guidance. For help connecting the form, shared queue and reminders, see Devsio’s small-business automation service.
