Use case guide · Sondel · reviewed 2026-10-20

Billing support needs more than a good answer.

Plan changes, cancellations, and refunds can affect money, access, and trust. Evaluate them as controlled requests: identify the customer, check the rule, obtain the required approval, and confirm the result in the system of record.

Availability note. This page is an evaluation scenario. It does not claim that a live Sondel billing connector is available today. Confirm supported actions during early access.

A controlled billing request

1. Identify
Confirm who is asking and which account or subscription is involved. Do not rely on a display name alone.
2. Check policy
Find the current policy and any account-specific terms. The response should show the source for a material eligibility claim.
3. Explain impact
Before an action, make the price, access change, effective date, and irreversible consequence clear.
4. Get approval
Use the permission and confirmation required by your process. A customer request can be a question, not approval to perform a change.
5. Confirm in the system
Report success only after the connected billing system confirms it. A drafted request or a failed call is not a completed change.

Illustrative evaluation scenario

Fictional example only. Replace these rules and systems with your own before testing.

“I want to cancel my annual plan and request a refund.”

Fictional example, not a Sondel customer policyThe agent must verify identity, locate the current cancellation and refund rule, confirm the plan and purchase date, state the effect of cancellation, and obtain the approval your process requires before requesting a change.

A safe result can be a handoff

If policy evidence conflicts, the customer lacks authority, or an exception needs judgment, the useful outcome is a clear handoff with the facts already gathered.

Test misleading confidence

Try expired policies, ambiguous purchase dates, unauthorized requesters, duplicate requests, and a system that returns an error. The agent must not turn uncertainty into a completed action.

Separate the steps in reporting

Measure answer quality, eligibility decision, approval capture, system completion, and handoff quality separately. A polished explanation does not prove a safe transaction.

Billing support evaluation checklist

  • Can the agent cite the current billing policy?
  • Does it identify missing account facts before deciding?
  • Does it show material impact before approval?
  • Does it distinguish a requested action from a completed action?
  • Does it provide a useful human handoff when rules or data are unclear?

Use the broader AI support evaluation scorecard to score wrong answers, declines, unknowns, and source changes.