Interpreter.io Automated Unfilled Booking Digest
Every morning, WebRun opens Interpreter.io, looks across the next several days of court bookings, groups the ones that still need an interpreter by lead time, and sends your coordinator one internal Telegram digest summarizing what is unfilled, what is at risk, and what to work first.
How do I get a daily summary of unfilled interpreting bookings?
WebRun reviews the next several days of court bookings in Interpreter.io every morning, separating assigned jobs from those still needing an interpreter and grouping the unfilled ones by day and lead time. It sends your coordinator one internal Telegram digest of what is unfilled and what to work first, so each day starts with a clear coverage plan.
- Coordinators start the day with one coverage digest, not a scattered board
- At-risk unfilled jobs are grouped and surfaced first
- Nothing external is sent, so all outreach stays a human call
Built for court interpreting agencies · language service providers · interpreting coordinators · scheduling managers
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
interpreter.ioin a real browser with your saved login - no setup, no API keys. -
1
Interpreter.io - review upcoming unfilled bookings
WebRun opens Interpreter.io to review upcoming unfilled bookings. - Open Interpreter.io and review bookings across the next several days
- Separate confirmed, assigned jobs from those still needing an interpreter
- Group the unfilled bookings by day and by lead time remaining
- Capture the language, court, and delivery method for each unfilled job
Done when Every upcoming unfilled booking is grouped by day and lead time with its key details.
-
2
Telegram - send the daily coverage digest
WebRun opens Telegram to send the daily coverage digest. - Send an internal digest to your coordinator's Telegram
- Lead with a count of unfilled bookings for today, tomorrow, and the rest of the week
- List the at-risk jobs first with their language, court, and lead time
- Keep the digest internal so nothing reaches an interpreter or the court
Done when Your coordinator has one Telegram digest of what is unfilled and what to work first.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Does this contact interpreters or requesters?
No. It only sends an internal Telegram digest to your coordinator. It never messages an interpreter or a requester, so all outreach stays a human decision.
How is the digest organized?
It groups unfilled bookings by day and by lead time, leading with a count for today, tomorrow, and the rest of the week and listing the at-risk jobs first with their language and court.
How is this different from an unfilled alert?
This is one planned morning summary of the whole open board, so your coordinator starts the day with a coverage plan rather than reacting to each booking as it surfaces.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.