Lesson 3 of 7 · 10 min

Estimate follow-up workflow: day 1, 3, 7 and 30

Follow up on every quote on day 1, 3, 7 and 30, without anyone remembering to.

Read the lesson

Goal: Build a workflow that follows up every open quote on day 1, 3, 7 and 30. It stops for won deals.

You need: Core or above. Screens: Workflows, Contacts → Deals, Contacts → Reports.

Why this matters

Only 37% of in-home sales close on the first visit (industry data). The rest decide later. Most offices send the quote and then wait. The homeowner gets busy, a competitor calls, and the quote goes quiet.

Follow-up is simple work, but people skip it. The tech is on the next job. The office is answering phones. Nobody owns the open quotes. A workflow owns them. It sends the right message on the right day, every time.

This is the heart of the Estimate Follow-Up Machine Blueprint. Its KPI is estimate close rate. You read that rate in Contacts → Reports → Win Rate.

The scale changes the problem:

  • An owner-operator such as Brightline Electric sends a handful of quotes a week. Owner Dev remembers some and forgets others.
  • A fleet such as Summit Roofing sends dozens a month from several estimators. Each estimator follows up in a different way, or not at all.
  • A multi-location business needs the same sequence at each location, so the results compare fairly.

The idea: four touches, each with one job

Each message answers one worry the homeowner has at that time. No message invents a deadline or a discount the owner did not set.

DayChannelThe worry it answersExample message
1Text"Did I understand the options?""Thanks for having us out, [first name]. Any questions on the options? Reply here."
3Text"Is this company reliable?""Our crews are licensed and insured. Want me to hold a date for you?"
7Email"Am I paying a fair price?"A short email on what each option includes, and the warranty
30Text"Is it too late?""Still thinking about your project? We can still help when you are ready."

Day 0 is the day the quote goes out. The delays between touches are 1 day, 2 days, 4 days and 23 days.

Fig 1

The four touches after a quote

  1. Day 0Quote sent, deal in Proposal
  2. Day 1Delay 1 day → Condition → Send SMS
  3. Day 3Delay 2 days → Condition → Send SMS
  4. Day 7Delay 4 days → Condition → Send Email
  5. Day 30Delay 23 days → Condition → Send SMS → Create CRM Task
Each delay counts from the touch before it. A Condition checks the deal before every message.

Two rules make the workflow safe.

  1. A Condition before every message. ServiceAgent workflows have no stop or goal rule. A running workflow keeps going until its last step. So before each send, a Condition checks the deal. If the deal is no longer in Proposal, that path ends.
  2. New quotes only at launch. Do not load old quotes on day one. Old quotes may have no texting consent, and some customers already hired someone else. The owner decides if older quotes get any message, after a consent check.

There is no "wait for reply" step either. A Delay waits for time only. If the customer replies, the office moves the deal stage. The next Condition then stops the sequence.

Fig 2

What happens at each touch

  1. Delay ends
  2. Is the deal still in Proposal?YesSend the next messageNoPath ends, no messageEnds here
  3. Did the customer reply YES, DONE or "we hired someone"?YesOffice moves the deal to Won or LostEnds hereNoThe next Delay starts
  4. After day 30: a named person callsCreate CRM Task with an Owner and a due date
There is no stop rule, so every message needs its own check. A person moves the deal; the next check ends the path.

Writing the four messages

Good follow-up sounds like the owner, not like a robot. Use these rules for every message.

  • Keep texts under 160 plain characters. One segment costs 2 credits. An emoji cuts the segment to 70 characters, so skip emoji.
  • Use the first name and the business name. "Hi Maria, it's Summit Roofing" tells them who is texting.
  • Invite a reply. End with a question or "Reply here." Replies land in Conversations, where the office sees them.
  • Name a real person for the day 7 email. Sign it with the estimator's name and direct number.
  • Put the facts in the day 7 email. List what each option includes, the warranty and the license number. Homeowners compare quotes side by side. Make yours easy to compare.
  • Make day 30 easy to answer. Give the customer a simple way out. For example: "If you went another way, reply DONE and we will stop."

