Tour operators
Keep supplier changes, traveler decisions, and the final outcome in one case.
Post-booking operations for travel teams
Handle every travel change
from one place.
HANDA finds the booking behind a customer message, checks what must change, prepares the next step, and keeps the supplier result with the same request.
Find the booking Review the cost Confirm the result
Built for travel & operations-heavy teams
🇻🇳 HND-4821 · HO CHI MINH CITY → DA LATSAMPLE CASE · TOMORROW 23:00
TRAVELER MESSAGE“Can we leave at 23:00?”
BOOKING RECORDABX-74Q9 · matched
CASEHND-4821
REVIEW REQUIREDFROMHo Chi Minh City
TODa Lat
WHAT HAPPENS NEXTAsk the traveler to approve
WAITING FOR APPROVAL- Request
- Booking found
- 3Approval
- 4Supplier result
ONE REQUESTMessage, booking, and next step are linked.
One request, kept together
See how a customer change actually gets finished.
Follow one customer request as HANDA finds the booking, prepares the change, pauses for approval, and records the supplier's result.
REQUEST RECEIVEDCustomer asks for a change
WhatsApp · 10:42
BOOKING FOUNDThe right trip is attached
VN-4821 · ABX-74Q9
READY FOR REVIEWTraveler approves the exact change
23:00 · max ₫320,000
RESULT CONFIRMEDSupplier result is recorded
PRV-8291 · supplier confirmed
Sample case. This page shows the workflow only; it does not send a message, change a booking, or take payment.
ONE CASE · TWO VIEWS
Operators get context. Travelers get clarity.
Scroll once to move from the team's operating record to the traveler's decision screen.
TEAM VIEW · SAMPLE CASE
Ho Chi Minh City — Da Lat
Give every agent the complete picture.
The owner, booking, supplier decision, and evidence stay in one record instead of disappearing into side conversations.
- CASE
- HND-4821
- OWNER
- Mina Park
- NEXT STEP
- Traveler approval
CASE
SHARED RECORD · LIVEHND-4821HCMC → Da Lat · Maya Chen
- OWNER
- Mina Park
- SERVICE
- An Binh Sleeper
- DEPARTURE
- Tomorrow · 22:00
- NEXT STEP
- Traveler approval
Existing reservation identified
The supplier booking now points to the same trip and traveler record.
BEFOREUnlinked message→AFTERABX-74Q9 · matched
WHAT HAPPENS NEXTAsk the traveler before contacting the supplierMatched the supplier booking to trip VN-4821.
Sample case. This page does not send a message, change a booking, or take payment.
PERSONAL AND TEAM WORKSPACES
Traveling yourself, or running the operation?
Use Personal to manage your own requests. Use Business to coordinate travelers, suppliers, approvals, and departures as a team.HANDA PERSONAL
Manage my own travel.
Start withName · language · contact · consentTrip details come later.
- Traveler conversationAsk, clarify, and keep the trip context in one thread.
- Trip and booking memoryAdd the booking when you have it; signup is not tied to one itinerary.
- AI-prepared requestsTurn a change, cancellation, or local need into a reviewable proposal.
- Traveler-owned decisionsSee the exact action and ceiling before any supported execution.
Multi-country trip records are supported. Live place discovery and local map handoffs currently launch in Korea first.
Create a personal workspaceHANDA FOR TRAVEL TEAMS
Run travel operations.
Start withCompany · markets · volume · first sourceNo individual trip dates.
- Bulk booking intakeImport reviewed CSV data instead of rebuilding every trip by hand.
- One exception inboxKeep supplier messages, trip context, owner, and deadline together.
- Supplier and fleet operationsManage services, suppliers, vehicles, drivers, and assignments.
- Verified supplier contactUse verified channels, explicit approvals, and confirmed provider results.
CSV, manual intake, and the web workspace work now. Provider-backed channels activate only after that business verifies its account.
Create a business workspace TRAVELER DECISIONThe traveler sees only what they need to decide.
It is the traveler-facing side of a business case: a simple message, a bounded approval, and a status update backed by the same request history.
- 01Receive
- 02Match
- 03Approve
- 04Contact supplier
- 05Confirm result
START WITH WHAT YOU HAVE
Bring in bookings first. Connect messages when ready.
Upload the booking file your team already uses. HANDA creates the trip records, then connects verified messages to the right customer and service.
01
WORKS NOWBring in bookings
Bulk CSV turns rows into trips, travelers, services, and exceptions.
summer_departures.csv248 rows · mapped
02
VERIFY TO USEConnect a message channel
HANDA marks a channel active only after the exact account and reply route are verified.
WhatsApp Business
Credentials → callback → test
03
READY FOR REVIEWOpen one customer request
The message, booking, owner, required approval, and supplier result stay together.
VN-4821
Departure changeApproval required
Works nowCSV import · Web requests · manual message capture
Verify to useWhatsApp Business with an approved account and signed route
Manual captureEmail · LINE · Zalo original messages entered by a team member
Start with CSV or manual message capture. WhatsApp works only after its business account and signed callbacks are verified. Email, LINE, and Zalo can be recorded manually today; direct sync and replies are not connected. A delivered message does not mean the supplier completed the change.
FROM CUSTOMER QUESTION TO CONFIRMED RESULT