Use case · Support
The bot knows when to step back. People take the hard ones.
Start from the support-triage bot, which answers only from your documents. It hands over to your team when someone sounds upset or it isn't sure. Chatbot is in beta.
A bot that keeps answering an angry customer makes things worse. The customer wants a person and can't find one.
Frustrated or unclear conversations land in your shared inbox with the full chat history. A person picks it up without asking the customer to repeat anything.
How it works
Set it up once. Let it run.
- 01
Start from the template
Use the support-triage bot. It answers only from your documents.
- 02
Set the hand-off phrases
Add words and situations that should pass to a person, such as "refund", "complaint" or "speak to someone".
- 03
Set your hours
Tell customers when a person will reply.
- 04
Read the handed-over chats
Review them weekly and improve the documents the bot reads.
What changes
What you get back
Fewer escalations gone wrong
People take over at the right moment.
Context kept
The whole chat lands in the inbox.
Safer bot
It stays inside your documents.
Templates
Copy these workflows
- support
Website chatbot → hand over to a person
A visitor chats on your site. The Beta chatbot answers from your documents and hands over to a teammate when it can't help or the visitor is frustrated.
- support
Resolved chat → quick Good/Bad feedback
A support chat is marked resolved. An hour later Montr asks how it went with two buttons and flags unhappy customers to your manager.
Built with
The parts of Montr this uses
FAQ
Questions you might have
How does it know someone is upset?
You set the phrases and situations that trigger hand-off. Review the handed-over chats regularly, because the bot is imperfect.
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.