Use case · Support
Refunds wait for a yes. No manager, no refund.
Put an approval step in front of anything you can't undo. The run pauses until a named teammate approves, rejects or times out.
Support agents can issue refunds, but you want a second pair of eyes above a certain amount. Today that means a chat message someone might miss.
Refund requests above your line wait for a named approver. If nobody answers, the gate stays closed.
How it works
Set it up once. Let it run.
- 01
Build the automation
Start from the refund request, form or message that begins the process.
- 02
Add the approval step
Name the teammate who must approve and set how long to wait.
- 03
Add what happens next
On approval, run the refund step. On rejection, send the customer a message.
- 04
Review the queue
Check pending approvals in the review queue.
What changes
What you get back
Four-eyes on money
A second person for every sensitive step.
Fails safe
No answer means the gate stays closed.
Everything logged
See who approved what, and when.
Built with
The parts of Montr this uses
FAQ
Questions you might have
What if the approver is away?
An unanswered request never opens the gate. Set a time-out and decide what happens next.
Put your growth on autopilot. Keep your hand on the wheel.
Join the waitlist. We open Montr BI to teams in India, the US and the GCC in small groups, and we set up your first workflows with you.