Enquiry and lead follow-up automation for Australian businesses
Every enquiry sorted, answered by a person and followed up on time.
This page walks through one task from start to finish: what happens after someone sends an enquiry through your website. True North Innovations is a Melbourne-based team that works with businesses across Australia. We build this kind of follow-up for our own CRM work, so it is the closest example to what we do ourselves. The page shows a made-up enquiry moving through the steps, the exceptions, and where a person decides. For the wider picture, see AI automation.
Enquiry sorted · Reply drafted · A person approves · Record and reminder
Melbourne based.
Australia-wide delivery.
Melbourne · Sydney · Brisbane · Perth · Adelaide · Canberra
Enquiry follow-up, before and after
The task as many teams live it today, and the state once it is set up. A person keeps the decisions that matter in both.
Today: enquiries wait in an inbox
Messages arrive by email and form. Someone reads them when they can, decides who should answer and types a reply from scratch. A busy day means a slow answer.
Today: the record is updated by memory
The customer's details are copied into the CRM by hand, if at all, and the reminder to call back lives in someone's head.
After: the system prepares
The enquiry is sorted, the customer is matched or created in the CRM, a draft reply is written from your own wording and a follow-up reminder is set.
After: a person still decides
A named person reads the draft, edits it and sends it. Nothing reaches the customer without that step, and anything unusual is handed to a person.
A worked example: one website enquiry
A made-up example for a small joinery business that receives enquiries through its website form.
Demonstration with dummy data
01 · Trigger
The form is submitted
A visitor fills in the enquiry form. The submission reaches the workflow the moment it is sent.
02 · AI step
The enquiry is sorted and a reply drafted
The AI reads the message, labels the type of job and the urgency, and writes a draft reply using your approved wording.
03 · Check by a person
A person approves
The owner or a sales person sees the enquiry, the label and the draft. They edit, approve or hand it to someone else.
04 · Action
The reply goes and the record is updated
After approval the reply is sent from your own mailbox, and the customer record and the enquiry status are updated in the CRM.
05 · Record
A reminder is set and logged
A follow-up task is created for a set day, and the run is logged with who approved what.
What the person sees before approving
The card that reaches the approver in this made-up example.
Demonstration with dummy data
Enquiry card (made-up example)
- From
- Sam Example (new customer). Form: website enquiry.
- Message
- Asking about a built-in wardrobe for a spare bedroom and when a site visit could happen.
- Sorted as
- New customer · Wardrobe job · Wants a site visit · Normal urgency.
- Draft reply
- Thanks for getting in touch, Sam. We would be glad to look at the wardrobe. Could you tell us the room size and a few times that suit for a visit?
- CRM update
- New contact created, enquiry linked, status set to Replied once sent.
- Reminder
- Follow up with Sam if there is no answer after the agreed number of days.
- Your options
- Approve and send · Edit · Reassign · Mark as spam
Made-up names and numbers. This is not a client result.
What happens when an enquiry is not simple
The exception rules are agreed with you before the build. The system never guesses on a case it was not built for.
What we build and hand over
The trigger
How an enquiry enters the workflow, from your form, your email address or both.
The steps
Sorting, drafting, matching the customer and creating the task, written down so anyone can read them.
The rules
Which enquiry types go to whom, how urgent is defined and what wording the drafts may use.
The exceptions
A written list like the table above, built into the workflow and tested.
The approval
A named person sees the draft and sends it. Nothing reaches a customer without them.
The record and the alert
The CRM is updated after approval, and a person is alerted when any step fails.
Examples to assess. The scope is agreed in writing before work starts.
The tools this task usually touches
Tools differ between businesses. We check features, permissions and licences of each one before we promise a connection.
Your CRM
Where the customer record and the follow-up task live. If you have none yet, see custom CRM development.
Your mailbox
Where the approved reply is sent from, so it comes from your own address.
A step-by-step guide to the connection itself is in connect website enquiries to your CRM.
What you give us to start
- Access to your website form, CRM and mailbox, set up inside your own accounts.
- Five to ten real past enquiries, including a vague one, a spam one and an unhappy one.
- Your usual replies, so the drafts sound like you.
- The rules: which job types go to which person, and what counts as urgent.
- How long to wait before a reminder, and who gets it.
- The one person who approves replies, and a second person for when they are away.
- What must never be said automatically, such as quotes or timeframes.
A clear process: review, design, build, hand over
- 01
Review
We read your past enquiries and watch how they are handled today.
Output: A map of the enquiry path
- 02
Design
We write the sorting rules, the exception list and the approval point.
Output: A written workflow
- 03
Build
We connect your form, CRM and mailbox in your accounts and test with your real enquiries.
Output: A tested workflow and test results
- 04
Hand over
We train the approver and write down who looks after each part.
Output: Training and written responsibilities
What affects the cost of enquiry follow-up automation
Every project is scoped individually.
Which page do you need?
Choose this page when the problem is slow or forgotten answers to new enquiries. If you need a quote prepared from an enquiry, see quote automation. If the problem is the inbox of existing customers, see customer support automation.
Enquiry and lead follow-up automation: good to know
What is lead follow-up automation?
It means that when an enquiry arrives, the system sorts it, prepares a draft reply, updates the customer record and sets a reminder. A person reads the draft and sends it.
Does the reply go to the customer without anyone reading it?
No. A named person approves every reply before it is sent. The system prepares, the person decides.
What happens when the AI is wrong?
A wrong label or a poor draft is caught at the approval step, where the person edits or rejects it. Nothing is sent or changed in the customer record as final until they decide. We also keep a log, so a repeated mistake can be traced and fixed in the rules.
What if the CRM or the mailbox is down?
The reply is held, not sent. The run tries again a set number of times, then stops and tells the named owner. The enquiry stays visible the whole time.
Can it handle an angry customer?
It does not reply to one on its own. The enquiry is marked urgent and passed to a senior person with the message exactly as written.
Can it follow up when the customer does not answer?
It sets a reminder for a person on the day you choose. A person decides whether to send another message.
Do I need a CRM first?
The follow-up needs somewhere to keep the customer record. If you have none, we can talk about a CRM first, or we can start with a simple record in a tool you already own.
Related AI automation pages and services
All our AI automation services, workflows, platforms and guides in one place.
The connection behind this workflow, explained step by step.
When your CRM is HubSpot.
A workflow tool we can use to connect these steps.
A system to hold the records your automations read and update.
Tell us how enquiries are handled today
Describe where enquiries arrive and who answers them. We will explain the clearest next step, in plain English.
Call 03 4158 4444info@truenorthinnovations.com.au
AI automation work is scoped individually.