Turn finished Workiz jobs into text review requests

By General Input

Every day at 5pm we text your finished customers for a review, skip anyone who seemed unhappy, and send those to Slack so a manager can call first.

Integrations

  • Workiz
  • ClickSend
  • Slack

Type

Agentic Task

Categories

  • Customer Support
  • Operations

Every day at 5pm, turn the jobs my team finished today into review request texts, while making sure that customers who had a bad experience get a call from a manager instead of a public review ask.

Start with the Workiz List Jobs operation and page through the results. It returns at most 100 records per page, so keep advancing the offset until you have every job. Keep only the jobs whose status is completed and whose completion date is today. For each one, read the customer first name and phone number, the job type, the assigned technician, the SubStatus field, and any job notes. Workiz has no separate sub status or notes endpoint, so take all of that from the job record in the List Jobs payload.

Drop any job that looks like a callback, a warranty visit, or a redo of earlier work. Check the job type, the SubStatus, and the notes for wording like callback, warranty, redo, rework, recall, or return visit. Those are not moments to ask someone for a review.

Also drop customers who have already been texted in the last 90 days. Use the ClickSend Get SMS History operation with a date range covering the last 90 days and compare those recipient numbers against today's customers. When you are unsure whether a number matches, skip it rather than risk texting the same person twice.

Before drafting anything, judge whether the customer seemed unhappy. Read the SubStatus and the job notes for signs of a complaint, an argument about price, a missed or late appointment, damage caused on site, or a problem that was not actually fixed. If a job reads that way, do not text that customer at all. Instead post it to the Slack channel #service-recovery using the Slack Send a Message operation, including the customer name, the job type, the technician, the SubStatus, the exact wording from the notes that concerned you, and one line on why it needs a phone call. A manager will call them.

For every job still on the list, write a short friendly text of no more than two sentences. Thank the customer by first name, mention the specific work using the job type, name the technician who did it, and ask for a review. Vary the wording between customers so the messages do not read like one template, keep the tone warm and plain, and skip emoji. Send each message with the ClickSend Send SMS operation. ClickSend needs full international numbers with a leading plus and country code, so normalize each Workiz phone number first and skip anything that is clearly not a mobile.

Finish by posting one summary to the Slack channel #field-ops with Slack Send a Message: how many review requests went out, how many jobs you skipped and why, broken down into callback or warranty or redo, already texted in the last 90 days, and unusable phone number, and then a list of the jobs you deliberately held back for service recovery with the customer name and job type for each. If nothing qualified today, still post the summary saying so.

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 leadsWin 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 teamsCatch feature flags that never got switched on in productionKajabi customer support console for member access fixes