Overview
Some of the most useful communications are the ones that happen automatically. A welcome email the moment a new member joins, an SMS when a claim status changes, a reminder when a balance hits a certain threshold. Behind the scenes, these are powered by custom events — signals from your own systems that tell CX Platform it's time to send something.
Because every business is different, custom events aren't enabled out of the box. They need a bit of design work upfront so we can map your triggers to the right Applications, channels, and rules. The good news is that once it's set up, the rest happens on its own.
Below is a quick rundown of what's possible, and how to get the conversation started with your ChandlerCX team.
Trigger sends from events in your systems
We can help you set up communication journeys that fire automatically when something specific happens in your environment. A few common examples:
- Status changes — a new member joins, a claim is lodged, an account is updated.
- Data conditions — balances cross a threshold, a risk indicator changes, or a value falls outside expected limits.
- One-off operational processes — special sends tied to a particular event, project, or business rule.
If you'd like CX Platform to send cross-channel communications or documents automatically when one of these conditions is met, get in touch and we'll work through it with you. You can learn more about the available APIs in CX Platform here.
Schedule sends via API
If your communications need to be scheduled from an external system rather than set up manually inside CX Platform, we can help with that too. Typical things we'll work through together:
- API call design — shaping the requests that create or update your scheduled sends.
- Inbound ETL layer — getting your data into shape before it triggers a send. We'll set up the extract, transform, and load steps so feeds coming in from your source systems are cleansed, mapped to the right Application fields, and ready to merge into your templates without any manual tidy-up.
- Recurring schedules and time zones — handling repeat sends and making sure they land at the right local time for each recipient.
- Batch coordination — lining schedules up with your internal batch jobs and cut-off windows so nothing fires at the wrong moment.
This is handy when you've already got an orchestration layer or scheduler on your side and want CX Platform to slot in alongside it.
Get started
Because these setups involve solution design and configuration specific to your tenant, they're not something you'll find as a toggle in the platform. The starting point is a quick chat with your Chandler CX team.
- Reach out to your support team to flag your interest.
- Share a brief description of your use case — what should trigger the send, what should go out, and to whom.
- Send through any existing API documentation or architecture notes you've got, so we can see what your systems already do.
- We'll arrange a scoping session to walk through the detail and agree on the right approach.
Not sure yet exactly what you need?
That's fine — a rough idea of the trigger and the message is plenty to start with. We'll help you shape the rest during scoping.
From there, our team will handle the configuration on the CX Platform side and work with you on any integration work needed at your end. Once it's live, your events will trigger sends automatically, with no manual lift each time something happens.