Walking Tour Software: Ticketing, Guide Rotas and AI Enquiries

A small walking-tour company needs a booking tool that sells tickets against a group-size cap for each departure, plus a shared rota that names one guide for every departure. AI then drafts the writing around them: enquiry replies, private-group quotes, weather notices and guide briefings. The owner still sets the caps, confirms the rota and calls the weather.

A walking tour is simpler to run than a bike or boat tour, because the guide and the meeting point are the whole product and there is no fleet to schedule. That puts two numbers at the centre of everything: how many people one guide can lead well, and which guide leads which departure. Most of the software you will pay for exists to enforce those two.

Follow me on Instagram@sagnikteaches

Everything here assumes two to ten guides, fixed departures from one meeting point and private groups on request. If you also hire out bikes, the bike tour start-up tutorial covers the kit-hire questions that a walking operation never meets.

Connect on LinkedInSagnik Bhattacharya

Set the cap before you look at any software

The cap is the most people one guide can lead well along your actual route, and a booking tool can only enforce a number you have already chosen. Walk the route with a friendly group and ask four questions. Can the person at the back hear without a headset? Does the group fit on the narrowest pavement without spilling into the road? Do the stops (a courtyard, a tasting counter, a venue doorway) hold that many people, or does the venue set its own limit? Can the guide count heads at every road crossing? The lowest number that passes all four is your cap.

Subscribe on YouTube@sagnikteaches

Each tour gets its own cap. Say a history walk is capped at 16, a food walk at 10 because that is how many seats the tasting stops have, and a premium small-group version at 6. The booking tool should hold each cap separately, so a food-walk departure never sells place 11. The six settings below turn a cap into a working rule; the example values are illustrative.

Two of those rows are decisions rather than settings. The second-guide trigger is the one owners forget: on a busy Saturday the 17th booking either becomes a second departure with a second guide, or the tool closes sales at 16. Choose before the weekend, because "we'll see" is how one guide ends up leading 23 people along a narrow pavement.

A cost-per-departure sum that fixes your minimum group

The minimum group is a sum, not a feeling. Take a morning history walk with illustrative figures: a $24 adult ticket, a freelance guide paid $85 per departure, $3 for headset batteries and printed route cards, a booking plan at $39.95 a month spread over 60 departures (about $0.67 each) and card processing at an assumed 3% of the ticket. Your own figures will differ; the method is what to copy.

• Cost of running one departure: $85 + $3 + $0.67 = $88.67.
• Income from one ticket after processing: $24 x 0.97 = $23.28.
• Break-even: $88.67 divided by $23.28 = 3.8, so four guests.

Break-even is not the same as a minimum you can run on. Four guests leave $4.45 and still use a guide's morning, so I'd set the minimum a notch above, at 6 in this example, and decide in advance what happens at 4 and 5: run anyway, merge into the afternoon departure, or move guests to another day with a small credit. Writing that rule down before the first thin departure saves the awkward text at 7 am.

The same sum shows why fee structure matters. A 3% online fee on a $24 ticket is 72 cents, which nobody notices at 20 tickets a week. At 1,500 tickets a month it is $1,080 (3% of $36,000) before any monthly charge. Rerun the sum whenever your volume doubles.

Choosing a booking tool: eight questions, then the published prices

Tours are sold in small, fixed batches, so put these eight questions to any tool before you compare prices.

1. Can it hold a separate cap for each tour and each departure time, and show remaining places live?
2. Can you set a sales cut-off in hours before the start, and a minimum that alerts you rather than cancelling automatically?
3. Does it take $0 reservations, and deposits for private groups?
4. Can a guide open the guest list for their own departures on a phone, with notes and contact numbers, without seeing the whole business?
5. Does it send reminders and a weather message by email and text from one screen?
6. Does it sync with the calendar your guides already use, and with the marketplaces you list on, so a place sold in one cannot be sold again in another?
7. How does it handle refunds, reschedules and "move me to another day" requests?
8. What would it cost at ten times your current volume, counting the monthly fee and any percentage fee?

One guide running two departures a day rarely needs more than a hosted booking page and a calendar, and that is the end of the market where a flat monthly plan makes sense. Once you have several guides, private-group enquiries and a marketplace listing, questions 4 and 6 (guide access and calendar sync) decide the choice more than price does. Start with the cheapest tool that passes questions 1 to 5, and re-test question 6 the week you add a marketplace. The tour booking software comparison goes through more vendors and what small operators should test.

Free and pay-what-you-want departures need their own rules

