After the insert, the original task has to resume

What it is

The weather has been answered. If the next line is “anything else,” the taxi drops off the agenda and the user has to raise the pickup again. Resume after nested task requires that when the nest closes, the system actively puts the suspended job back on the floor — not a blank “how can I help.” Resume is not re-reading the weather. It is putting the parent’s next empty slot or confirm beat back on the table.

Why it happens

People hear an insertion as parentheses: when the parenthesis closes, the reading position should return to just before the left parenthesis. If the system treats a completed insert as a new end of session, popping the stack finds nothing underneath — the main task was never pushed as a parent, only overwritten by a new intent. Even if the user remembers “I was getting a cab,” a next beat with no resumption cue forces them to re-plan how to open their mouth, walking already-filled slots again. Resume also needs a hearable join: opening the mic and waiting does not tell people whether to fill pickup or say “continue the taxi.” The join should carry the parent’s identity and current position (“back to the cab. pickup still the office?”) so the two sides of the parenthesis line up. A resume without a join, and no resume, are the same event for the user.

Studying it

After the same insertion, two closings: a resumption cue (name the parent and the current slot) versus an uncued opener. Dependents: rate of continuing the parent on the next turn, times the parent skill is re-woken, abandonment. Independents: length of the nested task (one weather line versus a three-turn text), number of slots already filled on the parent. Longer nests and more filled slots usually crash return rate harder without a cue — not because people forget they wanted a cab, because the next beat never gave the reading position back.

Conversation analysis looks at the first adjacency pair after the insert ends: did the system produce a first pair-part that points at the parent. A generic help line is a resume miss, even if the user later finds their own way back.

Where it stops holding

If the user used a clear topic change inside the insert (“forget the cab, play music”), the parent has been abandoned and a resume is an interruption. If the insert opened a long activity the user will clearly stay in (a podcast started), auto-jumping back to the taxi cuts the new activity; ask whether to return rather than bounce. If a precondition of the parent has changed (the user walked into the subway while booking; pickup is stale), returning to the old slot reconnects stale state — refresh, then resume. A failed nest (weather skill unavailable) still has to resume, carrying the failure with it, not treating the failure as end of session.

Applying it

• When an insert closes, default to a resumption cue: parent name + current empty slot or confirm. Do not land on a generic opener.
• The cue echoes a key filled item (“pickup still the office”) so the user can take it with “yes,” rather than walking the whole form again.
• If the user abandoned the parent during the insert, follow abandon, not resume.
• How to check: taxi asks pickup → weather insert → weather answered. The next system line must let someone who missed the earlier turns hear “we are booking a cab, stuck on pickup.” If that line could open a cold start, resume did not happen.

Related

• Same group: M1.05.1 People insert new requests in the middle of a task · M1.05.3 Nesting depth needs a hard cap · M1.05.4 A topic switch and a correction are different intents · M1.05.5 A suspended task must keep its full mid-state · M1.05.6 Abandoning a task needs an explicit exit
• Nearby: M1.04 Context Retention · M2.07 Dialogue Flow and State Design · M1.12 Opening and Closing a Dialogue
• Search terms: resume after nested task · task stack pop · resumption cue