Deploy an AI agent today. More agents ship weekly.

You are the dispatcher for a mid-size HVAC and plumbing contractor. Build tomorrow's route plan that maximizes billable hours, minimizes drive time, and never assigns a tech to a job they aren't certified for. Here are tomorrow's open work orders:

[PASTE JOB LIST — address, trade, priority, estimated hours]

Here is the available roster:

[PASTE TECHS — name, certs, current truck/van inventory]

Here is today's service-area policy:

[PASTE RULES — max drive time, lone-tech exclusions, parts-short trucks]

Return: a numbered route for each tech, in order, with the job address, window, required parts they need to load before they leave the shop, and any job that should slip to Friday if a tech is short. Flag conflicts before listing the plan.

Draft a two-message text-and-call pair to win back a customer who cancelled an install this morning. The tone is friendly, never desperate, and never mentions the cancellation first. Here is the context:

Original job: [TRADE / SCOPE / QUOTED PRICE / SCHEDULED DATE]
Reason given: [PRICE / TIMING / OTHER / NONE]
Open slots this week: [MORNING / AFTERNOON / EMERGENCY]

Return: an SMS text (under 300 characters, designed for the thumb) and a phone-call opener (under 60 seconds to deliver). End with a single yes/no question so the office can book it on the next pass.

Write a same-day invoice for a completed service call in plain contractor English — line items, totals, payment terms, and a one-paragraph thank-you that asks for a 5-star review if the job went well. Here are the inputs:

Work performed:
[PASTE LINE ITEMS — labor hours, parts, trip charge]
Customer:
[PASTE NAME / ADDRESS / EMAIL]
Payment options on file:
[PASTE — card on file / ACH / check on delivery]

Return: the invoice body (header through balance due), a payment-terms paragraph, and a review-request paragraph to include as the email P.S. Use plain language, no jargon, no exclamation marks.

Write a 4-step dunning sequence for an overdue invoice that doesn't damage the relationship. Each step gets friendlier-to-firmer, and each step includes the exact ask and the exact next action if the customer responds. Here is the context:

Invoice:
[PASTE — number / amount / original due date / work performed]
Customer history:
[PASTE — on-time / first late / slow payer]
Hard stops:
[PASTE — calling hours / texting hours / escalation rules]

Return: four messages (Day 1 SMS, Day 4 email, Day 8 phone script, Day 14 final-notice email). Each must end with a single next step (pay link, callback window, or escalation to collections). Skip small talk; respect the hard stops.

Draft a 2-sentence text-back to a missed call that books the next step before the lead goes cold. The tone is human, not a chatbot, and never apologizes for missing the call. Here is the context:

Caller:
[PASTE — name if captured / area code / time]
Shop policy:
[PASTE — 24/7 emergency / same-day callback / fit-call booking]
Sending number:
[PASTE — the phone number that will appear]

Return: the SMS (under 280 characters), a separate voice-memo option for the on-call tech if it's after-hours, and a single follow-up question if the lead doesn't reply within 2 hours.

Write a short re-engagement email to a lead who ghosted the quote last quarter. The goal isn't to sell — it's to reopen a conversation. Here is the context:

Original quote:
[PASTE — trade / scope / quoted price]
What they said:
[PASTE — reason for pause / ghost]
What's new:
[PASTE — off-season promo / open slot / new certification]

Return: a 5-line email, a 1-line subject that doesn't sound like marketing, and one specific question that makes it easy to either re-engage or politely close the loop forever. No exclamation marks.