mirror of
https://github.com/langbot-app/LangBot.git
synced 2026-10-30 20:35:22 +08:00
RockChinQ
9d2042478a
git-subtree-dir: docs git-subtree-mainline:0582d1b3d4git-subtree-split:51dddcb3f8
50 lines
1.9 KiB
Plaintext
50 lines
1.9 KiB
Plaintext
---
|
|
title: "Submit a ticket"
|
|
description: "How subscribers report issues or book consultations in LangBot Space."
|
|
---
|
|
|
|
<Tip>
|
|
[Open LangBot Space tickets →](https://space.langbot.app/profile?tab=tickets&language=en)
|
|
</Tip>
|
|
|
|
## Steps
|
|
|
|
1. Sign in with the Space account registered in your contract.
|
|
2. Go to **Profile → Tickets** and pick a template:
|
|
- **Enterprise Support: issue intake**: report a suspected LangBot Core defect
|
|
- **Enterprise Support: upgrade and consultation**: upgrade compatibility, consultation booking (Assurance), documentation and procurement materials
|
|
3. Enter your subscription/contract ID and organization name, then complete the form.
|
|
|
|
We verify the contract, registered account and service term before confirming entitlements. A subscription ID alone doesn't prove identity.
|
|
|
|
## What to include
|
|
|
|
**Issue intake**
|
|
|
|
- LangBot version and deployment method
|
|
- Expected vs. actual behavior
|
|
- Reproduction steps
|
|
- Redacted logs (explain if unavailable)
|
|
- Business impact
|
|
|
|
**Upgrade and consultation**
|
|
|
|
- Registered instance and current version, target version if relevant
|
|
- Goals and context
|
|
- Preferred times, if a meeting is needed
|
|
|
|
<Warning>
|
|
Don't submit access tokens, passwords, full chat histories, personal data or raw configuration files. Redact screenshots. Never post vulnerability details in a public GitHub issue.
|
|
</Warning>
|
|
|
|
## After you submit
|
|
|
|
Once your subscription is verified, we triage the request and may:
|
|
|
|
- Point you to documentation or ask for more information
|
|
- Book a consultation (Assurance)
|
|
- Confirm a LangBot Core defect and move it into public maintenance
|
|
- Explain that the request is out of scope
|
|
|
|
For confirmed general defects, only the minimum redacted reproduction details go into public maintenance. Contracts, logs and business information are never synced to public GitHub. Please reply in the same ticket rather than opening duplicates elsewhere.
|