A tip-based tour sells places at $0, and a $0 place is easy to abandon. The screen says 16 booked, eight people turn up, and the person who wanted place 11 was turned away last night. Three rules keep the list close to the real group. Collect a mobile number or email at booking, because that is how the weather message reaches everyone. Send a confirm-your-place message 24 hours before and release any place not confirmed 12 hours before; if your tool cannot do that, do it by hand from the guest list. And apply the same sales cut-off you use for paid tours.

Do not overbook free departures unless a second guide can take the overflow. A group of 22 with one guide spoils the walk for the 16 who arrived on time, and an empty place costs you far less. Decide too how tips are collected on the day (a card reader, a QR link or cash) and who counts them, because that is a cash-handling routine and no booking tool will do it for you.

Building the guide rota with AI doing the first pass

Rota trouble is mostly a calendar problem with three causes: guides give their availability in different ways, swaps happen by text message, and nobody sees the whole month at once. Fix the cycle first, then let AI help inside it.

1. By the 15th, publish next month's departures: date, time, tour and cap.
2. By the 18th, every guide fills in one shared availability sheet, a row per departure and a column per guide, marked yes, no or prefer not.
3. On the 19th, paste the sheet into an AI assistant along with your rules and ask for a draft.
4. Check the draft against the sheet, correct it and publish by the 20th.
5. Swaps go through you: two guides agree in the shared thread, and you update the sheet and the guide assignment in the booking tool the same day.

A single week shows how this behaves. The prompt below uses four guides and ten departures: a 10:30 morning walk every day and a 17:30 food walk from Thursday to Saturday.

You are drafting next week's guide rota for a small walking-tour company. Follow the rules exactly. If you cannot meet a rule, say so instead of bending it.

Departures:
- Morning highlights walk, 10:30, Monday to Sunday
- Evening food walk, 17:30, Thursday to Saturday

Rules:
1. Exactly one guide per departure.
2. A guide leads at most one departure a day.
3. Each guide leads 2 to 4 departures a week.
4. Only use a guide on a day and time they marked yes.

Availability (yes only):
Guide 1: mornings Monday to Friday
Guide 2: any departure Wednesday to Sunday
Guide 3: evenings Thursday to Saturday, and Sunday morning
Guide 4: mornings Monday, Tuesday, Friday and Saturday; Saturday evening

Output a table with the departure, the guide and a one-line check against each rule. Then list any rule you could not meet.

Here is a draft of the kind assistants return, with the slips left in (illustrative).

Below the table it added "Rules not met: none". Three rules are in fact broken, and two corrections repair all of them.

• On Thursday, Guide 2 leads both the morning and the evening walk, which breaks rule 2. Guide 3 marked Thursday evening, so the 17:30 goes to Guide 3.
• On Saturday, Guide 3 only marked the evening, yet the draft gives them the morning walk as well. That breaks rule 4, and two walks in a day break rule 2. Guide 4 marked Saturday morning, so the 10:30 goes to Guide 4.
• Guide 4 ended the draft with one departure against a minimum of two. The Saturday fix gives them a second, so rule 3 is met without a third change.

Notice that the assistant wrote a plausible reason for every line, including the wrong ones. A tally catches what reading does not: =COUNTIF(B2:B11,"Guide 4") counts one guide's departures when column B holds the guide names. Ask the assistant to list each guide's departures and totals as well, and send the draft back whenever its count disagrees with yours.

Name one on-call guide for each weekend and agree what standby is worth, whether that is a small fee or first pick of next month's departures. A sick-day swap is then one message to one person, not a group chat of five. If your guides would rather claim shifts than be assigned them, a sign-up tool can do that: SignUpGenius lists Free, Silver ($8.99), Gold ($22.49) and Platinum ($44.99) plans a month, with waitlists from Gold. Put a limit on claims per guide, or the first person to log in takes the best departures. The guide scheduling tutorial compares a shared sheet, a sign-up tool and a scheduling app for freelance guides.

Weather rule: write it once and let the software send it

Weather causes more arguments than any other booking issue, because the guest, the guide and the owner each have a different idea of "bad". Settle it once, in writing, and let everyone see it before they book. Here is a rule you could adapt.

Weather: our walks run in rain, wind and heat unless conditions are unsafe. We cancel or delay for lightning, severe wind, or when an official severe-weather warning covers the route. We decide 2 hours before the start and message everyone booked by email and text. If we cancel, you choose a full refund or a new date. If we run and you decide not to come, our normal cancellation terms apply.

