Automated Assembled Time-Off Request Chase
Every morning, WebRun opens Assembled, collects the time-off and shift-swap requests still sitting in a pending state, creates a Trello card per request with who asked and which shift it touches, and drafts a WhatsApp update to each waiting agent for a manager to approve before it sends.
How do I stop time-off requests sitting unanswered in Assembled?
WebRun opens Assembled every morning and finds the time-off and shift-swap requests still waiting on a decision. It creates a Trello card for each with the agent, the dates, and the days waited, then drafts a WhatsApp holding message for a manager to approve, so no request quietly ages out.
- No time-off request ages out unanswered
- Managers open Trello to an oldest-first decision queue
- Agents get a same-day acknowledgement once a manager releases it
Built for support managers · workforce management teams · BPO operations · contact centers
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
www.assembled.comin a real browser with your saved login - no setup, no API keys. -
1
Assembled - find pending requests
assembled.com
WebRun opens Assembled to find pending requests. - Open Assembled and go to the time-off and shift-change requests view
- List every request still in a pending state
- Capture the agent, the dates, the shift it affects, and how many days it has waited
- Note whether the requested day already looks thin on coverage
Done when Every undecided request is listed with its agent, dates, and waiting time.
-
2
Trello - queue each for a decision
trello.com
WebRun opens Trello to queue each for a decision. - Open your scheduling board and create a card for each pending request
- Title it with the agent name and the dates requested
- Add the shift, the waiting time, and the coverage note in the description
- Sort the oldest requests to the top of the list and skip anything already carded
Done when Every pending request has one Trello card, oldest first.
-
3
WhatsApp - draft the agent an update
whatsapp.com
WebRun opens WhatsApp to draft the agent an update. - Draft a short, friendly WhatsApp message to each waiting agent confirming the request is being reviewed
- Leave every message unsent as a draft for a manager to read and approve
- Never send a decision on a request. Only a manager confirms an approval or a refusal
Done when A draft update sits ready for each waiting agent, unsent until a manager approves.
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
Will it approve or deny time off on its own?
No. WebRun never decides a request. It only lists what is pending in Assembled, cards it in Trello, and drafts a holding message. A manager makes every approval and every refusal.
Does it message agents without me?
No. Every WhatsApp message is left as an unsent draft for a manager to read and release, so nothing reaches an agent until a person approves it.
What if a request was already decided?
It reads the live request state in Assembled each morning, so anything already approved or denied is skipped and its Trello card is not created again.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.