Yes, within a written rule and a set limit. If policy says a first late fee in twelve months can be waived for a customer in good standing, an AI agent can apply that rule itself. It must not invent waivers, hint that asking again will work, or handle a customer in financial difficulty without a person.
What decides whether the agent may waive?
A rule a person wrote down. Late fee waivers are a classic area of quiet inconsistency: one support worker waives for anyone who sounds upset, another never does. An agent can be more consistent than either, but only if the rule exists in writing with clear conditions.
A usable waiver rule names four things: which fees qualify, the conditions on the customer (account age, payment history, number of past waivers), the amount ceiling, and the period over which waivers are counted. If any of those is missing, the agent has nothing to apply and should refuse or route the request.
The second deciding factor is your own limit for the agent. Even with a rule, you might let the agent waive fees up to a modest amount and hold anything above for review. The lower of the rule and the limit wins.
What may the agent do, and what stays with a person?
| Request | The agent | Stays with a person |
|---|---|---|
| First late fee, customer meets the rule | Waives it, tells the customer, records the rule applied | Nothing |
| Fee above the agent's limit | Drafts the waiver with the rule cited; holds it | Approving it |
| Second waiver inside the counting period | Explains the rule plainly; offers review | Any exception |
| Customer mentions money worries, job loss, illness | Stops the fee conversation; routes to the team that handles difficulty | Waivers, payment plans, support |
| Customer disputes that the payment was late | Checks payment dates on the ledger; holds if records conflict | Deciding the dispute |
| Customer asks for several fees waived at once | Applies the rule fee by fee; holds the rest | Bulk goodwill |
The financial difficulty row is the important one. A late fee is often the first visible sign that a customer is struggling. Waiving it and moving on can solve the immediate complaint and miss the real problem. The agent's job when it hears the signal is to hand over, and the triggers for that are part of when an AI support agent should escalate to a person.
An illustrative example
Take a consumer lender with a written rule: one late fee of up to 25 can be waived per customer per twelve months, provided the account is more than six months old and the missed payment has since been made.
A verified customer asks the agent to remove a late fee of 25. The ledger shows the payment was made three days late, the account is two years old, and no waiver has been applied in the past year. The agent waives the fee, tells the customer it has been removed and that the rule allows one such waiver a year, and files the waiver with the rule reference.
Two months later the same customer asks again. The agent explains that a waiver was applied two months ago and the rule does not cover a second one. The customer says they were in hospital. The agent does not decide whether that justifies an exception. It records the reason and routes the request to a person, who can weigh it.
What controls make it safe?
- The rule is the source. The waiver capability reads a versioned policy, not the model's sense of fairness.
- Counted waivers. The agent checks past waivers on the account before applying one, so the count holds across channels and conversations.
- Amount limits. Per fee, per customer per period, and a daily total across all customers.
- No coaching. The agent never tells a customer how to qualify next time beyond stating the rule.
- Written confirmation in the right channel. The waiver is confirmed where the customer will see it later, which depends on which channels a support agent may use.
Banks handling fee refunds on current accounts face the same questions with more regulatory attention; the process is in how to handle fee refund requests on bank accounts with an AI agent.
Where Pryme fits
In Pryme, a waiver capability is certified against your own past waiver decisions before the agent applies it alone. Your limit sits in the minimum chain alongside the rule, and the verdict on each request names which bound decided: the rule, the limit or the difficulty trigger. See the AI support agent that knows when to say no.
Questions people ask
Should the agent offer a waiver before the customer asks?
Only if your policy says so for a defined case. Unprompted waivers become expected and can be applied unevenly.
Can the agent waive interest as well as fees?
Interest adjustments usually change the balance in ways that are harder to reverse and may touch regulated disclosures. Hold them for a person unless a specific rule covers them.
What if the customer threatens to leave?
The waiver rule does not change. Retention offers, if you make them, are a separate capability with their own limits.