Use for
Billing disputes and service failures
Choose the grievance route when the issue needs formal tracking, an explicit resolution record, or compliance-sensitive handling.
Evidence
Reference-led escalation
Invoice numbers, coupon or referral references, payment intent IDs, and incident dates make compliance review materially faster.
Outcome
Tracked case history
Signed-in grievance submission keeps the case tied to the user account so follow-up, ownership, and status changes remain visible inside STAN.
Before you submit
What the grievance form should contain
Formal complaints move better when the case enters with evidence and expected resolution criteria.
- A clear subject that explains the incident or dispute.
- References such as billing identifiers, coupon codes, or prior support ticket links when they exist.
- The impact on your account, payment, or workflow and the response you expect.