Update getting-help contact guidance and Discord branding#490
Update getting-help contact guidance and Discord branding#490
Conversation
Co-authored-by: WcaleNieWolny <50914789+WcaleNieWolny@users.noreply.github.com>
Co-authored-by: WcaleNieWolny <50914789+WcaleNieWolny@users.noreply.github.com>
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 5f0f4d8517
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
|
||
| ## Support by email | ||
|
|
||
| Email is the recommended way to get support. |
There was a problem hiding this comment.
Changing the sentence to Email is the recommended way to get support. reverses the page’s previous Discord-first guidance and conflicts with the rest of this document, which still walks users through posting in Discord (including sharing the secure account ID there). For users following this page, this can reroute requests to a slower/manual channel and undermine the intended triage flow in src/content/docs/docs/getting-help.mdx.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Pull request overview
This PR updates the “getting help” documentation to remove wording that implies response-speed guarantees for Discord support, and adjusts the placement/copy of the email support section.
Changes:
- Removed the “fastest ways to get a response” phrasing from the Discord support sentence.
- Moved the “Support by email” section above the Discord section and updated its copy.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| ## Support by email | ||
|
|
||
| Email is the recommended way to get support. | ||
|
|
||
| If you need to contact us by email, please send an email to support@capgo.app. |
There was a problem hiding this comment.
The PR description says this change only removes the response-speed claim from the Discord sentence, but this hunk also moves the email section above Discord and changes the guidance from "slowest way"/"use Discord first" to "recommended way". Either update the PR description to match this broader behavior change, or revert/limit the email copy changes to keep the PR focused.
There was a problem hiding this comment.
Updated the PR description checklist to reflect the email-first guidance and confirmed the copy remains in place. Screenshot: https://github.com/user-attachments/assets/1e7c6330-0fbc-4604-ad64-d3779cb68cb0. Commit: 829a5bc.
| ## Support by discord | ||
|
|
||
| Capgo has an official [discord server](https://discord.capgo.app). Getting tech support there is likely one of the fastest ways to get a response. | ||
| Capgo has an official [discord server](https://discord.capgo.app). |
There was a problem hiding this comment.
Capitalization: "discord" should be "Discord" in headings and in the sentence text (proper noun/brand). This also matches usage elsewhere in the docs (e.g., src/content/docs/docs/cli/cloud-build/getting-started.mdx:287).
There was a problem hiding this comment.
Capitalized Discord in the heading and sentence text. Screenshot: https://github.com/user-attachments/assets/1e7c6330-0fbc-4604-ad64-d3779cb68cb0. Commit: 829a5bc.
| @@ -33,9 +39,3 @@ To share this, please go to [capgo's settings](https://console.capgo.app/dashboa | |||
| <figure><img style="margin-left: auto; margin-right: auto" src="/share-secure-id.webp" alt="Share your id without leaking your info" /><figcaption></figcaption></figure> | |||
|
|
|||
| This will copy the secure account id to the clipboard. Please include that in your discord post. | |||
There was a problem hiding this comment.
Capitalization: consider "Discord post" instead of "discord post" for consistency with the rest of the docs and the "Discord" brand capitalization.
There was a problem hiding this comment.
Updated the copy to say “Discord post” for consistent capitalization. Screenshot: https://github.com/user-attachments/assets/1e7c6330-0fbc-4604-ad64-d3779cb68cb0. Commit: 829a5bc.
There was a problem hiding this comment.
Already updated the copy to “Discord post” for consistent capitalization. Screenshot: https://github.com/user-attachments/assets/1e7c6330-0fbc-4604-ad64-d3779cb68cb0. Commit: 829a5bc.
Co-authored-by: WcaleNieWolny <50914789+WcaleNieWolny@users.noreply.github.com>
|
|
Just as a heads up, I was blocked by some firewall rules while working on your feedback. Expand below for details. Warning Firewall rules blocked me from connecting to one or more addresses (expand for details)I tried to connect to the following addresses, but was blocked by firewall rules:
If you need me to access, download, or install something from one of these locations, you can either:
|
Updates the “getting help” documentation to remove response-speed claims, keep email as the recommended support path, and standardize Discord capitalization.
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.