The thresholds are yours to set; the point is that a guide can apply them without ringing you. Put a calendar reminder on each departure for three hours before, so the person who decides checks the forecast and warnings at a fixed time rather than when they remember. The decision stays human. What AI can do is write the three messages that follow from it, so that when you decide, nothing is composed under pressure.

Our weather rule is below. Write three customer messages for a walking tour: (1) we are running as planned, (2) we are running with a change, (3) we have cancelled. Each under 60 words, friendly and plain, with [first name], [tour name], [day], [start time] and [rebooking link] placeholders. Do not promise refund timings, compensation or anything that is not in the rule.

Rule: [paste the weather rule]

A typical cancellation message from that prompt reads: "Hi [first name], we're sorry to say tonight's [tour name] at [start time] is cancelled because of the severe-weather warning for the route. You can choose a full refund or a new date at [rebooking link]. We'll refund within 24 hours of your request. Thank you for understanding, and we hope to walk with you soon." Three edits are needed. "Within 24 hours" is a promise your rule does not make, and your payment provider may not keep it, so cut it. "Tonight's" breaks for a morning departure, so use [day]. And "severe-weather warning" is only true when that was the reason, so the template needs a [reason] placeholder you fill in.

Check where the messages go. Many booking tools can email and text from the guest list, so confirm yours does both. If you also message guests through the WhatsApp Business Platform rather than the free Business app, read Meta's pricing page first. Since 1 October 2026 each number pays for service messages after its first 1,000 in a month, and for utility templates sent while a guest's 24-hour window is open. If a departure was sold through a marketplace, read its supplier terms on weather cancellations before the first wet Saturday. For fuller wording and refund rules, the weather cancellations tutorial goes deeper.

Private groups: a flat fee, a per-head step and a quote email

A private booking is a different product: the group is fixed, the guide's time is exclusive and the price is quoted rather than listed. Keep it from eating your evenings by capturing the same ten facts every time. A short website form, or a list you reply with, should ask for the date and start time and how flexible they are on both, the group size split into adults and children, the children's ages, the language, the tour or theme they want, any mobility or access needs, whether they meet at your usual point or elsewhere, how they will pay (card or invoice), and the organiser's name and organisation.

Then price from a sheet, not from memory. This one is illustrative.

A staff team of 18 asks for a two-hour Friday afternoon walk. The first 12 people for 90 minutes cost $240. The six extra people add $90 (6 x $15) and the extra half hour adds $60, so the quote is $390, which is $21.67 a head. The deposit is $117 and the balance of $273 falls due a week before. Compare $21.67 with your public $24 ticket: the group pays a little less each and gets the guide to itself, a trade you can choose to offer or not.

Now let the assistant write the email, but do the sum yourself. Paste the enquiry and your price sheet, give it the total, and tell it not to recalculate.

Below are a private-group enquiry and our price sheet. 1) List the facts you can extract and any that are missing. 2) Draft a reply of under 150 words offering the quote. Use exactly these figures and do not recalculate: total $390, deposit $117, balance $273 due 7 days before. Do not add inclusions, discounts or extras that are not on the sheet. If a fact is missing, ask for it in one short question.

The usual slip is a friendly extra: "including a complimentary headset", or "a group discount has been applied", neither of which you offered. The other is quoting $21.67 a head as if it were a fixed rate, when the price changes if two more people join. The email should say "for up to 18 people". The per-person and group rates tutorial shows how to build the sheet itself.

Enquiry replies from a fact sheet, and what AI must not answer

Most enquiries ask the same handful of things. Put the answers in one fact sheet per tour: the meeting point described in words (a landmark, which side of the street), duration, distance and pace, surfaces and steps, where there is shelter or seating, toilets, pushchair and wheelchair access, dogs, children, languages, what is included, group size, the weather and cancellation rule, how to pay and move a booking, and how private groups are handled. Then give the assistant one instruction that does most of the safety work: answer only from the sheet, and where the sheet is silent, write "I'll check with the guide and reply today" and list the question for me.

The reason is that a missing fact is not a yes. Here is an illustrative enquiry:

Hi, there are two adults, a wheelchair user and a four-year-old in our group. Is the walk step-free, how long is it, and can we bring our small dog? We'd like Saturday morning.

A draft written without a steps line in the sheet will often say "Yes, the route is step-free and suitable for wheelchairs", because that is the friendliest answer. Your sheet said the route includes two flights of steps and that no step-free route has been mapped. The right reply says so plainly, offers what you can really offer (a private walk on a route you have checked, or a different tour), and does not guess about the dog until the sheet says whether dogs are allowed on the tour and at the stops.

