Find the unanswered handoff.
See conversations passed to the team without a person’s reply after the configured wait. The source and operating hours determine the alert.
AI-to-human handoffsCarry on.
Carry on.
Without the catch-up.
Know when AI has passed the conversation to a person and the customer is still waiting. Claim it with the history in view.
New hands.
Same conversation.
The handoff is recorded, but the reply has not happened. BearScope puts the waiting customer in the queue so someone can take responsibility.
AI agent · June
This needs a person.
The customer is asking for an exception outside the agent’s role.
Context included
Conversation history, linked order, and the unresolved request.
Support team · Alex
Ready to pick it up.
Alex can review the source and decide how to handle the exception.
Read the handoff note
Maya’s order now shows Friday. She is requesting a delivery exception. June has read the order but has not promised an exception or changed the record.
Example handoffProduct preview with example data.
Claim the follow-up.
Give the work one owner, read what was tried, and open the source conversation to respond.
Check what happened next.
Observed replies can close the waiting item. A person can also mark it handled or dismiss a false alert with a reason.
Questions,
answered.
Are possible missed promises verified?
AI-detected promises appear separately as unverified findings. A person checks the conversation before treating one as a missed commitment.
Where does the team reply?
In the connected conversation system. BearScope coordinates the follow-up and evidence; its current action gateway does not send messages.
Can we inspect the AI’s role?
Yes. Quality shows agent handoffs and performance, while Settings and Approvals hold decision rules, shadow results, and held actions.