Skip to main content
A Participant is a named individual linked to transcription jobs — a support agent, job candidate being interviewed, salesperson, or any person whose performance you want to track. Attaching a participant to a transcription lets the platform attribute quality metrics to that individual and track their performance over time. For the full data model, see Participant.
Unlike Configurations and Evaluators, there are no separate create or detail pages. All creation and editing happens in a side drawer that slides in from the right without leaving the list.

Your participants

Search, sort, and filter in real time by name or participant ID. Sort by name or last updated date (ascending/descending). Toggle between card grid and table layout.

Metadata filters

Click the sliders icon (to the right of the search bar) to expand the metadata filter panel. The panel generates filter dropdowns dynamically from the actual metadata keys present in your participants — no pre-configuration needed. Each dropdown shows all values found for that key across your participants. Selecting a value narrows results to participants that have that exact value for that key.
BehaviorDetail
Active filter badgeA number bubble on the sliders icon shows how many filters are currently active — no need to open the panel to check
AND logicAll filters are combined as an intersection — results must match every active filter simultaneously
Cross-filter with searchText search and metadata filters apply together — type a name and set a role filter at the same time
Clear filtersA “Clear filters” link appears in the panel header when any filter is active
No results stateWhen no participants match the active combination, a “No results” message includes a button to clear all filters and the search text at once
Each participant has a gradient avatar showing their initials. The color is determined by their name — the same name always produces the same gradient. Metadata is shown as pills directly on each card: grid view shows the first 4 entries, table view shows the first 2, with a +N more badge when there are additional fields. To delete participants, hover over a card or row to reveal a checkbox in place of the avatar. Select one or more items, then click Delete in the blue action bar that appears. A confirmation modal is shown before deleting.
Single-item deletion works the same way — select its checkbox and use the Delete button. There is no delete option inside a drawer.

Creating a participant

Click New Participant to open the drawer.

Name (required)

The participant’s display name — their label throughout the platform. As you type, a live gradient avatar preview updates in real time showing the initials and color that will be assigned to this participant.

Metadata (optional)

Structured key-value pairs that describe the participant. Max 10 fields, shown with a N / 10 counter. Use the preset quick-add chips to add common fields instantly:
ChipKeyExample value
Emailemailagent@company.com, candidate@example.com
RoleroleSupervisor, Agent, Candidate, Interviewer
Phonephone+1 600 000 000
DepartmentdepartmentCustomer Support
RegionregionNew York, London
LanguagelanguageEN, ES, FR
TimezonetimezoneUTC+1
SkillsskillsSQL, Customer Service
Employee IDemployee_idEMP-001
Clicking a chip adds a row with the key pre-filled. A chip is disabled once that key is already in the form. For any field not listed above, click + Add custom field to add a blank row.
Keys must be unique within a participant. Rows left completely empty are silently ignored on save.
Click Create Participant in the sticky footer to save. The drawer closes automatically on success.

Editing a participant

Click any card or table row to open the Edit Drawer. The drawer header shows the participant’s ID with a copy button. The same name and metadata fields are available. The participant name can be changed after creation.
Updating metadata replaces the entire metadata object — keys not included in the update will be lost. To preserve existing fields, include them in the update. See Participant — metadata.
Click Save Changes in the sticky footer to confirm, or close the drawer to discard.

Metadata keys reference

KeyCommon use
emailagent@company.com, candidate@example.com
roleSupervisor, Agent, Candidate, Interviewer
phone+1 600 000 000
departmentCustomer Support
regionNew York
languageEN, ES
timezoneUTC+1
skillsSQL, Customer Service
employee_idEMP-001
Any key not listed above is stored normally and displayed with a generic icon.

Participant

Full data model and metadata reference

Participant Analysis

View performance insights for this participant