You pick the segment, and the message goes out by itself
Today we send by email and SMS, with a quota of its own per branch and templates with variables. WhatsApp and push come later, and we're telling you that plainly.
Email and SMS send; the rest, not yet
The system declares 5 channels, but only 3 really deliver: email, SMS and the panel alert. Don't build a campaign on one that doesn't deliver anything today.
- Email via AWS SES, at 14 sends per second to protect your domain
- SMS via AWS SNS, active from day one
- WhatsApp and mobile push: they don't send anything yet
Which channel sends today, and which ones don't yet
- Email (AWS SES) — active, with a limit of 14 sends per second so as not to overload the provider.
- SMS (AWS SNS) — active.
- Real-time panel alert — active; it is an alert inside the Dashboard, not a push notification to the member's phone.
- Coming soon: WhatsApp. The channel type exists in the template and the Dashboard has its own composer, but there is no real sending class behind it: today a message marked as WhatsApp doesn't go out.
- Coming soon: push notification to the app. Sending via Firebase is written in the code, but switched off: it doesn't run.
- No opt-out management yet. There is no per-channel opt-out that the member can switch on themselves, nor a consent record in the backend; if your center needs to manage them, that is currently outside the product.
You launch the campaign; the sending chains itself together
You choose the segment and the date; the system builds the message, sends it and stores the provider's response. You don't touch anything else after launching it.
- Segment by conditions, processed in batches
- The scheduled message is generated automatically, with no manual steps
- Send date and time, with its own time zone
The full chain, from campaign to sending
- You create the campaign — with its segment of recipients and its channels, as a draft, recurring, paused or archived.
- You run it — an engine evaluates the segment's conditions in batches and publishes an event for each recipient and channel pair.
- The scheduled message goes out by itself — a listener picks up that event and generates it; you build nothing by hand after launching the campaign.
- Scheduling — send date and time, with its own time zone.
- The real sending — a job resolves the provider, dispatches the message and stores its response and whether it arrived or not.
- Quota per branch and channel — a configurable limit per branch and provider, with a counter of sent, successful and failed messages.
You build the template once, for good
A template with variables leaves the message ready before you launch the campaign. When you no longer use it, you archive it: it stays there so you can look up old campaigns.
- System templates and templates of each branch's own
- Variables in square brackets, such as [nombre]
- Reply-to, CC and BCC per template; they're archived, never deleted
What can be customized in a template
- Two origins — system templates, common to the whole product, and templates of each branch's own.
- Variables — placeholders in square brackets, such as [nombre], in the subject and in the body of the message.
- Reply-to, CC and BCC — configurable per template, from the same form.
- Archived, not deleted. A template you no longer use stays archived and remains available so you can look up the old campaigns that used it.
- Channels declared in the template — it supports Email, WhatsApp, Push, SMS and Realtime, although today only three of those five (Email, SMS, Realtime) really send.
What people tend to ask about this module
Can I send campaigns over WhatsApp?
Not yet. The template type exists and the composer is in the Dashboard, but today there is no real WhatsApp sending behind it: a message marked as WhatsApp doesn't go out. It arrives in the next channels package.
Can I schedule an automatic birthday campaign?
Today it doesn't fire by itself on an event, such as a birthday or an overdue fee. You launch it yourself: by hand, or at the date and time you schedule.
How do I avoid burning my email domain when sending to the whole database?
Sending runs at a controlled rate of 14 messages per second, and each branch has its own quota per channel, with a counter of sent, successful and failed messages.
Can I manage a member's communication opt-outs?
Not within the system today. There is no per-channel opt-out or consent record in the backend; if your center needs to manage them, that is currently outside the product.
Modules that often go with this one
- CRM and customer lifecycleEvery prospect with their stage, their owner and their follow-up date.See the module
- Surveys and feedback collectionQuestions designed so members genuinely answer, not just to get it over with.See the module
- Fee, access and facility usage controlYou set once what each fee allows, and the turnstile enforces it on its own.See the module
Want to see it working?
We'll show it to you with your own case: your fee types, your branches and whatever currently forces you to use two programs.
Request a demo