Reviewing Interactions (The Audit Tab)

The Audit tab is where you review individual evaluated interactions. This is the starting point for daily QA work -- finding calls to review, examining scorecards, reading transcripts, and submitting feedback.

  1. Log in to Ema at app.ema.co
  2. Navigate to your Agent QA AI Employee
  3. Click the Audit tab

The list syncs automatically, and shows when it last did so (e.g. "Synced a few seconds ago" or "Not synced yet"). Click Refresh at any time to pull the latest data without waiting.

Each row in the interaction list displays:

FieldDescription
Interaction DetailsCombined column showing the Interaction ID (resource_id, truncated to first 12 characters with # prefix) and the Agent ID displayed below it. A New badge appears next to interactions you haven't opened yet, and clears once you view that interaction's details.
DurationCall length in seconds
QA StatusThe current state of the evaluation
QA ScoreOverall score out of 100. If the score has not been computed yet, it displays as "--".
Call Time (UTC)When the call actually took place. Immutable -- unaffected by reruns.
Ingested At (UTC)When the interaction was last processed by Ema. Normally the same as when it was first ingested, but a rerun (see 3.3 Rerunning an Interaction) updates this timestamp and floats the row to the top of the list, while Call Time stays fixed.
FeedbackCount of feedback items submitted on this interaction's scorecard.

QA Status Values

StatusWhat It Means
QA completedEvaluation is finished and the score is available. Click in to see full details.
QA in progressThe system is still processing this interaction. Check back shortly.
QA failedSomething went wrong during processing. Ema automatically retries a failed or stuck interaction internally for a period before treating it as permanently failed. If it's still failed after that, use Rerun (3.3) to trigger it manually, or check audio quality, file format, or contact your administrator.

A transcript missing an agent turn, missing a customer turn, or with no utterances at all cannot be evaluated. These rows show QA failed with a status-cell tooltip and, in the detail view, a "Could not evaluate this interaction" empty state naming the specific reason -- rather than being silently scored.

3.2 Filters and Sorting

Available Filters

FilterDescription
Date rangeCustom date range (UTC). Presets: Today, Last 7 Days, Last Week, Last 14 Days, Last 30 Days, Last Month, or custom range.
AgentDropdown to select a specific agent or view all agents.
Interaction IDText search field to find a specific call by resource ID (UCID).
QA StatusFilter by evaluation status.
QA ScoreFilter by preset score bands: Auto-fail (0), Low (1-50), Medium (51-75), High (76-100).

Sorting Options

Sort ByDirections
Call Date (default)Ascending or Descending
Call LengthAscending or Descending

Pagination

Results display 25 interactions per page. Navigation uses token-based pagination.

3.3 Rerunning an Interaction

Permission required: Builder, Manager, or Admin.

A rerun re-processes an interaction end to end -- re-transcribing/re-redacting and re-scoring -- and refreshes the same row in place with new verdicts, score, insights, and CSAT. Use it after editing a rule, fixing a processing issue, or when an interaction is stuck or failed.

  1. In the Audit tab, select one interaction, or multi-select any number of them.
  2. Click Rerun.
  3. Confirm the warning -- rerunning deletes any existing feedback on the selected interaction(s). For a multi-select, the warning states how many of the selected interactions have feedback that will be lost.

The row shows "QA in progress" while it reprocesses, then settles with refreshed results. Its Ingested At timestamp updates to the rerun time (floating it to the top of the list), while Call Time never changes.

An interaction can only be rerun while its raw source (audio or transcript) is still within its data-retention window -- see 2. Setting Up Agent QA for retention periods. Interactions past that window are shown blocked/non-selectable, since there is no longer a source to re-process.

3.4 View Interaction Details

Click View Details on any interaction to open the detailed view.

Interaction Summary

A collapsible panel at the top of the detail view gives an AI-generated plain-language summary of the call -- what the customer needed, what the agent did, and how it was resolved. It uses the same PII redaction as the transcript, so sensitive values appear as redaction placeholders (e.g. a masked name or account number) rather than the original text.

Below the summary, the detail view has the following tabs:

Scorecard Tab

The core evaluation view. A summary bar at the top shows the total parameter count with Pass and Fail totals.

FieldDescription
ResultColor-coded badge -- Pass (green), Fail (red), or N/A (gray)
Parameter name and categoryWhat was being evaluated and which group it belongs to
Pass/Fail instructionThe evaluation criteria used for this parameter
RationaleDetailed, plain-language explanation of why the parameter passed or failed. This is the most important field for understanding a score.
VerbatimsClick the "Source" accordion to expand and see the exact transcript excerpts used as evidence

Transcript Tab

Full conversation text with speaker labels and timestamps. Every speaker the transcript carries is shown under its own label -- not just Agent and Customer. A supervisor, an IVR/bot segment, or an external third party (e.g. a hotel receptionist or interpreter brought into the call) appears under its own descriptive label. QA scoring still evaluates only the interaction's designated agent; every other party, including third parties, is treated as context.

The Transcript tab does not currently have an in-panel search feature.

Strengths Tab

Positive agent behaviors identified during the interaction.

FieldDescription
DriverThe positive behavior identified (e.g., "Clear policy explanation"), displayed as bold title
CategoryThe broader behavioral category (e.g., "Communication Skills"), displayed as a badge
JustificationWhy this was identified as a strength, labeled "Key insight" in the UI

Opportunities Tab

Areas for improvement with coaching recommendations.

FieldDescription
DriverThe issue identified (e.g., "Did not confirm customer understanding"), displayed as bold title
CategoryThe broader behavioral category (e.g., "Active Listening"), displayed as a badge
JustificationWhy this was identified as an opportunity and what could have been done differently

CSAT Mapping Tab

Shows Ema's AI-derived customer satisfaction analysis for the interaction, plus any customer-submitted survey feedback ingested via the CSAT Ingestion API.

FieldDescription
Overall SummaryA banner giving the overall sentiment (positive, negative, or neutral) and a plain-language summary of the customer's experience.
Customer SatisfactionSentiment badge, evaluation text, and supporting transcript verbatims (via the "Source" accordion) for how satisfied the customer appeared.
Issue ResolutionSentiment badge, evaluation text, and sources for whether the customer's issue was resolved.
Call to ActionSentiment badge, evaluation text, and sources for any follow-up action expected from the call.
Customer BehaviorSentiment badge, evaluation text, and sources describing how the customer behaved during the call.
Customer FeedbackA survey score or comment submitted via the CSAT Ingestion API. A value of 1-5 renders as a star rating; anything else (including an emoji-derived score) renders as text. Hidden if no survey feedback was submitted.

If Ema has not yet produced a CSAT analysis for this interaction, the tab shows an empty state instead of the fields above.

Additional Data

Agent Talk Time, User Talk Time, and Dead Air are computed in the backend and stored in the database, but are not currently displayed in the evaluation details drawer in the UI.

FieldDescription
Agent Talk TimeHow much of the call the agent was speaking
User Talk TimeHow much the customer was speaking
Third-Party Talk TimeHow much any other speaker (supervisor, IVR/bot, external third party) was speaking. Only populated when the transcript carries a third party and per-utterance timestamps.
Dead AirPeriods of silence during the call

Last updated: Aug 13, 2026