A8gent
Build guide - Housecall Pro estimates

Housecall Pro estimate follow-up: past the third touch

Housecall Pro's Pipeline resends an estimate three times, then declines it. Here is how to tune that, and the MAX-plan build that adds touches four and five.

A8gent

What you get from this guide

  • How Pipeline's estimate automations work: three follow-ups, then decline
  • The detail most people miss: each follow-up resends the estimate, by the channel it was first sent on
  • What Smart Recommendations controls, and what it locks
  • The MAX plan gate on the API, from Housecall Pro's developer docs
  • A build that starts where Pipeline stops, without doubling up

What Housecall Pro actually ships

Housecall Pro handles estimate follow-up inside Pipeline. Its help article Getting Started with Pipeline lists the estimate automations in order.

Pipeline estimate automations, as documented
When an estimate isHousecall Pro does this
Sent for X daysResends the estimate and updates the status to First Follow-Up
First Follow-Up for X daysResends the estimate and updates the status to Second Follow-Up
Second Follow-Up for X daysResends the estimate and updates the status to Third Follow-Up
Third Follow-Up for X daysDeclines the estimate
Accepted or Rejected for X daysArchives the estimate

You set each X. The article also describes Smart Recommendations, a toggle at the top right of the estimate board's automation settings. Housecall Pro says it automates three estimate follow-ups and sets the timing for you, using factors such as industry and seasonality. With it on, you can edit what the messages say, but you cannot change the timing or disable a follow-up.

The message templates themselves appear in the email and SMS communications article, which lists Estimate Status messages for Sent, First Follow-Up and Second Follow-Up as available by email and SMS and customisable.

Check your own account

This was verified against Housecall Pro's help centre in November 2026. The help articles we read do not state which plans include Pipeline, so confirm it in your own account. If your Pipeline shows more stages than described here, use them.

A follow-up is a resend

Read the table again and notice the verb. Each automation resends the estimate. The customer receives the estimate a second, third and fourth time, with the message you have set for that stage.

Two consequences follow. First, if all three messages say the same thing, the customer gets the same email four times, which reads as a system and not a person. Second, the channel is fixed at the start. The Pipeline FAQ says the follow-up goes by email or text depending on how the estimate was originally delivered, and if it was sent both ways, by whichever was used last. An estimate emailed to a homeowner who never opens email will be followed up by email three more times.

Neither is a flaw. It is a design that suits most estimates. But it tells you exactly where to put effort: the wording of each stage, and the channel you pick when sending.

Tuning Pipeline first

Do these before considering any build. They are free and take an afternoon.

  • Decide between Smart Recommendations and your own timings. If your jobs have a known decision cycle, set the days yourself.
  • Write three different messages. First: did it arrive, any questions. Second: something useful about availability or scope. Third: a direct question and when the price expires.
  • Send estimates by the channel the customer actually reads, since the follow-ups inherit it.
  • Use decimals for short delays. The FAQ gives 0.25 days for six hours.
  • Decide whether to tick the option to send to customers with notifications turned off. It applies to the whole rule, not to individual customers.
  • Resend older estimates by hand. A new rule only applies to estimates inside its timeframe.
  • Set the decline rule late enough that you are not declining estimates customers are still considering.
A starting cadence for manual timings
StageDays in previous stageMessage focus
First Follow-Up2Arrived safely? Questions welcome
Second Follow-Up4Availability and one scope clarification
Third Follow-Up7Direct question, price expiry date
Decline30Leave room for an external tail, or for a late yes

These timings are our suggestion, not Housecall Pro's. Adjust them to how long your customers take to decide.

What Pipeline does not describe

Pipeline's follow-ups against an external tail
NeedPipelineExternal tail on the API
Three follow-ups with editable contentYesNot needed
A fourth and fifth touch for long decisionsStages end at Third Follow-UpYes
A different channel from the original sendFollows the original channelYes, with consent
A call task for large estimatesNot describedYes
Stop when the customer repliesNot described in the articles we readYes, on your own inbound channel
A message that is not a resendEach follow-up resends the estimateYes

