Notification severity tiers

travel.tech push and in-app notifications carry a severity field that tells
the mobile client how urgent the disruption is and how to present it to the
traveler. There are exactly three possible values.

Each event_type has a default severity, listed below. A strike-related
segment.at_risk, segment.disrupted, segment.cancelled, or
segment.delayed is always critical, whatever its default. For what each
event means and which ones reach the real-time stream, see
Event types.

Severity tiers

`info`

Low-urgency informational update. The traveler does not need to take action.

Examples

Event	Description
`segment.departed`	Flight or train has departed on time
`segment.completed`	Segment has arrived at the destination
`segment.rebooked`	Traveler has been moved to another service
`segment.rescheduled`	Schedule changed but no action required
`segment.risk_resolved`	A previously flagged risk has cleared
`segment.checked_in`	Check-in confirmed
`segment.boarding`	Boarding call issued
`segment.platform_changed`	Train platform change at departure station
`segment.early_checkin_available`	Early check-in is available at the stay (in-app only; no push)
`leg.fields_updated`	Gate, terminal, platform, coach, or seat change
`booking_lifecycle.submitted`	Booking has been submitted
`booking_lifecycle.sent_for_approval`	Booking is waiting for approval
`booking_lifecycle.confirmed`	Booking is confirmed
`assistant_reply`	The assistant replied in a conversation
`live_agent_reply`	A live travel agent replied in a conversation

UX guidance

Present as a transient toast that auto-dismisses after 3–4 seconds. A brief
appearance at the top or bottom of the screen is sufficient. No haptic feedback.

`warning`

Actionable update requiring traveler attention. The traveler should review the
alert and may need to act.

Examples

Event	Description
`segment.at_risk`	Connection or departure is at risk
`segment.connection_at_risk`	Connecting segment may be missed
`segment.disrupted`	Service disruption has been detected, including a diversion
`segment.delayed` (≤ 60 min)	Moderate delay; monitor for further updates
`booking_lifecycle.rejected`	Booking was rejected by an approver
`booking_lifecycle.fare_expired`	Fare expired before the booking completed

UX guidance

Present as a persistent banner that remains visible until the traveler
dismisses it. Use a medium haptic pulse (iOS: UIImpactFeedbackGenerator.medium;
Android: VibrationEffect.createOneShot(100, 128)).

`critical`

Urgent action required. The traveler must act immediately — rebooking,
contacting support, or making alternative arrangements.

Examples

Event	Description
`segment.cancelled`	Segment has been cancelled outright
`segment.partially_cancelled`	Part of the booked segment was cancelled
`segment.delayed` (> 60 min)	Severe delay likely requiring rebooking
`segment.overbooked`	The stay is overbooked
`booking_lifecycle.payment_failed`	Payment for the booking failed

Variable severity

Event	Description
`human_task.created`	A new task needs the traveler's decision. Severity rises as the task's deadline approaches.

UX guidance

Present as a full-screen modal or high-prominence alert sheet with a clear
call-to-action (e.g. "View options", "Contact support"). Use a heavy haptic
pattern (iOS: UINotificationFeedbackGenerator.error; Android:
VibrationEffect.createWaveform([0, 200, 100, 200], -1)).

Haptic summary

Severity	iOS feedback type	Android vibration
`info`	None	None
`warning`	`UIImpactFeedbackGenerator.medium`	`createOneShot(100, 128)`
`critical`	`UINotificationFeedbackGenerator.error`	`createWaveform([0,200,100,200], -1)`

Integration notes

severity is guaranteed to be one of info, warning, or critical. The
API enforces this at the schema level; no other values will ever be returned.
The event_type field (string, dot-separated domain event name) can be used
to determine which deep-link or contextual action to surface alongside the
notification.
Operational notifications (every segment.* and leg.* event) are sent for
a flight booking only once it is confirmed or issued. A flight still awaiting
approval, or one that was cancelled, rejected, failed, or voided, receives no
operational push or in-app entry, and events that happened while it was not
live are not replayed once it becomes live. Booking lifecycle notifications
(booking_lifecycle.*) are unaffected.
A critical notification for segment.cancelled bypasses the
policy-level suppression rules (it is always marked meaningful by
MeaningfulChangePolicy). It is still subject to the dispatcher-level
deduplication window. All other types are subject to both the policy
suppression rules and the deduplication window.

Reporting issues

This page is maintained by the BizAway integration team. To request changes or
report an error, contact your BizAway integration contact. Edits made directly
in the ReadMe dashboard are overwritten on the next publish.