Guest chooses the service
Service, route, vehicle, extras and guest details are selected once so Collins receives a complete request.
How booking works
Your reservation stays clear from the first request to the final confirmation.
Choose the service, send the trip details once and let Collins confirm the route, timing, payment option and next step without forcing you to rebuild the plan in chat.
Booking promise
After you send the booking, Collins should already have the details needed to confirm it cleanly.
One reservation: route, guest, payment option and notes stay tied to the same booking code.
No repeated chat: Collins should not need to ask for the same route, date and guest details again.
Guest confidence: you get a clear recap and next step instead of vague messages.
Steps
The booking should stay easy to understand from first click to confirmation.
Collins confirms the payment option
The payment step uses the same booking code, guest details, route and selected extras so nothing changes after the recap.
Confirmed payment keeps the recap updated
Once payment is confirmed, the booking recap and next step stay attached to the same reservation.
Follow-up stays consistent
Email, WhatsApp and the secure status link all repeat the same reservation details for the guest and Collins.
One booking recap
Every next step should read from the same reservation recap, not from screenshots, chat fragments and voice notes.
The recap has to be useful on the ground. That means guest identity, route, timing, service details, payment state and notes all stay tied together.
Lead name, email, WhatsApp and country so support starts from one contact record.
Airport, hotel, villa, Bavaro, Uvero Alto and the exact lane that was sold.
Date, pickup time, flight or booking reference and any arrival dependency.
Vehicle class, package logic, add-ons and the price that was actually accepted.
Deposit or full payment, paid status, transaction reference and currency.
Birthday details, child seats, grocery stop, villa check-in support or any note Collins needs for the service.
Payment support
PayPal is the online checkout now. CardNET and Square stay as confirmed payment paths when Collins activates them for a specific booking.
PayPal online: guests can pay deposit or full amount after the required booking details are complete.
CardNET and Square: used only after Collins confirms that payment path for the booking.
Same booking code: PayPal, manual confirmation and follow-up all stay tied to one reservation.
No guessing: if an option is not active for the guest, the page should ask for confirmation instead of showing a broken checkout.
Confirmations
Each message should make the booking easier to trust.
Client recap
Booking code, paid status, route, date, pickup time, add-ons, total paid and reply path.
Collins recap
Guest contacts, route, service type, add-ons, notes, pickup timing and booking reference.
Client follow-up
Fast reassurance in the channel that most guests actually answer after paying.
Collins follow-up
A short service recap that helps Collins reply fast and keep the plan clear.
Payment protection
The booking should be clear before the guest pays.
Clear acceptance before payment
The guest should accept route, timing, cancellation rules and service details before paying.
Clear receipt and booking recap
The receipt, booking reference and selected service should match what the guest accepted.
Proof after service delivery
Guest recap, Collins follow-up and post-service confirmation should prove that the service was actually delivered.
Manual ID only when something looks unusual
Do not ask everyone for documents. Reserve manual ID review for high-risk, inconsistent or suspicious bookings.
Connected support
The booking path keeps payment, email, WhatsApp and status updates connected to the same reservation.
Payment: Square, CardNET and PayPal can use the same booking code and reservation summary.
Verification: confirmed payment should update the booking before final follow-up.
Email: guest and Collins can receive the same clear reservation recap.
WhatsApp: guest and Collins can continue from the same booking details.
Duplicate protection: the same confirmation should not be sent twice for one booking.
Before the service
Before the guest is charged, the payment method and message contacts need to be clear.
Payment method on the same booking
PayPal, CardNET or Square should use the same reservation details the guest already confirmed.
Correct message contacts
Booking recaps should come from the correct Mr Collins Travel email and WhatsApp contact.
One complete booking check
One complete booking should prove that guest recap and Collins follow-up arrive correctly after payment.
Manual fallback if one message does not arrive
If one channel fails, Collins still needs the booking summary and route details in a usable manual recap.
Ready to reserve
Choose the service, confirm the details and keep one clear booking.
Start with the ride or experience, send the exact route and contact details, then Collins confirms the next step from the same reservation.