@silvio6
Most custom SMS providers support webhook functionality, a standard mechanism for real-time, event-driven communication between systems.
Here in AJO, an SMS webhook acts as an automated notification system. When a specific event occurs within the SMS provider's platform (e.g., a customer replies to an SMS, or the message is marked as 'delivered,' 'failed,' or 'opt-out'), the provider automatically sends an HTTPS POST request containing the event data to a predefined URL.
To ensure that these critical real-time events—such as inbound replies, delivery receipts (DLRs), or opt-out requests—are correctly recorded and associated with the individual customer's profile within AJO.
Now you have the AJO webhook URL must be shared with the custom SMS provider. Usually, providers configure their platform to use this URL as the endpoint for all relevant inbound and feedback events.
What this enables,
- Real-time Journey Adjustment: Journeys can be dynamically updated based on immediate customer interaction (e.g., exiting a journey upon receiving a reply).
- Accurate Reporting: AJO's reporting and analytics will reflect the true delivery status and customer engagement level.
- Compliance and Suppression: Opt-out messages can be processed instantly to ensure compliance with communication regulations.
