Request context
Include the route, approximate time, and non-sensitive request ID.
Support
A direct path for bounded help.
Ask about pilot access, integration, billing, privacy, or provider participation. Replies are handled by the ResolveMesh operator; no guaranteed response time is offered during the private pilot.
Useful context
Send identifiers, not payloads
A compact operational description is enough to begin an investigation without expanding the data boundary.
Expected and observed state
Describe the expected status and the status or error code received.
Account context
Include the organization name and billing email when relevant.
Submission boundary
Keep sensitive content out of support
Do not send credentials, raw prompts, documents, personal data, provider response bodies, or tool output. Revoke any secret accidentally disclosed before contacting support.
Secrets and credentials
Never send API keys, tokens, OAuth grants, cookies, or private keys.
Prompts and documents
Summarize the capability requirement without source content.
Provider output
Share a bounded error code or status, not the provider payload.