Priya Raghunathan
EmailThere is a $70.97 charge on my card from 12 March. I pay $39 a month. What is this?
Zendesk ZD-4821 · Coilbook · Unrecognised charge on my card
It arrived at 09:14, closed at 09:38, and left this trail.
There is a $70.97 charge on my card from 12 March. I pay $39 a month. What is this?
sub_1P7dK2 · Studio · $149.00/mo
$96.13 Studio, less $25.16 unused Solo
That charge is the switch to Studio on 12 March. Stripe bills the new plan for the twenty days left in the period and credits the same twenty days you had already paid on Solo, so the invoice is $96.13 minus $25.16.
From 1 April it settles at $149.00 a month on the normal date. Your $39 payments were the old plan and have stopped.
That makes sense, thank you. Can I have the $70.97 back and go to Solo? We are not using the extra seats.
blocked · above the $50 ceiling
A refund of this size needs a person. I have passed the thread to Dana Okonjo with the invoice, the plan history and a reply drafted, and told Priya someone will answer today.
Refund approved and the plan moves back to Solo on 1 April. Priya sees $70.97 returned within five working days.
The run log
What Relay touched, in what order, and what came back, with nothing hidden behind a spinner.
The decision
One check decides whether a billing ticket ends with Relay or with a person.
trigger
Ticket arrives
A billing question lands in the queue with the customer's account id attached.
lookup
Read the account
Four reads before a word is drafted: Stripe, the accounts replica, the help center, and the ticket's own thread.
check
Does it clear policy?
Two tests in the tool layer, run before every send: the help center match scores 0.8 or better, and no money moves past $50.
clears · 65%
step
Relay answers
ZD-4821 cleared here at +1.44s. The reply cites the policy section it came from, and a credit up to $50 can go with it.
step
Ticket closes
The run keeps every call, input and rule that allowed it for 13 months.
trigger
The customer asks again
ZD-4821 came back at 09:31 wanting the charge refunded, so the same loop ran a second time and met the same check.
returns to Read the account
blocks · 35%
handoff
A person takes it
The second check stopped ZD-4821: a $70.97 refund against a $50 ceiling.
handoff
Dana gets the brief
Four facts and a drafted reply: the account, the charge, the payment history, and the rule that stopped it.
Ticket arrives
trigger · starts the run
A billing question lands in the queue with the customer's account id attached.
Read the account
lookup · after Ticket arrives · also after The customer asks again
Four reads before a word is drafted: Stripe, the accounts replica, the help center, and the ticket's own thread.
Does it clear policy?
check · after Read the account
Two tests in the tool layer, run before every send: the help center match scores 0.8 or better, and no money moves past $50.
Relay answers
step · after Does it clear policy? · branch clears (65%)
ZD-4821 cleared here at +1.44s. The reply cites the policy section it came from, and a credit up to $50 can go with it.
Ticket closes
step · after Relay answers
The run keeps every call, input and rule that allowed it for 13 months.
The customer asks again
trigger · after Ticket closes
ZD-4821 came back at 09:31 wanting the charge refunded, so the same loop ran a second time and met the same check.
A person takes it
handoff · after Does it clear policy? · branch blocks (35%)
The second check stopped ZD-4821: a $70.97 refund against a $50 ceiling.
Dana gets the brief
handoff · after A person takes it
Four facts and a drafted reply: the account, the charge, the payment history, and the rule that stopped it.
The handoff
The account, the charge, the rule that stopped it, and a reply ready to send.
Handed to Dana Okonjo
billing on-call · 09:31Hi Priya, I have approved the $70.97 back to your card and moved you to Solo from 1 April. The refund lands within five working days.
Stopped by refund.ceiling, not by a hunch.
Guardrails
Your security review will ask these four questions, so here are the answers first.
The ceiling is a number in your config, checked in the tool layer before the call is made. A prompt cannot argue with it.
Below 0.8 match against your help center, Relay drafts and escalates instead of sending. The threshold is yours to move.
Account data comes from a read replica. There is no path from Relay to a row in your primary database.
Each call is logged with the ticket, the inputs and the rule that allowed it, kept 13 months and exportable as CSV.
Connect Stripe and one helpdesk, approve its first 50 replies, then let it send.