When a customer replies DONE or "we hired someone", the office moves the deal to Lost. The next Condition then ends the sequence.

Fig 3

Three touches and an easy way out

  1. noteDay 1
  2. Summit Roofing · 10:00 amHi Maria, it's Summit Roofing. Thanks for having us out. Any questions on the options? Reply here.
  3. noteDay 3
  4. Summit Roofing · 10:00 amOur crews are licensed and insured. Want me to hold a date for you?
  5. noteDay 30
  6. Summit Roofing · 10:00 amStill thinking about your roof? If you went another way, reply DONE and we will stop.
  7. Customer · 1:15 pmDONE. We went with another roofer.
  8. noteThe office moves the deal to Lost
Each text names the business and invites a reply. Day 30 makes no feel easy to say.

Fit the sequence to the business

The four touches are a starting point. Change the spacing to match how the trade sells.

  • Roofing and HVAC replacement: keep day 30. Insurance, financing and a second opinion take weeks.
  • Electrical panels and EV chargers: the customer may wait for a car or a permit. Add a task tied to that date, not more texts.
  • Plumbing repairs: most decide within a week. Day 1, 3 and 7 may be enough. End with the task on day 7.
  • Cleaning and lawn quotes: a short sequence of day 1 and day 3 usually works. The decision is small.

A small shop may want the owner to make the day 30 call themselves. A fleet assigns it to the estimator who wrote the quote. Name one person for each task. A task with no owner waits forever.

Build it in ServiceAgent

  1. Start from the template. Open Workflows → Templates. Find "Estimate Follow-Up Sales Sequence". It uses an event trigger and 5 steps. Open it as your starting point. You can also use Build from scratch.
  2. Set the trigger. In the trigger, choose Trigger Type → Event Trigger. Pick Deal Status Changed or Deal Updated, whichever the template uses. Then the workflow starts when a deal moves stages.
  3. Add the first Condition. Check that the deal stage equals Proposal. A Condition reads a field typed as text. Use the exact stage name the account shows. Deals in any other stage end here.
  4. Add the day 1 touch. Add step → Delay of 1 day. Then a Condition: stage equals Proposal. Then Send SMS with the day 1 text.
  5. Add the day 3 touch. Delay of 2 days. Condition again. Send SMS with the day 3 text.
  6. Add the day 7 touch. Delay of 4 days. Condition again. Send Email with the day 7 email.
  7. Add the day 30 touch. Delay of 23 days. Condition again. Send SMS with the day 30 text. Then add Create CRM Task for the estimator. Set Title to "Call about open quote". Pick a named Owner, a due date and Priority MEDIUM.
  8. Use the client's real names. Check the exact stage names in Settings → Contacts & Pipeline → Pipeline stages. If the client renamed Proposal, use the new name in every Condition.
  9. Test with sample data. Click Test in the builder header. This runs a free simulation with sample data and sends nothing. Test two cases: a deal in Proposal, and a deal already in Won. The won deal must get no messages.
  10. Publish. Click Publish. Until you publish, the workflow is a draft and sends nothing. On Core, this workflow counts as 1 of the 10 active automations.
  11. Check real runs. After the first real quote, open the builder History → View run history. Each run shows its steps. A failed step retries up to 3 times.
Fig 4

The follow-up workflow in the builder

Estimate Follow-Up Sales Sequence

Trigger TypeEvent Trigger (the deal event the template uses)
ConditionStage equals Proposal (before every send)
Delay1, 2, 4 and 23 days
Send SMSDay 1, day 3 and day 30 texts
Send EmailDay 7, signed by the estimator
Create CRM TaskCall about open quote, named Owner
Publish
Start from the template, add a Condition before each send, then test and publish.

Texts need consent. Customers who asked for a quote and gave a phone number usually expect texts about that quote. Check the client's consent setup in SMS registration & consent. Marketing messages need more. Keep these messages about the quote only.

Worked example: Summit Roofing

Summit Roofing has 15 people and runs on Growth. These are example inputs for the lesson.

  • Quotes a month: 40
  • Average roof job: $12,000
  • Close rate today: 25%, or 10 jobs a month

