Start workflow automation with one type of customer enquiry from one source. Set up your customer relationship management system (CRM) so that an eligible enquiry gets a record, a named owner and a follow-up task with a deadline. Leave the first reply to a person. In a shared inbox, a message marked as read tells colleagues that someone opened it, not that anyone has agreed to reply. Make that handover explicit before automating any part of the conversation.
1. Pick an enquiry with a repeatable next step
Look at a few working days of incoming enquiries and trace what the team actually does with them. A request for an introductory call might always go to the person on duty. A detailed request for a custom quote might need input from several colleagues before anyone knows what to ask next. Start with the enquiry that has the more predictable handover, even if the other one looks more valuable. The aim is to remove routine coordination without automating a decision that still needs judgement.
Choose one entry point, such as a service enquiry form. Keep support requests, replies to existing conversations and messages from other channels in their current workflows. If the selected form takes several kinds of request, identify the field that distinguishes the ones in the pilot. If the form does not make that distinction reliably, let a person sort the submissions or start with a form dedicated to one service.
Define where the automated work stops. For the pilot, an enquiry has been handed over when the right person can see it and knows what to do by when. It does not have to lead to a booked meeting or a sale. The guide to moving from first contact to the next action in a sales CRM explains the difference between a sales stage and the task that moves an enquiry forward.
2. Write the rule before configuring the CRM
Describe the process in terms a colleague could follow by hand: “When a new installation enquiry arrives through the form, check whether that submission has already been logged, assign it to the person on duty and set a task to review it and make contact by the end of the next working day.” That deadline is an internal agreement, not a response time promised to the customer. Agree how it applies to a Friday evening submission or a public holiday. If your CRM cannot calculate deadlines using your working calendar, choose a practical alternative or have the owner set the deadline.
Decide what the owner needs to see: who sent the enquiry, how to reach them, when it arrived and what they asked for. Show where to find the original message so the owner can check the exact wording. If the team already has access to the message and its attachments, a short summary and a reference may be enough. For help choosing fields, see what contact information belongs in a CRM.
Write down the exceptions as part of the rule. An enquiry with no usable contact details needs review rather than a task that assumes the owner can reply. Name the person who checks these cases and agree when they will look. Also distinguish between finding an existing contact and recognising a repeat delivery. The same email address can help you find the right contact record, but it does not tell you whether that person has made a new request.
3. Worked example: a four-person installation business
Imagine a business that supplies and installs office blinds. Two of its four staff handle sales and take turns covering incoming enquiries each week. Both see form notifications in a shared inbox. One sometimes reads a message between appointments and marks it unread as a reminder. The other sees the unread message and assumes nobody has picked it up. The team wants to avoid both missed replies and two people contacting the same prospect.
They start with the new-installation form. Once they have confirmed in testing that the form passes the necessary information to the CRM, they use a rule to log each new enquiry and assign a follow-up task to the person on duty. On Monday afternoon, a facilities coordinator asks about blinds for three meeting rooms. The task is to review the request and contact the coordinator by the end of Tuesday. The owner reads the original message and asks for approximate dimensions and a preferred installation period rather than quoting from the form alone.
After replying, the owner marks the initial task complete, records that the enquiry is awaiting measurements and sets a date to follow up if the coordinator has not replied. The task is complete, but the enquiry remains open. If the integration delivers the same submission twice with the same reliable submission ID, the rule can use that ID to avoid creating a second task. If the coordinator fills in the form again to add a fourth room, the owner reads that new submission and decides how to update the existing enquiry.
The team also tests what happens if the person on duty calls in sick. The backup takes new enquiries and checks the absent colleague’s open tasks, reassigning the ones that need attention. Changing who receives new work does not necessarily transfer tasks that have already been assigned. The team keeps that check manual rather than assuming the CRM knows who is available.
4. Test the handover, not just the trigger
Use test data before switching on the live workflow. Send an ordinary enquiry, deliver the same submission twice and check what happens if a record reaches the CRM without a field the owner needs. Test an enquiry that arrives after hours and check what the team can see when a transfer fails. Write down the expected result for each case, then inspect the outcome from the owner’s point of view. Can they find the original request, tell who is responsible and see when to act? A confirmation on the form is not proof that the CRM task exists.
During the first week, give one person time each day to compare incoming submissions with CRM records and review overdue follow-ups. Track missing records, duplicate tasks and unassigned enquiries separately. A missing record may point to a transfer problem. An overdue task may mean the deadline was unrealistic or the owner could not see the task. Find out which step failed before adding notifications. A reminder cannot help if the enquiry never reached the CRM.
5. Use this checklist before switching it on
- Choose one enquiry type and one source. List what is out of scope.
- Confirm which fields the owner needs and where to find the original message.
- Name the owner and backup. Check that both can see and act on the task.
- Specify the follow-up action and set a deadline that fits working hours.
- Test duplicate deliveries, missing information, failed transfers and absence cover.
- Decide who will check incoming enquiries, when to pause the rule and how to switch back to manual logging.
Ask a colleague who did not configure the rule to handle a test enquiry without guidance. If they cannot tell which message to reply to or what to do after replying, revise the task instructions. “Review the installation request and ask for any missing measurements” gives them a clearer first step than “New lead”.
Write down the fallback before launch. If the rule is paused, the designated colleague checks submissions in the original source from the last completed reconciliation and enters only those missing from the CRM. Before restarting, check whether the integration will retry failed transfers and whether those retries could create tasks for enquiries already entered by hand.
Can we start without connecting the form to the CRM?
Yes. Have someone log each enquiry manually, then let the CRM create a follow-up task from the new record if it supports that rule. This lets you test assignment and deadlines before relying on an automated transfer.
Does the first workflow need AI?
No. If the form already identifies the enquiry type, a fixed rule is enough. Consider AI separately if the team spends substantial time reading free-form messages or preparing draft replies for review. Compare those options in the guide to which sales tasks to automate first.
When should we add another source?
Add one when you can account for every enquiry in the pilot and colleagues can handle exceptions without relying on the person who set up the rule. Keep assignment and deadlines the same while you test the new source. If records from that source go missing, you can investigate the new connection without also having to untangle a change in who receives the work.
