Follow the onboarding checklist, activate an assistant profile and test with your own information. The console shows what is ready and what still needs attention before your assistant can serve customers.
Create an account, review the agreements shown during signup and verify your email. After signing in, the welcome page lists the requirements that apply to your deployment. You can invite teammates at any time: they are not taken through setup, and go straight to the areas their role opens; see team and access.
Channel access, content readiness and assistant activation are separate requirements. Uploading a document or writing a goal does not assign a profile.
In Assistant → Setup, describe your organization, the work customers need help with, the information you will provide, any sensitive data, and situations that need a person. Review the resulting checklist and proposed capabilities.
Complete the requirements and use the activation control when it becomes available. Some profiles require MFA or a platform review. If review is required, request it from Setup and wait for the displayed status to allow activation. Revisit Capabilities to see what the active configuration permits.
After activation, shape the assistant through Behavior and Goals, a reviewed setup template, or supplemental Agent Guidance. These configuration paths are explained in assistant setup and guidance.
Start at Content Home. Use Knowledge for business information and policies, Catalog for structured products, and Media library for photos of your products and services your assistant may share. Knowledge accepts supported PDF, Word, spreadsheet, text and Markdown files, or pasted text; the uploader shows file limits.
Wait for processing to finish, inspect the result and review the exact content. Processing status and approval status are different: an indexed source can still need approval, and an edited source can have an outdated approval. Where the publication boundary is enabled, only content that passes its current approval and validity checks can serve. Media must be published before it is eligible for sharing.
See Knowledge, catalog and carts and media and voice for their distinct workflows.
Open Settings → Channels & routing. Connect your WhatsApp Business number using the available Meta connection flow or supported manual credentials, or connect a Telegram bot using its BotFather token. Follow verification and readiness results before enabling the channel. For web chat, use Settings → Web widget, add allowed origins and install the supplied snippet.
Send a real test message. Check that it reaches the correct workspace, uses current information, appears in Conversations and responds through the same channel. Test any enabled cart, appointment or handoff workflow separately. Full connection instructions are in channels.
Where the platform publishes shared channels, Demo links provides WhatsApp links, Telegram links and QR codes using your routing tag. Open a link and send the pre-filled routing command. The conversation then uses your workspace configuration.
Demo links concern the shared sandbox only — a missing routing tag or private directory visibility can suppress them, and neither affects your own WhatsApp number, Telegram bot or website widget, which reach your workspace without a tag. Demo availability also depends on shared-channel policy and your onboarding state. A demo link does not bypass subscription, profile or capability requirements. Connect your own channel for a production identity.