On the reply row: the help articles describe the stages and timings, not what happens to a pending follow-up when a customer replies without approving. Test it in your own account with a real estimate before assuming either behaviour.

An illustrative sum, with invented figures for the arithmetic only: 50 estimates a month, 20 still open after the third follow-up, and an average estimate of 2,000. If two extra touches and a few phone calls win 1 of those 20, that is 2,000 a month. If nearly all your estimates are decided within a week, the tail is not worth building.

The API and the plan gate

Housecall Pro's developer documentation is clear about access: any Housecall Pro user on the MAX plan can create API keys. It lists what an integration can do, including receiving events when estimates are created, scheduled, completed and won, and when jobs are created, scheduled, completed and paid.

Rate limits are described without a number. Once the limit is exceeded, requests receive a 429, with a RateLimit-Reset header giving the reset time in epoch format. Build a retry that reads that header rather than guessing.

If you are not on MAX, there is no API route, and this guide ends at the tuning section for you. That is still most of the value.

The build alongside Pipeline

Pipeline keeps the first three touches. The workflow adds a tail. Written for n8n with a Webhook node and the HTTP Request node.

1

Create the API key and webhook

On MAX, generate an API key and set up the webhook to your automation platform. Subscribe to the estimate events. The Housecall Pro to Google Sheets guide covers the webhook setup and failure handling in detail.

2

Write a record when an estimate goes out

On the estimate event, fetch the estimate and store its id, customer contact, total, the date sent, status = open and step = 0.

3

Schedule the tail after Pipeline finishes

Set next_touch to a few days after Pipeline's third follow-up is due. With the starting cadence above, the third goes out on day 13, so the tail starts around day 18. Move Pipeline's decline rule beyond your last touch.

4

Route large estimates to a person

Above your threshold, do not wait for day 18. Create a task for the person who walked the job, due two working days after the estimate was sent, with the estimate linked.

5

Build the stops

The won event closes the record. So does an inbound reply on your own channel, an opt-out, and a manual stop for the customer who phoned. Before every send, fetch the estimate again and confirm it is still open.

6

Send touches four and five

An hourly sweep sends the due touch, inside business hours, then advances the record. Touch four around day 18 and touch five around day 28, then close.

7

Report the outcome

Log every touch and its result in one sheet the office can open: estimate, what was sent, when, and how it ended. Review it monthly. If touches four and five never produce a reply, switch them off.

Message copy

Touch 4 - day 18, not a resend

Hi {first_name}, it is {business}. You have had our
estimate for {job_description} a couple of weeks now.

Is it the price, the timing or the scope that is
holding it up? Tell me which and I will see what
I can do. A no is fine too.

Reply STOP to opt out.

Touch 5 - day 28, close out

Subject: Closing out your estimate

Hi {first_name},

I will stop following up on the {job_description}
estimate. The price holds until {expiry_date}.

If you want to pick it up later, reply to this
email and I will re-check the numbers.

{business} - {phone}

These work because they are not the estimate again. For the full set, see the unsold estimate follow-up guide.

Testing and measuring it

Start by testing Pipeline, because its behaviour sets the rules for everything you add.

  1. Create a customer with your own email and mobile. Send yourself an estimate by email and set the first follow-up to a short delay using a decimal, as the FAQ describes.
  2. Confirm the resend arrives, by the channel you used, and that the estimate moves to First Follow-Up on the board.
  3. Reply to that message without approving. Watch whether the second follow-up still goes out. Write down what you see, because the help articles do not say.
  4. Approve a second test estimate and confirm no further follow-ups are sent for it.
  5. Send a third estimate by text only and confirm the follow-up arrives by text.
  6. With the external tail running, confirm a record is created once per estimate and that the first external touch is scheduled after the third native follow-up.
  7. Approve a test estimate the day before an external touch is due and confirm the re-check stops it.

The third test decides one design point. If Pipeline keeps resending after a customer has replied, then your office needs a habit of moving the estimate on the board when a conversation starts, so the customer is not sent the estimate again mid-discussion.

