> ## Documentation Index
> Fetch the complete documentation index at: https://docs.exterview.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Operations

> Operational configuration in Exterview covering channels, pipeline stages, rubric concepts, gating rules, candidate communication, and connector integrations.

<Info>
  **Applies to Enterprise.** Operations is part of the full configuration set,
  guided during Enterprise onboarding. Starter and Growth don't configure this,
  see [Configure Overview](/configure/overview).
</Info>

## Purpose

Operations defines how evaluations actually run, the channels, the journey, how scoring is structured, and how candidates are contacted. It builds directly on your [Foundation](/configure/foundation): your org structure and calibration become a running hiring process here, and [Governance](/configure/governance) wraps it next.

<Note>
  Public documentation explains the model and the process, not the values. Exact
  scoring weights, thresholds, session limits, and billing meters are never
  published, they live in your signed configuration.
</Note>

## Interview channels

The channels a candidate can be evaluated through. Not all channels are live yet — see [Session Types](/deploy/session-types) for current availability.

<CardGroup cols={3}>
  <Card title="Phone Screen" icon="phone">
    Short phone screening for qualification signals.
  </Card>

  <Card title="Voice" icon="microphone">
    AI voice screening interview.
  </Card>

  <Card title="Avatar" icon="video">
    AI avatar (video) interview.
  </Card>

  <Card title="Panel" icon="users">
    Panel evaluation with consolidated scoring.
  </Card>

  <Card title="HR" icon="user-tie">
    HR / behavioral round, including offer and likelihood-to-join.
  </Card>

  <Card title="Skill Assessment" icon="clipboard-check">
    Role-relevant skill assessment.
  </Card>
</CardGroup>

## The rest of Operations

<CardGroup cols={2}>
  <Card title="Pipeline Templates" icon="diagram-project">
    Reusable hiring-journey structures you apply to roles.
  </Card>

  <Card title="Scoring Rubrics" icon="list-check">
    How evaluation criteria are structured, the dimensions, not the weights.
  </Card>

  <Card title="Assessment Types" icon="clipboard-list">
    Role-relevant evaluation modes for different roles.
  </Card>

  <Card title="Evaluation Gating" icon="filter">
    Whether a step is a gate or a signal (see below). Coming soon.
  </Card>

  <Card title="Candidate Communication" icon="comments">
    Email and interview links today; SMS and WhatsApp are coming soon.
  </Card>

  <Card title="Enterprise Connectors" icon="plug">
    Customer systems that trigger or support workflows.
  </Card>
</CardGroup>

## Gate vs. signal

<Note>
  This distinction is planned and not yet configurable. Today, every step
  informs the decision without automatically blocking a candidate's progress.
</Note>

Each evaluation step will be configured as one of two things:

```mermaid theme={null}
%%{init: {'theme':'base','themeVariables':{'primaryColor':'#EEF2FF','primaryBorderColor':'#4B6CFE','primaryTextColor':'#0F172A','lineColor':'#64748B','clusterBkg':'#F8FAFC','clusterBorder':'#E2E8F0'}}}%%
flowchart LR
  A([Evaluation step]) --> B{Gate or signal?}
  B -->|Gate| C([Blocks progress])
  B -->|Signal| D([Informs decision])
```

| Type       | What it does                                                       |
| ---------- | ------------------------------------------------------------------ |
| **Gate**   | A pass/fail checkpoint that controls whether a candidate advances. |
| **Signal** | An input that informs the decision without blocking progression.   |

## FAQs

<AccordionGroup>
  <Accordion title="Which channels do we have to use?">
    Only the ones that fit your roles. Channels are enabled per role and per pipeline during setup.
  </Accordion>

  <Accordion title="Do you publish scoring weights or thresholds?">
    No. Public docs describe how rubrics and gating work; the actual weights,
    thresholds, and limits stay in your signed configuration.
  </Accordion>

  <Accordion title="What's the difference between a gate and a signal?">
    A gate can stop a candidate from advancing; a signal informs the decision but
    doesn't block it. Gating is planned and not yet configurable, so today every
    step behaves as a signal.
  </Accordion>

  <Accordion title="Can candidates be contacted on WhatsApp?">
    Not yet. Email is supported today, subject to your communication and consent settings. SMS and WhatsApp are coming soon.
  </Accordion>
</AccordionGroup>

## Related

<CardGroup cols={2}>
  <Card title="Deploy" icon="rocket" href="/deploy/overview">
    Launch the sessions you've configured here.
  </Card>

  <Card title="Governance Setup" icon="shield-halved" href="/configure/governance">
    Control who runs and reviews them.
  </Card>
</CardGroup>