Soundly RunSound familiar?

Two teams, two answers

Support hours changed on Monday. Sales heard. Support didn't. By Wednesday one customer had been told both.

InsteadEvery team a change affects gives customers the same answer.

The video

Video planned52 secondsHow every video is made
The script
The one point
A change that reaches some teams and not others gives customers two answers; one entry, confirmed by each affected lead, gives them one.
Why a video
The same question asked twice: one customer hears two different hours from two desks in two days; then the same Monday, with the gap showing before any customer asks.
  1. Intro0:00-0:03sting

    Picture
    Brand mark and sound, then the heading ‘Two teams, two answers’ on the site’s background, fading straight into the guide with no black.
    On screen
    Two teams, two answers
  2. The moment0:03-0:10person

    Picture
    The guide in the usual place and framing. Lower third with first name and ‘Soundly Run guide’.
    Voice
    Support hours changed on Monday. Sales heard. Support didn’t. By Wednesday one customer had been told both. As teams multiply, each hears a change from someone different, or not at all.
    On screen
    One customer, told both
  3. The cost0:10-0:17motion

    Picture
    Example tag top left. Two desks, two speech bubbles to one customer dot: one reads ‘until 18:00’, the other ‘until 20:00’. The customer dot turns amber and its message lands back on both desks. No other figures.
    Voice
    The change reached the team nearest the decision. The rest kept the old answer, and the customer found the gap first.
    On screen
    Example: Two desks, two answers
  4. The mechanism0:17-0:26screen

    Picture
    Drawn Needs you screen, Example tag top left, context ‘Priya’s crew’. Step band on ‘prepare’. Heading ‘Support hours changed. Confirm Support has it.’ Callout 1 on Change. Callout 2 on Decided by: ‘Dana, Mon 19 Oct, in the decision record’.
    Voice
    Dana commits the change once, in the decision record, with every team that answers customers on it. Here it reaches Priya, the support process owner.
    On screen
    Example: one change, every team it affects
  5. The mechanism0:26-0:35screen

    Picture
    Same screen, step band ‘review’. Callout 3 on Your team: ‘14 people, and the AI that answers support chat’. Cursor moves to Other teams: ‘Sales confirmed by Lena · Accounts by Leo’, then Support: ‘Not yet confirmed: still quoting 7:00 to 20:00’.
    Voice
    Sales and Accounts have confirmed. Support has not, so the change shows Support as not yet reached, on Monday, before any customer asks.
    On screen
    Example: Support not yet confirmed
  6. The decision0:35-0:42person and screen

    Picture
    Step band on ‘decide’. ‘Confirm for Support’, ‘Ask Dana’ and ‘Pass’ all visible. Cursor clicks ‘Confirm for Support’, held two seconds. Row updates: ‘Confirmed by Priya, Mon 19 Oct, 15:10’. Guide in picture-in-picture.
    Voice
    Priya decides for her team: confirm for Support, ask Dana, or pass. She confirms.
    On screen
    Confirmed. All three teams now give one answer.
  7. The difference0:42-0:48person

    Picture
    The guide, same place and framing as the moment, so it reads as a return.
    Voice
    Nobody learns of the gap from a customer quoting one team to another. The helper drafts; each lead decides. It does not watch, score or replace anyone.
    On screen
    Every team a change affects gives customers the same answer.
  8. Outro0:48-0:52sting

    Picture
    Standard end card, the same in every video: the page title, the brand mark and one small line, ‘Example screens’.
    On screen
    Two teams, two answers

On screen as proof

  • Needs you screen tagged Example: Support not yet confirmed while Sales and Accounts have
  • Example hours ‘8:00 to 18:00, not 7:00 to 20:00’ only inside the tagged screen and the motion scene
  • Confirm for Support, Ask Dana and Pass all visible; click held two seconds

Before and after

Before
The decider tells the nearest teams and assumes the rest heard
After
The work shows who it affects: every team that answers on it
Before
Each team keeps its own notes, so one goes stale (no single source of truth)
After
Every team answers from one entry in the decision record
Before
Only a customer quoting one team to the other shows the gap
After
Until each lead confirms, the change shows who has not heard

How it works

A change reaches every team it affects from one entry in the decision record, which shows who has not confirmed.

  1. The decider writes the change once in the decision record, with every team and AI helper it affects.
  2. Each affected team’s lead confirms; until then, the change shows that team as not yet reached.
  3. Where a customer heard both, their account owner gets a drafted reply and decides what to send.
Needs youExample

Priya's crew

Support hours changed. Confirm Support has it.

Change
8:00 to 18:00, not 7:00 to 20:00, from Mon 19 Oct
Decided by
Dana, Mon 19 Oct, in the decision record
Your team
14 people, and the AI that answers support chat
Other teams
Sales confirmed by Lena · Accounts by Leo
Support
Not yet confirmed: still quoting 7:00 to 20:00

Source: decision record, 19 Oct

Confirm for SupportAsk DanaPass

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.