Weekday morning dispatch digest for field service crews

Every 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.