Lesson 5 of 7 · 7 min

Stage tasks and follow-up for each deal stage

Add a task and a follow-up to each deal stage so nothing waits.

Read the lesson

Goal: Create 3 to 5 tasks when a deal reaches a stage. Each task has one person and one due date.

You need: A pipeline (lesson 4). Workflows access. Named team members to own tasks. Growth, or a free slot among Core's 10 active automations.

Why this matters

Deals do not die from a "no". They die from silence. The estimate goes out, the office gets busy, and nobody calls on day 3. By day 10, the customer has signed with someone who did call.

Tasks fix silence. When a deal moves to Proposal, the right person gets a task to call, with a due date. Nobody has to remember. The task list remembers.

But tasks can fail too. Give an estimator 9 tasks per quote, and they tick the boxes without doing the work. The goal is a few tasks that really move the deal.

Fig 1

9 tasks vs 4 tasks per quote

9 tasks per quote
  • 360 tasks a month at 40 quotes
  • Boxes ticked
  • Quotes still stall
4 tasks per quote
  • 160 tasks a month at most
  • Each task changes the decision
  • Real calls get made
Fewer tasks, more real follow-up.

The rule: 3 to 5 tasks per stage

Each stage gets 3 to 5 tasks at most. Each task has:

  • One action, written as a verb. "Call to walk through the estimate."
  • One owner, a named person.
  • One due date.
  • A priority: LOW, MEDIUM or HIGH.

If a task does not change what the customer decides, cut it. "Update the spreadsheet" is not a sales task. The pipeline already holds that.

How it works without a playbook feature

ServiceAgent has no built-in stage playbook. You build the same thing with a workflow:

  1. A trigger: Event Trigger with the event Deal Status Changed or Deal Updated.
  2. A check: a Condition that the deal is now in the stage you want.
  3. The first task: a Create CRM Task step, due today or tomorrow.
  4. Later tasks: a Delay, then a Condition that the deal is still in that stage. Then the next Create CRM Task.

The Condition before each later task matters. Nothing ends a running workflow on its own when a deal moves on. Without the check, a Won deal still gets a "chase this quote" task on day 7.

Fig 2

A stage-task workflow

  1. Event Trigger: Deal Status Changed
  2. Condition: is the stage Proposal?YesCreate CRM Task 1, due todayNoNothing runsEnds here
  3. Delay until the next task
  4. Condition: still in Proposal?YesCreate the next taskNoSkip: the deal moved onEnds here
  5. Repeat the delay and the check for each task
A Condition before each later task stops chase tasks on won deals.

A Condition reads a field typed as text and compares it: Equals, Not equals, Contains, Greater than or Less than. Check the exact field path for the deal's stage in the client's account. Use the builder's Test with sample data to see what the fields contain.

Who owns the task

Create CRM Task has a fixed Owner: a named, active team member. There is no "deal owner" option. So plan the owner:

  • One estimator: that person owns every task.
  • Several estimators: give the tasks to the office lead, who reassigns them. Or build one workflow per estimator, with a condition that checks who the deal belongs to.

On Core, each switched-on workflow counts as 1 of 10 active automations. One workflow per estimator uses slots fast. On Growth and Franchise, workflows are unlimited.

Fig 3

One task, one owner, one date

Create CRM Task

TitleCall to walk through the estimate
OwnerA named, active team member
Due dateToday
PriorityHIGH
There is no deal owner option. The Owner is a fixed, named person.

Build it in ServiceAgent

  1. Write the 3 to 5 tasks for the stage with the owner. Give each a day and a person.
  2. Go to Workflows → Create → Build from scratch.
  3. Set Trigger Type to Event Trigger. Pick Deal Status Changed.
  4. Add step → Condition. Check the deal's stage equals "Proposal". Use the exact stage name.
  5. Add step → Create CRM Task. Fill Title, Description, Owner, due date and Priority.
  6. Add step → Delay. Set the days until the next task.
  7. Add step → Condition. Check the deal is still in Proposal.
  8. Add step → Create CRM Task for the next task. Repeat 6 to 8 for each task.
  9. Click Test. It runs a free simulation with sample data and sends nothing.
  10. Click Publish. Every workflow is a draft until you publish it.
  11. Check it works. Move a test deal to Proposal. Check the first task appears. Move it to Won. Check no later task appears.

