When enquiries build up, start by separating two problems: messages waiting for a reply and work waiting for someone to do it. Sales AI can help with both, but an inbox that replies quickly can still hide an overloaded callback queue. The useful unit of progress is a completed next step, not a message sent.
Choose a specific queue before introducing automation. For example, a training business might need to answer course questions and arrange adviser calls. A property business might need to coordinate viewings. Those workflows need different information and different rules even if they share the same messaging channels.
Define a small set of working states
Use states your team can act on: new enquiry, waiting for customer, action pending, assigned to a person, completed and closed. Give each state an entry condition and an owner. An enquiry should not remain labelled new after an adviser has already taken responsibility for it.
For every pending item, record the next action, who owns it and when it should be reviewed. Where the business has made a customer commitment, record that separately from an internal target. The assistant must not turn a team's preferred response time into a promise nobody has agreed to keep.
Route by the work required
- Information request: answer from current approved material and offer the relevant next step.
- Appointment request: use the configured calendar and report whether the booking succeeded.
- Existing conversation: preserve the current owner and latest commitment instead of starting another sales sequence.
- Exception or complaint: send the context to the responsible team and pause routine sales follow-up where appropriate.
- Unclear intent: ask a short clarifying question instead of making a consequential assumption.
Avoid labels such as low-value or time-waster based on writing style, accent or personal characteristics. Route by the task and the customer's expressed request. A person asking an unusual question may simply need a different kind of help.
Make duplicate prevention part of the design
Illustrative example: Morgan asks about a course by email and then calls to confirm the dates. If the call creates a second lead, two advisers may contact Morgan with different next steps. Define how records are matched, when an uncertain match requires review, and which system owns the final status.
Use the same discipline for retries. A failed calendar response should not trigger repeated appointments, and a delayed email event should not restart a completed follow-up sequence. Ask your implementation team to demonstrate these cases with fictional records.
Set a follow-up policy with an end
A useful follow-up offers something relevant: a missing answer, an available appointment or a requested document. Set a cadence, maximum attempts and explicit stop conditions. Customer replies, opt-outs, complaints and completed actions should be handled before another scheduled message goes out. Have the appropriate reviewer approve channel and consent requirements.
Review the queue, not just the dashboard total
Track the age of pending work, missed commitments, duplicate contacts and completed next steps. Sample closed conversations to check that closed means resolved or intentionally ended. Include the time staff spend correcting automation when assessing effort saved.
Tykuno's UK HGV story provides a training-business example of sales and follow-up work. Use published customer evidence to understand the workflow, then test the fit against your own queue, systems and responsibilities.