See the work it leaves behind.
Review AI handoffs and conversation evidence in Quality. Use the decision ledger to see shadow assessments, acted decisions, and requests passed to a person.
See decisions and handoffs, set the rules, and review what needs a person. Try an agent draft on the test bench before a separate deployment.

Keep AI oversight close to the work: agent performance in Quality, held decisions in Approvals, and rules, skills, and drafts in Settings.
Decision recorded in shadow. No action executed.
Inspect the available evidence, proposed response, and configured mode. A recorded decision and an executed action are different events.
Current app workflow with fictional records. Features depend on connected sources and workspace access.

Review AI handoffs and conversation evidence in Quality. Use the decision ledger to see shadow assessments, acted decisions, and requests passed to a person.
Configure decision thresholds, guardrails, and approved skills. Read access and permission to change a record are separate; only supported, enabled actions may run.
Choose an approved model, write a prompt, and run a scripted conversation against the active rubric. Bench tools are off. Save or export the configuration; deployment is a separate step.
Quality contains AI performance and handoffs. Approvals contains held plans, decisions, and matches. Settings contains decision rules, automations, guardrails, skills, and draft agents.
No. The bench tests a prompt with tools off and scores the transcript where a rubric is available. Deployment and connected-tool checks happen separately.
Supported gateway actions acknowledge, resolve, or reopen internal BearScope worklist records. They do not send customer messages or change fulfillment in another system.
Yes, for configured decision panels. Shadow results record what was assessed without executing an action. The app shows the mode in use.