Keep a short list of enquiries that always go to a person: specific access needs beyond what the sheet states, a child's medical or safeguarding question, refunds outside your policy, complaints, and questions from schools or companies about insurance and permits. For other languages and review replies, the tour guides and AI tutorial covers multilingual enquiry replies.

The same fact-sheet habit helps the guide. The evening before, paste the guest list into the assistant and ask for a briefing of under 120 words: group size, the lead booker's first name, notes such as a mobility need or a birthday, the weather decision time and the meeting-point reminder. Give it first names and notes only, not payment or full contact details, and read it before it goes.

Tests before the first paid departure, then a monthly look

Try to break the set-up before a guest does.

• On your phone, try to book place 17 on a departure capped at 16. The tool should refuse or offer a waitlist.
• Try to book one minute after the sales cut-off. It should be refused.
• Send the three weather messages to yourself by email and text. Check the placeholders filled in, the links work and nothing reads oddly on a phone screen.
• Ask a guide to open their guest list on their own phone, outdoors, in daylight, on mobile data. Can they read it and find the notes?
• Change the guide on a departure and see whether the guide's calendar updates the same day.
• Ask a friend to send you a private-group enquiry and time yourself from email to quote. Over ten minutes means the sheet needs work.
• Read every AI-drafted enquiry reply before it goes for the first twenty, then sample one in five for the first month.

Once running, a short monthly look keeps the set-up honest. Compare headcount at the meeting point with bookings to see how many people did not turn up, especially on free departures. Compare the average group with the cap: if departures sit at the cap, add one; if they sit near your minimum, merge two. Count the departures that ran below the minimum, the weather cancellations and refunds, the rota swaps, and how long enquiries waited for a reply. Ten minutes with those six numbers tells you which part of the system to change next.

Walking tour software: questions owners ask

Do I need ticketing software for a free or tip-based walking tour?

Yes, once you run more than a couple of departures a week. A reservation tool holds the group cap, collects a mobile number or email for weather messages and gives the guide a headcount. One or two departures a day can run from a shared spreadsheet, but when guests book the same slot from different places, double-booking and hand-typed messages cost more than a basic plan.

Should I pay walking tour guides per departure or per guest?

Either works if the rule is written down before the season. A flat fee per departure is the easiest to budget and protects guides on thin days. A base fee plus a small amount per guest above an agreed number rewards full groups. On tip-based tours, agree in writing who keeps the tips, and check the arrangement with an accountant or employment adviser.

Can AI build my guide rota?

It can draft a first pass from a written availability sheet and a short list of rules, which saves time. It will also say the rules are met when they are not, so check every line yourself, for example with a COUNTIF tally per guide, and publish the rota yourself. Never let an AI tool message guides or change assignments on its own.

Should the booking tool cancel a walk automatically in bad weather?

No. A person should make the call at the decision time written in your policy, because forecasts and warnings need judgement. Let the software do the sending: prepare run, change and cancel messages in advance so that once you decide, every guest gets an email and text within minutes and the refund or rebooking link is ready.

What should a private-group quote include?

State the date and start time, the group size the price assumes, the duration, the route or theme, what is and is not included, the deposit and when the balance is due, the weather and cancellation terms, and how long the quote holds. Keep the arithmetic in your own price sheet and let AI only turn your figures into a clear email.

Further reads

• Tour Cancellation Policy: Draft the Wording and Customer Messages With AI — Wording for the cancellation terms your weather rule points to.
• Reply to TripAdvisor Reviews as a Tour Company With AI — Reply to reviews once guests start leaving them.
• Viator and GetYourGuide Listings: Rewrite Titles With AI — Marketplace listings need different wording from your own site.
• Travel Industry AI Chatbot: What a Tour Operator Website Should Answer — What a website chatbot should and should not answer.
• How Small Tour Operators Use AI for Bookings and Itineraries — The wider picture of AI across bookings and itineraries.
• Mini Golf Business Software: Party Bookings and Season Passes — What mini golf software must do on a busy Saturday, with party and season-pass sums worked through, a rain rebooking rule, and where AI helps with the emails.
• 8 Examples of AI in Tourism From Guided Tours to Group Bookings — Eight practical AI uses for tour guides and attractions, each with the tool type, set-up time, a worked example and a check that it worked.
• Can You Make an AI Audio Tour Guide? Scripts, Voices and Licensing — A claim-log method for scripts, what four speech services' own terms say, consent wording for cloned voices and the royalty-free music trap.
• AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.

Sources: Bookeo, Checkfront, ROLLER and SignUpGenius pricing pages; Viator supplier cancellation policy; Meta's WhatsApp Business Platform pricing notice (all checked October 2026).