Submit a support ticket

Subscriber? Submit a ticket

Sign in with the Space account registered in your contract. Open Profile → Tickets and choose Enterprise Support: issue intake or Enterprise Assurance: upgrade and consultation. Templates are available to signed-in users; staff verify the contract, registered account and service dates before confirming enterprise entitlements. A subscription number is not proof of identity.

Information to provide

• Subscription/contract number, organization, request type and summary.
• Defects: LangBot version, deployment method, expected and actual behavior, reproduction steps and business impact.
• Redacted log excerpts; explain if unavailable. Do not include tokens, passwords, full conversations, personal customer data or raw configuration files.
• Upgrade/consultation: registered instance, current/target versions where relevant, goals and preferred meeting times.
• Documentation or procurement-material questions do not require invented logs or reproduction steps. Use the consultation form to describe the request; technical consultation sessions are an Assurance benefit.

Forms collect text and do not automatically collect instance data or generate a diagnostic archive. Only attach necessary, redacted screenshots. Do not post vulnerability details in public GitHub issues.

What happens next

The team checks the subscription and scope, then provides documentation guidance, asks for information, schedules an eligible consultation, identifies a public Core defect, or explains an exclusion. Automatic email notifications are not a first human response.

Only necessary, redacted reproduction details for confirmed general defects enter public maintenance. Contracts, customer logs and business information are not automatically copied to GitHub. Continue in the same ticket instead of duplicating requests across channels.