After a late or damaged delivery, customers expect a gesture. With Memberr, your team books that gesture as store credit, right from the ticket. The credit can be spent straight away, and the money stays in the shop.
The AI agent can propose such credits. For every booking it has to give a reason, which the approver sees. How much it may offer in which situation is set in its instructions, because the action itself has no amount limit.
| Point | What applies |
|---|
| Minimum amount | 0.01, no upper limit |
| Undo | not possible, a mistake is corrected with the opposite booking |
| Reason for the booking | no field of its own, so note it in an internal note on the ticket |
| Reducing below zero | not prevented, check the new balance before confirming |
| Currency | the currency of the existing balance, otherwise euros |
| Which customer | always the customer matching the ticket's email address |
Store credit is real money in the shop. That's why every AI booking requires approval by default and deducting is switched off. You only need deducting if the agent should correct credit that was booked twice.
If you connect several Memberr shops, armincx needs to know which one a ticket belongs to. For chat widget tickets, armincx compares the website the customer wrote from with each shop's ticket origin domain and opens the matching one automatically. For emails and all other tickets, your team picks the shop in the card.
