# Morning dispatch brief in Slack for every technician

> Every weekday at 6am each technician gets a Slack rundown of their stops, with prep notes from past visits so nobody arrives cold.

- Workflow type: agent
- Services: Housecall Pro, Slack
- Categories: Operations
- Published: 2026-08-14

## What it does

- Pulls today's scheduled work and groups it by the technician assigned to each stop, skipping anyone with an empty day.
- Sends each technician a private Slack message with their stops in time order, including arrival window and address.
- Adds two or three lines of prep per stop from the customer's service history: what was done last visit, problems that keep recurring, and equipment or access notes.
- Flags customers carrying an unpaid balance so the tech can collect before starting, and calls out an upsell worth mentioning when the history supports it, like a system overdue for a tune-up.

## What you'll need

- A Housecall Pro account on the MAX plan, which is the tier that lets outside tools connect, plus an admin to switch the connection on.
- A Slack workspace your technicians already use.
- Technician email addresses that match between Housecall Pro and Slack, so each brief reaches the right person.
- Jobs scheduled in Housecall Pro with a technician assigned to them.

## Prompt

Every weekday at 6am, send each of my Housecall Pro technicians a morning dispatch brief as a Slack direct message, so nobody walks into a job cold. Run this on a schedule, Monday through Friday at 6am in my business's local time zone.

Start by pulling today's work with Housecall Pro List Jobs filtered to today's date. Drop any job whose work_status is user_canceled or pro_canceled, since those stops are not happening. Group the remaining jobs by their assigned employee, and call List Employees to resolve each assigned employee into a technician name and email address.

For each stop on a technician's list, call Get Job for the full detail (scheduled time, arrival window, job type, line items, and any notes) and Get Customer for the service address and contact details. Then call List Jobs again filtered by that customer to pull their previous visits, and read that history for what was done last time, issues that keep recurring, and equipment or access details worth knowing in advance.

Check List Invoices and identify any customer on today's schedule who is carrying an outstanding balance. Housecall Pro returns monetary fields as integers in cents, so divide outstanding_balance and total_amount by 100 and format them as dollars before they appear in any message.

Deliver one Slack message per technician. Use Slack List Users to match the technician's Housecall Pro email address to their Slack account, then Open a Conversation with that user to get the direct message channel, then Send a Message to that channel. If a technician has no matching Slack account, skip them and note it in the run summary.

Structure each message as that technician's stops in time order. For every stop, lead with the arrival window, the customer name, and the service address, then two or three lines of prep covering what was done on the last visit, any recurring issue, and equipment or access notes such as gate codes, pets, or parts to bring. Flag any stop where the customer has an outstanding balance so the tech knows to collect before starting, and call out an upsell worth mentioning when the service history genuinely supports it, such as a system overdue for its annual tune-up. Keep the prep specific and grounded in the actual history. If a customer's record has nothing useful in it, say the visit looks routine rather than inventing detail.

If a technician has no jobs scheduled today, skip them entirely instead of sending an empty message. Format the messages with Slack mrkdwn, which uses single asterisks for bold rather than double.

## How to customize

- Change the delivery time or which days it runs. 6am on weekdays fits most crews, but earlier works if your team rolls out at dawn.
- Set how far back the service history goes and how many prep lines you want per stop.
- Turn the balance reminders or upsell suggestions off, or post one combined brief to a dispatch channel instead of private messages.

## FAQ

### What happens if a technician has no jobs scheduled?

Nothing gets sent. We skip technicians with an empty day rather than delivering a blank message, so a day off stays quiet.

### Where do the prep notes come from?

From that customer's earlier jobs in your Housecall Pro account. We look at what was done on previous visits, spot issues that keep coming back, and pull out equipment or access details worth knowing before the tech knocks on the door.

### Does it include jobs that were cancelled?

No. Cancelled stops are filtered out, whether the customer cancelled or your office did, so the brief only lists work that is actually happening.

### How does it know which Slack account belongs to which technician?

We match the email address on the Housecall Pro employee record to the email on the Slack account. If a technician has no matching Slack account they are skipped, and you can correct the address in either system.

### Will this work for a plumbing or electrical business, not just HVAC?

Yes. Nothing in the brief is trade specific. It reads whatever service history exists on the customer, so it works for any trade running scheduled jobs out of Housecall Pro.

Use this prompt in General Input: https://www.generalinput.com/prompts/morning-dispatch-brief-in-slack-for-every-technician