CheckAI beta is in Private Preview, available only to the existing beta tester group. This includes the in-app assistant and AI file ingestion preview. Signing up, choosing a paid plan, upgrading, contacting support, or viewing a public demo does not grant access.
Where you can reach it
CheckAI is available on the channels your organization has enabled:- Slack. Mention CheckAI in a channel it’s in, or send it a direct message. It replies in the same thread. The first time you ask it to do something, it asks you to sign in and link your Soundcheck account before it acts on your behalf.
- The work dock in the web app. Click CheckAI in the bar at the bottom of the screen to open the assistant window. Use New chat to start a fresh conversation, and expand or minimize the window as you work. The same window has a Help mode for questions about using Soundcheck; people outside the preview see only Help.
- Email and SMS, where enabled for your organization.
What existing testers can do
Use whatever CheckAI channels and tools are already available to your tester account; that depends on your organization’s setup and your role.Ask about a show
Ask “What is scheduled for Friday, and which crew invitations still need a response?” CheckAI reads records your account can access.
Prepare a crew update
Ask for a message about a changed call time. Check the recipients and wording before approving a send.
Review gig paperwork
Extract proposed schedule, crew, and financial records from a call sheet or rider, then review what to commit.
Work through a staffing task
Inspect open positions and candidate crew, then review the proposed invitations before contacting people.
A practical example
For a fictional production company’s conference, start with: “Summarize tomorrow’s crew, load-in time, and any unanswered invitations.” Check the answer against the gig and venue instructions. If the call time has changed, update the show record and ask CheckAI to prepare a message for the affected crew. Review the recipient list and message before approving it. AI output can miss details or misread paperwork. Review dates, time zones, names, fees, and destination records before applying a proposal.Review and confirmation
CheckAI uses your account’s permissions. It does not expand your access to another organization’s records or to features outside your preview. Actions such as sending messages, committing imports or ingestion proposals, converting leads, and deleting supported records require confirmation through the connected tools. A confirm card shows the proposed change before anything happens: what CheckAI wants to do, and for a record change, the specific fields it wants to add, remove, or update. Choose Approve or Reject. If the data changes during review, refresh the proposal before continuing. See the MCP security model for the connected tools’ authorization and confirmation behavior.CheckAI and external AI clients
The Soundcheck MCP integration lets supported external AI clients connect to Soundcheck tools. It is a separate integration with its own authentication and available tools. Connecting Claude Code, Cursor, or another MCP client does not enroll an account in CheckAI Private Preview. Public MCP helpers can draft or validate the Universal Event Format. Reading or changing your organization’s live records still requires you to be signed in with the right access. A public demo is separate from your organization’s live records and does not grant beta access.Related
MCP server
Set up the separate external-client integration.
AI file ingestion
Review and commit paperwork proposals in the Private Preview.
Universal Event Format
Understand the structured event format.