A booked visitor waits at the main entrance while the guide meets everyone across the square. At departure time the group moves away, and an ordinary address no longer helps find the leader. Guided tour bookings need instructions for gathering, identifying the group and handling arrival after departure. This example of one public walk shows how to prepare those arrangements before opening bookings and verify them while reading the participant list.
Name the route, language and type of participation
First distinguish a public tour selling participant places from a private route ordered by one group. This example concerns a single public walk booked by different people. Its name should identify route and delivery language, such as “Market square history — in Polish”. Do not leave customers guessing whether their whole party receives a private guide.
Delivery language forms part of the service. Switching form text to English does not automatically change a Polish-language walk into an English one. If you provide a separate walk in another language, name and describe it according to actual staffing. The guide to multilingual customer service develops the broader communication.
Include route scope and planned duration according to the organiser's arrangements. Do not describe an automatically generated route or guarantee travel time from any hotel. Customers choose specific delivery at a given place and in a given language. Available variants should match what the guide can actually conduct.
Separate gathering from the beginning of the walk
Our fictional walk starts at 10:00 and the organiser requests arrival at 09:45. The first time means departure; the second allows visitors to find the guide and check their request. Do not display both as alternative starts customers can freely choose. The table assigns tasks around one delivery of the route.
Scroll the table sideways to see all columns.
| Moment | Task | Responsibility |
|---|---|---|
| Before 09:45 | prepare list and marker | guide |
| 09:45 | participants reach the meeting point | participants |
| 09:45–10:00 | identify requests and people | guide with party contacts |
| 10:00 | depart under agreed rules | organiser and guide |
Use “Arrive at the meeting point at 09:45; we depart at 10:00” in the description. Someone reading confirmation should understand which time begins the booked service. If the public calendar shows 10:00, do not change that to 09:45 in a later conversation without explaining gathering. Two times help only when their meanings remain unambiguous.
Also agree the guide's preparation before participants arrive, but do not transfer every internal task into visitor instructions. List and material checks belong to the organiser. Customers mainly need to know when to reach the right point. Do not promise the calendar automatically summons participants or conducts an attendance check.
Show the meeting point and how to recognise the guide
Enter a recognisable place name, full address and map link. Then check the exact pedestrian meeting point: side of the square, particular entrance or agreed marker. A pin at a large building may be insufficient when several groups gather nearby. Add the information needed to find this particular leader.
Take a current meeting-point photo and use it in the offer. If the guide uses a group marker, explain the actual identification method instead of inventing a universal umbrella colour. Check whether instructions remain accurate if the guide changes. A business name on a sign can be more durable than one person's name if that is how the organiser identifies groups.
Ask someone unfamiliar with the route to find the point using only the description. If they reach another gate, improve the location and photo. The service page guide covers clear scope. On a walk, this has an immediate delivery consequence: after departure, the correct building address no longer means the guide is present.
If building work or a closed entrance forces a new point, review already accepted requests. A new description helps later bookings but does not establish that earlier participants know the change. The organiser must communicate current instructions and check map and photo consistency. Do not leave the old meeting point in materials supplied to the guide.
Count places and request contacts
Count participants rather than requests alone. If a party of four submits one request, it takes four places on the public route. Its contact represents that particular party. Do not require four separate contacts simply to understand headcount.
In Meetlead Bookings, you can prepare an offer with participant places and location details. Set capacity according to the organiser's decision and check participant quantity selection. A place limit is not an automatic minimum for running the tour. If departure depends on a minimum number, organise that decision and its communication separately.
Keep headcount and recognisable requests on the gathering list so the guide distinguishes one party from several individual bookings. Do not expand the basic request with unnecessary data for every participant. If headcount changes before departure, check current capacity and agree the result. An extra person arriving does not establish that a place is free.
Agree the departure decision and handling of lateness
Agree beforehand who decides whether to start when operating conditions change. This could be the guide or the offer coordinator. Do not promise automatic departure once attendance reaches a number. The calendar contains an appointment, while actual departure needs your process and an assessment of the current situation.
The lateness rule should explain whether the group waits, for how long and whom a visitor contacts after departure. Do not copy another operator's rules as an industry standard. In our example, the organiser gives contact instructions after leaving without guaranteeing joining along the route. If the team offers another arrangement, its description must match real capabilities.
Separate the fixed meeting point from the group's current position. An offer map shows where to meet; do not call it guide tracking or a dynamic route. Staff should answer “I am here but nobody is present” by checking the appointment and departure stage. That question needs a responsible person rather than another decorative city photo.
Check the list before leaving the meeting point
Before departure, the guide reads specific requests and counts the people present. They compare this with planned attendance, identify parties and review unresolved cases according to the organiser's instructions. Counting everyone nearby is insufficient if other tours share the location. Each step should lead to an identified list for your particular departure.
Practise a missing party and a person who arrives with another date. Apply the agreed departure rule in the first case; in the second, check the booking instead of automatically increasing headcount. Read the contact for a meeting-point mistake too. The exercise covers leaving the location, which distinguishes a tour from a service premises waiting for its customer.
The online booking system guide covers intake more broadly. The next example, escape room bookings, gives another meaning to arriving before service. A route's result should be an offer whose participants understand language, place, gathering and start. The organiser also needs a workable group check before the guide leaves.
Meeting points and participation arrangements are illustrated in BerlinWalks' operator FAQ. Its lateness terms are not copied; the gathering example and group-list procedure are original.
Questions about tour requests
Does form language change the guide's language? No. Delivery language belongs to the selected offer's scope and should be stated clearly.
Does the map show the group's current position? Do not describe it that way. Offer location marks the meeting point; contact after departure needs separate handling.
Does reaching minimum attendance automatically start the tour? No. Place capacity and the organiser's departure decision are separate matters.
