StandIn in practice

Three scenarios. Each one shows something different.

Tokyo goes offline. Amsterdam keeps moving.

Sarah finishes her day in Tokyo and publishes her brief before closing her laptop.

Sarah's brief90s
What shipped today
Auth API refactor complete. PR #402 pushed and ready for review.
What's blocked
Ticket #482: waiting on Ops for a configuration credential before merge.
Who owns the next action
Dave Chen: review PR #402 and approve when Ops resolves #482.
Back online
Tomorrow 09:00 JST
Once published, your team can ask about this. You won't be pinged.Publish brief

Sarah's brief became a record her team can ask about.

StandIn holds it until her window expires at 09:00 tomorrow.

No one needs to ping her overnight.

Alex in Amsterdam asked about the API at 10:00 his time. He had his answer from what Sarah wrote down. Nobody waited.

Same question. Two very different answers.

Ask Something
✦Generic AI twin
Waiting for a question…
Sarah's StandIn
Waiting. It only says what's been confirmed.
Sarah's roll-up reportopens 9:00 am CEST
Overnight so far · 2 answered on their own, 0 guesses
Anything StandIn can't answer lands here, held, never guessed at.

Nobody waited until she was back.

The auto-reply said nothing. Her StandIn answered, in her words, with her name on it.

She came back to a summary, not a full inbox.

The out-of-office reply says: wait until I'm back. A StandIn answers instead. That's the retirement of the auto-reply.

Want to see it on your team’s questions instead?

See it on your team’s work

She came back to a summary, not a full inbox.

These scenarios run on what your team writes.

There's no AI reading your messages, guessing your status, or watching your screen. StandIn answers from briefs your team publishes, and says "I don't know" when the information isn't there.

See this on your team’s questions, not ours.

Read how the first 30 days work →Understand the philosophy →