Billing inquiry voice agent

A billing inquiry voice agent may speak a balance, a due date, or a payment schedule only when that figure is present on the authenticated billing file. If authentication fails, or the file does not return the field, the agent leaves the field empty. It does not guess, round from a prior call, or fill a gap so the conversation sounds complete.

Every answer that contains a dollar amount or a due date must cite a retrieve for this account on this call. The voice channel is a read path into billing, plus a narrow write path for payments the file already supports. It is not a place to invent dollars.

A spoken balance with no file cite is a defect. Stop the amount, log the miss, and move the call to a billing agent. Do not correct the number with a second guess.

Empty stays empty when the caller is not bound to an account, when the billing file is missing or timed out, or when the field exists on the policy but is not the billed amount. A premium from a quote or a coverage screen is not a balance. Do not substitute it.

Do not retrieve, recite, or collect until the caller is bound to a policy and a billing account. Authentication is a gate, not a greeting.

Use the factors the carrier already relies on: policy number plus a second match such as date of birth, ZIP, last four of SSN, or a one-time code. Match those values to the identity record. If the match fails, the billing file stays closed. The agent says it cannot open the account and offers a transfer. It does not try a likely policy from the inbound number.

Partial matches are not enough. A name that sounds right, ANI on the telephone line, or a menu choice from the IVR does not open the file. If the identity record is incomplete, or the caller cannot complete the factors, a billing agent owns the exception. The voice agent does not almost authenticate.

This gate does not change with the platform mix. Policy administration may sit in Guidewire or Duck Creek, the customer record in Salesforce, and the call in Genesys. Those systems hold identity, billing, and the voice session. None of them authorizes a spoken amount that the billing file did not return for a bound account.

Retrieval is a query against the billing file, not a summary of the conversation. The agent asks for named fields: current balance, next amount due, due date, installment schedule, last posted payment, and open billing status. The response either contains a value plus a source identifier (account, invoice, installment, or transaction id) or it contains nothing.

Speak only cited values. The utterance that states a current balance must be bound to the retrieve that returned that amount for this account on this call. If the retrieve is stale, truncated, or timed out, do not speak a cached line from an earlier session.

Leave the field blank when authentication did not bind the caller, when the file returned no value, or when a display rule blocks the figure. A disputed invoice, an account in collections, or a line that billing invoice anomaly detection has flagged is not something the voice agent should smooth over with a round number. The correct speech is a refusal plus a path to a person.

The retrieve the caller hears should be the same retrieve a billing agent sees on warm transfer. If the screen and the phone disagree, the phone was wrong. Do not let the model invent a balance that makes the two match.

Illustrative path: a caller asks whether this month's auto draft already ran. Authentication succeeds. The file returns a next amount due and a due date; last posted payment is empty. The agent cites the due amount and due date, says it does not show a posted payment for this cycle, and does not treat the call as a payment. If the caller asks to pay now and the file does not support that amount or method, the agent does not collect. It transfers to a billing agent with the retrieve attached.

Routine payments are a write only when the billing file already allows them: the amount is the open balance or a scheduled installment the file will accept, the method is on file or newly captured under the carrier's existing card and consent rules, and the account status permits collection.

Do not auto-take a payment the file does not support. Unsupported includes an amount above the billed balance without a documented surplus rule, a method the account cannot use, a lapsed or cancelled status that blocks collection, a payment already in flight, and a request to reverse a posted item. Those are exceptions. A billing agent owns them.

The call is not a posted payment. A promise to pay or a transfer does not create a transaction. Only a successful posting in the billing system does. Treating the call as posted is a failure mode: the caller believes the premium is current, the file still shows past due, and failed payment recovery sequencing may start against an account the caller thought they settled.

If a collection attempt is submitted and the processor declines, report the decline as the file or the processor returned it. Do not retry beyond the rule set. Do not round the amount down so it goes through. Do not invent a remaining balance after a partial the file never posted.

When a payment does post, read back only what the file now shows: amount, allowed method detail such as last four, and the confirmation or transaction id from the posting, not from the dialogue.

Keep a short exception list. Everything on it goes to a person with the retrieve, the authentication result, and what the caller asked.

Typical exceptions include authentication failure or incomplete identity, a missing billing file or missing fields the caller needs, disputed charges or amounts that do not match a notice the caller has in hand, payments that fail rules, hardship or reinstatement requests, and any ask to change the billed amount, waive a fee, or backdate a payment.

The voice agent may capture the request in the caller's words. It may not approve, deny, or split the difference. lapse propensity scoring may later use the same billing events. The voice turn still must not invent a balance to keep the policy in force.

Warm transfer, not a cold drop. The billing agent should see the bound account, fields retrieved, fields left blank and why, payment attempts and outcomes, and the caller's last ask. If that packet is missing, the person on the phone will re-ask and may speak a number the file never cited.

This path matches ai voice agent for policy servicing: authenticate, retrieve with cites, leave blanks, human owns exceptions. That page is endorsements and coverage. This page is dollars on the billing file. Do not mix a coverage quote into a balance.

Sample recordings against the retrieve log and treat mismatches as stop-the-line events.

A spoken balance with no file cite: if the model produced a number from the prompt, a prior session, or a similar-sounding account, the utterance is unauthorized. Cut the amount. Do not replace it with another guess. Transfer.

Treating the call as a posted payment: until the billing system returns a post, the account is unchanged. Do not confirm a payment that exists only in the conversation.

Inventing a balance: rounding, averaging installments, subtracting a pending draft the file does not show, or filling a blank so the call feels finished. Empty stays empty if authentication or the file is missing.

If speech contains a dollar amount, the log must contain that amount with a cite for that call. If a payment confirmation was spoken, the posting record must exist. Identity, billing, and the call typically live across Guidewire, Duck Creek, Salesforce, and Genesys. The control is the same: no cite, no number; no supported payment, no collection; no post, no confirmation.