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

# CheckAI — the Soundcheck assistant

> CheckAI is Soundcheck's AI layer — read and act on your live-event data in plain language, and turn gig paperwork into structured records.

**CheckAI** is Soundcheck's AI layer over your live-event operations. It reads your events, crew, availability, setlists, and CRM, and runs the everyday workflows of putting on a show — in plain language, from where your team already works.

CheckAI runs on the same [Model Context Protocol (MCP) server](/integrations/mcp-server) that powers Claude Code and Cursor, so it acts strictly **as you**: it sees only what your account can see, and the consequential actions (messaging real people, committing imports) require your explicit confirmation first.

CheckAI has two sides:

<CardGroup cols={2}>
  <Card title="AI file ingestion" icon="file-import" href="/features/ai/file-ingestion">
    **Available now.** Drop a contract, call sheet, rider, or email thread onto a gig and CheckAI extracts the schedule, crew, money, and leads into a clean draft you review before it's written.
  </Card>

  <Card title="Conversational assistant" icon="comments">
    Ask about your week, clear pending offers and invitations, build and message a crew — in chat. <strong>Coming soon</strong> on Slack (see below).
  </Card>
</CardGroup>

## AI file ingestion (available now)

Gig details rarely arrive as clean data — they show up as PDFs, call sheets, riders, and forwarded emails. CheckAI reads those files and proposes the structured records: a timeline, a crew list with fees, ledger items, and any leads. You review every proposal and choose what gets written. Nothing lands on the event until you commit.

This is the same pipeline you can drive from the [MCP ingestion tools](/integrations/mcp-server#available-tools) in Claude Code or Cursor. See the full walkthrough:

<Card title="AI file ingestion" icon="wand-magic-sparkles" href="/features/ai/file-ingestion">
  Upload → analyze → review → commit, and how it maps to the Universal Event Format.
</Card>

## Conversational assistant (coming soon)

<Info>
  The conversational CheckAI assistant on **Slack** is rolling out. The capabilities below already exist through the [MCP server](/integrations/mcp-server) for Claude Code and Cursor today; the Slack experience — `@checkai` mentions, DMs, and one-tap account linking — is in progress. Want early access? [Contact support](mailto:support@soundcheck.live).
</Info>

Once live, you'll be able to, right inside Slack:

<CardGroup cols={2}>
  <Card title="Ask & get briefed" icon="message">
    "What's on for this week?" or "Summarize Friday's show and who's playing what." CheckAI pulls your gigs and pending actions into one answer.
  </Card>

  <Card title="Clear your queue" icon="handshake">
    Accept or decline invitations and crew offers, set your availability, and respond to availability requests — without leaving the thread.
  </Card>

  <Card title="Build & staff events" icon="calendar-plus">
    Create or duplicate a gig, attach a venue, add members, and draft a call list from chat.
  </Card>

  <Card title="Reach your crew" icon="paper-plane">
    Draft and send an SMS or email to a roster — CheckAI previews recipients and the message, and only sends after you reply <strong>YES</strong>.
  </Card>
</CardGroup>

## How it stays safe

CheckAI acts as you, never as an admin, and it never deletes data or changes billing. The truly consequential tools — sending messages, broadcasting reminders, and committing an import or ingestion — run through a **confirmation gate**: CheckAI shows you a plain-language summary of exactly what will happen and does nothing until you approve. A single stray instruction can't message your crew or write to a gig.

See the full [MCP security model](/integrations/mcp-server#security-model) for how this is enforced.

## Related

<CardGroup cols={3}>
  <Card title="MCP server" icon="robot" href="/integrations/mcp-server">
    Connect Claude Code or Cursor to the same tools.
  </Card>

  <Card title="File ingestion" icon="file-import" href="/features/ai/file-ingestion">
    The live upload → review → commit flow.
  </Card>

  <Card title="Universal Event Format" icon="code" href="/features/imports/universal-event-format">
    The canonical shape every ingestion produces.
  </Card>
</CardGroup>