Can AEP Use a Custom Service for SMS, Push, and Email?
Hello AEP Community,
I hope you’re all doing well.
TL;DR:
Can we use an external (custom) service to handle all email, SMS, and Push communications in AEP, instead of directly connecting to providers like SendGrid, FCM, Apple, or the built-in ones? What would be the compromises or challenges in doing so?
Detailed:
I’m exploring the idea of integrating a custom enterprise messaging service with AEP for managing all outbound communications (SMS, Push, and Email). Our service would act as the final step in delivering messages to customers or leads, replacing AEP’s direct connections to services like SendGrid, FCM, or telcos. Instead, AEP would route these requests to our centralized Message Delivery Service through:
- REST API (single and bulk)
- Pub/Sub Events
- File uploads
The idea is for AEP to send just the Universal Customer ID and some basic message details, while our service handles contact details, customer preferences (e.g., time of day they accept notifications, language, preferred channel, consent, etc.), and the actual message delivery.
The minimum required inputs for our service are:
- Universal Customer ID
- Preferred channel(s) to use (ordered by priority) or "ALL" for splashing
- Message priority (immediate, high, medium, low)
- Template to use
- Campaign ID (optional)
Our service would asynchronously return statuses such as:
- Bounced
- Delivered
- Read (if applicable)
My question is:
Does AEP support using an external message sender (instead of directly connecting to services like SendGrid, FCM, or Apple) for SMS, Push, and Email? What are the potential challenges or compromises we should consider when integrating this setup with AEP?
Thanks in advance for your insights!
Best regards,