Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

basic support page update #1820

Merged
merged 1 commit into from
Sep 3, 2024
Merged

basic support page update #1820

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion about/support.html.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -33,11 +33,11 @@

Our Launch, Scale, and Enterprise plans have access to email support. These plans come with an organization-specific address for emailing support questions, typically <org-name>@support.fly.io.

Your support address is in the [Fly.io dashboard](https://fly.io/dashboard). Select your organization, and look for your Support email address in the Billing section.
You can find your support address is in the [Fly.io dashboard](https://fly.io/dashboard). Select your organization, and look for your unique email address in the Support section. You'll also find a form to submit new support tickets, as well as an overview of recent support interactions.

## Support metrics

The Fly.io Support team publishes our email support response time metrics in order to better set expectations regarding response times and help to you understand how we're doing. You can view these metrics in the public [Support Metrics Dashboard](https://fly.io/support).

Check warning on line 40 in about/support.html.md

View workflow job for this annotation

GitHub Actions / Vale linter 

[vale] reported by reviewdog 🐶
[Fly.WordList] Consider using 'to' instead of 'in order to'.

Raw Output:
{"message": "[Fly.WordList] Consider using 'to' instead of 'in order to'.", "location": {"path": "about/support.html.md", "range": {"start": {"line": 40, "column": 75}}}, "severity": "INFO"}

## Working with support

Expand All @@ -49,7 +49,7 @@
- What you were trying to achieve (e.g. deploy the application).
- What you did (e.g. I ran `fly deploy`).
- UTC timestamps for when the issue occurred.
- Prepending `LOG_LEVEL=debug` to any flyctl command will provide insight into the lower-level API calls being made.

Check warning on line 52 in about/support.html.md

View workflow job for this annotation

GitHub Actions / Vale linter 

[vale] reported by reviewdog 🐶
[Fly.Spelling] Is 'Prepending' a typo?

Raw Output:
{"message": "[Fly.Spelling] Is 'Prepending' a typo?", "location": {"path": "about/support.html.md", "range": {"start": {"line": 52, "column": 3}}}, "severity": "INFO"}
- If you are sending us error messages or log output, it's best to send that as plain text in the body of the email (or upload a `.txt` or `.log` file for longer outputs), rather than attached screenshots of your terminal window.

## Other questions?
Expand Down
Loading