Tour & transport operators
Respond to assistance requests linked to bookings your business owns.
Travelzi / Zi Safety by Travelzi
Safety Assist · booking-linked incidentsGive travellers a direct way to request assistance during an active booking.
Zi Safety connects eligible bookings to a structured assist path: the traveller requests help, booking and incident context reach the responsible vendor, your team acknowledges and responds, and unresolved cases can follow configured platform escalation — with a recorded timeline from open to close.
Eligible booking → traveller request → vendor response → configured escalation → closed with a timeline.
Eligible trips · Traveller SOS · Vendor triage · Location context · Timeline · Escalation
Who it is for
Tourism businesses that need clearer ownership when a traveller needs help mid-trip.
When a guest is on an active booking, informal chat threads lose context and ownership. Zi Safety gives travellers a supported assist entry and gives vendors a tenant-scoped desk to respond against their own bookings.
Multi-service agencies
Apply Safety Assist across supported booking families where eligibility windows are configured.
Guest apps & Tourism Portal
Eligible travellers can request help from the Tourism Portal, Travelzi tourist app or your branded customer app.
Platform operations
Use the Safety Control Room for cross-vendor visibility when incidents escalate beyond tenant acknowledgement.
The gap on trip day
Assistance needs context, ownership and a record — not only a phone call.
Without a structured path, teams waste time deciding who owns the booking, what the traveller already reported, and whether anyone acknowledged the request.
Unclear ownership
Staff may not know which vendor should respond first for a multi-party trip.
No incident trail
Chat history is a weak audit of what was requested, acknowledged and resolved.
Silent alerts
Unacknowledged requests need a configured escalation path — not hope.
Mixed channels
Portal, tourist app and branded customer apps need one assist workflow, not three competing processes.
Zi Safety structures the assist workflow your team can operate — with booking context attached from the start.
Traveller experience
How eligible travellers request assistance from supported guest surfaces.
Safety Assist is available to the traveller who owns an eligible booking — through the Travelzi Tourism Portal, the Travelzi tourist application, and vendor-branded traveller/customer apps that call the white-label Safety APIs. These are guest surfaces, not vendor staff tools.
Tourism Portal
Eligible guests can start Safety Assist from supported portal booking flows with category and booking context.
Travelzi tourist app
The public marketplace tourist app lets travellers view eligibility, choose an emergency category and submit an SOS against their booking.
Vendor-branded customer app
White-label traveller apps reuse Travelzi Safety Assist APIs so your brand can offer the same booking-linked request path.
Category + booking context
Travellers select an emergency category and attach the eligible booking (and item when required) so vendors see the right trip.
Location during an active incident
While an incident is active, travellers can share location updates. This is not continuous background tracking of every trip.
Device tokens & status updates
Supported apps can register device tokens and receive status / push updates where push delivery is configured.
Practical workflow
From eligible booking to a closed incident with a recorded timeline.
Faster context for the responsible vendor, clearer ownership, and a trail of what happened — then configured escalation if acknowledgement does not arrive in time.
Eligible booking
Safety Assist appears only for supported booking families inside configured eligibility windows.
Traveller requests help
The guest chooses a category, adds context and submits an SOS from a supported guest channel.
Vendor receives the case
Booking and incident details reach the responsible tenant’s contacts via supported notifications.
Acknowledge & respond
Vendor staff acknowledge, mark responding and work the case from the Vendor Safety Dashboard.
Location context (if shared)
When the traveller shares location on an active incident, teams can review freshness-aware context.
Configured escalation
If acknowledgement targets are missed, the incident can escalate for platform Control Room visibility.
Close with a timeline
Resolve the incident and retain the operational event trail for the assist case.
Official emergencies stay local
For immediate danger, travellers should still use official local emergency numbers and services.
Operator experience
A tenant-scoped Vendor Safety Dashboard for your own bookings.
Your Safety Assist desk only shows incidents linked to eligible bookings your business owns. One vendor cannot browse another vendor’s incidents — platform-wide visibility lives in the separate Safety Control Room.
Active incidents for your bookings
See open and in-progress assist cases tied to your tenant’s eligible bookings.
Needs acknowledgement
Identify requests waiting for acknowledgement or further response from duty staff.
Status & timeline
Review incident status and the recorded timeline of events as the case moves.
Location context
View available location updates shared during the active incident — with freshness awareness.
Escalate or resolve
Follow the verified acknowledge → responding → resolve path, with escalation when targets are missed.
Configurable response targets
Set acknowledgement minutes per tenant as operational targets — not a guarantee that help will arrive.
Supported capabilities
What Zi Safety implements in Travelzi today.
Mapped to the SafetyTracking module — traveller SOS APIs, tenant Safety settings, Vendor Safety Dashboard, notifications and the platform Safety Control Room.
Booking-linked eligibility
Assist appears for supported bookings inside eligibility windows — not for every historical record.
Emergency categories
Medical, accident, security, vehicle breakdown, lost/separated and related categories for clearer triage.
Vendor Safety Dashboard
Tenant-scoped desk for active, awaiting, escalated and in-progress incidents on your bookings.
Incident triage states
Acknowledge, mark responding and resolve — with events written to the incident timeline.
Notifications where configured
Database and email alerts to configured contacts; WhatsApp and push where those providers are enabled.
Configurable response targets
Vendors set acknowledgement minutes as targets that drive escalation — not guaranteed rescue SLAs.
Safety Control Room
Platform-admin cross-vendor visibility and escalation layer — separate from each vendor’s daily desk.
Active-incident location context
Location updates attach to an open incident when the traveller shares them — not continuous tracking of every trip.
See it live
Walk traveller SOS, vendor triage and Control Room escalation in one demo
Request a Zi Safety walkthrough mapped to how you handle trip-day assistance today.
Two different desks
Vendor Safety Dashboard vs Safety Control Room.
Keep tenant operations and platform oversight clearly separate so sales conversations stay accurate.
Vendor Safety Dashboard
Your tenant only. Duty staff respond to assist cases for bookings your business owns.
Safety Control Room
Platform-level cross-vendor operational visibility and escalation layer for Travelzi operators — not a government emergency dispatch centre.
Use cases
Where Safety Assist fits real tourism operations.
Tour departure days
Eligible guests signal for help while the trip window is active.
Fleet & transfer days
Vehicle and transport bookings can surface relevant categories where eligibility allows.
Vendor on-call response
Duty staff acknowledge and update status from the Vendor Safety Dashboard.
Branded traveller apps
White-label customer apps reuse the same booking-linked assist APIs beside the public tourist app.
Important Safety Notice
Zi Safety is travel-operations software for eligible bookings. It does not replace police, ambulance or other official emergency services, and it does not guarantee that help will arrive. For immediate danger, travellers should use official local emergency numbers. Location context applies to active incidents only — not continuous background tracking. Database, email, WhatsApp and push delivery depend on configuration and providers.
Related Travelzi products
Safety Assist sits beside the bookings you already sell.
Zi Tours
Tour bookings and tour-day operations that can become Safety-eligible.
Explore →
Travelzi One
Multi-service agencies running several booking families.
Explore →
Tourism Portal
Public discover-and-book surface where Safety Assist can appear for eligible trips.
Explore →
Smart Tour Planner
Private packages that convert into operable bookings.
Explore →
Frequently asked questions
Common questions
Is Zi Safety a government emergency service?
No. Zi Safety is Travelzi Safety Assist software for eligible bookings. For immediate danger, travellers should use official local emergency numbers and emergency services.
Which bookings can use Safety Assist?
Only bookings that pass eligibility rules and windows for supported module families. Ask Zi SoftTech which booking types are enabled for your tenant.
Where can travellers request assistance?
From supported guest channels: the Travelzi Tourism Portal, the Travelzi tourist application, and vendor-branded traveller/customer apps that use the white-label Safety APIs. These are not vendor staff applications.
What is the Vendor Safety Dashboard?
It is the tenant-scoped desk where your team reviews and responds to Safety Assist incidents for your own bookings. You do not see other vendors’ incidents there.
What is the Safety Control Room?
It is the platform-admin oversight surface for cross-vendor escalation visibility. It is not each vendor’s daily desk and not a national emergency control room.
Do acknowledgement minutes guarantee help will arrive?
No. Vendors configure acknowledgement or response minutes as operational targets that can drive escalation. They are not a guaranteed rescue SLA unless your commercial agreement separately defines one.
How do notifications work?
Vendor contacts can receive database and email alerts. WhatsApp and push notifications are available where those providers and channels are configured — delivery is not universal.
Does Zi Safety track travellers continuously?
No. Location updates are tied to an active assist incident. Do not market continuous background tracking, emergency geofencing or guaranteed live accuracy.
Can I request a demo?
Yes. Request a demo to walk through eligibility, traveller SOS, vendor triage, notifications and Control Room escalation.
Ready to operationalize trip-day assistance?
See booking-linked Safety Assist inside Travelzi.
We will show traveller request flows, your tenant dashboard, configurable response targets and how Control Room escalation differs from vendor triage.