This static safety flow defines how Globotrip should protect travelers and guides before we connect real accounts, messages, bookings, and MySQL reporting.
Identity, local expertise, and safety agreement checks.
Keep itinerary, price, and safety-critical notes reviewable.
Reports route to admin review before real support tooling exists.
Verified guide steps
5
before approval
Safety report path
Admin queue
static now
Emergency profile
Recommended
traveler side
MySQL status
Final phase
not connected
These become backend policies, support templates, and guide approval rules later.
For first meetings, travelers and guides should start in a visible public location such as a hotel lobby, museum entrance, cafe, or official pickup point.
Share the meeting point inside the request thread before the tour starts.
Messages, itinerary notes, special needs, and agreements should stay inside the platform so support can review context later.
Avoid moving price or safety-critical discussions to external apps before confirmation.
Travelers should check that the guide name, profile photo, language, and destination match the request before starting the experience.
Use the verified guide badge and profile details as the trust source.
Travelers should add an emergency contact, allergies, mobility notes, and medical restrictions before multi-hour or outdoor tours.
Store this in the travel profile before requesting a proposal.
Travelers or guides should report requests for off-platform payment, unsafe itinerary changes, harassment, fake identity, or pressure tactics.
Use the static report form now; later it will create a support case in MySQL.
Before payment exists, cancellation rules remain a static policy placeholder. Later, each booking will inherit cancellation terms from the guide proposal.
Show policy summaries before proposal acceptance in the backend phase.
Name, language, destination, and verified badge match your request.
Use hotel lobby, official site entrance, or public cafe for first contact.
Emergency contact, allergies, mobility, food restrictions, and children ages.
Agree itinerary, price scope, and included items inside Globotrip messages.
Confirm legal name, profile photo, primary location, and contact method before guide approval.
Review destination knowledge, languages, sample tour ideas, and local experience evidence.
Guide accepts marketplace rules: public meeting points, no unsafe detours, no pressure, no off-platform payment requests.
Guide profile should include a strong bio, clear languages, tour categories, availability notes, and real traveler-friendly details.