One system for bookings, payment, and guide scheduling in inbound travel.
What I built
Everything from a booking arriving to a guide starting work, connected as one flow.
- 01
Booking form
English and Spanish
- 02
Automatic pricing
Party size, itinerary, options
- 03
Payment through Shopify
Creates a draft order
- 04
Guide notifications
Sent to WhatsApp
- 05
Monthly reporting
Aggregated from booking data
The screens
I built the booking screen customers use, and the admin screen the internal team uses.
The figures below are illustrative diagrams. They are not screenshots of the actual product.
The customer-facing screen. Days are added one by one, and the price updates as details are entered. Displays in English and Spanish.
Internal screen. Cases can be filtered by status, from new request to paid and completed, with dates and party size at a glance. Values are hidden in this diagram.
Guides are managed with their rank, areas, and contact details. Notifications go to the contact registered here.
Each guide's open and confirmed days on a monthly grid. This is where available guides are found when scheduling.
Design decisions
I kept it from becoming over-built, so the team could use it as it is.
Connect to the existing payment flow
Rather than building a new payment flow, I connected it to the Shopify draft orders already in use.
Send notifications to WhatsApp
Guide notifications are sent to WhatsApp.
Show the booking form in more than one language
The booking form can be displayed in English and Spanish.
Screens that work without a manual
I designed the screens so the internal team and the guides could use them without reading a manual, with the state of things clear at a glance. Cases are colour-coded and filterable by status, such as new request, recruiting a guide, or paid, and the shift calendar shows open and confirmed days as symbols.
Protect customer and guide information
Because the system handles contact details for customers and guides, I built it with protections against attacks such as XSS (cross-site scripting). The admin screens require sign-in and separate what administrators and guides can see, and guides join by invitation.
If any of thissounds familiar
The work after an order comes in still depends on people. Details get copied between services. That is a fine place to start. I reply to every enquiry within 24 hours.