Tech, ExplainedNetworking, infrastructure and security
Product

Notification infrastructure

One call decides: push, SMS, email or WhatsApp.

BEFORE ITAFTER ITNotificationinfrastructureSuprSendCOVERSChannel choiceFallbacksUser preferencesTemplatesChildcaremanagement software↗ CAMPUS MANAGEMENT SYSTEMSsends parentupdatesGovernmentcommunication platform↗ GOVTECHsends citizenalertshands overeach messageMessaging andvoice APIs (CPaaS)sends the SMSA2P SMS aggregatorBEFORE ITAFTER ITNotificationinfrastructureSuprSendCOVERSChannel choiceFallbacksUserpreferencesTemplatesChildcaremanagementsoftware↗ CAMPUSMANAGEMENT SYSTEMSsends parentupdatesGovernmentcommunicationplatform↗ GOVTECHsends citizenalertshands overeach messageMessagingand voiceAPIs (CPaaS)sends the SMSA2PSMS aggregatorBEFORE ITChildcare management software↗ CAMPUS MANAGEMENT SYSTEMS↓ sends parent updatesGovernment communication platform↗ GOVTECH↓ sends citizen alertsNotification infrastructureSuprSendChannel choiceFallbacksUser preferencesTemplatesAFTER IT↓ hands over each messageMessaging and voice APIs (CPaaS)↓ sends the SMSA2P SMS aggregator
Notification infrastructure receives one request for a class reminder, sends an app notification first, and sends a WhatsApp message when the student does not open it within 5 minutes.
opens a page inside this one a page in the same scene a page in another scene a concept page a label only, with no page

Notification infrastructure is software that lets an app send a notification with one API call, and then decides how it reaches the user: by app notification, email, SMS or WhatsApp. An API is a fixed format in which one program asks another to do something. The software keeps each user's preferences, applies the company's rules, and hands the message to the right delivery service.

Without it, every team in a company writes its own code for every channel. The payments team writes code to send emails, the orders team writes code for SMS, and nobody checks whether one user received three messages in a minute. Notification infrastructure puts all of this in one place.

Imagine a coaching institute's app in Kota that reminds students before each live class. The app's code makes one call: "Send the 'class starting' notification to student 40512, for the 7 p.m. physics class." The notification system looks up the student. He has the app installed. He has turned off marketing messages, but class reminders are allowed. The rule for this notification says: first send an app notification at 6:45 p.m.; if it is not opened within 5 minutes, send a WhatsApp message; if that is not delivered, send an SMS. At 6:45, the app notification goes out. By 6:50, he has not opened it. So the system sends a WhatsApp message through the WhatsApp Business API. He reads it at 6:52 and joins the class on time.

The system does several other jobs. It stores the wording of each notification as a template, in each language, so that the product team can change the wording without changing the code. It holds back messages that are not urgent during quiet hours, such as late at night. It combines many small updates into one summary, so that a user is not disturbed ten times. It also keeps a log of every attempt, so the company can see why a message did not reach someone.

The notification system does not deliver the messages itself. It hands each one to a delivery service: a messaging and voice API platform or an A2P SMS aggregator for SMS, an email service for email, and the phone maker's notification service for app notifications.

Notification infrastructure is different from a customer engagement platform. Marketing teams use an engagement platform to plan campaigns for groups of users. Engineers use notification infrastructure for the messages that the product itself sends when something happens, such as an OTP, a receipt or a class reminder. Urgent warnings to every employee, such as a fire alarm, are sent with critical event management instead.

Tech, Explained is a part of ingrid.fyi. Every page explains one piece of technology in plain words.