The pickup problem a coloured map cannot solve
A guest books a tour with included pickup and selects a villa inside the advertised area. The map looks straightforward. On departure morning, the driver discovers a steep final road, no turning space and several buildings with similar names. The guest waits at reception while the vehicle stops at a different entrance.
This is a service-design problem before it becomes a communication problem. A coverage zone answers whether a location is normally served; it does not answer which vehicle can reach a particular door, where waiting is permitted or whether a shared route can absorb an unusual detour.
The method below is an original operating framework for a small tour company. It does not set universal transport charges, define a platform's current features or replace a driver's assessment of a road. Its purpose is to turn an ambiguous exception into a decision the team can deliver.
Use it alongside a normal pickup process, not as a reason to scrutinise every familiar hotel from scratch. The largest benefit comes from making unusual cases visible early enough to resolve them calmly.
Separate four different kinds of exception
An address exception means the booking location is incomplete, duplicated or points to the wrong building. Solve the location first; a price quote is premature when nobody knows where the guest will be.
An access exception means the destination is understood but the planned vehicle cannot use the final approach as expected. The solution may be a public meeting point or a different transfer arrangement, subject to operational approval.
A route exception means the location is reachable but its detour does not fit the shared departure. The issue is time and routing, not necessarily physical access. A private transfer might solve it, or the guest may choose to meet the existing route.
A service exception means the guest requires something not included in the standard transfer, such as a different vehicle arrangement or a collection outside the advertised area. Identify what is requested before offering a cost.
These categories keep the conversation precise. Telling a guest that their hotel is difficult is vague; explaining that the shared minibus cannot collect from that entrance gives them something they can act on.
Create a compact location record
For an unfamiliar property, record the public name, address, map pin, collection entrance and a short identifying description. Add the date checked and the person who confirmed the approach. A map pin and a hotel name should support each other, not compete.
Use a separate field for the guest-facing meeting instruction. Internal notes such as narrow driveway, dispatch approval needed should not be copied automatically into a confusing customer message. Convert the operational decision into a simple action.
Keep a photo of the approved public meeting point when you have permission and a valid business reason to retain it. It should show the entrance or landmark the guest will actually see, rather than a beautiful property image that does not help them find the driver.
Review who can see the record. A reusable public hotel entrance is different from a guest's private accommodation details. Avoid putting personal contact information into a shared public map list simply because it is convenient for dispatch.
Verify the approach with the people who use it
Ask the transport lead or driver to assess the proposed collection against the actual vehicle and route. A road that works for one vehicle may not suit another, and a turn that is possible when empty may be impractical during busy collection periods.
When appropriate, ask the accommodation for its recommended transfer meeting point. Confirm whether that is the same entrance the guest recognises and whether staff can explain it. A property may have a service gate, reception gate and roadside sign in different places.
A map can help locate and share a place, but it is not the operational approval. Google's saved lists and shareable location links are useful references; they do not establish turning room, permission to wait or the suitability of a road for your vehicle.
If you cannot verify the access before the booking cutoff, offer an arrangement you can verify or explain that the request is still awaiting confirmation. Avoid converting an unanswered question into a promise simply because the guest wants to complete the purchase.
Give the guest a choice they can understand
A useful response states the standard collection you can provide, an alternative if available and the point at which the guest must choose. Keep the difference practical: where they go, when they are ready and whether there is an additional transfer charge.
For example, an operator might offer included collection at a named roadside meeting point or a separately quoted private connection from the property. This is an illustrative service choice, not a statement that every property or operator can provide both.
Explain who arranges each section. If the guest must ask their hotel to reach the meeting point, say so before booking. If your company provides the connection, identify the contact and how it joins the main departure.
Do not present a meeting point as equivalent to hotel-door pickup without explaining it. A transparent alternative is usually easier to sell than a surprise on the morning of the tour.
Build a quote from the actual extra work
Price a separately offered connection from the service required: additional vehicle time, distance where relevant, waiting, coordination and any supplier charge. Use your own cost information and commercial decision, not a generic surcharge copied from another island.
Consider a fictional example. An approved additional vehicle connection costs the operator THB 600 to arrange, and the business decides to quote THB 750. The THB 150 difference is before any other applicable costs; it is not automatically profit. These figures are arithmetic examples only.
Write down whether the quote is per booking, per vehicle or per person. State passenger and luggage limits and whether the return section is included. Many disputes begin because one side understands a whole group transfer while the other understands a single direction.
Keep the quote linked to the approved arrangement. If the guest changes accommodation, the old quote may no longer describe the service being requested. Reassess before confirming rather than treating a previously paid amount as unlimited transfer credit.
Put the decision into one booking record
Once agreed, save the collection point, ready time, collection window if used, extra-transfer arrangement, contact method and approval status. Include who accepted the change and when. The team should not have to reconstruct the plan from several message threads.
Separate request, approved and communicated states. A guest asking for pickup at a new hotel is a request; a dispatcher approving the new route is an operational decision; the guest receiving and accepting the new instructions is another step.
Avoid marking the process complete merely because one staff member sent a message. Check that the departure team has the same version and that the guest has enough information to follow it.
If your software does not support all these fields, use a simple controlled template within the tools you already maintain. A consistent short record is better than an elaborate new system that staff abandon during the first busy morning.
Write instructions that work at the meeting point
Start with the action: be at the specified entrance or landmark at the stated time. Add the property name and a direct map link, then explain the identifying feature and contact method.
Use a photograph or short description that survives translation. In front of the blue gate beside the named shop is more useful than near the usual place. Avoid relying solely on left and right when the guest and driver may approach from opposite directions.
Distinguish ready time from the vehicle's expected collection window. If the guest should be present before a shared route reaches them, explain that plainly without promising a precise minute you cannot deliver.
For multilingual guests, review the final instruction in the language they will use. Confirm that times, names and the actual meeting location remain unchanged. A fluent translation of an incorrect pin is still an incorrect instruction.
Rehearse three common failure cases
First, the guest changes hotels the evening before departure. The staff member should reopen the location assessment, check the new route and replace the old instruction only after approval. The old property must not remain on the driver's active list.
Second, the accommodation says the guest can wait at reception, while dispatch has approved a roadside meeting point. Resolve the conflict directly and send one final instruction. Do not leave the guest to decide which organisation has the more authoritative message.
Third, a driver arrives and cannot safely use the planned approach. The operational lead should choose an appropriate next step and communicate it to the guest. Do not pressure the driver to continue because a sales message promised door pickup.
Use these examples in a short team practice session. Ask a new staff member to find the current arrangement from the booking record without help. If they cannot, simplify the record before adding another checklist.
Handle late guests without improvising a new policy
Define who can authorise waiting, a route change or a replacement transfer. The driver should know whom to contact and what information to report, while the guest receives a calm update.
Keep the evidence factual: vehicle location, contact attempts, the approved meeting instruction and relevant times. Avoid emotional internal notes that blame the guest before the situation is understood.
Apply the actual booking terms and authorised service decisions. Do not create a new penalty, no-show rule or refund promise in an improvised message. A pickup exception may involve a company error, a guest change or a communication failure; those situations require different responses.
After the immediate departure is resolved, record what should change in the reusable location record. A known entrance problem should not become a new surprise for the next booking.
Measure whether the process helps
Track a few useful outcomes: exceptions identified before departure day, bookings requiring repeated clarification, guests waiting at the wrong place, extra vehicle time and complaints linked to collection.
Use consistent definitions. An exception solved successfully before travel is different from a failed pickup. Combining them into one problem count can make a better process look worse simply because staff are recording more information.
Review a small sample of cases each week. Ask whether the location was identified correctly, the choice was clear, the price basis was understood and everyone used the approved version.
Do not judge the process only by surcharge revenue. A well-designed meeting-point alternative may produce no additional sale while protecting the departure time and improving the guest's experience.
A one-week implementation plan
Start with the ten locations that create the most repeated questions. Build a short approved record for each, check it with transport staff and prepare one guest-facing instruction. Leave unfamiliar properties on a separate review queue.
Next, assign one person per shift to approve exceptions and one place where the current decision is recorded. Give sales staff a clear way to request a decision without promising its outcome.
Finally, review the first week with drivers and customer-service staff. Remove fields that nobody uses, clarify repeated misunderstandings and keep the useful records current.
For the wider departure process, see captain and shore-team handovers. This pickup method supports any suitable booking workflow; it does not depend on an unverified promise about a particular marketplace feature.
Sources and method notes
Prepared on 22 October 2026. This article's operating framework, classifications, examples and sample figures are original Tripnatic editorial guidance. Map-list and location-sharing references were checked against Google Maps Help and Google's Maps tips. Road suitability and vehicle decisions belong with the operator's qualified transport team; maps provide location references rather than a vehicle-access certification.
