Pause and resume a session mid-workout

Halfway through chest day, the phone rings — your kid forgot a permission slip and needs a pickup. You're not done training, but you can't stay either. Tell the agent to pause, deal with the thing, come back to where you left off.

What the agent needs to hear

Behind your sentence, the agent works backwards to one piece: whether you’re pausing or resuming. The active session is implicit context — there’s only one open at a time, and the agent already knows which. « Pause » plus an active session freezes it; « resume » or « let’s start » plus a paused session unfreezes it and drops you back into the queue.

An optional reason rides along if you give one — « stepping out for 15 minutes », « kid pickup », « lunch break ». The agent logs it as context on the pause but doesn’t act on it. If you’re silent, the pause is just a pause; the reason is for your own thread back.

What pause actually freezes

The pause works on one axis: the session clock. Duration stops counting the moment you say pause and starts again when you resume — the gap doesn’t show up as training time. Logged sets stay attached exactly as you logged them; nothing rewrites or moves. The queue holds at the next planned exercise, so when you come back, the agent picks up there, not from the top.

Pause is open-ended — you can pause for five minutes or five hours; the system doesn’t auto-cancel. A pause that runs into the next day will draw a flag on the closing card, but it won’t be cancelled for you. You decide whether to resume or to walk away from it.

How pause keeps duration honest

Duration is one of the metrics the system reads from every session — for weekly trends, training quality, density per minute, recovery between sets. A 90-minute session that includes a 30-minute phone-call gap reads as 90 minutes if you didn’t pause; a paused 60-minute session reads as 60.

The difference matters. Density drops when total time inflates, weekly volume per hour reads softer than it was, and the patterns the weekly review surfaces start to drift. Pausing for genuine interruptions keeps those signals real. Skipping the pause inflates duration and deflates apparent density on a session you actually trained hard.

When the agent gets it wrong

Three failure modes show up. The agent paused when you meant cancel — you’re not coming back today, the session shouldn’t sit open: « no, cancel it — I’m not coming back today ». The agent resumed a paused session when you wanted a fresh start: « actually start a new one — skip the paused one ». The agent treated « pause » as « end » and closed the session: « reopen it — I’m not done ».

In each case you keep talking. The agent reverses the call, the card updates, you move on. The chokepoint is the moment after you said pause — if the card shows the wrong action, push back before you walk away.

What makes pause worth using

Three things decide whether pausing is the right move: you’re actually coming back (pause for real interruptions; cancel for « not happening today »), the pause is brief enough to be a pause, not a session split (a multi-hour gap between halves of a workout is two sessions, not one — pause makes sense up to around 90 minutes), and the active session is the right one (a stale session from yesterday still paused is the kind of thing the agent will flag, but cleaning it up before pausing today’s is cheap).

Pause used this way keeps duration metrics readable across weeks where life interrupted training.