PROBLEM 01
Double bookings
Seats are tracked in Excel or a notebook. Two operators working at once sell the same seat twice. Then someone has to ring one of them and apologise.
Travel agency system
✈ Built for Mongolian tour operators
Get your travel business out of Excel.
Every step from the first seat booking to the traveller coming home — in one system. Built for Mongolian tour operators.
- Seats never double-sold
- Payments chase themselves
- AI assistant around the clock
0
double-booked seats
0
SMS reminders only (7·3·1)
0
question types the AI knows
0
automated tests
0/7
AI assistant answering
Sound familiar?
Every tour operator meets these
every single day.
PROBLEM 02
Chasing payments
Who paid how much, and who is behind, is tracked by hand. Nobody knows a deadline passed until someone remembers to call. Money comes up short as departure approaches.
PROBLEM 03
Messages at 11 at night
Forty questions a day arrive on the Facebook page. Thirty are the same: “how much”, “do I need a visa”, “can I pay in instalments”. An operator answers each by hand.
PROBLEM 04
After departure, only the guide
Once the group leaves, every question goes to the guide. While the guide sleeps, travellers ring the office. Nobody else can repeat the itinerary, the times, or the meeting point.
PROBLEM 05
“Who are you again?”
When a customer calls, it takes minutes to work out who they are, what they booked, how much they paid and what they asked last time.
The answer
One answer for each problem.
01
SOLUTION
Seats cannot be double-sold
Every booking re-reads the free seats inside a transaction and takes the lowest number. The constraint is enforced in the database itself — two requests taking the same seat is technically impossible. A cancelled seat frees itself and goes to the next booker.
Proof: an automated test fires 12 simultaneous bookings at a 4-seat tour — exactly 4 succeed, 8 get “sold out”, zero duplicates. It reruns on every code change.
02
SOLUTION
Payments chase themselves
A 30/40/30 schedule is created the moment a booking is made. As each deadline nears, the system sends an SMS by itself — 7, 3 and 1 day before. Operators can add a line by hand and adjust amounts or dates.
QPaySocialPayPocketStorepayBank transfer
03
SOLUTION
An AI assistant that answers from your data
The website chat and Facebook Messenger run on one brain. Not a general AI: prices, dates, remaining seats and itineraries all come from your own database. It never invents what it does not have — it says “please contact an operator”. Signed-in customers can ask about their own booking, payments and seat.
04
SOLUTION
The chatbot tells you what it does not know
The admin has a “questions it could not answer” list. Beside each row is a “Teach an answer” button — write the answer and the bot starts giving it immediately. No developer needed.
05
SOLUTION
Nobody is left alone mid-tour
Each morning the day's itinerary arrives on the traveller's phone — times, stops, the first meeting point. By location: as the group nears Mount Fuji, the chat opens itself with the history of the place, how long they will stay and where they go next. The operator writes the description once. Travellers can ask follow-up questions right there.
06
SOLUTION
A single file per customer
One screen: who they are, what they booked, how much they have paid, what is left, which SMS went out, what they asked the chatbot, which promo code they used, and whether they are on a tour right now. Five seconds before an operator picks up the phone.
Why us?
Four things other systems
do not have.
Information reaches the traveller's phone by location
From the moment they land, the handbook, the guide and the reminders are all on the phone. The tour continues even while the guide rests.
SMS cost cut on purpose
Texting every day means roughly 98 messages for a group of 14 over a week. We send SMS at three moments only — everything else is in-app chat and push, free.
Your own staff train the chatbot
Most chatbots stay exactly as installed. Here an operator reads the “did not know” questions and adds answers — it improves with use.
A separate instance per company
Each company gets its own address, its own database, its own colours and logo. Your data stays yours.
Who is it for?
Outbound tour organisersGroups, seats, instalment paymentsDomestic tour operatorsKhuvsgul, Gobi, Altai routesSmall agenciesOne to five operators, tired of ExcelJust starting outOn an organised system from day one
Not a fit: if you only sell tickets, or do not organise groups, something simpler will serve you better.
How to start
In three steps.
-
01
Introduction — 30 minTBC
We show you the working system. Together we check it fits how you actually work.
-
02
Set-up — TBC days
Your logo, colours, routes, prices and itineraries loaded. Staff trained.
-
03
In useTBC .
You go live on your own address. If something comes up we answer within
For those who want the detail
What is it built on?
- Size
- 19 pages, 14 API endpoints, 14 data models
- Tests
- 195 automated tests — they run on every code change
- Chatbot
- Recognises 27 question types, plus whatever operators teach it
- SMS
- Skytel, Messagepro, Mobicom — switchable in settings
- Notifications
- Phone push — arrives even when the site is closed
- Sign-in
- Phone number plus an SMS code. No password to remember
- Speed
- Pages are rendered on the server, so they stay fast on mobile connections
- Accessibility
- Fully usable on a phone, and operable from the keyboard
Security
- Sign-in codes are never stored in the database in the clear (hashed)
- Not even an admin can see a user's live sign-in code
- Every request from Facebook is signature-verified
- A traveller's location is used to measure distance and then discarded — never stored
Common questions
What people ask before deciding
Yes. Hand us your tour, customer and booking lists and we load them for you.TBC
Even if the office loses its connection, the system runs in the cloud and travellers can keep booking.TBC
The admin is built to make sense to anyone who knows Excel. We train you through it.TBC
In a database dedicated to your company. It is never mixed with another company's data.TBC
The chatbot only reads from your database and is forbidden from inventing. When it does not know, it points to an operator's number. Wrong answers show up in the admin and can be corrected there directly.TBC
TBC
TBC
Let's do a 15-minute demo.
See the working system with your own eyes and decide from there. No charge, no commitment.