Daily operations

Conversation detail

Read the transcript, understand decisions, and continue an authorized workspace conversation.

Know the panels

PanelPurpose
TranscriptMessages with speaker labels, timestamps, and redaction markers.
ActionsRequested operations, rule reasons, recorded status, provider references, and errors.
How this was handledPersisted processing stages. Sending a turn shows the newest trace and decision reasons.
Who this isIdentity state and caller address; a verification form appears when a matching record and current verification request are available.
Details gatheredCollected administrative fields and information still needed.
ReferenceConversation ID, linked agent, intent, and confidence when recorded.

Review an existing conversation

  1. Read the full transcript before deciding what to do.
  2. Compare the requested outcome with Details gathered; note anything still missing.
  3. Inspect the identity state. A matched record is not yet verified.
  4. Read the decision trace to find the stage that stopped progress.
  5. Check each action’s status and provider reference rather than relying on the conversation title or closing state.
  6. For approvals and handoffs, use Review queue. For interpretation feedback, use Intelligence.

Send a workspace turn

  1. Use this with an owner, admin, or supervisor account and approved test or staff-operated data.
  2. In an unresolved conversation, enter the next caller statement in Type what the caller says next. If the agent is waiting for information, the placeholder identifies the first missing field.
  3. Choose Send once and wait for the result.
  4. Read the updated reply, decision, trace, gathered details, and actions.
  5. If a supported live connection is present, a permitted action can update the real provider. Check the resulting status.

Verify identity when prompted

  1. Read which fields the current request requires.
  2. Enter the authorized verification answers in the displayed fields.
  3. Choose Check details and review the resulting identity state.
  4. Continue with the held request as directed by the reply or current conversation state.
  5. If verification fails repeatedly, follow the staff-review process instead of bypassing the rules.

The current implementation sends five failed verification attempts to staff review. The form is conditional: it appears when the conversation is matched and the latest workspace turn requested verification. An administrator must ensure the identity source and verification fields are appropriate for the workflow.

Mark resolved

  1. Confirm that the request and any needed staff follow-up have been addressed.
  2. Choose Mark resolved at the top of the page.
  3. The conversation becomes Resolved and the turn form is no longer displayed.

Closing a conversation records its closure. It does not approve a pending action, reconcile an uncertain provider response, or establish that a staff team accepted a transferred call.

Review participating agents

Team conversations include Participating agents. Review each specialist name and the reason it was selected, then open that agent to inspect its own rules. The coordinator remains the public voice. Actions keep the responsible specialist ID even when another specialist handles a later request.

Need help with your organization? Contact Korenact or your workspace administrator.

This guide describes the current workspace. Availability depends on your organization’s deployment and configured providers.