Education
Example storyHow a Doha language centre handles admissions after hours
Harbour Learning Centre routes admissions forms into one inbox shared by three staff, replies on WhatsApp within a minute and lets a Beta website chatbot answer fee and timetable questions at any hour.

This is an example story. Harbour Learning Centre is a composite business based on how teams like it work. It shows what Montr is built to do, not results from a named customer.
The problem
Harbour Learning Centre teaches English and exam preparation to adults and teenagers in Doha. Parents and working professionals ask the same things: how much is a term, when are the evening classes, what level will I start at.
Three admissions staff took the enquiries from the website form, WhatsApp and the front desk phone. Enquiries that arrived in the evening, after the office closed, waited for the next morning. A prospective student who asked twice sometimes got two different answers.
What they set up
They built one enquiry form that asks for the course, the preferred time of day and a WhatsApp number. Each submission becomes a contact in the CRM and is assigned to an admissions officer. Duplicates are flagged.
The form starts the form lead, WhatsApp first, email fallback automation. The prospect gets a WhatsApp message within a minute with the term dates and a link to book a free level check. If WhatsApp can’t carry the message, the same text goes by email. After two days, a call-back task lands on the officer.
The centre uses Meta-approved templates for its messages. The staff write them in English and in Arabic, because that is how their students write. Montr sends the text they wrote. The Montr interface is English only, and the team is comfortable with that.
All three admissions officers work from one shared Inbox. They use saved replies for fees, levels and documents to bring, and a business-hours setting tells people when the office replies. Each conversation has an owner.
The fee schedule, term dates and level descriptions live in Documents, and a website chatbot is pointed at them. The chatbot is in Beta. For the first weeks, the head of admissions read every conversation and added answers where the bot had none. The bot answers from the centre’s content only. When it can’t, it hands over, and the escalation lands in the Inbox for a named officer.
Registration for the free level check is handled by a second short form. After a first lesson, a WhatsApp message with Good and Bad buttons asks how it went. A Bad reply creates a follow-up task for the head of admissions.
What changed
A parent who writes at 9 p.m. gets a reply that night, with the dates and a way to book. The chatbot covers the most common fee and timetable questions at any hour, and the officers pick up anything it passes on.
Everyone sees the same answer. Saved replies keep fees consistent, and the history sits on the contact. An officer who takes over a conversation can read what was already promised.
The head of admissions reads the Bad-feedback tasks each morning. She reads them as a short list, not a search through chats.