AI Lead Follow-Up Approval Rules: What Can Run Automatically and What Needs a Human?

TL;DR: Sort follow-up actions by what they commit your agency to. Acknowledging an inquiry, asking one qualifying question, tagging a lead and assigning it internally commit you to nothing, so they can run without a person. Anything that states a price, confirms a property is available, proposes a firm viewing time, offers a discount or touches contract terms stays with a named person. Write the rules as your own operating policy first. Then take them to your provider and confirm which lines the software enforces and which you enforce yourself.

Approve the facts before you approve the actions

Two decisions get confused before launch. Which facts the assistant may state is the job of your agency knowledge base. Which actions the workflow may take on your behalf is this article. A fact can be accurate and the action still wrong, because sending it commits you to something.

This article assumes you have already mapped the workflow from inquiry to assigned agent, and that you are running, or about to run, TechTribe's AI lead nurturing and automated follow-up. Check the current packages for what your plan includes.

Nothing below assumes your software enforces any of it. Every row is your own operating policy. Whether a rule is held by the system or by a person is a configuration question to answer with your provider before go-live, which is why the matrix ends with a question rather than a claim.

The test that decides the tier

Ask one question of every action: does it commit the agency to a price, a property, a time or a person?

• A price: a figure, a range, a movement, a discount or a fee.
• A property: that a specific unit exists, is still available, or is as described.
• A time: a viewing slot, a callback or a deadline.
• A person: a named owner, landlord, agent or third party.

If none of the four apply, the action can run automatically. If one applies but a person can correct it with a phone call and an apology, it needs approval before it sends. If it is contractual, legal, or cannot be checked against an approved source, it stays human only. This is our method, not an industry standard.

What can run automatically

These six actions commit you to nothing.

• Acknowledge that the inquiry arrived.
• Ask one qualifying question about budget, timeline or area.
• Tag and score the lead internally.
• Assign the lead to an agent internally.
• Notify the assigned agent.
• Repeat a fact already approved for automatic use in your knowledge base.

Internal assignment sits here because routing changes who works the lead, not what you have promised. A bad route still costs you, but your routing rules manage that, not this matrix.

What needs approval before it sends

Hold these for a named person.

• Any reply that states a price, a price range or a price movement.
• Any reply confirming a specific property is still available.
• Any reply proposing a firm viewing date or time.
• Any offer of a discount, fee waiver or commission variation.
• Any reply to a complaint or a dissatisfied lead.
• Any message that re-opens contact after a lead has gone quiet.
• Any reply that refers to a named owner or landlord.

What stays human only

Do not automate these at all.

• Contractual terms, offers and counter-offers.
• Negotiation of any kind.
• Ownership, title, mandate or legal status questions.
• Anything the assistant cannot verify against an approved source.
• Anything involving a dispute, a regulator or a lawyer.

When the assistant cannot verify something, it should hand over rather than guess. Those handover rules are set out in what to do when the assistant cannot answer a property inquiry.

The matrix

Add your own actions, replace the role labels with real names from your agency, and fill in column four during implementation.

Stop conditions, and who can pause

These are conditions your people act on, not settings in a system. Pause and hand to a person when:

• Two approved sources contradict each other.
• The lead asks to stop being contacted or withdraws consent.
• A complaint, a legal word or a regulator is mentioned.
• The lead refers to a property that is not in your approved inventory.
• The same reply goes out repeatedly, or volume spikes without explanation.

Name the two people who may pause it, and write down how they do it.

What to record when someone approves an action

Record five fields for every approval decision: which action was proposed, which tier it fell into, who approved or refused it, when, and what the approver changed before it went out. The last field matters most: a pattern of edits shows which automatic wording is wrong. Keep this separate from the run log you keep once the workflow is live, which is covered in monitoring a business AI workflow after launch.

Consent, channels and the legal floor

Automating an action does not move responsibility off your agency. Commentary from DLA Piper Africa and Manokore Attorneys notes that data controllers are responsible for the acts of their agents, and that a decision based solely on automated processing needs the data subject's consent or another legal basis. That reading sits under the Cyber and Data Protection Act, Chapter 12:07. Take your own advice on how it applies to your leads.

Veritas Zimbabwe reports that POTRAZ compliance inspections begin on 1 September 2026, starting with nine priority sectors, and real estate is not one of them. The licensing duty for data controllers is separate from that inspection order, so ask your lawyer where you stand. Then check the channel. WhatsApp's own Business Messaging Policy states you may only contact people on WhatsApp if they have given you their mobile number and have opted in to receive your messages.

Who owns the matrix, and what triggers a review

The principal owns the matrix. The sales manager operates it day to day, and the listings manager owns the rows that depend on listing accuracy. We set out the same approver discipline for listing content.

Do not review it on a calendar. Review it when a trigger fires: a lead complains about a message they did not expect, an approved fact turns out to be wrong, you add a channel or a portal connection, you change fees or commission, or your provider changes what the workflow does. Simon covers the wider question of who sets an AI agent's default permissions across a business.

Test the rules against old inquiries first

Take twenty real inquiries from recent months, including the awkward ones. Sort each against the matrix on paper and write down the tier. Then ask your provider how you can put the same inquiries through the workflow before a live lead sees a reply, and compare. Every disagreement is either an unclear rule or one the workflow will not hold on its own. Fix the rule, or keep the action with a person until you have an answer.

Your next step

Fill in the first three columns this week. Bring column four to a demo and get the enforcement questions answered before anyone configures anything.

Common questions

Can the assistant send prices if the price comes straight from our listing data?

Only if a person has approved that listing data as accurate for automatic use, and a price change should still go to a named approver. A wrong price is a commercial exposure.

Who approves after hours?

Name a second approver per shift before launch. If nobody is available, the message waits and the lead gets an acknowledgement that a person will reply.

Does automated lead scoring need consent?

Take advice. Law firm commentary on the Cyber and Data Protection Act, Chapter 12:07, says a decision based solely on automated processing needs consent or another legal basis. Whether your scoring counts as one is a question for your lawyer.

How long should we keep approval records?

We do not publish a period, because none is established for lead communications. Keep them as long as your own record policy requires, and ask your lawyer to set it.