Dashboard
Sat 18 · what needs your attention today, plus the walk that is out right nowToday, in numbers updates itself
🚶 Tour in progress: Old Town · 10:00 · live
Guide: EmmaThe guide is at the meeting point: this updates itself as they check people in on their manifest. Yesterday’s reminder and this morning’s confirmation have already gone out.
“Sophie Maclean (6p)” + “Mark Maclean (5p)” = 11 people · same surname · booked 3 minutes apart · same channel (GuruWalk). A percentage, not a verdict — certainty would be a lie. Bookings on your own site add the strongest signal of all: the same connection, which no platform ever forwards. The deposit policy went out on their confirmation, and the guide has the note.
2 people · no guide. Liam marked himself available for that slot. One tap to assign (or see it under Team & availability).
ⓘ more
Close the platform that charges most per person first; your own site last (it costs £0 and gives you the contact). Closing happens in each platform’s own dashboard; tick them off here as you go so you don’t lose count.2 people (it needs 4 to run). Check the message and let them know if you decide to call it off — GuIA rebooks whoever had a place.
“María López” · 8 people · a private Old Town walk, Thursday next week. Real money on the table: reply soon.
Guide’s day
every tour of the day, with check-ins, walk-ins and takings — what Emma sees on her phoneThis list is from a moment ago
The day’s tours, in order of departure (swipe to see them all →).
GuIA
handles SMS, WhatsApp and the chat on your site — and passes anything it can’t answer straight to youⓘ more
The cache key is the fact itself, so editing a fact in the Brain retires the old translation on its own. And the mould is cached with the facts taken out, which means the same mould serves every tour and every company. If a translation is missing, GuIA does not send a half-translated sentence — it hands the question over, same rule as always.GuIA only states facts that are really in the business, and only acts when it has the booking code. Whatever it doesn’t know, it hands to you.
GuIA's brain
the facts it answers with — edit them and the chat changes instantlyI’m GuIA 👋 What you confirm here is the only thing I will tell your customers — anything I don’t know, I hand to you. I never make things up.
💬 What GuIA already answers
0 answerslive +50 rules built in
Every fact confirmed, every draft accepted and every answer you teach adds up here — the newest at the top. The questions that get handed over today (at the very bottom) can join this counter in one tap: answer them once and GuIA knows them for good.
💡 The number above counts only the answers you have confirmed. On top of that, GuIA ships with more than 50 built-in conversation rules for understanding cancellations, changes, delays, groups, languages and much more, and every common question arrives with its draft written. Those rules decide how to read the question and which fact to use — but GuIA only states what you have confirmed: what it doesn’t know, it hands to you.
📚 GuIA’s fact sheet — the company once, then one sheet per tour
ⓘ more
And every question already has a draft written — you change a word or fill in the [gaps], you don’t write the whole sentence. GuIA states only what you confirm (an unconfirmed draft comes to you instead: it never lets one out, and never borrows from another tour). ★ The important ones are in colour. Press 💾 Save and the sheet folds down to its progress bar. The 🏢 Company block is answered once and covers every tour. Watch the [square brackets]: they mark where your detail goes — when you type it in, delete the brackets too (leave “[10:00]” and GuIA would read the brackets out loud).📮 Post-tour message
whole companyⓘ more
Answer these quick questions and the finished message opens up below, adapted by itself to each of your tours.🎓 Teach it an answer of your own
For the things particular to your company that aren’t a standard fact (“are there toilets?”, “can I bring my dog?”, “do you take photos?”). GuIA will use it straight away.
Smart anti-no-show
tomorrow 10:00 AM · the sequence adapts to how risky each booking looks⚖️ Who you are allowed to message
The question is not "did they tick the box?" but
what right do you have to write to them. A reminder about their own booking is
performance of a contract, not advertising — so the GuruWalk traveller, of whom you
only have a phone number, can be reminded. ⓘ more
Contract
(they have a booking): all four messages, written as service. Consent (they
ticked the box when booking, or told you and you record it with one tap on the
send screen — it is stored with your name): plus the review link at the end, which is
the part that promotes. Opted out: nothing, ever — not even reminders.
And you mark the
opt-out yourself, one tap, on the same screen you send from. That is where you
read the reply: messages go out from your own WhatsApp, so "stop writing to me" reaches
you and Audutor never sees it. It is stored per person, not per booking: if they book
again in March, they stay out.
⚙️ The risk settings — each company sets its own
ⓘ more
The out-of-the-box weights come from a real city free tour — move them to fit your case (a ticketed tour with a deposit fails about half as often) and the table below recalculates instantly.| Booking | Channel | No-show risk | Reminder sequence |
|---|
ⓘ more
The guide sees it as a traffic light on their manifest.⏰→8:00 = that nudge would fall outside the sending window (8:00 AM–9:00 PM), so it goes at 8:00 — nobody gets a text at 11:40 PM.
What you sell besides the tour
your catalogue — on your site and in GuIA’s mouth🧺 Your catalogue of extras
Ticketed walks, private tours, tastings. You write it once in the Brain and it shows on your site and GuIA tells people.
🎟️ Your private tour, modular
This is how your customer sees it on your site: they choose and the price moves. The “from” comes from your Brain.
🔗 Combos: the second sale on the same trip
Whoever does the free tour today is your best customer for this week’s ticketed walk — at no cost to acquire.
✍️ The wording of the message is set under 🧠 Brain → 📮 Post-tour message.
Channels & sync
From setup to your first verified bookingTry the inbox, step by step
This demo does not connect accounts or send emails. Changes last until you reload. In the panel, a connection is only verified when there is evidence of reception.
1 · Set up reception
Use the forwarding address available in the panel or connect your mailbox through IMAP.
What setup needs
Forwarding: confirm in Gmail and create filters for bookings, changes and cancellations. IMAP: address, server, port, security and an app password if required by your provider. Enter credentials only in your panel.
2 · Verify reception
Saving an address is not enough. A diagnostic email checks access; a received booking lets you verify the tour, date and party size in the manifest.
3 · Review uncertain details
Compare the saved text, extracted fields and destination before confirming.
Before adding
Saved original: New booking GW-DEMO-101 · Ana Rossi · 3 people · GuruWalk.
Extracted fields: new booking, name and three people. The tour needs matching.
This sample proposal: add one booking to the manifest open in this demo. In your panel, you choose a departure with its date, time and available places.
What you can check in your panel
Setup shows the next pending step. For your website API, availability and change queries are checked separately: using the key is not enough. Bookings and their reference are saved together before confirmation; query measurements are saved in batches every 30 seconds.
Reception and review
Connection status, issues and oldest pending items. Median and p95 measured from reception or first IMAP detection.
Optional email alerts after 15 minutes of persistent connection failure or missing updates. One new alert per 24 hours; a complete Audutor outage needs an external monitor.
Email confirmations
An outbox with retries and messages needing review. Mail-server acceptance does not mean delivery or reading.
A reply from support
Opt into email alerts when support replies, then read and respond in the panel. Replies available for five minutes are grouped into at most one new batch every fifteen minutes. The Audutor team can also opt into internal alerts for missed response targets. In the live system, a pending support submission can be recovered after reloading the same tab and retried for 24 hours. This demo does not send support messages or email.
Human help in GuIA
A traveller requests help in the web chat; the team takes ownership and replies in the panel. The reply is available in that chat. A manager can opt into email alerts: new enquiries waiting five minutes, grouped into at most one new batch every fifteen minutes. This demo does not send email.
What each route connects
Email: creates, changes or cancels bookings from recognised formats. Uncertain messages need review. It does not change availability on platforms.
Your website: the page published by Audutor reads its capacity. Synchronisation with an external website requires implementing and checking its API connection. The panel separately shows availability requests, change retrieval, failed attempts and overdue checks against your expected interval. Receiving a response does not prove your website applied it.
WhatsApp / SMS: prepare reminders to send from your phone. Automatic GuIA transport and WhatsApp/SMS alerts still require integration.
A simulated sample is not proof of a real provider’s health. OAuth and the platform executor remain pending; the agent is unavailable for purchase.
Preview with simulated data. The platform agent is in preparation, unavailable for purchase and excluded from the price.
The agent that signs into your dashboards
reads your listings, counts the people each platform has on record and closes what is full — and nothing it says counts as done until you look at it🤖 The agent that signs into your dashboards off
You can run an agent that signs into your platform dashboards. It runs on your own computer, with your own session: Audutor stores no platform password. It closes full departures, yes — but what earns its keep is that it LOOKS: it counts how many people each platform has on record, so you learn about the bookings that never reached your inbox. And even when it says it has closed one, it still shows here as not closed until you check it yourself.
Count people. It opens your departure on each platform and says how many people they have on record. It touches nothing, and it is the most useful thing it does: it is how you learn about the bookings that never reached your inbox.
Read your listing. It reads what you have published and brings it back, to propose it in the brain. It does not even need to sign into your account for that.
Count reviews. How many sit unanswered. Answering them is yours: writing in your name is not something a program does.
Close. It tries, on the dashboards you tick, one by one. And even when it says it closed one, it still shows here as not closed until you look. It never paints a green ✓.
Reopen. Only what it closed, and only when you ask. It does the dashboard; you pick the moment.
✕ Open places on its own, or add capacity.
✕ Hold any password of yours: we never ask for one and never store one.
✕ Know who is coming. Each job tells it the platform, the dashboard and the time. No names, no booking references.
✕ Answer a review or write anything in your name.
✕ Enter a dashboard you have not ticked, or more times a day than you set.
Reconciliation & savings
the money you claw back from platforms — and the money you stop paying them⚖️ Platform reconciliation — who ends up paying for the gaps
ⓘ more
If fewer come, the only way to get that cost back is reporting the no-show in time; once the window closes, the company absorbs it. That is why the guide adjusts the head count on the manifest (timestamped) and why you set each platform’s rule here — configurable, because every one of them is different.From the guide’s head count plus these settings, Audutor builds the list of no-shows to report inside each platform’s deadline on its own, and works out what the company would absorb if they aren’t reported (you see it under 📈 Analytics).
💚 Your direct channel — the saving that pays for Audutor
Every person who books on your own site instead of a platform saves you their fee (~£2.50 per person on GuruWalk, and it varies by city). What you sell besides the tour, bundles, reviews and the guide’s QR all push this way. Drag the slider:
Guide payouts
tour by tour, with the books always balancedBy guide ·
| Guide | Tours | People | Takings | 💳 Booking costs | Net to split | 💵 To pay the guide | Company |
|---|
ⓘ more
With “taken off the takings”: the cost is paid first and the net is split. Either way, the guide never pays: a tour that took nothing leaves the shortfall with the company (shown in red). Worked out tour by tour, not in aggregate.Tour by tour
| Tour | Guide | Turned up | Takings | Platform fees | Guide’s share | Company’s share |
|---|
Revenue projection
your business plan, live — move a slider and watchⓘ more
It starts with Old Town Walks’ figures — in a meeting you put in the prospect’s instead and their business plan builds itself in front of them. Same split and cost modes as Payouts: what you project here is what you settle later.Analytics
how the business is doing, at a glance · July 2026Attendance by channel
Every point your own site gains is a fee that never leaves: try it on the Revenue projection.
Where your website bookings come from
By tour · by time slot
| Tour · time | Departures | People | Average per departure | Tip per person |
|---|---|---|---|---|
| Old Town · 10:00 AM | 3 | 57 | 19.0 | £12.10 |
| Old Town · 5:00 PM | 2 | 43 | 21.5 | £11.40 |
| Leith · 6:30 PM | 1 | 12 | 12.0 | £25.10 |
| Night walk · 9:00 PM | 1 | 2 | 2.0 | — (ticketed) |
ⓘ more
It is a ticketed walk, so the question is occupancy, not tips: move the time, cut the frequency, or push it harder to the people who did the free walk that morning. Leith is the opposite problem — small groups, but £25 a head in tips, so it earns its slot. Deciding this on the numbers instead of a hunch is what this page is for.By guide
| Guide | People | Tip per person | Rating |
|---|
The same numbers you’ll see under Guide payouts — one source of truth: what you analyse is what you pay.
📉 Booked vs actual — the gap the company pays for
ⓘ more
Every booked person who doesn’t appear costs you the platform’s fee unless you report the no-show in time. Here you see how much you have clawed back by reporting, and how much you would have absorbed otherwise.| Platform | Gap (people) | Reported | Clawed back | Absorbed |
|---|---|---|---|---|
| GuruWalk | 22 | 20 | £50.00 | £5.00 |
| Viator | 7 | 7 | — (no per-person fee) | £0.00 |
| FreeTour.com | 2 | 1 | £2.00 | £2.00 |
Each platform’s rule is set under 🔌 Channels → Reconciliation. Audutor builds the list of no-shows to report inside the deadline by itself — so none of them slip past you.
Your website
it comes from what you already wrote in the Brain — which is why it cannot go stale🕳️ What it still needs
An empty field does not appear: no label, no dash, no "ask us". If you did not say it, your page does not say it — same as GuIA.
👁️ How it will look
This is what a traveller sees. No photos, and it says why: the page holds up without them instead of leaving grey gaps. And no AI: these are your words, you sign the page.
🌍 Publishing it
Choose the address carefully: it will end up on posters and QR codes, and if you change it the links you already handed out stop working. What goes out to the street is put out by a person: choosing the address and flipping the switch are two gestures, never a side effect of saving a fact in the Brain.
Team & availability
who guides, when they can, and which departures need cover👥 Team ·
| Guide | Languages | Tours they guide | Rating | Guide can check in | Status |
|---|
“Guide can check in”: a permission you set guide by guide — switch it on and that guide can check people in from their own manifest; leave it off and only the manager can. Guides never see customer phone numbers: GuIA sits in between.
Already have a website? You do not
need to change it: Audutor can synchronise through its API. The connection needs adapting to your website and checking before it is operational. ⓘ more
It runs both ways, and
both are needed. Inbound: your site asks what departures exist and how many
seats are really left, then files the booking — if it retries after a double click
nothing is duplicated, because it matches on your own reference. Outbound: your
site asks every few minutes what changed, and hears that you cancelled Tuesday for
rain, that a walk-in took the last seats, or that you cancelled a booking from
here.
Without the way back, your site would sell seats that no longer exist and
stay quiet about cancellations that do — worse than no sync at all, because a site that
is half true gets used anyway and fails at the meeting point, in front of the
guide.
It asks rather than being told, on purpose: you open no port on your
server and sign nothing, and if one round fails the next one picks it
up.
If someone loses their email, you change
it from their row and they're back in. ⓘ more
Everything
about signing in hangs off the email address — the sign-in link, the code, and the way back
if a phone with a passkey is lost — so a guide who leaves the company where their mailbox
lived would be locked out for good. Changing it closes their open sessions and notifies the
old address: if someone ever took an account over by changing its email, the owner hears
about it from that notice rather than the day they can't get in. Your own address you change
yourself, in your own row. And if it's you who's locked out, we change it for you once we've
confirmed it by phone.
🔗 Guide page — the QR that turns a good tour into the next booking
ⓘ more
The moment that counts is the end of the tour: people have just had a good time and ask “what else do you run?”. The guide shows their QR and that recommendation lands on your site, not the platform’s. Each page carries the guide’s name, so the analytics tell you which guides bring bookings in.🗓 This week’s schedule
ⓘ more
Em·Ev, say — so nobody gets mixed up) and the cell takes on colour. If more than one guide is out, their initials run in order — and that order is the running order (first = lead guide). Hatched cells are days with no departure (tap them to add one); amber ones run but have nobody covering them.And when there is no previous week to
repeat — a new guide, the season starting, a tour you are launching — the panel
suggests who, and tells you why. ⓘ more
It suggests
by workload: whoever has fewest departures that week wins, which is the split you
already do in your head and the one your team argues about most. It says it with the
number in front — "2 this week, and has led it once before" — because a suggestion
without a reason is an order by another name: you cannot disagree with something when
you do not know how it was decided. It shows you the whole list before touching
anything, skips anyone who said they can't or would end up in two places at once, and
never overwrites what you set by hand. Accepting is yours: the system suggests,
it does not assign.
You do this once. The rota is a
weekly pattern, not a list of dates: you set it and it stays that way next week.
ⓘ more
When something changes — someone off
sick, high season, a new guide — you only touch what changed. The real panel also has
a “↺ Repeat last week” that copies who led each tour on the same day at the same time:
it tells you how many it will touch before touching them, never overwrites what you
set by hand, and skips anyone who said they can't or would end up in two places at
once.
In the live panel you review every proposal before saving. Each departure shows the guide, the reason, the duration and any language information still to check. If the proposal changes while you review it, you must review it again. Set the time between departures in Team & availability; scheduling respects it when the previous departure's end time is known. This demo shows a sample weekly pattern; it does not run the live panel's scheduling operation.
Time-based availability in the guide app. Guides can specify up to six time slots per day, unavailable, or unspecified. The panel checks whether the full departure fits their hours; missing duration leaves that check unresolved. Changing hours does not remove assigned departures. The manager can lock availability through a date for the whole company. A guide who cannot cover an assigned departure can still decline with a reason; the manager reviews the replacement. Scheduling preserves the historical guide of closed departures. Try time windows and assignment review in the pattern below. Date locking is available in the real app.
If a guide cannot cover a departure, they explain why in the app form. Their pending changes are checked before the departure becomes unassigned. The manager reviews the replacement, who then confirms coverage. The reason stays in the form if sending fails. This demo does not yet reproduce that form.
Guide access without a connection
In the app, guides can consult a previously downloaded manifest for the day and keep pending actions offline. If the server rejects their session, the app removes that copy and requires a new sign-in with a connection. Pending actions retain their guide. Access revocation cannot reach a device while it remains fully offline. This demo does not simulate sessions or offline storage.The new guide gets their own personal link (no account, no password) to set their availability. Phone and email are shown masked (GDPR).
🗓 Availability by guide
Each guide picks the tours they are available for, day by day — from their phone, on their personal link (no account, no password). Choose a guide and tick their cells; only days when that tour actually runs can be ticked.