Win back quiet Workiz leads with automated follow-ups

By General Input

Every weekday morning we find the Workiz leads that never became jobs, email each one a personal nudge, and recap the whole run in Slack.

Integrations

  • Workiz
  • Gmail
  • Slack Bot

Type

Agentic Task

Categories

  • Sales
  • Operations

Every weekday at 8am, chase the Workiz leads that have gone quiet so they stop rotting.

Use the Workiz List Leads operation to pull every lead created in the last 45 days. That endpoint pages with offset and records at a maximum of 100 per call, so keep paging until you have the whole window. Workiz stores ServiceArea and SubStatus as fields on the lead record itself rather than as separate endpoints, so read them straight off each lead.

Drop any lead that was already converted into a job, any lead marked lost or closed, and any lead with no usable email address. Keep a note of each exclusion and its reason so they can be reported at the end.

For every lead that survives, judge how worth chasing it is. Weigh the job type, the service area, the lead source, and how many days it has been sitting untouched. Rank them best first and work down that ranking.

Before emailing anyone, use the Gmail List Messages operation to search for recent mail to that address, and skip any lead that was already followed up with in the last 7 days. Cap the run at 25 emails so nobody gets blasted. If more than 25 leads qualify, email the highest ranked 25 and leave the rest for the next run.

Draft a short personalized follow-up for each remaining lead and send it with the Gmail Send a Message operation. Reference what the customer originally asked about in plain language, keep it under 120 words, and make one clear ask. Vary the tone by age: a lead around 4 days old gets a soft check in, a lead in the 10 to 20 day range gets a warmer nudge that offers to hold a slot, and a lead 30 days or older gets a stronger last call with a concrete reason to act now.

Estimate a value for each lead from its job type using typical ticket sizes for that kind of work, and label it clearly as an estimate rather than a quote.

Finish by posting to my sales channel with the Slack Send a Message operation. Group the contacted leads by tone bucket and give each one a name, job type, service area, days waiting, and estimated value. Include the total estimated pipeline touched, then list every lead that was deliberately skipped along with the reason. Format the message with Slack mrkdwn, using bold section headers.

Related prompts

Explore more prompts
Win back LiveChat visitors whose chats went unansweredA brand asset library your marketing team actually searchesTurn Mailjet email clicks into ranked HubSpot follow-upsClean out the Looker dashboards and Looks nobody opensLiveKit live operations console for room moderationWake up dormant Keap leads with a researched reasonLiveChat coverage board for planning next week's shiftsPhone routing control panel for LiveKit voice agentsLinkedIn Ads budget pacing dashboard for every client accountGive your team Looker numbers without buying more seats