Authenticate. Check policy. Run the action in Stripe. Close the ticket. Your team never opens the easy billing work.
Jobs that should never reach a person
Resolve the ticket. Not just the question.
Most AI support quotes your refund policy. Kal runs the refund when policy allows, then closes the conversation with a full audit trail.
Refunds
Policy check. Real refund. Closed.
Inside the window and under your ceiling, Kal issues the refund in Stripe and confirms the amount. Outside policy, it hands off with the trail attached.
Plan changes
Upgrades and downgrades that stick.
Customer asks to change plan. Kal verifies eligibility, runs the change in billing, and closes the thread. No copy-paste into the admin panel.
Cancellations
Cancel cleanly. Or save when you allow it.
Process the cancel when they mean it. Or offer a save path when your rules say so. Either way, the system of record updates and the ticket ends.
Invoices & updates
Receipts, addresses, the boring stuff.
Resend an invoice. Fix a billing address. Update a company name. The L1 work that should never fill a human morning again.
Autonomous.
Not unsupervised.
Ceilings you set. Auth before action. Every step logged. Handoff when unsure.
The loop
Authenticate. Decide. Execute. Close.
A chatbot that says "here is how to request a refund" still leaves a human to finish the work. Kal verifies the customer, checks your policy, calls Stripe or your billing system, tells the customer it is done, and marks the ticket resolved.
That is the Auto-Resolve loop applied to the money jobs. Full product detail lives on Auto-Resolve. This page is for the buyer searching for refunds and billing automation in chat.
Playbook
Three steps. Real money actions.
Connect billing. Draw the lines. Review the trail. Then stop staffing the easy refunds.
Connect billing.
Hook Kal into Stripe or your billing system. Refunds and plan changes only work when the agent can call the real API.
Set ceilings and scope.
Refund up to $X. Downgrade but never delete. Authenticate first, always. Kal stays inside the lines you draw.
Watch the audit trail.
Every closed ticket shows the checks, the policy match, and the API call. Exportable. Reviewable. Not a black box.
Stop staffing
the easy tickets.
Refunds, plan changes, cancels. Done and closed. Humans only for the edge.
FAQ
The questions before you connect Stripe.
Written by the team that built it. Sales fluff not included.
Refunds, plan changes, cancellations, invoices and receipts, and account or address updates. Each one is authenticated, checked against your policy, executed in the real system, and logged. Deep dive: Auto-Resolve.
Only with hard limits. You set ceilings and allowed actions. Kal authenticates the customer first. Anything outside policy or confidence hands off to a human. Every step is logged on the ticket.
A chatbot that says "here is how to request a refund" still leaves a human to finish the work. Kal runs the refund and closes the ticket. That is resolution, not deflection.
When Kal closes the conversation, it counts as one resolution: free within the first 50 each month, then $0.49. Handoffs are free. Full pricing →
Yes under the hood. This page is the job (billing and refunds). Auto-Resolve is the product feature page with the full agentic loop and guarantee language.
Updated July 2026
Close the refund. Keep the human free.
14-day trial. No card. Auto-Resolve on billing jobs your team should never touch.