Notification severity tiers

Mercury 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.

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
`leg.fields_updated`	Gate, terminal, platform, coach, or seat change

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
`segment.delayed` (≤ 60 min)	Moderate delay; monitor for further updates

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
`leg.diverted`	Flight or train has been diverted to a different endpoint

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.
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.