Push notifications Available now # Push notifications. Bring customers back to your app. Give customers a timely reason to return to your application, with the right screen waiting. Connect app and browser notifications to the customer’s next action. [Start now](/dashboard/signup) [Talk to sales](/demo?product=push) BIRD / PUSH Illustrative experience 01 The notification 02 The destination Reset example ↺ Friday, 18 September 13:30 f. Fieldnotes now ### Your afternoon awaits. ### Permission is off. ### Registration is no longer valid. ### Receipt is unknown. ### The useful moment has passed. Studio visit · Today at 14:00 No notification is shown to this example customer. Do not keep sending to this example registration. Provider acceptance does not confirm display or a read. This reminder expired at the visit start time. View your visit PUSH / EXAMPLE ### A timely invitation. One clear destination. Respect the customer’s permission. Open the screen the message promised. fieldnotes. / Your visit FRIDAY / 14:00 ### See you at the studio. Booking FN–1042 Experience Clay workshop Time Today · 14:00 Example content and data. Explore the workflow below; nothing is sent or changed in a live account. Companies that trust Bird across their communications. - [Airwallex](/customers/airwallex) - Uber - [Zillow](/customers/zillow) - [Glovo](/customers/glovo) - PayPal - Adobe [Read Bird customer stories](/customers) WHAT IT MEANS FOR YOUR CUSTOMER ## A useful nudge. A worthwhile return. Start with what the customer gains by opening the app. Plan the permission, the message, and the exact destination as one experience. 01 / Earn the invitation ### Ask at the right moment. Make the reason for notification permission clear inside a useful customer flow. 02 / Make it relevant ### Say why it matters now. Choose a timely update that helps a customer understand what has changed. 03 / Deliver the next step ### Open somewhere useful. Take the customer to the promised information or action in your application. PUSH / TRY IT YOURSELF ## One tap. The right place. Explore the link between notification permission and the application destination. Your product owns the experience after the notification opens. Interactive examples require JavaScript. Product details, setup choices, and guides remain available below. NOTIFICATION / THE INVITATION fieldnotes. now ### Your afternoon awaits. ### Permission is off. ### Registration is no longer valid. ### Receipt is unknown. ### The useful moment has passed. Studio visit · Today at 14:00 No notification is shown to this example customer. Do not keep sending to this example registration. Provider acceptance does not confirm display or a read. This reminder expired at the visit start time. Illustrative situation Permission allowed Permission denied Registration expired Receipt unknown Reminder expired Open concept ↗ Review recovery Allowed concept: the reminder is timely. A tap opens a destination; it does not prove an incremental booking. Respect denial. Keep visit details available in the app; do not repeatedly prompt or send an unsolicited alternate message. Stop targeting the invalid registration. The app team must obtain a current registration through the supported platform flow and recheck permission. Missing receipt stays unknown. Check supported telemetry and setup; do not infer delivery failure or send a duplicate reminder. Suppress the stale reminder. Re-evaluate the current booking before creating a new customer update; do not replay the old prompt. Recovery plan: the customer may change settings later. Read their current choice then; this example grants no permission. Recovery plan: retire the old registration, let the app refresh it using the supported platform flow, then recheck account and permission. No token was registered here. Recovery plan: reconcile the original attempt and supported receipt evidence. Keep unresolved delivery unknown; do not resend just because a receipt is missing. Recovery plan: discard the expired reminder and inspect the current visit. A useful new update needs its own trigger and deadline. Example destination opened. Provider acceptance, device receipt, opening and business outcome remain separate observations. YOUR APPLICATION / THE DESTINATION FIELDNOTES YOUR VISIT / FN–1042 ### A little space for your next visit. ### Friday, 14:00. See you at the studio. A sunlit ceramic studio Your application opens at the booking after the customer taps the notification. Normal authentication still applies. No destination opened. Resolve the selected situation before exploring the allowed concept. Illustrative booking FN–1042 opened. Your app authorizes access and records a booking-view event. No booking or device changed. ### Prepare the journey brief Useful trigger App owner and platforms Deadline and destination The trigger helps the customer now Permission and preferences are respected Deadline and safe destination are defined App owner and outcome measurement are assigned Prepare brief Export brief Configure your platform credentials and registration lifecycle. This illustration does not send a live notification. Measure eligible customers, provider acceptance, available receipts and authenticated booking views separately. Predefine a randomized holdout and outcome window to test incremental value. Planning example: remind Alex at 13:30 about the confirmed 14:00 visit. Respect permission, suppress stale reminders and open the authenticated booking. Measure a booking-view action separately from provider acceptance or receipt. Configure and test your platform setup first. Planning brief exported locally. Nothing was submitted to Bird. [Use the journey checklist ↗](#push-readiness) Interactive illustration · fictional customer and results · no messages are sent FIND YOUR WAY IN ## Earn the return visit. Bring a customer back ### Plan Push notifications. Scope platforms, permission, registration freshness and destinations. Connect your app and configure its notification credentials. [Talk to sales about Push ↗](/demo?product=push) Update a connected experience ### Use Realtime inside your app. Publish application events to connected subscribers when the person is already in the live experience. [Explore Realtime ↗](/realtime-messaging-api) ### The details behind your setup #### Permission & preferences Ask at a useful moment and respect the customer’s settings. Design what happens when Push is unavailable. #### Device lifecycle Associate the right account and device. Refresh registrations when tokens change and remove invalid registrations. #### The destination Deep-link to the promised information, with normal application authentication and access checks. GET STARTED ## Plan the reason to return. [Start now](/dashboard/signup) [Talk to sales](/demo?product=push) 01 [Choose the return moment ↗ Define what the customer should find after the tap.](/guides/design-a-push-notification-journey) 02 [Design preferences ↗ Plan devices, permissions, and unavailable-channel behaviour.](/guides/design-a-push-notification-journey) 03 [Open your Push account ↗ Configure credentials, register devices and send a first notification.](/dashboard/signup) THE COMPLETE BIRD PLATFORM ## Part of a bigger conversation. Keep building with Bird’s communication products today, and discuss where this channel can fit as the offering develops. f. Fieldnotes now #### Your visit is confirmed. Friday at 14:00 · Booking FN–1042 01 ### Push This step A concept notification points Alex to booking FN–1042. [Your studio visit. All in one place. fieldnotes. BOOKING FN–1042 Your studio visit. All in one place. Alex Lee · Friday, 14:00 Clay workshop · One guest View your booking ↗](/products/email) 02 ### [Email ↗](/products/email) Email retains the full booking details. [Today · 9:41 Your studio visit is tomorrow at 14:00. Booking FN–1042. Thank you. See you there!](/products/sms) 03 ### [SMS ↗](/products/sms) Your app chooses a consented text when appropriate; channel fallback is your policy. BUILD YOUR BIRD SETUP A useful next connection. [Realtime ↗ Update an active app Bring shared views and presence into the moment.](/realtime-messaging-api) [SMS ↗ Reach a phone number Plan reminders beyond the application.](/products/sms) [Email marketing ↗ Stay useful between visits Make email part of the customer relationship.](/email-marketing) [RCS ↗ Explore a richer message Plan how another channel supports the same customer moment.](/rcs-business-messaging) Plan the in-app moment alongside email confirmations and SMS reminders. Your application respects preferences and decides which channel should carry each update. [Plan your complete Bird setup ↗](/demo?product=push) LEARN / BUILD / OPERATE ## Go further with Push. [SETUP PLANNING Earn the return visit. A practical path through setup, implementation, and the choices that matter. Read the planning guide →](/guides/design-a-push-notification-journey) [Set up a Push campaign Register the app and devices, request permission in your application and connect the notification to its destination. Inspect the campaign result after a controlled send.](/docs/engagement-platform/knowledge-base/marketing/send-a-campaign/create-and-send-a-push-campaign) [01 Plan a push experience Permission, destinations, and the role of the application. ↗](#get-started) [Explore all resources Quickstarts, implementation guides, comparisons and migration.](/push/resources) PUSH / SETUP ## Plan the invitation and the destination. Connect your app or browser channel, configure credentials and register devices. Send timely notifications that open the right place in your application. [Start now](/dashboard/signup) [Talk to sales](/demo?product=push) [Talk to sales about Push ↗](/demo?product=push) YOUR PUSH SETUP Connect your app Set up Push and choose the platforms your customers use. Platforms Configure platform credentials and register customer devices. Lifecycle Plan account/device association and customer preferences. The wider journey Choose how Email or SMS supports the same customer moment. ## Push, answered. A FEW USEFUL ANSWERS ### Is this available for a new integration today? Push is available now. Follow the setup guide to connect your app or browser platform and configure credentials, device registration and notification permission. ### Can I begin with another channel? Yes. Explore the linked communication products and choose the ones that meet your current customer needs. Plan any additional channel once its requirements and availability are clear. ### Who owns notification permission and recovery? Your app team owns the permission flow, account association, registration freshness and destination access. Respect denied permission, stop using an invalid registration and suppress reminders after their useful deadline. Confirm platform-specific behavior before implementation. ### Does an opened notification prove business impact? No. Provider acceptance, any supported device receipt, opening and a completed business action are separate observations. A randomized holdout with a stated outcome window can test incremental impact; this concept measures none. ### How do I get started or speak to sales? Start in your workspace and follow the setup steps for your channel. Talk to sales for help planning a larger rollout. YOUR NEXT CONNECTION ## Make coming back feel worthwhile. [Start now](/dashboard/signup) [Talk to sales](/demo?product=push) [Explore the whole Bird platform ↗](/products)