Credits per quote, if the deal stays open to day 30:

  • 3 texts × 2 credits = 6 credits (each text is one segment)
  • 1 email × 0.5 credits = 0.5 credits
  • 1 workflow run = 1 credit
  • Total: 7.5 credits a quote

Credits a month: 40 × 7.5 = 300 credits. That is the worst case. Deals that close early skip the later messages. Growth includes 6,000 plan credits a month, so this fits easily. At Safe Pack prices, 300 credits cost about $12.

Fig 5Example numbers

Summit Roofing credits a month, worst case

3 texts × 2 credits6
+1 email × 0.5 credits0.5
+1 workflow run1
=Credits per quote7.5
×Quotes a month40
Credits a month300
Deals that close early skip the later messages. Growth includes 6,000 plan credits a month.

The result to watch: if the close rate rises from 25% to 30%, Summit closes 12 jobs instead of 10. That is 2 more roofs, or 2 × $12,000 = $24,000 a month in this example. Present this as a target to measure, not a promise.

Fig 6Example numbers

Roof jobs a month at two close rates

Close rate 25% today10 jobs
Close rate 30% target12 jobs
From 40 quotes, 5 more points of close rate is 2 more roofs, or $24,000 a month. Measure it in Win Rate.

Track the real result in Contacts → Reports → Win Rate. Write down today's rate before you publish. Compare it after 60 days, because roof quotes close slowly.

Day 30 matters most for roofing. Insurance claims and financing take weeks. A roof quote is often still alive on day 30. The task after day 30 makes a person call, so the deal does not die quietly.

Common mistakes

  • No Condition before each message. A won deal keeps getting "still thinking?" texts. Fix: check the stage before every send.
  • Loading every old quote on day one. Fix: start with new quotes. Ask the owner about older ones after a consent check.
  • A message with a fake deadline. "Prices go up Friday" breaks trust if it is not true. Fix: each message answers one real worry.
  • Stage names that do not match. The Condition checks "Estimate" but the stage is called Proposal. Fix: copy the exact names from Pipeline stages.
  • Publishing without a test. Fix: run Test with an open deal and a won deal first.

Do this now

Build the workflow in your practice account from the template. Write your four messages, each under 160 plain characters for the texts. Run Test twice: once with a Proposal deal and once with a Won deal. Save a screenshot of both results for your client folder.

Practice the conversation

  1. Operator How many quotes did your team send last month?
  2. Owner About 40. We close maybe a quarter.
  3. Operator What happens to the other 30?
  4. Owner We call some. Most we never hear from again.
  5. Operator We will set up four short messages for every quote. Day 1, 3, 7 and 30.
  6. Owner I don't want to look pushy.
  7. Operator Each message answers one question they have. No fake deadlines, no discounts you did not approve.
  8. Owner And if they already said yes?
  9. Operator Before each message, the system checks the deal. If it is won, the messages stop.
  10. Owner What does it cost to run?
  11. Operator About 7.5 credits per quote at most. For 40 quotes, that is about 300 credits a month.

Quick check

  1. You run `Test` on the follow-up workflow. A sample deal already in `Won` still gets the day 3, 7 and 30 messages. What is wrong?
    • The delays between messages are too short
    • The trigger should be a booking event
    • No `Condition` checks the deal before each message
    • The messages need first-name tokens
  2. A client sends 60 quotes a month. Each open quote gets 3 one-segment texts, 1 email and 1 workflow run. What is the most this uses in credits a month?
    • 300
    • 390
    • 420
    • 450
  3. The workflow passed its tests. The office manager wants all 70 open quotes from the last 6 months loaded tomorrow. What do you do?
    • Load all 70 so every quote gets the full sequence
    • Turn it on for new quotes only, and ask the owner about the old ones
    • Send all 70 the day 30 text, since they are old
    • Delete the 70 old quotes for a clean start

ServiceAgent UniversityLearn to run a service business on autopilot. Free courses, Blueprints and certification for Service Operators.

Learn

Get certified

Community