Find out why a customer was charged twice

Supahelp checks the ticket, Stripe, your logs and the code, then gets the refund ready for your approval.

USE CASE · BILLINGEnds resolved
Starts with
“We were charged twice”
Checks
ZendeskStripeNew RelicGitHub
Who
Support, engineering only if it is a bug
You approve
The refund
Ends with
Refund confirmed in Stripe, reply sent
TodayZendesk→ Stripe→ New Relic→ Slack engineering→ wait→ Stripe→ ZendeskWith SupahelpPaste the ticket→ read the answer→ approve

01

The ticket

A customer writes in. Paste the link, or forward it from Zendesk.

02

What it checks

Four tools, in 18 seconds. Sentry stays closed because nothing points to an error.

03

What it found

Each finding says where it came from, and goes into the case for the next person.

04

What you approve

The refund waits for your yes. After you approve, it checks the refund went through in Stripe.

05

The reply

Drafted from what was confirmed. Edit it, or send it as it is.

06

The playbook

Save the checks once. The next double charge runs the same way, for anyone on the team.