Summary: Match messages to the correct enquiry, assign one owner and stop queued follow-ups when the conversation changes. Test duplicates and replies before expanding automation.
Duplicate lead follow-ups make a tradie business look as though nobody is reading the conversation. A customer replies to the office, then receives an automated “we haven’t heard from you” message. Another staff member calls with the same questions an hour later.
The problem is often ownership and state, not the wording of the message. Before writing another sequence, decide which record represents the enquiry and who is responsible for it.
Separate a person from a job
One customer can have several jobs. Several people can also be involved in one property or project. A phone number match is useful, but it does not settle every relationship.
Keep contact records and enquiry or job records distinct where your system supports that. Link them deliberately rather than merging everything with the same address.
When a possible duplicate arrives, review the service, timing and conversation before combining records. Do not erase a separate job simply because it came from an existing customer.
Give the enquiry one active owner
An owner is the person responsible for the next step, not necessarily the person doing every task. Make that responsibility visible in the system the team actually uses.
| Situation | Ownership action | Automation action |
|---|---|---|
| New enquiry | Assign the intake owner | Start only the relevant process |
| Customer replies | Alert the active owner | Pause messages that assume silence |
| Team member takes over | Record the handover | Preserve conversation context |
| Job is booked | Confirm booking responsibility | Stop pre-booking follow-ups |
| Customer declines | Close or record the agreed outcome | Stop the sequence |
| Duplicate detected | Review and link or merge appropriately | Prevent a second parallel sequence |
Use a small set of states the team understands. A long list of nearly identical statuses can be harder to maintain than a simple process.
Define stop rules before send rules
For each follow-up, write what must be true immediately before sending. Has the customer replied? Is the job already booked? Has somebody agreed on a later contact date? Has the person asked to stop?
Check the current state at send time where the platform supports it, not only when the sequence begins. A message queued yesterday may be inappropriate after a conversation this morning.
Make the opt-out route work across the relevant marketing systems. ACMA's commercial-messaging guidance should inform promotional follow-up processes; a separate tool should not restart messages somebody has declined.
Use a handover note with a next action
A useful note might say: “Customer supplied photos; awaiting estimator review; Alex to call after reviewing; automated reminders paused.”
That is more helpful than “spoke to customer”. Include only the information needed for the next step, and keep sensitive details in appropriate fields rather than broad team notifications.
If the owner is away, name the replacement. A shared inbox without a named responsibility can hide an enquiry just as easily as a private inbox.
Test the cases that create embarrassment
Create a fictional test contact and submit twice. Reply from the customer side, book the job, decline it and request a later conversation. Check what messages remain queued after each change.
Also test manual staff messages during an automated sequence. The system may not automatically interpret a phone call or a conversation outside its own inbox.
Write down which actions require a staff member to pause or update the record. Automation limitations should become clear operating steps rather than surprises discovered by customers.
Review repeated contacts as a process signal
Ask customers and staff where repetition occurs. If everyone keeps asking for the suburb again, the information may not be visible at handover. If two teams call, assignment rules may overlap.
Fix the underlying route before adding more conditions to individual messages. A clean ownership model makes later automation simpler and gives customers the sense that the business remembers what they have already said.
For help putting clear enquiry handling into a repeatable process, see Tradie Local’s automated lead follow-up.
Sources & further reading
Frequently asked questions
Should I merge all records with the same phone number?
No. Check whether they represent separate jobs, shared contacts or genuine duplicates before merging.
What should stop an automated follow-up?
Relevant changes include a reply, booking, decline, agreed later contact or opt-out. Define the rules for each workflow.
Can two staff members work on one enquiry?
Yes, but one person should own the next step and the handover should be visible. Shared work still needs clear responsibility.
Why did a follow-up send after a phone call?
The system may not know the call changed the enquiry state. Staff may need to update or pause the workflow explicitly.
How do I test duplicate prevention?
Use a test contact through repeated submissions, replies, bookings and declines. Inspect the queued messages after every change.
