Every quote chased. Every call answered. You approve every message.

Same infrastructure underneath — a trigger, a draft, an approval gate, sending, a reply handler. Only what starts it changes. Grouped by what it does for the business.

Four statuses, and each one means exactly what it says. Live: sending real messages today — only Outbound. Built · not live yet: built and tested end to end, every rule enforced, but writing to a local outbox instead of delivering. On request: not built yet — built for the first client who needs it, on the same engine and the same gate. By enquiry: an engagement scoped with you. Nothing on this page claims to be running until it is.

One approval gate, shared by every system.

There is a single implementation of “nothing sends without a human”. Each system registers its own rules; the gate applies them identically and knows nothing about which system produced a draft. Two copies of that logic would drift, and the promise would quietly stop being true.

• The gateA draft that fails its check cannot be approved at all — the button refuses rather than asking twice. Editing an approved draft revokes the approval and re-checks from scratch.
• At sendEvery rule runs again at the moment of sending, not only when drafted. An opt-out or a signed quote between approval and send stops the message.
• Opt-outOne list across every system and both channels. Stop hearing from one, stop hearing from all — a customer doesn't think in terms of your subsystems.
• The logEvery stage change is recorded with a timestamp, including the ones that sent nothing. A call that produced no text is a decision with a reason, not a gap.

Verified by 158 automated checks: 44 unit tests, 38 end-to-end steps through the real API, 49 adversarial probes that try to bypass the gate, and 27 checks on this site. The adversarial pass is the one that matters — it found three defects, including compliance rules that could be evaded by spacing out letters.

You can switch the gate off. The rules get stricter when you do.

Reading every draft stops being realistic at volume, so auto mode exists. It is not the same product with the safety removed — when nobody is reading, less gets through, not more.

• StricterOnly a clean pass sends. In manual mode you can read a flagged draft and send it anyway; auto mode cannot. Anything flagged waits for a person.
• Checked firstAddresses are verified before a draft is written. Role addresses, disposable domains and obvious typos never reach the drafting step at all.
• Fails closedTwo bounces in a single sending run switches auto mode off for that system and puts everything back in front of you, with the reason on the record.
• AuditableEvery message records whether a human or the machine approved it. You can always answer "who sent this".

Off unless you turn it on, one system at a time, and reversible in a click. The gate is the default because it is the part worth paying for — auto mode is for when you have read enough of them to know what the system writes.

Built and run for ClipZone since June 2026.

Every email identifies the sender and carries a functional unsubscribe, and opt-outs are actioned on receipt — the requirements of the Spam Act 2003 (Cth).

Live within a week. You see everything first.

Most of the setup happens on day one. The rest is you checking our work: nothing reaches a customer until you've seen exactly what it says and who it goes to.

1. Call, scope and kickoff Day 1

   One sitting. We work out where jobs are slipping through, agree a fixed price in writing, and collect your sign-off, a few messages you've sent, your customer list and anyone who's asked not to be contacted.

2. Your accounts connected Day 1

   Messages come from your own email and number. We start your email authentication the same day so nothing lands in spam, and clear out dead addresses before anything is written. For Outbound we also set up a separate sending domain, so your main business email is never at risk.

3. Draft wording in your inbox Day 1

   Every message template, written in your voice, sent to you that afternoon.

4. You approve the wording Day 2

   Read it with a clear head, change anything. Nothing sends on wording you haven't signed off.

5. A short dry run Days 2–4

   It runs on your real jobs and quotes but sends nothing. You see exactly what would have gone out, and to whom, before anything does.

6. Live, with you approving every message Day 5

   Running from the end of the first week. For the first month every message still waits for your OK — live, just with you saying yes to each one. Outbound starts at a handful of emails a day and builds up while the inbox warms up.

7. A review at four weeks Week 4

   Replies, bookings, money chased. Then you decide whether any system should run on its own. Your decision, never the default.

8. Ongoing Weekly

   One short summary a week with the numbers that matter, and a monthly check-in.