Email, text and WhatsApp your customers.
An email, SMS and WhatsApp sender that works with all of your operational data inside Calisto Pro. Pick a segment and write. Everyone who booked or ordered is already on the list.
The Campaign App for Email, Text and WhatsApp
A drag-and-drop builder, segments that stay current, automation triggers, signup forms, and deliverability. Pick a segment and write.
Email Builder
Build the email, with conditional content where the audience splits.
Send on the channel your customers actually read.
Templates
Start from a send that already works rather than a blank canvas.
Your Contacts
Hand-picked lists and segments that rewrite themselves.
Three Ways to Send
Campaigns, broadcasts, and announcements.
Automation
Sends already waiting on an event that has not happened yet.
Signup Forms
Where a new subscriber comes from, and what consent they gave.
Deliverability
What keeps the send landing in an inbox rather than a folder.
Performance
Opens, clicks, unsubscribes, and the split test decided for you.
0
delivery channels from one composer
0
contact list across every app
0
block types in the email builder
0
merge fields that read live data
Build the email out of blocks. Fill it from the record.
Eight block types dragged into order, rendering the same brand kit your website and your portals read. What goes in the gaps is a merge field, and conditional blocks show different content to different segments in the same send.
Header
Logo, masthead and preheader, from the brand kit.
Text
Rich text and links, in your own typography.
Image
From the shared asset library, with alt text.
Button
The call to action, pointing at a page or a form.
Divider
A rule between sections, so a long email breathes.
Spacer
Vertical space you control, in every mail client.
Social
Your channels as icons, declared once at brand level.
HTML
Raw markup for what the blocks do not cover.
Every field resolves against the live record at the moment the send goes out, not against a column in a list somebody exported three weeks ago.
{{contact.first_name}}MarisolRegistry{{booking.arrival}}14 Sep, 15:00Bookings{{deal.owner}}R. FerreiraDeals{{service.next_due}}21 SepDispatch{{event.venue}}Sala CaribeTickets{{listing.nightly_rate}}RD$8,400Listings · PulseBroadcasts on your own business number.
Through the official API, on the number your customers already have, with templates you submit once and reuse. Variables fill from the same merge fields the email builder reads, and delivery and read state come back per recipient.
Sending to eleven thousand people is easy. The forty who write back land on the same record, on the channel they replied on, in front of somebody who can answer.
Browse the library. Reuse across campaigns.
Filtered by channel, and authored centrally in Purview so every campaign starts on brand rather than on a blank canvas.
Rich HTML from the same blocks as any other send, with conditional sections. 24 templates.
Welcome
Sent when somebody joins, whichever surface they joined on.
Anniversary
On a membership or booking anniversary, read off the record.
Renewal
Before a renewal date, while there is still time to act.
Confirmation
Booking or purchase, with the details filled from the record.
Your contacts, segmented by what they did.
Everyone who booked, ordered, messaged or filled out a form is already a contact, so a segment is written out of what people did rather than what they clicked in an email. Open and click rates sit on the subscriber, not only on the send.
Subscribers
Your marketing contact list, with consent and its date on the record.
Lists
Static segments you build by hand and target when building a campaign.
The segment is a query over the operation itself, so it is right the first time and stays right without an import.
Everybody who stayed twice this year and has not been back since June is a segment, not a request to your data team.
Segment on what somebody bought and on what they did not. The customers who took the treatment but never the package are one line.
Consent, its date and the suppression state ride on the contact, so an opted-out customer cannot be reached by accident.
Three ways to send.
What separates them is the audience, the channel, and whether it is marketing at all.
Campaign
Targets a segment. Scheduled, or sent the moment you are happy with it.
Broadcast
Goes to everyone, on email, SMS, push and in-app at once.
Announcement
Not marketing. An operational notice that shows up inside the app.
There is a fourth way to send that nobody opens this app for: the other products queue their sends through the same engine.
One subscriber record, one consent state, one sending reputation and one set of results, no matter which app pressed the button. Bolt a standalone marketing tool onto a business and you get the opposite of all four.
The best sends are not the ones you remember to write.
They are the ones already waiting on an event that has not happened yet.
Set the trigger once, write the message once, and it sends itself.
Triggers fire on an event. Conditions filter who qualifies. Sequences drip the steps out over days or weeks, waiting and branching without anybody opening the app.
A marketing tool can only trigger on marketing events. These fire on a reservation confirmed, a payment cleared, a parcel delivered or a form submitted, because the operation is in the same database.
A form on your website that adds them to the list.
Submissions arrive as subscribers with consent recorded and its date kept, so nobody is on the list without a reason to be.
- 1
A form on your site
Published from Forms, or a signup block on any page you have built.
- 2
They submit it
Their details, and the consent box they ticked, with its date.
- 3
They are a subscriber
On the list, reachable, with the lawful basis to send held on the record.
A campaign is only half a purchase. The other half is the page the click goes to, and it is built in the same account.
The landing page composes from the same blocks and the same brand kit as the email, so the offer does not change on the way.
The click opens a booking screen with the dates and the rate filled in, and the reservation is attributed to the send.
The price in the message is the live price, so a promotion cannot quote a rate that no longer exists.
DKIM, SPF, DMARC, and bounce handling. Your emails arrive.
Rates over a window, suppression counted by reason, and a per-domain breakdown of exactly where sends are failing.
Reach is mostly identity. The domain, the sending brand and the lawful basis to send are three separate facts, and all three are held outside this app, which is why they hold up.
Who opened it, who clicked, who unsubscribed.
Per campaign and over time, exportable when somebody wants it in a spreadsheet. A split test runs two versions at a slice of the audience, then switches the rest to whichever won without waiting for you.
And if somebody on the list actually books or orders, you see what the campaign earned, counted in revenue from your own books.
Analytics
Open, click, unsubscribe, delivery and bounce rates per campaign, with trends over time and export.
A/B Testing
Subject line or content variants against sample groups, with the winner auto-selected.
ROI
Revenue generated against the cost of the send.
12.4K
Sends
+8%
34.2%
Open Rate
+2.1
1.8%
Bounce
-0.3
Where Campaigns touches everything else.
4 of these 6 connections are in your plan today. The rest stay visible so you know the instrument is there before you need it.
Deals
A segment is built from contact records rather than an uploaded list, so a send never goes to somebody who left last month.
Circle
A referred contact enters the welcome sequence with the referral already attached.
Reputation
A review request is sent as a campaign and its outcome is recorded against the review store.
Impreta
The same message published to your connected accounts is the message you sent, not a retyped version of it.
Studio
Artwork is designed in Studio and used here rather than uploaded twice.
Purview
The selected purview scopes the audience, the sending identity and the reporting.
No setup cost. Pay when you start using.
Email, SMS, WhatsApp, push and in-app, from one composer.
Unlimited contacts. Nothing is due when you subscribe; sends are charged as they happen. The Calisto Engage rate includes 10,000 emails a month.
Recommended for you
Works well together.
Calisto Deals
Calisto Circle
Calisto Reputation
Calisto Impreta
Calisto Studio
Calisto Purview
Included with every Calisto account
Account configuration and data rules.
Learn more →Everything included in Calisto Campaigns.
- Deals, Dispatch, Reputation, Circle, Impreta and the automation rules all queue sends through Campaigns, against one subscriber record, one consent state and one sending reputation. Engagement scores and recent campaign performance read back into those apps.
- Subscriber management with import/export. Static list segmentation. Consent tracking. Pending, unsubscribed and cleaned are separate subscriber states, because they mean different things.
- Segment on reservation history from Bookings, purchase history from Catalog and Orderflow, memberships lapsing or unused from Registry, attendance from Tickets, and guest network or terminal sign-ins from WiFi and Kiosks. Consent, tags, lifecycle stage and the interaction history on the Registry and Orbit contact are inherited by every segment.
- Fire a send on the reservation lifecycle from Bookings and Today, the five shipment events from Orderflow, paid, refunded or a cart abandoned from Payments, a submission from Forms and Sites, a resolved ticket or a satisfaction score from Desk, or any rule in Automations.
- Palette, fonts and logo declared once in Purview and composed into every template. Content scored against your brand standard by Ethos while the send is still a draft. Images from the shared Depot and Studio library, so a replaced photo is replaced everywhere. Group templates authored centrally in Blueprint with each location composing inside them.
- An offer page built once in Sites, the same offer inside your mobile app with push and in-app on the same campaign, a Bookings screen with the dates and rate prefilled, a live price from Catalog and Pulse, a published Forms submission returning as a subscriber or an RSVP, and the same offer on Navigator portals and Display screens.
- Replies across email, messaging and social arrive in Inbox beside the campaign that prompted them. A WhatsApp broadcast and the conversation it starts are one Link thread. A question becomes a Desk ticket with an owner, interest becomes a Deals opportunity with the campaign attached, and a call back from Voice or a room in Live files against the same contact.
- Campaign builder with audience targeting and geographic targeting map. Scheduling.
- Subject lines written and rewritten, a recommended send time, alt text for your images, and segment suggestions. Available as a paid add-on.
- Email with sender/domain verification, DKIM and a test send before the real thing. SMS with delivery tracking. WhatsApp with templates, tracking, and abandoned-cart. Mobile push and in-app messages on the same broadcast.
- Eight block types (header, text, image, button, divider, spacer, social and raw HTML), a call-to-action block linking to a published form, and merge fields across nine kinds of record: contact, account, deal, booking, service, event, listing, talent and app.
- Per-block rules combining with and/or, using is, is not, and any of, on guest segment, language, reservation type, length of stay and booking source. One email, a different paragraph per reader.
- Handset preview while you write, a segment and cost counter before you send, pass-through message pricing at carrier rates, per-recipient delivery status, and a text template library.
- Guided connection of your own business account, approved templates synced with their state, variable inputs filled from merge fields, delivery and read tracking, broadcast history, and abandoned-cart recovery.
- Channel-filtered template library. Milestone email templates for lifecycle automation.
- Event-driven triggers. Rule-based conditions. Multi-step drip sequences with a visual journey builder.
- Five shipment events (shipped, out for delivery, delivered, exception, return initiated) firing any of five actions, with a delay set in minutes up to thirty days and conditions on carrier, region and order value.
- Multichannel send across email, SMS, push and in-app, with total sent, average open and average click across every broadcast, and drafts that resume where you left them.
- Operational messaging for urgent, non-marketing sends.
- Campaign analytics with per-campaign metrics and export. ROI tracking. A/B testing with auto-winner selection.
- Delivered, bounced and complained rates over a window, suppression counted by reason, a per-domain breakdown of where sends are failing, and a trend line. Find unengaged contacts and clean the list.
- Newsletter signup forms whose submissions land as subscribers with consent recorded.
- GDPR consent tracking. Suppression lists. Data requests. Sender verification. Which brand and which location a message comes from is a governed Purview record, so a group with several trading names sends as the right one from one account. The preference centre is a page on your own site reading the same subscriber record, so somebody choosing to hear less does not have to choose to hear nothing.
- Event invitation campaigns with RSVP tracking.
- Campaign approval queue. Performance reporting.
Questions about Calisto Campaigns
Bookings and orders, not opens. The send is attributed to the revenue it produced because the campaign and the commerce records are in the same account, which is the thing an email tool bolted onto a business cannot do.
Your own records. Guests who stayed twice, members whose plan lapses next month, customers who bought one category and not the other. The segment is a query over the operation rather than a list you upload.
Yes, with consent state intact, which matters more than the addresses. A contact arriving without a lawful basis to send is imported as a contact rather than as a subscriber.
One composer, three channels, with the message adapted per channel rather than pasted. WhatsApp additionally requires template approval, which is handled in the app.
They pass through at what the carrier charges rather than being marked up, and SMS is counted by segment, so a long message costs more to send than a short one.
Yes. You connect your own WhatsApp Business account through a guided setup, and your approved templates sync in from the provider rather than being re-created here.
Sending from a domain you authenticated with DKIM rather than a shared one. Bounces and complaints go to a suppression list on their own, and a per-domain breakdown shows where sends are failing.
Yes. A campaign can sit in an approval queue so the audience and the content are signed off before the send is released.
Merge fields span nine kinds of record: the contact, their account, the open deal, the reservation, the service due, the event, the listing, the talent and the app. They resolve at send time against the live record, so the arrival time in the message is the arrival time in the booking. Individual blocks can also carry their own rules, which is how one email reads differently for a returning guest and a first-timer.
Yes. Five shipment events, from shipped through delivered, exception and return initiated, each fire any of five actions after a delay you set in minutes up to thirty days, and can be narrowed by carrier, by region or by what the order was worth.
A broadcast covers email, SMS, mobile push and in-app messages in one send, so somebody who has your app gets a push and somebody who does not gets an email without you running two campaigns.