{"meta":{"title":"Creating a support ticket","intro":"You can use the GitHub Support portal to create a support ticket and speak to GitHub Support.","product":"GitHub Support","breadcrumbs":[{"href":"/en/support","title":"GitHub Support"},{"href":"/en/support/contacting-github-support","title":"Contacting support"},{"href":"/en/support/contacting-github-support/creating-a-support-ticket","title":"Creating a ticket"}],"documentType":"article"},"body":"# Creating a support ticket\n\nYou can use the GitHub Support portal to create a support ticket and speak to GitHub Support.\n\n## About support tickets\n\nIf your account uses a paid GitHub plan, Copilot Business, or Copilot Enterprise, you can directly contact GitHub Support.\n\nIf your account uses GitHub Free, you can speak to GitHub users and staff on the [GitHub Community discussions](https://github.com/orgs/community/discussions) for most issues, and you can contact GitHub Support to report account, security, and abuse issues.\n\nTo share feedback with GitHub, you can use the GitHub Community discussions. For more information, see [Sharing feedback with GitHub](/en/support/sharing-feedback-with-github).\n\nAfter you create your ticket, you can view your ticket and the responses from GitHub Support on the [GitHub Support portal](https://support.github.com/). For more information, see [Viewing and updating support tickets](/en/support/contacting-github-support/viewing-and-updating-support-tickets).\n\n## What to include in your support ticket\n\nGitHub Support does not have access to any private or internal GitHub resources. Providing GitHub Support with everything they need to understand, locate, and reproduce an issue will allow for a faster resolution and less back-and-forth between yourself and the support team. To ensure GitHub Support can assist you, consider the following points when you write your ticket:\n\n* Obtain information that can help GitHub Support track, prioritize, reproduce, or investigate the issue.\n* Include full URLs, repository names, and usernames wherever possible.\n* Reproduce the issue if applicable and be prepared to share the steps.\n* Be prepared to provide a full description of the issue and expected results.\n* Copy exact wording of all error messages related to your issue.\n* Determine if there is an existing ticket number in any ongoing communications with GitHub Support.\n* Include relevant logs and attach any screenshots that demonstrate the issue.\n  * When providing screenshots, ensure the full URL is visible in the address bar. This helps GitHub Support locate the relevant information more quickly. Be sure to redact any sensitive information.\n\n## Creating a support ticket\n\nBefore you submit a ticket, you have the option of using Copilot in GitHub Support to receive an immediate response to your question. If Copilot in GitHub Support is unable to resolve your issue, you can continue submitting your ticket. For more information, see [About Copilot in GitHub Support](/en/support/learning-about-github-support/about-copilot-in-github-support).\n\n> \\[!IMPORTANT]\n> If your enterprise uses data residency, you must sign in with your GHE.com account when creating a support ticket about your data-resident enterprise. Otherwise, you will be asked to open a new ticket using your GHE.com account.\n\n1. Navigate to the [GitHub Support portal](https://support.github.com/) and choose one of the following options:\n\n   * To sign in with your GitHub account, click **Sign in with GitHub**.\n   * If your enterprise uses data residency (you will use a domain like `octocorp.ghe.com`):\n     1. In the sign-in dialog, click **Sign in to your .ghe account**.\n     2. Enter your enterprise or tenant name (provided by your administrator) and continue.\n     3. Complete the SAML authentication process as prompted. This will sign you in to your .ghe enterprise-managed account.\n   * To sign up for GitHub, click **Sign up for GitHub**.\n   * If you can't sign in or sign up, click **Can't sign in?** and fill out the form. You will be guided through an email verification process.\n\n2. At the top of the page, under \"How can we help?\", choose a topic or click **open a support ticket**.\n\n   > \\[!NOTE]\n   > You will only see the link to open a support ticket if your account uses a paid GitHub product or you are a member of an organization that uses a paid product. If you don't see the link, you can speak to GitHub users and staff on the [GitHub Community discussions](https://github.com/orgs/community/discussions) for most issues, and you can still contact GitHub Support to report account, security, and abuse issues.\n\n3. Select the **From** dropdown menu and click the email address you'd like GitHub Support to contact.\n\n4. Under \"Subject\", type a descriptive title for the issue you're having.\n\n5. Under \"How can we help\", provide any additional information that will help the Support team troubleshoot the problem. You can use markdown to format your message.\n\n   Helpful information may include:\n\n   * Steps to reproduce the issue\n   * Any special circumstances surrounding the discovery of the issue (for example, the first occurrence or occurrence after a specific event, frequency of occurrence, business impact of the problem, and suggested urgency)\n   * Exact wording of error messages\n\n   You can attach files up to 50MB.\n\n   > \\[!WARNING]\n   > When you upload an image or video to a pull request or issue comment, or upload a file to a ticket in the GitHub Support portal, anyone can view the anonymized URL without authentication, even if the pull request or issue is in a private repository. To keep sensitive media files private, serve them from a private network or server that requires authentication. For more information on anonymized URLs see [About anonymized URLs](/en/authentication/keeping-your-account-and-data-secure/about-anonymized-urls).\n\n6. Click **Send request**.\n\n## Further reading\n\n* [About GitHub Support](/en/support/learning-about-github-support/about-github-support)"}