Notifications

Push, SMS, and voice fallback delivery paths.

Overview

When a call arrives, Core chooses how to reach residents:

Push via registered Device tokens (FCM / APNs).
SMS approve/deny links when fallbackSmsEnabled is true.
Voice fallback to phoneNumber when fallbackCallEnabled or emergency forwarding flags apply.

Device API

Method	Path	Description
`GET`	`/api/admin/devices`	Audit devices
`POST`	`/api/admin/devices`	Register (typically mobile clients hit Core directly)
`DELETE`	`/api/admin/devices/:id`	Revoke

User fields

Field	Role
`preferredNotificationSound`	Default tone for new devices (`default`, `urgent_chime`, `intry_chime`)
`phoneNumber` / `phoneVerified`	SMS + voice fallback eligibility

Operational notes

Token rotation: expect periodic FCM/APNs updates from the app.
Do not log raw device tokens in analytics pipelines — treat as secrets.
Mixpanel / PostHog events may duplicate telephony logs; use Call IDs as correlation keys when possible.

Registration & invites

How residents onboard and tie accounts to units.

Webhooks

Inbound webhooks from Twilio, Stripe, and partners.

On this page

Overview Device API User fields Operational notes