Help next to the work, and support with the evidence attached.
Each dashboard page links to its guide, the guides are searchable from the dashboard and by agents, and a support request carries only the evidence you agree to share.
Learn more on every panel
Every dashboard page and website section has a Learn more link to the guide that covers it, and to the guide's Markdown twin: the same address followed by .md. Agents read the same text through the twins and llms.txt, which lists every guide.
Search the guides
Press Ctrl K (Cmd K on a Mac) in the dashboard, or use Help & support. The search covers these guides, their Markdown twins and the agent guides. Agents use the MCP tool help_search, the REST route GET /api/v1/help/search?q=domains or the CLI command docs-search domains.
Platform status
When an externally hosted status page and outside checks are configured, they can continue reporting if this application server is down. A configured URL alone does not prove independent monitoring. The dashboard, the REST route GET /api/v1/platform-status, the MCP tool platform_status and the CLI command status show its latest summary and open incidents. When no external status page is configured they say so: DeployBeacon never shows an "all systems operational" answer measured on the same server. No uptime percentage is promised during the private beta.
Send a support request
Open Help & support, choose a category and describe what happened. You then choose what to attach: the request IDs of recent failed requests (the Ref shown with each error), the project's name, address, status and live release, and recent findings, meaning the codes and severities from its latest inspection and security scan. Nothing is attached unless you tick it and give your consent to share it. File contents, contact-form messages, passwords and tokens are never attached. Each person can send 10 requests a day.
Hand off from an assistant
A connected assistant can prepare a draft with the MCP tool support_handoff, or the CLI command support-handoff draft.json --confirm with a scoped token. The JSON contains subject, summary and optionally category, projectId and requestIds, within 16 KiB. Keep credentials and file contents out of it. The draft is visible only to you and the operator never sees it. Open its review link, check the text, choose what to attach and send it. An assistant cannot send a draft or agree to share evidence on your behalf.
Replies and history
Replies appear in Help & support, where you can answer, close or reopen the request. Optional email copies use the configured Microsoft Graph service and your verified primary address. A queued copy is not yet submitted; Accepted means the provider accepted the request, not that you received it. Unavailable, expired or uncertain copies are shown honestly, and your dashboard reply remains available. Assistants can read a request and its replies with support_list and support_get. Requests are included in account and workspace data exports.
Who can see a request
You, the platform operator, and the owners and admins of the workspace once it is sent. Drafts are visible only to the person who will send them. See the roadmap for what is planned and the deprecation policy for how changes are announced.
Explore the product and guides
Access is invitation-only. No payments are collected during the private beta. Sign in to your invited workspace.