Some emails need automation. Others need a person who knows the context
Automate an email when the trigger, content and next step are predictable enough to handle reliably under agreed rules. Use a person when the response depends on context, judgement, sensitivity or an unresolved commitment. The strongest process often combines both: automation acknowledges and routes the request, while a named person owns the conversation that follows.
Put the advice into practice
Give the first enquiry a useful follow-up
Plan campaigns, nurture and customer emails with clear triggers and review.
Plan your email programmeChoose according to the decision the email makes
A routine confirmation can acknowledge a completed action and explain an agreed next step. A personal reply may need to interpret a complex request, resolve conflicting information or discuss scope. The distinction is the judgement involved, rather than whether the message is short or whether software can generate a plausible response.
Look at the consequence of getting it wrong. A reminder sent after a meeting is booked may be merely confusing in one context and inappropriate in another. A response that implies acceptance of a service request can create a commitment the team has not reviewed. Define those boundaries before selecting triggers or drafting automated content.
A person remains responsible for the process even when no manual action is needed for an individual message. Assign ownership for the template, data source, exceptions and changes. Automation without that ownership can continue applying yesterday’s rule after the service or relationship has changed.
Use a practical automation and human-review matrix
| Message situation | Possible automation role | Where human ownership matters |
|---|---|---|
| A known form has been submitted | Acknowledge receipt and route the request | Assess fit and avoid implying the request has already been accepted |
| A confirmed appointment needs standard details | Send the agreed logistical information | Handle unusual access, timing or service requirements |
| A reader requests an agreed resource | Deliver the resource and explain the expected next step | Respond to a specific follow-up question outside the routine |
| An active proposal raises a scope question | Notify the responsible person and preserve context | Interpret requirements and confirm any commercial commitment |
| A complaint or sensitive situation arrives | Acknowledge appropriately and route promptly | Review the circumstances and provide a considered response |
The table presents process choices, not a claim that every message type should be automated. The organisation should decide what is appropriate for its actual service, audience and responsibilities, then test the resulting behaviour.
Design the handover before writing the sequence
In a hypothetical specialist practice, a website enquiry includes a selected service and a short description of the need. A useful automated acknowledgement confirms receipt, explains that the request will be reviewed and identifies the next step the organisation has actually committed to. It does not diagnose the problem or promise that the team will accept the engagement.
The enquiry then reaches a named owner with its service context intact. If a conversation is booked, an agreed status change prevents a generic reminder from asking the person to submit the same request again. If the enquiry falls outside scope, a person decides on the appropriate response rather than forcing it through an unsuitable nurture path.
This invented example uses automation to reduce routine handling while preserving judgement. The process needs clear states, reliable data and an exception route. If the status connection fails, someone must be able to identify and correct the resulting messages rather than assume the platform will understand the relationship.
Keep purpose, permissions and stopping rules explicit
Write down what starts each message, what must be true before it sends and what stops it. Include booked conversations, active proposals, resolved requests, changed preferences and other states relevant to the service. Test both the intended path and the exceptions using approved records.
Classify the actual content. A message described as a service confirmation can still contain promotion. ACMA notes that a message may be commercial when promotion is only one part of it, so review the purpose and obligations of the complete email rather than rely on its internal label. ACMA’s spam guidance is the appropriate starting reference.
Give recipients a usable route to a person where the message invites a reply. Confirm who monitors that route and how context reaches them. Avoid an apparently personal message from a named sender if nobody is responsible for the conversation it creates.
Review the programme when the team, offer or integration changes. A reliable automation is a maintained process, not simply a sequence switched on once. Our guide to lead nurture and sales stopping rules examines the wider follow-up system; this decision matrix helps identify where human judgement belongs inside it.
Choose one recurring email and document its trigger, exclusions, owner and exception route. Use that map to scope an email automation programme that supports the team’s judgement.