Skip to content

docs: describe support channels and what to include in a support request - #31945

Closed
coder[bot] wants to merge 1 commit into
mainfrom
docs/support-request-guidance
Closed

coder[bot] wants to merge 1 commit into
mainfrom
docs/support-request-guidance

Conversation

@coder

@coder coder Bot commented Nov 9, 2026

Copy link
Copy Markdown
Contributor

Expands the Support landing page, which currently only points to GitHub issues and Discord:

  • Splits Community support (GitHub, Discord) from Premium support (the Coder support portal and the account team).
  • Adds What to include in a support request: version (GET /api/v2/buildinfo), support bundle and logs, reproduction steps, impact, and deadlines. Deadlines matter most here: knowing a customer's event or rollout date early changes how we prioritize.
  • Notes that a proposed fix is welcome but doesn't replace reproduction details.

The manifest description already mentions premium support, so no manifest change is needed.

Needs Support / CS confirmation before merge

  • OK to publish help.coder.com as the Premium support entry point
  • Wording for contacting the account team, and whether to mention shared Slack channels
  • Wording of the proposed-fix paragraph

Linear: DOCS-1731

@coder
coder Bot temporarily deployed to main November 9, 2026 23:37 Inactive
@coder
coder Bot temporarily deployed to main November 9, 2026 23:37 Inactive
@github-actions github-actions Bot added the community Pull Requests and issues created by the community. label Nov 9, 2026
@coder
coder Bot requested a review from nickvigilante November 9, 2026 23:37
@linear-code

linear-code Bot commented Nov 9, 2026

Copy link
Copy Markdown

DOCS-1731

@nickvigilante
nickvigilante marked this pull request as ready for review November 10, 2026 14:58
@nickvigilante
nickvigilante temporarily deployed to main November 10, 2026 14:58 — with GitHub Actions Inactive
@nickvigilante

Copy link
Copy Markdown
Collaborator

Closing and reopening under a human author, as required for this repository.

@nickvigilante
nickvigilante temporarily deployed to main November 10, 2026 15:55 — with GitHub Actions Inactive
@nickvigilante
nickvigilante temporarily deployed to main November 10, 2026 15:55 — with GitHub Actions Inactive
@nickvigilante
nickvigilante temporarily deployed to main November 10, 2026 15:55 — with GitHub Actions Inactive
@github-actions github-actions Bot locked and limited conversation to collaborators Nov 10, 2026
@nickvigilante
nickvigilante temporarily deployed to main November 10, 2026 15:55 — with GitHub Actions Inactive

This branch was previously deployed

1 inactive deployment
main — 0c221c1b Deployed Nov 10, 2026 by nickvigilante via cla #253489
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

community Pull Requests and issues created by the community.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant