NuVentrec

Guides / Automations that draft

Guide · Lead follow-up

Automations that draft instead of send: follow-up without the risk

Automation is supposed to save time. In real estate follow-up it also creates risk: a text that goes out at the wrong hour, to someone who already said stop, or to a seller who just told your caller they signed with someone else. There is a middle path. Let the system decide what should happen and write the message, and let a person press send. This guide explains how to set that up and when full automatic sending is reasonable.

By the NuVentrec team · Published October 14, 2026 · Sources last checked October 14, 2026

General information, not legal advice. Texting and email rules depend on your situation. Check with a lawyer before you switch on automatic sending.

The short answer

  • Automate the decision, not the send. A rule can notice "no reply in 7 days" and prepare the follow-up. A person reads it and sends it.
  • Check opt-outs before anything is drafted, and again when it is sent. A draft to someone who said stop should never exist.
  • Every rule starts switched off, with a log of what it did, so you can see it working before you trust it.
  • Automatic sending is a per-rule decision made by the owner, with consent on file and sending hours enforced.
  • Remember you are responsible for every message, including the ones your software wrote.

Why "draft first" is worth the extra click

A follow-up message is only as good as the system's picture of the lead. That picture is often wrong in ways a person would catch at a glance: the seller called your cell instead of the office line, the deal is already under contract, the last message was angry. A fully automatic text goes out anyway.

The rules behind messages are also strict. The FCC's rules require that a request to revoke consent "made in any reasonable manner must be honored within a reasonable time not to exceed ten business days" (47 CFR 64.1200(a)(10)). Telephone solicitations to homes are limited to between 8 a.m. and 9 p.m., local time at the called person's location (64.1200(c)(1)). For email, the FTC's CAN-SPAM guide says you "must honor a recipient's opt-out request within 10 business days", and that each separate email in violation can bring a penalty of up to $53,088.

A draft that a person reviews is a second chance to catch the message that should not go. It costs a few seconds per message and keeps the speed of automation where it matters: noticing that something needs doing.

What to automate, and what to leave to a person

Good candidates for fully automatic actions are the ones that only touch your own records:

  • Move a deal to a stage when a form comes in.
  • Add or remove a tag.
  • Assign an owner and create a task with a due date.
  • Notify a team member that a lead replied.
  • Stop a follow-up sequence when the person replies or is marked do-not-contact.

Anything that reaches a person outside your team, such as a text or an email, starts as a draft. The rule writes it, fills in the name and the property, and puts it on someone's task list. The person reads it, edits it if needed, and sends it.

Building a rule that drafts

  1. Choose the trigger. A new lead, a stage change, a form, an inbound text or call, a missed call, a tag, an appointment booked, or "no reply in X days".
  2. Add conditions. Only this pipeline, only this stage, only this tag. A rule that fires for every lead in the company is rarely what you mean.
  3. Add the steps. For example: move to "Follow up", create a task for the owner, and draft a text that says what you would say yourself.
  4. Check the opt-out list inside the rule. If the person is on it, the rule should skip the message step and say so in its log, not quietly draft it.
  5. Leave it off and read the log. Turn it on for a day, read what it did, then decide whether to keep it.

Our guide to a follow-up schedule suggests the timing, and the guide on text consent covers what "consent on file" should mean before any automatic text.

When automatic sending is reasonable

Some messages are low risk and time sensitive: a confirmation that an appointment is booked, or a reply to someone who just filled in your form and asked to be texted. For those, a business may decide to let a rule send on its own. If you do:

  • Make it an owner's decision per rule, not a setting anyone can flip.
  • Require consent on file for that person and channel.
  • Enforce sending hours in the person's local time, and turn an out-of-hours send back into a draft.
  • Keep the log: who, when, what was sent, and which rule sent it.

The FTC's guide makes a point that applies here: you "can't contract away your legal responsibility" by hiring someone else to send for you. Handing the job to software does not move the responsibility either.

Mistakes that cause trouble

  • Rules that trigger rules. One rule moves a deal, which triggers a second rule, which tags it, which triggers a third. Keep rule actions from triggering other rules, or you will not know why something happened.
  • No reply detection. A sequence that keeps going after the person answered is the fastest way to an angry reply. Stop on any reply, call or form.
  • Copying an old system's automations blindly. When you move CRMs, rebuild each automation on purpose, read what it does, and leave it off until you have checked it.
  • No owner for the drafts. A draft nobody is assigned to never gets sent. Every draft lands on a named person's task list.

How this fits in NuVentrec today

NuVentrec's follow-up sequences already work this way: email steps never send on their own; they create a "Send email" task with the message ready, and a sequence pauses when the person calls, texts, emails or fills in a form. Anyone on the opt-out list is stopped for good. The Automations page adds rules on the same principles: every rule starts off until someone switches it on, each has a run log, text and email steps are drafts, rules never set off other rules, and automatic texting happens only where the business owner allows it for that rule, with consent on file and inside sending hours. See what is live or request access.

Questions people ask

Doesn't a person sending each message defeat the point of automation?

No. The slow part of follow-up is remembering who needs a message and writing it. The rule does both. Pressing send after a glance takes seconds.

What if nobody sends the drafts?

Then the drafts show up as overdue tasks for a named person, which is visible in a way a silent automation failure is not. Review overdue drafts in your daily routine.

Can a draft still go to someone who opted out later?

It should not. Check the opt-out list again at the moment of sending, not only when the draft was made. Our opt-out list guide explains why the list must be checked everywhere.

Are emails safer to automate than texts?

The rules are different but both are strict, and an unwanted email still costs you the lead. Treating both as drafts is the simple, consistent choice.

Sources

  1. 47 CFR 64.1200, "Delivery restrictions", paragraphs (a)(10) and (c)(1), Legal Information Institute
  2. Federal Trade Commission, "CAN-SPAM Act: A Compliance Guide for Business"
  3. "The Kanban Guide", version 2025.5 (managing and limiting work in progress, which drafts on a person's task list make visible)

Let the system notice and write the follow-up. Let a person send it.

Try the interactive demoBook a walkthrough
Call now