Follow up on stale Service Fusion estimates twice a week

By General Input

Every Tuesday and Thursday morning, send personalized follow-up emails on Service Fusion estimates that customers have gone quiet on.

Integrations

  • Service Fusion
  • Gmail
  • Slack

Type

Agentic Task

Categories

  • Sales
  • Operations

Every Tuesday and Thursday at 9am, chase Service Fusion estimates that customers have gone quiet on.

Start in Service Fusion by calling List Estimates with a date-range filter of 4 to 21 days ago and a status filter that keeps only open or pending estimates (skip anything already accepted, declined, or expired). Page through the full result set.

For each estimate that survives the filter, call Get Estimate to pull the full line-item detail and total, and Get Customer to resolve the primary contact's name and email. Then call List Jobs filtered by that customer to check whether the quoted work has already been converted into a job. If any job for that customer looks like it corresponds to this estimate (matching description, address, or line items), drop the estimate from the follow-up list. Service Fusion is read-only for estimates, so job creation is the only reliable signal that a customer has moved forward.

For each remaining estimate, draft a short, personalized follow-up email in the estimator's voice. Reference the specific work quoted (name the main line items, not just 'your estimate'), state the total price, and offer one soft next step: answer any lingering questions, get on the calendar, or extend the quote if pricing is the sticker. Keep it to a few sentences, no hard sell. Send it with Gmail Send a Message from the connected mailbox, using the customer's email as the To address and a subject line that references their project.

Once every eligible customer has been emailed, post a single digest to the sales Slack channel using Slack Send a Message. The digest should list each customer that was nudged (name plus estimate total), the count of estimates followed up on, and the total pipeline value covered. If nothing qualified, post a short 'no stale estimates today' note so the team knows the workflow ran.

Rules to bake in: never chase the same estimate twice in the same week (use estimate age plus the job-existence check to make that reliable); treat any estimate flagged as accepted, invoiced, or converted as booked; and if Get Customer returns no email, skip that estimate and mention the missing contact in the Slack digest so someone can fix it.

Related prompts

Explore more prompts
Call overdue Xero customers with an AI collections agentWin back LiveChat visitors whose chats went unansweredChat quality review board for LiveChat support leadsChase the paperwork every new client and vendor still owesFile Gmail attachments into storage with names you can findWin back no-show and cancelled appointments every morningLive Loop returns analytics with product-level drill-downNewsletter pre-flight and approval board for Mailjet sendsTurn a prospect spreadsheet into personalized sequence enrollmentsMailjet email delivery lookup console for support teams