Let users get a refund without a ticket
Peeve handles refund requests inside your product. Within the policy and limits you set, it confirms the exact refund, completes it as a backend action and writes a signed audit entry, or hands off to a human when a request falls outside policy. Issuing a refund is a Do action, available on the Growth plan and up.
New to the category? Read what AI customer support is and how it works.
With your Do connector and a policy you define, Peeve confirms the refund amount and reason, issues it, and logs it. When a request is outside policy or needs judgment, it hands off to your team with the full session attached rather than guessing.
Peeve runs only the actions you allow, within the logged-in user's permissions, and it confirms the exact effect before anything changes. Every action is written to a signed audit log, and the model never sees a password or token: it requests a capability by name.
Issuing a refund is a Do feature, on the Growth plan ($199 a month) and above. On Starter (Answer and Show, read-only) Peeve answers the question and shows the user where to go, then hands off for the refund itself.
Can an AI agent issue a refund?
Yes, if you connect it to your payment system and set a policy. Peeve issues a refund only within the limits you define, confirms the amount first, acts within the user's permissions, and logs every step. It is a Do feature on the Growth plan and up, and the model never sees a payment credential.
What happens if a refund is outside policy?
Peeve does not guess. When a refund falls outside the policy and limits you set, it hands off to a human in Peeve Hand-Offs with the full session attached, so your team decides with the context already in front of them rather than starting from a cold ticket.
Related: How Do works, How Show works, Hand-off, all use cases.