Instructions, in your own words
Who the digest is for, how it reads, and the rules that apply.
Your instructions
Write it for roofing crews. Call out wind over 25 mph on tear-off days, and keep Austin and Houston in their own sections.
The morningweather call, readyfor your whole crew
Weather Agent checks every region on your map and posts a crew-ready digest to Zuper, written to your instructions, on a schedule you set.
Austin, TXRain band 6am to 2pm18mm4 cities, one post#service-ops, 6:00am
Weather AgentSchedulingThe real problem
The weather call only happens if somebody remembers.
Every morning, someone looks up the forecast for each city and posts it in the group chat before 7. It works right up until that person is on a roof, on vacation, or running late. Add a second town, and it starts slipping.
Nothing catches a missed morning
Miss a morning or skip a place and nobody catches it until the crew is already on site with yesterday's forecast.
Nobody checks five areas by 7am
One place, you remember. Five is a chore, and a chore gets cut down to whichever you thought of first.
The cost lands on the crew
A wasted crew day, a decision made two hours late, or a truck sent to a site the weather had already ruled out.
How it works
Set it once. It runs every morning.
- 01
You set it up, in minutes
Pick the regions you work, write the instructions the digest should follow, set the time and where it lands. No sales call, no prompt engineering.
- 02
It checks every area you work
Forecast, wind, heat, UV and air quality, pulled per city. Five markets get the same check as one.
- 03
It posts before the day starts
A digest in the Zuper Chat tab on web, where your crews already are, with email too if you want it. Written the way you told it to write.
- 04
Every run is on the record
Log each run and don't lose track. If a forecast call times out or delivery drops, the agent flags it instead of going quiet.
Weather Agent setup
Agent Studio · configuration
Cities you work
4 citiesRuns at
DailyLands in
Chat + emailThursday outlook
4 cities
Austin, TXRain 6:00am to 2:00pm18mm · 80%Rain band
Houston, TXGusts building after 11:00am32mph · WHigh wind
Dallas, TXClear, hot from noon101°F · UV 9Heat & UV
San Antonio, TXPartly cloudy all day88°F · 10%Clear to work
Digest posted
06:00 CT · before first roll-out
#service-ops
Austin: rain 6:00am to 2:00pm, 18mm. No tear-off and no ladder work before it clears, check with the office first.
Houston: gusts to 32mph from 11:00am. Nothing on a lift above 20 feet until they drop off.
Dallas: 101°F and UV 9 after noon. Shade break every 45 minutes, load water before you roll.
Delivered to#service-opsEmail
Recent activity
Agent Studio · last 30 runs
Posted the morning digest
CompletedRun failed: forecast call timed out at 30s
FlaggedManual run, Houston added mid-week
CompletedWhat you set
You write the instructions, the agent writes the digest.
Pick Weather Agent in Agent Studio, choose your towns, write the instructions and set a delivery time. It comes with what it needs to check the weather and post the digest: nothing to integrate, and no new app to open.
What you give it
Four things, once
The regions you work
Every market on your list, in one digest. Five as reliably as one.
- Austin
- Houston
- Dallas
- San Antonio
Your own documents
Write them in, paste a URL to scrape, or upload a file.
- City and audience listWritten in
- Weather safety SOPUploaded
Where it lands
A Zuper Chat channel you create or pick, email, or both.
- #service-opsChat
- dispatch@Email
It works from your definitions, so the digest reads the way your ops manager writes it.
What sets it off
Two triggers
- Scheduled run
Daily or weekly, at the time you set.
- Run now
Pull a digest from the back office, without waiting for the schedule.
Turn Weather Agent on before tomorrow morning.
Pick your regions, write the instructions, set the time. The first digest lands in chat before your crews roll.