Who owns the next callback update?
Carry the customer’s question and next commitment through a handoff.
The question
A chat about a missing course registration confirmation ends before a specialist can check it. The customer agrees to a callback by 15:00 and accepts in-app messages if that time changes.
- ChatRequest RC-29. The customer completed 2 checks. They looked in their junk mail and in-app messages.
- AppointmentA specialist has accepted the callback and can review the record.
The first agent owns progress updates until the callback occurs or another named agent explicitly accepts the next update. The customer can confirm whether a new callback time works.
“What do you pass to the specialist, and what stays with you?”
Not saved by this site. Your browser may restore text when you navigate back.
A strong answer, step by step
Open each step in turn. This is one strong answer, not the only one.
Step 1: What does the specialist need?
What would you do here? Open the move you’d make.
Send the relevant record and agreed callback time
The strong move. This carries the evidence and the promise into the next contact.
Send only the customer’s name
Tempting, but it misses something. The specialist would lack the checks and the reason for the call.
Send every unrelated case on the account
Tempting, but it misses something. The specialist needs the record for this request.
See how a strong candidate says it
“I’ll pass RC-29, the missing registration confirmation and the two places the customer checked. The callback is due by 15:00.”
Why it works: The specialist can continue the same conversation without asking the customer to repeat their work.
Step 2: Who owns an update before the call?
What would you do here? Open the move you’d make.
Keep progress updates with the first agent
The strong move. No other agent has accepted that commitment.
Treat appointment acceptance as ownership of every update
Tempting, but it misses something. It covers the call only under the stated case rule.
Close the case because the appointment exists
Tempting, but it misses something. The original question remains unresolved.
See how a strong candidate says it
“The specialist owns the accepted callback. I own any progress update before the call unless another named agent accepts it.”
Why it works: The case distinguishes the appointment from keeping the customer informed.
Step 3: How do you revise the promise?
Before 15:00, the specialist cancels the appointment. The next authorized slot is 15:40, and no other specialist can review the record earlier.
What would you do here? Open the move you’d make.
Update by 15:00 and offer 15:40 for confirmation
The strong move. It informs the customer by the promised time and respects their choice.
Wait and call at 15:40 without notice
Tempting, but it misses something. The original promise would pass without an update.
Tell them a review will finish by 15:00
Tempting, but it misses something. Nobody authorized can complete that review earlier.
See how a strong candidate says it
“The next slot is 40 minutes after the agreed time. I’ll send an in-app update by 15:00, explain the change and ask whether 15:40 works.”
Why it works: The customer has approved updates in this channel and can choose the new time.
Step 4: What will you record and carry forward?
What would you do here? Open the move you’d make.
Record the offer, confirm the time and keep the case open
The strong move. It preserves both the next commitment and the original task.
Mark the callback complete after sending the message
Tempting, but it misses something. The message explains a delay. It does not record a completed call.
Book the new slot and discard the chat
Tempting, but it misses something. The customer has not accepted the slot and the next specialist still needs the existing checks.
See how a strong candidate says it
“I’ll record the update and whether the customer accepts 15:40. I’ll keep the case open and carry the reference and the two completed checks into the new appointment.”
Why it works: The next agent can see the customer’s decision and pick up the unresolved question.
The answer, in short
- Decision
- Update the customer by 15:00 and confirm whether the 15:40 slot works.
- Because
- The earlier appointment is cancelled. The case still needs a specialist review and a named owner.
- What would change it
- If another named agent accepts the next update, record the transfer and the agreed time.
Common traps
- Treating an appointment as a completed callback.
- Requiring the customer to repeat completed checks.
Check your answer
- What question is still open?
- Which two checks follow the case?
- Who owns the update by 15:00?
- Did the customer accept the new slot?
Last reviewed Nov 11, 2026