> ## 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.

# Smaya Capabilities

> What Smaya is designed to do across Exterview, by area: the ask-and-navigate actions available first, and the acting capabilities that run with human approval.

The goal for Smaya is simple: anything you can do on Exterview, you should be able to do by asking. Smaya hasn't shipped yet — its first release will cover the read-and-navigate half of that. The acting half comes later and always runs through a human approval gate, so nothing consequential happens without a person confirming it. See [Meet Smaya](/smaya/overview) for the tier model and [How It Works](/smaya/how-it-works) for the loop.

<Note>
  Each capability below is tagged **Coming first** (read and navigate, no data
  changes — arriving in Smaya's first release) or **With approval** (an acting
  capability further out on the roadmap that proposes, then waits for you to
  confirm). Example prompts are illustrative, not a fixed command syntax.
</Note>

## Coming first: ask, explain, navigate

Read-only, and not available yet. Once live, Smaya will answer and take you places, without ever changing data in this tier.

<CardGroup cols={2}>
  <Card title="Understand a candidate" icon="user">
    Get a plain-language summary of a candidate's fit, strengths, and gaps for the role on screen.

    *Ask: "Summarize this candidate's fit for the role."*
  </Card>

  <Card title="Read back a report" icon="file-lines">
    Pull the key points from any completed evaluation without opening and scrolling it.

    *Ask: "What did the phone screen flag for this candidate?"*
  </Card>

  <Card title="Compare candidates" icon="scale-balanced">
    Put the top candidates for a role side by side on the dimensions that matter.

    *Ask: "Compare the top three candidates for this job."*
  </Card>

  <Card title="Explain a score or verdict" icon="magnifying-glass-chart">
    See the reasoning and the evidence behind a score, so a decision is defensible.

    *Ask: "Why did this candidate score well on communication?"*
  </Card>

  <Card title="Check a pipeline" icon="diagram-project">
    Ask where a role stands: who is in which round, and who is waiting on a decision.

    *Ask: "Which candidates are waiting on a decision for this job?"*
  </Card>

  <Card title="Find and navigate" icon="compass">
    Jump straight to a job, a candidate, or a view instead of clicking through menus.

    *Ask: "Open the leaderboard for this role."*
  </Card>
</CardGroup>

## With your approval: acting

<Info>
  These are the acting capabilities, on the roadmap. Each one **proposes** an
  action and waits for you to approve before anything changes. Actions that
  spend money, message candidates, or change a hiring decision always require
  confirmation, and every approval is recorded. None of this executes on its
  own.
</Info>

<CardGroup cols={2}>
  <Card title="Create a role" icon="file-plus">
    Turn a JD or a short brief into a drafted role with screening configured, for you to review and publish.

    *Ask: "Draft a backend engineer role from this JD."*
  </Card>

  <Card title="Add candidates" icon="user-plus">
    Bring candidates into a role from your pool or an upload, ready for you to confirm.

    *Ask: "Add these candidates to the pipeline for this role."*
  </Card>

  <Card title="Run an evaluation" icon="paper-plane">
    Line up a phone screen, voice, or other round for selected candidates. You approve before any invite or call goes out.

    *Ask: "Send a phone screen to the shortlisted candidates."*
  </Card>

  <Card title="Move candidates" icon="arrow-right-arrow-left">
    Advance or hold candidates across rounds in one step, on your confirmation.

    *Ask: "Advance these two candidates to the next round."*
  </Card>

  <Card title="Record a decision" icon="gavel">
    Log or override a verdict with a note. The change is proposed, and the approval is captured in the audit trail.

    *Ask: "Mark this candidate as hold, with a note about availability."*
  </Card>

  <Card title="Offer and post-hire" icon="handshake">
    Draft an offer or start a post-hire check-in as the funnel's later stages come online.

    *Ask: "Draft an offer for this candidate."*
  </Card>
</CardGroup>

## The rule for every action

The controls do not change as capability grows. Read and navigate assist you directly. Anything that changes data is proposed and held until a person approves it, and every answer and approval is grounded, specific to your organization, and audited. See [Human Oversight](/smaya/oversight) for the full control model.

## FAQs

<AccordionGroup>
  <Accordion title="Which of these can I use today?">
    None yet — Smaya hasn't shipped. The ask, explain, and navigate capabilities will be the read-only first release. The acting capabilities come later and add the propose-and-approve step. See [Upcoming](/product-updates/upcoming) for timing.
  </Accordion>

  <Accordion title="Will Smaya ever take an action without asking me?">
    No. Read and navigate assist you directly. Every action that changes data,
    spends money, or messages a candidate is proposed and waits for your
    confirmation.
  </Accordion>

  <Accordion title="Do I have to phrase requests a specific way?">
    No. The prompts here are examples. Smaya interprets natural requests in the
    context of the record you are viewing.
  </Accordion>

  <Accordion title="Can Smaya do something I do not have permission to do?">
    No. Smaya operates within your own role and your organization's permissions. It cannot reach data or actions you could not reach yourself.
  </Accordion>
</AccordionGroup>

## Related

<CardGroup cols={2}>
  <Card title="Meet Smaya" icon="compass" href="/smaya/overview">
    The three tiers and the governed foundation.
  </Card>

  <Card title="How It Works" icon="arrows-spin" href="/smaya/how-it-works">
    The loop, and how an action gets approved.
  </Card>

  <Card title="Human Oversight" icon="user-check" href="/smaya/oversight">
    The approval gate and control model.
  </Card>
</CardGroup>