Weekday morning dispatch digest for field service crews
Every weekday at 7am, post each technician's route to Slack in start-time order so crews and dispatchers see the day's plan before they clock in.
Service Fusion
SlackOperationsDaily DigestsNotifications & AlertsEvery weekday at 7am local time, kick off the morning dispatch digest for our field service shop and post one Slack message per crew channel so dispatchers and technicians see today's plan the moment they clock in.
Trigger: cron running Monday through Friday at 7am. Service Fusion does not push outbound webhooks and is not a poll provider, so a scheduled pull is the correct pattern.
Step 1: Use the Service Fusion List Jobs operation to pull every job scheduled for today. Filter by a start-date range covering the current day (from today's date at 00:00 to today's date at 23:59, in the shop's local timezone). Page through results until the returned page count is reached so long dispatch days are never truncated. Ask for the fields the digest needs: customer name, service address, job category, scheduled start time, assigned tech (or techs), status, and any notes.
Step 2: Use the Service Fusion List Techs operation to pull the technician roster so you can resolve each job's assigned tech id or reference into a human-readable technician name. Cache the roster in memory for the run.
Step 3: Group the jobs by assigned technician. Sort each tech's stops by scheduled start time, ascending. Skip any technician who has zero jobs today; do not post an empty block for them. Collect any job with no tech assigned into a separate 'Unassigned' bucket.
Step 4: Use the Slack Send a Message operation to post the digest to the shop's dispatch channel (the channel should be configurable). Format the message in Slack mrkdwn with a short header ('Morning dispatch — <weekday>, <date>'), then one block per technician:
Bold the technician name and show their stop count.
Under it, list each stop in start-time order as: start time, customer name, service address, job category, and any notes (truncate long notes gracefully).
After all assigned techs, add an 'Unassigned' section listing the same fields so the dispatcher can hand those out before the crews leave the yard.
If the message would exceed Slack's per-message length, split it across a small number of follow-up posts in the same channel rather than dropping stops. If Service Fusion returns zero jobs for today, still post a short 'No jobs scheduled for today' message so the team knows the pull ran.
Keep the tone tight and scannable. This is a pre-shift briefing, not a report — no filler, no restating the date twice, no extra commentary beyond what a dispatcher would actually shout across the room.
What does this prompt do?
- Runs every weekday at 7am and pulls today's scheduled Service Fusion jobs.
- Groups stops by assigned technician and lists them in start-time order with customer, address, job category, and notes.
- Posts one Slack message per shop channel and skips any tech with no jobs today.
- Calls out unassigned jobs at the bottom so the dispatcher can hand them out before crews leave the yard.
What do I need to use this?
- A Service Fusion account with today's jobs and technicians already scheduled.
- A Slack workspace where the workflow can post to your dispatch channel.
How can I customize it?
- Change the send time or days of the week to match your yard's start-of-shift.
- Route each shop or region to its own Slack channel, or send a per-tech DM instead.
- Filter the job list by category, priority, or status so the digest only shows the stops that matter.
FAQs
What if a job has no technician assigned yet?
Will techs with no jobs today get an empty message?
Can I send a separate digest per shop or region?
Does the message include job notes and the service address?
Do I need a paid Slack plan?
Related templates
Every weekday at 10am, an AI voice agent phones your most overdue Xero accounts, logs what each customer promised, and reports back to finance in Slack.
Every couple of hours we find the chats your team never answered, email those visitors a real reply, and hand the sensitive ones to a support lead.
Score last week's finished live chats against one rubric, let an AI grader draft the notes with quotes, and send coaching straight to the agent.
Every weekday morning, every appointment that fell through yesterday gets a personal text or email inviting them to rebook, plus a task for the right rep.
Pick any date range up to 120 days and see return volume, refund versus exchange mix, and the products behind every number, recalculated each time you open it.
Every newsletter gets read, checked and signed off in one place, so nothing goes out with a broken link or a half-filled greeting.
Give your crews the day's plan the moment they clock in.
Stop reading job cards over the radio. Let the morning dispatch digest post itself before anyone leaves the yard.