Tasks and customer messages are different

Stage tasks are for your team. Messages to the customer are a separate build. The Collect course uses the "Estimate Follow-Up Sales Sequence" template for texts and emails to the customer.

Keep them apart. A task tells a person to call. A text reaches the customer without a person. Both need the same Condition checks, and both must stop when the deal is won or lost. If you build both, line up the days. The estimator should call the day after the text, not the same hour.

Credits and limits

Plan for 1 credit per workflow run. A run with only internal steps, such as tasks, may show no charge. Check real use in Billing → Usage history after the first week.

Runs retry up to 3 times if a step fails. Open History → View run history to see each run and its attempts.

Worked example: Summit Roofing

Summit Roofing has 3 estimators on Growth. They used to get 9 tasks per quote. Quotes still stalled.

You cut the Proposal stage to 4 tasks. The timeline shows each task with its owner and priority. The estimator owns both calls, because the customer knows their voice.

Fig 4Example numbers

Summit Roofing Proposal tasks

  1. Day 0Call to walk through the estimate. Estimator, HIGH
  2. Day 2Answer any financing question. Office lead, MEDIUM
  3. Day 7Second call: any questions on options? Estimator, HIGH
  4. Day 14Owner call if the quote is over $15,000. Owner, MEDIUM
Four tasks, each with one owner and one date.

Volume: Summit sends about 40 new proposals a month.

  • Tasks a month: 40 x 4 = 160, at most.
  • Per estimator, for the 2 estimator tasks: 40 x 2 / 3 = about 27 a month.
  • Planned credits: 40 runs x 1 = 40 credits a month.
Fig 5Example numbers

Who gets Summit's tasks at 40 proposals

  • Estimator calls: 40 × 280
  • Office lead: 40 × 140
  • Owner calls, if over $15,000up to 40

Tasks a month160 at most

The two estimator tasks split across 3 estimators: about 27 each a month.

Some deals move to Won before day 7. The Condition skips their later tasks. So the real task count is lower than 160.

Common mistakes

  • Too many tasks. People tick boxes. Fix: 3 to 5 tasks that move the deal.
  • No Condition before later tasks. Won deals get chase tasks. Fix: check the stage before each task.
  • Tasks with no owner. Nobody does them. Fix: a named Owner on every task.
  • Wrong stage name. The condition never matches. Fix: copy the exact name from Pipeline stages.
  • Forgetting to publish. Fix: Publish, then check the switch in My Workflows.

Do this now

Write a 4-task plan for one stage at a real or practice client. Build the workflow in your practice account. Test it with Test, then with a test deal moved to Won partway through. Record what happened.

Practice the conversation

  1. Operator How many tasks does an estimator get per quote now?
  2. Owner Nine. They hate it.
  3. Operator Do the quotes close faster?
  4. Owner No. They just click done.
  5. Operator Let's keep four tasks that change the customer's mind. Call, financing, second call, your call.
  6. Owner My call?
  7. Operator Only on quotes over $15,000, on day 14.
  8. Owner And if they already signed?
  9. Operator The workflow checks first. No chase task after a win.

Quick check

  1. Estimators get 9 tasks per quote. They tick boxes without doing the work. What do you change?
    • Add more tasks
    • Move the tasks to the Won stage
    • Cut it to 3 to 5 tasks that move the deal
    • Replace them with 9 texts
  2. A deal moves to Won on day 4. Your workflow still creates the day 7 chase task. What is missing?
    • A `Condition` before the day 7 task that checks the stage
    • A longer `Delay`
    • A second trigger
    • A higher priority
  3. A client sends 30 proposals a month. The workflow creates up to 4 tasks per deal. What is the most tasks it can create in a month?
    • 34
    • 120
    • 90
    • 150

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

Learn

Get certified

Community