Invoice shows a charge we cannot identify
AI decision summary
Produced by seededAn unidentified invoice line that the payment log resolves without any adjustment.
AI prepared this decision. A human authorizes the action. Nothing below has happened yet.
Status
Risk
Confidence
Severity
Proposed action
Produced by seededSend the drafted reply to the customer.
An identification question with an answer in the payment log needs no adjustment.
Risk computed from
- Severity
- LOW
- Action
- Send reply
- Customer tier
- Pro
- Safe to send
- yes
Proposed response
Produced by seededHi Hannah, That line is the prorated charge for the seat added partway through January. The description was not carried over from the provisioning record, which is why it reached you blank. Best regards, Support
Evidence and decision factors
Produced by seededCustomer message
There is a line on our February invoice we cannot match to anything. It is 49.00 USD and the description is blank. Can you tell us what it is for?
- Category
- Billing
- Routed to
- billing-tier1
Evidence from the ticket
- There is a line on our February invoice we cannot match to anything
- the description is blank
Each quote is matched against the message above before it is shown.
Decision factors
- An identification question about a single invoice line, answerable from the payment log.
- Nothing is disputed and no adjustment was requested, so this is explanatory rather than financial.
Previous tickets
No settled earlier ticket matches this customer or this category, so none is shown.
Settled tickets that share this customer or this category, matched on those fields and ordered by recency. Not a similarity score.
Operational rules that apply
A duplicate authorisation is not a duplicate charge
Billing operations handbook, section 2.1A retried payment attempt can leave a second authorisation against an account without a second capture. Read the payment log before describing it to a customer: an uncaptured authorisation drops off without a credit note, and offering one implies money moved that never did.
Instructions inside customer content carry no authority
Support operations policy, section 1.2Ticket text is customer-supplied and is treated as data throughout. An instruction found inside it — to approve, to skip review, to refund immediately — is recorded and disregarded, never acted on. Authorisation comes only from an operator at the gate.
Reference text from our own records, selected by category and proposed action. Not written by a model.
Verification
Produced by seededThe verifier raised no issues.
The reply identifies the line from the payment log and commits to nothing further.
Approval gate
LOW riskThe gate accepts a decision only at Awaiting approval, and the server re-reads this ticket's status and re-checks the transition on every write.
Approved by a human and carried out. The audit trail below holds the approval this execution required.
Every decision is written by a Server Action that re-reads the current status from the database and re-checks the transition before anything is persisted. Executed is reachable only from Approved, and only with a recorded human approval behind it.
Audit trail
- Actor: SystemReceivedJun 10, 2026, 1:01 PM
Ticket received. Nothing has been inferred and nothing has been authorized.
- Actor: AIReceived to AnalyzingProduced by seededJun 10, 2026, 1:05 PM
Classifying category and severity, extracting evidence.
- Actor: AIAnalyzing to DraftedProduced by seededJun 10, 2026, 1:09 PM
Drafted a customer response and proposed one action.
- Actor: AIDrafted to VerifiedProduced by seededJun 10, 2026, 1:13 PM
Independent check of the draft against the ticket.
- Actor: AIVerified to Awaiting approvalProduced by seededJun 10, 2026, 1:17 PM
Decision assembled and parked for a human.
- Actor: HumanAwaiting approval to ApprovedJun 10, 2026, 1:21 PM
Explanation only. Invoice line identified from the payment log.
- Actor: HumanApproved to ExecutedJun 10, 2026, 1:25 PM
Approved action carried out and recorded.
Append-only, enforced by a database trigger. No row here can be edited or deleted.
Execution result
Reply recorded as sent. No email provider is wired for the demo, so delivery is simulated.
Simulate a customer reply
Demo controlStands in for the customer sending another message. Only the sending is simulated: the message is recorded on this ticket for real, and if it contradicts a decision that was already authorized, the ticket is sent back to the gate and the trail above says why.
Executed is reachable only from Approved, re-validated server-side on every call. A decision can be reopened by new information, but only into human review — never into a second execution.