Automated Bird Shift Handover Briefs
At the end of every shift, WebRun opens the Bird inbox, lists every conversation still open or waiting on a reply across your channels, notes who owns each one and how long it has been waiting, posts the handover brief to Microsoft Teams, and writes the same brief into the shift handover event on Google Calendar.
How do I hand over open customer conversations at shift change?
WebRun opens the Bird inbox at the end of every shift and lists the conversations still open or awaiting a reply, with the channel, the owner, and how long each has waited. It posts the brief to Microsoft Teams and writes it into the next shift's Google Calendar handover event.
- Nothing waiting in the inbox gets lost at shift change
- Unassigned conversations are named instead of buried
- The incoming agent reads the brief on the calendar invite itself
Built for support teams · contact centres · operations managers · ecommerce brands
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
app.bird.comin a real browser with your saved login - no setup, no API keys. -
1
Bird - list conversations still waiting
WebRun opens Bird to list conversations still waiting. - Open the Bird inbox and filter to conversations that are open or awaiting a reply
- Capture the channel, the contact, the assigned agent, and the time of the last inbound message for each
- Work out how long each conversation has been waiting and sort oldest first
- Note any conversation with no agent assigned so it does not fall through the gap
Done when Every open conversation is listed with its owner, its channel, and how long it has waited.
-
2
Microsoft Teams - post the handover brief
WebRun opens Microsoft Teams to post the handover brief. - Post the handover brief to the support channel in Microsoft Teams
- Put the longest-waiting conversations at the top with the customer, the channel, and the last message time
- Call out unassigned conversations in their own short block
- Leave every reply to the incoming agent. Never answer a customer from this run
Done when The support channel has the full end-of-shift handover brief.
-
3
Google Calendar - attach it to the handover event
WebRun opens Google Calendar to attach it to the handover event. - Open the shift handover event on your team calendar for the next shift
- Write the count of open conversations and the count of unassigned ones into the event title
- Paste the full brief into the event description so the incoming agent sees it on the invite
- Update the existing event rather than creating a duplicate
Done when The next shift's handover event carries tonight's brief in its description.
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 reply to customers in Bird?
No. WebRun reads the inbox only. It never sends a message, closes a conversation, or reassigns an agent. The handover brief goes to your own Teams channel and your own calendar event.
Does it cover every channel in the inbox?
Yes. It walks each channel connected to your Bird inbox and lists open conversations from all of them in one brief, with the channel named on every line.
What happens to conversations nobody owns?
They get their own block at the top of the brief. An unassigned conversation is the easiest one to lose at shift change, so WebRun separates them out rather than burying them in the list.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.