Then measure by stage. Each month, count how many estimates were approved while in Sent, in First Follow-Up, in Second Follow-Up and in Third Follow-Up, and how many after that. The Pipeline board shows you where estimates sit, and your own log covers the tail. If almost every approval comes in the first two stages, your customers decide quickly and the tail will add little. If a real share arrive in the third stage or later, you have a long decision cycle and the tail and the call task are worth having.

Review the wording quarterly. Read your three Pipeline messages and two tail messages in a row, as a customer would receive them. If any two say the same thing, rewrite one. Sequences go stale quietly, and the cheapest improvement available is usually a better second message.

Where these builds go wrong

  • Leaving all three Pipeline messages identical, so the customer gets the same email four times.
  • Starting an external sequence on day one while Pipeline is also following up.
  • Leaving the decline rule early, so Pipeline declines an estimate your tail is still chasing.
  • Expecting a new rule to pick up estimates sent weeks ago.
  • Planning an API build without being on the MAX plan.
  • Texting from your own number without consent or US A2P 10DLC registration.
  • Not re-checking the estimate before a send, so an approved customer is asked if they are still interested.
  • Automating the follow-up on a five-figure estimate that deserved a phone call.

US texting registration is covered in the A2P 10DLC guide. For the other end of the funnel, see Housecall Pro missed call text back. Sector context is on the HVAC and plumbing page, and what an automation build costs covers pricing.

Sources checked

FAQ

Does Housecall Pro follow up on estimates automatically?
Yes, through Pipeline. Housecall Pro's Pipeline documentation lists estimate automations that work in stages: when an estimate has been Sent for a set number of days, it is resent to the customer and its status becomes First Follow-Up; the same happens again for Second Follow-Up and Third Follow-Up; and after a set time in Third Follow-Up the estimate is declined. That is three automated follow-ups.
What are Smart Recommendations in Housecall Pro?
A toggle on the estimate board's automation settings. Housecall Pro says it automates three estimate follow-ups and sets the timing using factors such as industry and seasonality, adjusting over time. With it enabled you can edit the content of the messages, but you cannot change the timing or disable a follow-up. Turn it off if you want to set the days yourself.
Are the follow-ups sent by text or email?
Whichever the estimate was sent by. The Pipeline FAQ states that the follow-up is sent as an email or a text depending on how the estimate was originally delivered, and if it went by both, the follow-up uses whichever was sent last. So you choose the follow-up channel at the moment you send the estimate.
Why are my Pipeline follow-ups not going out for older estimates?
Because a rule only applies to estimates that fall inside its timeframe. Housecall Pro's FAQ gives the example of a rule set today that applies to an estimate sent yesterday but not to one sent three weeks ago, which has to be resent manually. Customers with notifications turned off are also skipped unless you tick the option on the rule to send to them anyway.
Can I add a fourth and fifth follow-up?
Pipeline's documented estimate stages end at Third Follow-Up, followed by decline. Anything after that has to come from outside Housecall Pro, using its API and webhooks, which the developer documentation says are available to users on the MAX plan. If you are not on MAX, tune the three you have and consider a manual call list for the rest.
Can I set a follow-up delay in hours?
Yes. The Pipeline FAQ explains that timeframes are entered in days and that hours are entered as a decimal, giving the example of 0.25 days for a six-hour delay. Weeks and months are converted to days, so two weeks is 14.
Do I need the API to improve my estimate follow-up?
Usually not at first. The biggest gains come from switching Pipeline's automations on, choosing sensible timings, and rewriting the three messages so they are not identical. Build on the API only when you have a clear reason: a long sales cycle that outlasts three touches, large estimates that need a call, or a second channel.
What does it cost to have the extra sequence built?
It is a modest build, since Pipeline already handles the first three touches. The variables are whether you are on MAX, whether texting needs registering, and how much is written back into Housecall Pro. We quote a fixed price in writing per scoped workflow after a free consult.

Done for you

Want estimates followed up past the third touch, with the big ones getting a call?

We tune Pipeline first, then build the tail on Housecall Pro's API where it pays: touches four and five, call tasks for large estimates, every stop signal and a monthly report. The audit that scopes it is free.

The consult is free, and you keep whatever we build.

Keep building

The rest of the cluster