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.
What existing testers can do
Use the CheckAI surface already available to your tester account. Channels and tools depend on that preview’s configuration and your organization 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. Review the summary of the specific action before approving. 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; access to live organization records and write actions requires the appropriate signed-in 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.