Morning dispatch brief in Slack for every technician

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.