Routed to someone who moved
The approval went to Felix. Felix moved teams in July. The Team page still says Felix, so everything still asks Felix.
InsteadWhen someone moves, what they held is handed on that week.
The video
Video planned52 secondsHow every video is made
The script
- The one point
- When a person moves teams, what they held is handed on through the Team page, so requests stop going to the old name.
- Why a video
- Time passing: July to October in seconds while requests keep landing on Felix’s new desk. Then Grace’s own click redraws where they go.
- Picture
- Brand mark and sound, then the heading ‘Routed to someone who moved’ on the site’s background, fading straight into the guide with no black.
- On screen
- Routed to someone who moved
- Picture
- The guide in the usual place and framing. Lower third with first name and ‘Soundly Run guide’.
- Voice
- The approval went to Felix, who moved teams in July. Everything still asks Felix. In a company this size, people move often, and updating the Team page is nobody’s step in a move.
- On screen
- Everything still asks Felix
- Picture
- Example tag top left. Felix’s name card slides from a Finance desk to a Platform desk. Months flip July to October; request cards keep arriving at his new desk, some answered, some stacking up. No figures.
- Voice
- Felix still answers out of kindness, so nobody notices, and some requests just wait.
- On screen
- Example: nobody notices the drift
- Picture
- Drawn Team screen, Example tag top left, context ‘Grace’s crew’. Step band on ‘prepare’. Heading ‘Felix moved in July; the Team page still sends him requests’. Callout 1 on Moved. Callout 2 on Still named for.
- Voice
- Felix moved on the first of July. The Team page still names him for software subscriptions, month-end accruals and supplier queries.
- On screen
- Example: still named for 3 kinds of request
- Picture
- Same screen, step band ‘review’. Callout 3 on Sent to him since: 41 requests, 23 from AI helpers. Cursor moves to Answered, then Drafted holders.
- Voice
- Forty-one requests went to him since, twenty-three from AI helpers. Twelve still wait. New holders are drafted: Kim for two, Grace for accruals.
- On screen
- Example: 41 requests, 23 from AI helpers
- Picture
- Step band on ‘decide’. ‘Move all three’, ‘Change’ and ‘Pass’ all visible. Cursor clicks ‘Move all three’, held two seconds. Rows update to the new holders, and ‘12 waiting requests sent on’. Guide in picture-in-picture.
- Voice
- Grace was Felix’s lead, so she decides: move all three, change them, or pass. Her click updates the Team page.
- On screen
- Moved. Requests now go to Kim or Grace, not Felix.
- Picture
- The guide, same place and framing as the moment, so it reads as a return.
- Voice
- Nobody chases requests sent to an old name any more. The helper drafts; leads decide. It does not watch, score or replace anyone.
- On screen
- When someone moves, what they held is handed on that week.
- Picture
- Standard end card, the same in every video: the page title, the brand mark and one small line, ‘Example screens’.
- On screen
- Routed to someone who moved
On screen as proof
- Team screen with what Felix is still named for, walked row by row, tagged Example
- Example figures ‘41 requests, 23 from AI helpers’ and ‘12 still waiting’ only inside the tagged screen
- Move all three, Change and Pass all visible; click held two seconds
Before and after
- Before
- Nobody’s step in a move updates the Team page (stale ownership)
- After
- Their holdings listed for the old lead to hand on
- Before
- Felix still answers out of kindness, so nobody notices the drift
- After
- Requests go to whoever holds the call now
- Before
- AI helpers read the Team page and ask the old name
- After
- Each quarter, every lead confirms who holds what in their team
How it works
Ownership is kept true when people move: the Team page changes that week, and the old holder’s requests are sent on.
- On the move date, the Team page lists everything the person holds for their old lead.
- The old lead names a new holder for each, or leaves it with them on purpose; people and AI helpers then ask that holder.
- Each quarter, every lead confirms who holds what in their team; a holder now in another team is flagged.
TeamExample
Grace's crew
Felix moved in July; the Team page still sends him requests
- Moved
- Felix, from Finance operations to Platform, 1 Jul
- Still named for
- Subscriptions under $1,500, month-end accruals, supplier queriesKim: subscriptions, supplier queries · Grace: accruals
- Sent to him since
- 41 requests, 23 of them from AI helpers
- Answered
- 29, as a favour; 12 still waiting, oldest 9 days12 waiting requests sent on to their new holders
- Drafted holders
- Subscriptions and supplier queries to Kim; accruals to you
Source: Team page, 21 Oct
Move all threeChangePassMoved. Requests now go to Kim or Grace, not Felix.
Built to work in the email, calendar, chat, finance and sales tools you already use.
What it never does
- Acts alone only inside limits a person sets; asks first for anything else.
- Reaches only what its job needs.
- Never watches, scores or replaces anyone.