Urgent: Refund Ticket #4072164 pending for 18 days ($390 charge)

[zhangyanzhi520-jpg]

Select Topic Area

Question

Copilot Feature Area

Copilot in GitHub

Body

"Hi, I accidentally purchased a yearly Copilot subscription for $390.00 on Feb 10. I opened ticket #4072164 immediately, but it has been 18 days without a response. Can a staff member please escalate this? Thank you."

[nishantXnova]

This is a billing issue that needs direct escalation. Here's what to do right now:

1. Escalate the existing ticket
   Go to support.github.com and reference ticket #4072164 directly. In your follow-up message write:
   'I am following up on ticket #4072164 opened on February 10, 2026 regarding an accidental yearly Copilot subscription charge of $390.00. It has been 18 days without a response. I am requesting urgent escalation as this involves a significant billing dispute and time-sensitive refund eligibility.'
2. Contact GitHub Billing directly
   Go to github.com/contact and select Billing as the topic. This routes to a different queue than general support and gets faster responses.
3. Dispute with your bank/card as a backup
   If you get no response within the next 7 days, file a chargeback with your bank or card provider. The charge was February 10 — most banks allow disputes within 60-120 days. Don't wait too long or you'll lose this option.
4. Twitter/X escalation
   DM or tag @githubsupport on Twitter/X with your ticket number. Public visibility often gets billing issues resolved faster than the ticket queue.
   Key point to emphasize in all communications: You opened the ticket the same day as the purchase. This shows clear intent to cancel and strengthens your refund case significantly. Make sure you say that every time

[chiranjib13992]

A typical reply from GitHub would thank you for your patience and confirm they’ve located your support ticket (#4072164). They would say the issue has been escalated to the billing team for review. The staff member would mention that further communication will continue via email for security reasons. If eligible, they will process the refund for your GitHub Copilot yearly subscription. They may also explain the expected timeline for the refund to appear on your payment method. Finally, they will close by asking you to monitor your email for updates.

[rakesh774]

1. Pivot to a Different Support Channel
   If the standard ticketing system is silent, the most effective way to get a response is to use a high-visibility or real-time channel.

Social Media (The "Public" Push): Tag @githubhelp or @MicrosoftHelps on X (formerly Twitter) with the ticket number. Public-facing teams often move faster to avoid the appearance of poor service.

Official Community Forums: Post in the GitHub Support Community. Staff members frequently monitor these boards to assist with "stuck" tickets.

2. Check for "Billing" Specific Chat
   Billing issues are usually prioritized over technical bugs.

Log back into the support portal and check if there is a Live Chat option specifically for Billing & Payments.

Even if they can't process the refund instantly, a chat agent can "flag" the existing ticket for immediate review by the billing department.

3. The "Force" Move: Contact Your Bank
   If it has been 18 days and the subscription was clearly accidental (e.g., you haven't used the service since the charge), you have a fallback:

Initiate a Chargeback/Dispute: Contact your credit card provider or bank. Tell them you have an "unauthorized or accidental charge" and have attempted to resolve it with the merchant for 18 days without a response.

Warning: Only do this as a last resort. Companies sometimes suspend accounts if a chargeback is filed, so only use this if you are okay with potentially losing access to that specific account.

4. Documentation is Key
   While waiting, ensure you have the following ready to share when a human finally responds:

A screenshot of the original confirmation email (showing the date Feb 10).

A screenshot of your initial ticket submission (showing it was sent "immediately").

A log of your login activity to prove you haven't been using the Copilot features since the purchase.