AI

Automations From One Sentence: Workflows Every Home Service Team Should Run

When, do, who, until. Six ready workflow sentences for roofing, solar and home service teams, the rules for every text step and a test sheet to run first.

GameForce Team

Automations From One Sentence: Workflows Every Home Service Team Should Run title card

A good automation fits in one sentence with four parts: when something happens, do the next thing, who owns the reply, and until what changes. If a new office hire could read your sentence and do the work by hand, it is ready to automate. If they could not, adding boxes and arrows in a builder will not fix it.

Below are six workflows a roofing, solar or home service team can run from the first week, each written as the sentence you would type, with the stop rule that keeps it from texting the wrong person at the wrong time.

Turn a goal into a sentence

"Follow up faster" is a goal, not a workflow. Here is the same goal as a sentence:

When a web form lead comes in, text them our booking link within one minute, give the on duty setter a call task due in five minutes, and stop as soon as they reply, book or text STOP.

Check each part:

  • When: one event, named exactly. "A web form lead comes in" is not the same as "a new lead," because an imported list also creates new leads, and you do not want to text a whole import.
  • Do: one action or a short chain. A text, then a task.
  • Who: the person who answers when the homeowner writes back. Name a backup for days off.
  • Until: the change that ends it. A reply, a booking, a cancellation or a STOP.

If your sentence needs the word "maybe," split it into two workflows.

The rules for every text step

This is general information, not legal advice. Laws change and differ by state. Talk to a lawyer about your own calls and texts.

Before any workflow sends a text, check four things against the FCC rules in 47 CFR 64.1200:

  1. Consent that fits the message. Under paragraphs (a)(1) and (a)(2), a text sent with an autodialer to a cell phone needs the person's prior express consent, and a marketing text needs their prior express written consent. Keep the form, the consent wording the person saw and the date. Ask your lawyer whether your texting tool counts as an autodialer.
  2. Calling hours. Paragraph (c)(1) bars telephone solicitations before 8 AM or after 9 PM at the called person's location, and paragraph (e) applies it to marketing texts sent to cell phones. Some states set tighter hours; the calling hours guide covers them.
  3. STOP ends it. Under paragraph (a)(10), a reply of "stop," "quit," "end," "revoke," "opt out," "cancel" or "unsubscribe" revokes consent, and so does any reply a reasonable person would read as a request to stop. The request must be honored within a reasonable time, no more than ten business days. Build every workflow to end the moment a stop arrives, in every sequence the lead is in, not only the one that sent the text.
  4. Say who you are. Start each text with the rep's name and the company name so the reader knows who is writing.

The opt out guide shows how to log a stop that comes in by phone, by text or at the door.

Workflow one: the new web lead

When a web form lead comes in during calling hours, text them our booking link within one minute, give the on duty setter a call task due in five minutes, and stop when they reply, book or text STOP.

Sample text:

Hi [first name], it's [rep] with [Company]. Thanks for asking about a [roof inspection]. Pick a time here: [link], or reply with a good time to call. Reply STOP to opt out.

The backup: if the setter has not called in 15 minutes, the task moves to the sales manager. Leads that arrive after hours get the call task for the first hour of the morning, and the text waits until calling hours open. The speed to lead guide gives the minute by minute routine for the call itself.

Workflow two: confirm and remind

When an appointment is booked, text a confirmation with the day, the time and the rep's name, send one reminder the evening before, and stop if the appointment is canceled or moved.

Sample confirmation:

Hi [first name], it's [setter] with [Company]. You're set for [Thursday] at [6 PM] with [closer], who will go over [your roof options]. Need to change it? Reply here. Reply STOP to opt out.

The stop rule matters most here. When the time moves, the old reminder must die and the new time starts a fresh confirmation. Otherwise the homeowner gets two reminders for two different times. The no show guide covers the read back on the booking call and the day of text.

Workflow three: the missed appointment

When an appointment is marked no show, give the setter a task to call within one hour, send one text offering two new times, and stop after any reply or a second no show.

Sample text:

Hi [first name], it's [setter] with [Company]. Sorry we missed you today. Would [Tuesday at 5] or [Wednesday at 6] work better? Reply STOP to opt out.

One text, not a chase. A homeowner who does not answer the call or the text goes to a person for review, not into a longer sequence.

Workflow four: the hot lead nobody touched

When a lead marked hot has no call, text or note for 24 hours, alert the sales manager with the lead's name and the last note, and stop as soon as anyone logs contact.

This one sends nothing to the homeowner. It catches the lead that fell between two reps over a weekend. Put the last note in the alert so the manager can act without opening five screens.

Workflow five: signed deal to production

When a deal is marked signed, create the job, give the production manager a task to call the homeowner within one business day, and attach the signed agreement and the rep's notes.

The homeowner's first call after the sale should come from the person who runs the job, with the scope already in front of them. A date the homeowner asked for stays a request until production confirms it. The signed to paid guide maps every stage from here to the money.

Workflow six: the finished insurance job

When a job paid through an insurance claim is marked complete, give the office manager a task to send the final invoice and the completion photos to the homeowner that day, and remind them weekly until the final payment is recorded.

On many replacement cost claims the insurer holds back part of the payment until it receives the bill for the finished job. A same day invoice keeps that money from waiting on paperwork. The insurance claims guide lays out the full claim timeline.

Test it before it runs

Run each workflow with a teammate's phone number as the lead before it touches a real homeowner. Five tests catch most mistakes:

  • Normal: the lead books. Did everything after the booking stop?
  • Duplicate: the same person submits the form twice. Did they get one text or two?
  • STOP: reply STOP to the first text. Did every other workflow for that lead stop too?
  • After hours: submit a form at 10 PM. Did the text wait for morning?
  • Owner out: mark the setter away. Did the backup get the task?

Read every text the workflow sends in its first two weeks. Fix the wording before you add the next workflow.

Automations in GameForce

Automations: describe one in a sentence, or build the steps yourself.

By default, calls and automated texts keep to 8 AM to 9 PM in each lead's own time zone, and stricter state hours narrow that window.

Start with the sentences in this guide, swap in your own trade and timing, and run the five tests. See it on our home page.

FAQ

What makes a good one sentence automation?

One trigger, one short chain of actions, a named owner and a stop rule. "When a web form lead comes in, text them the booking link, give the setter a call task, and stop when they reply" is a good one. If you need "unless" twice, make two workflows.

Should every new lead get an automatic text?

No. Text the leads who agreed to texts from you, inside calling hours. A web form with a clear texting consent line is the usual case. An imported list or an old file is not the same thing; give a person a call task instead and check the consent records first.

What should stop an automation?

A reply, a booking, a canceled or moved appointment, any opt out word or request, and a manager's pause. Build the stop into the sentence before you build the steps.

How many automations should a team start with?

Two: the new web lead and the confirmation. Run them for two weeks, read what went out, then add the missed appointment and the hot lead alert.

Start with one sentence

Book a demo and bring the one sentence you want running first, or start a free trial.

Put your next step into practice.

See what a clearer sales day can look like.

Read next