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.
| Day | Channel | The worry it answers | Example message |
|---|---|---|---|
| 1 | Text | "Did I understand the options?" | "Thanks for having us out, [first name]. Any questions on the options? Reply here." |
| 3 | Text | "Is this company reliable?" | "Our crews are licensed and insured. Want me to hold a date for you?" |
| 7 | "Am I paying a fair price?" | A short email on what each option includes, and the warranty | |
| 30 | Text | "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.
The four touches after a quote
- Day 0Quote sent, deal in Proposal
- Day 1Delay 1 day → Condition → Send SMS
- Day 3Delay 2 days → Condition → Send SMS
- Day 7Delay 4 days → Condition → Send Email
- Day 30Delay 23 days → Condition → Send SMS → Create CRM Task
Two rules make the workflow safe.
- A
Conditionbefore every message. ServiceAgent workflows have no stop or goal rule. A running workflow keeps going until its last step. So before each send, aConditionchecks the deal. If the deal is no longer inProposal, that path ends. - 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.
What happens at each touch
- Delay ends
- Is the deal still in Proposal?YesSend the next messageNoPath ends, no messageEnds here
- Did the customer reply YES, DONE or "we hired someone"?YesOffice moves the deal to Won or LostEnds hereNoThe next Delay starts
- After day 30: a named person callsCreate CRM Task with an Owner and a due date
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.
Three touches and an easy way out
- noteDay 1
- Summit Roofing · 10:00 amHi Maria, it's Summit Roofing. Thanks for having us out. Any questions on the options? Reply here.
- noteDay 3
- Summit Roofing · 10:00 amOur crews are licensed and insured. Want me to hold a date for you?
- noteDay 30
- Summit Roofing · 10:00 amStill thinking about your roof? If you went another way, reply DONE and we will stop.
- Customer · 1:15 pmDONE. We went with another roofer.
- noteThe office moves the deal to Lost
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
- 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 useBuild from scratch. - Set the trigger. In the trigger, choose
Trigger Type→Event Trigger. PickDeal Status ChangedorDeal Updated, whichever the template uses. Then the workflow starts when a deal moves stages. - Add the first
Condition. Check that the deal stage equalsProposal. AConditionreads a field typed as text. Use the exact stage name the account shows. Deals in any other stage end here. - Add the day 1 touch.
Add step→Delayof 1 day. Then aCondition: stage equalsProposal. ThenSend SMSwith the day 1 text. - Add the day 3 touch.
Delayof 2 days.Conditionagain.Send SMSwith the day 3 text. - Add the day 7 touch.
Delayof 4 days.Conditionagain.Send Emailwith the day 7 email. - Add the day 30 touch.
Delayof 23 days.Conditionagain.Send SMSwith the day 30 text. Then addCreate CRM Taskfor the estimator. SetTitleto "Call about open quote". Pick a namedOwner, a due date andPriorityMEDIUM. - Use the client's real names. Check the exact stage names in
Settings→Contacts & Pipeline→Pipeline stages. If the client renamedProposal, use the new name in everyCondition. - Test with sample data. Click
Testin the builder header. This runs a free simulation with sample data and sends nothing. Test two cases: a deal inProposal, and a deal already inWon. The won deal must get no messages. - 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. - 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.
The follow-up workflow in the builder
Estimate Follow-Up Sales Sequence
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.
Summit Roofing credits a month, worst case
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.
Roof jobs a month at two close rates
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
Conditionbefore 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
Conditionchecks "Estimate" but the stage is calledProposal. Fix: copy the exact names fromPipeline stages. - Publishing without a test. Fix: run
Testwith 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
- Operator How many quotes did your team send last month?
- Owner About 40. We close maybe a quarter.
- Operator What happens to the other 30?
- Owner We call some. Most we never hear from again.
- Operator We will set up four short messages for every quote. Day 1, 3, 7 and 30.
- Owner I don't want to look pushy.
- Operator Each message answers one question they have. No fake deadlines, no discounts you did not approve.
- Owner And if they already said yes?
- Operator Before each message, the system checks the deal. If it is won, the messages stop.
- Owner What does it cost to run?
- Operator About 7.5 credits per quote at most. For 40 quotes, that is about 300 credits a month.
Quick check
- 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
- 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
- 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.