Automate
We build email and SMS automation: order and account emails sent by API, lifecycle and trigger sequences, segmented campaigns and SMS reminders, all driven by current CRM and shop data. Consent is stored per contact, and domains are authenticated the way Gmail, Yahoo and Microsoft now require.
Email and SMS automation sends the right message when something happens in your business: an order, a booking, a sign-up, an unpaid invoice, a customer who hasn’t bought in months. Sensaria builds it for companies in Switzerland and abroad on the data you already have in the CRM, shop or your own application, so every message uses current information and stops when it should. We cover transactional email, campaigns, lifecycle sequences and SMS, plus the parts that decide whether mail arrives at all: consent records, domain authentication and bounce handling.
Automate every message that follows a predictable event and says roughly the same thing each time. Start with transactional messages, because customers expect them within seconds. Then add lifecycle emails such as welcome and onboarding, then trigger marketing such as abandoned-cart reminders. Keep campaigns for content that really changes from one send to the next.
| Type | Examples | Trigger | Consent basis |
|---|---|---|---|
| Transactional | Order confirmation, invoice, password reset, appointment confirmation | Event in your system | Not advertising, as long as it carries no promotion |
| Lifecycle | Welcome, onboarding, renewal reminder | Sign-up, first order, contract date | Service information or advertising, depending on content |
| Trigger marketing | Abandoned cart, back in stock, win-back | Behavior or inactivity | Consent or the existing-customer exception |
| Campaigns | Newsletter, promotion | Schedule | Consent or the existing-customer exception |
| SMS | Appointment reminder, delivery window, promotion | Event or schedule | Consent for anything promotional |
In Switzerland, the Unfair Competition Act (UCA Art. 3 para. 1 let. o) requires prior consent for mass advertising by email, SMS and similar telecommunication, a correct sender and an easy, free opt-out in every message. Customers whose details you received through a sale may get advertising for your similar products or services without new consent, if they were offered an opt-out when you collected the details. The rule applies to B2B as well as B2C.
The Federal Data Protection and Information Commissioner summarizes the rules on its advertising page; complaints go to SECO. The revised FADP governs how the contact data itself is handled, and for recipients in the EU the GDPR and national e-privacy rules apply as well. We store consent as data: channel, status, source, timestamp and the text the person agreed to. The UCA does not prescribe double opt-in; we recommend it anyway, because it gives you proof when someone disputes a sign-up.
Mailbox providers filter on authentication and complaints, not only on content. Since February 2024, Gmail and Yahoo require senders of around 5,000 messages a day to their users to pass SPF and DKIM, publish a DMARC record (p=none at minimum) aligned with the From domain, offer one-click unsubscribe for marketing mail and keep reported spam below 0.3%. Microsoft has enforced similar authentication rules for Outlook.com since May 2025 and rejects bulk mail that fails them. Gmail moved to rejecting non-compliant traffic in November 2025.
What we set up:
This is familiar ground. We built InboxRatio, whose 15 free tools check SPF, DKIM, DMARC, BIMI, reverse DNS and blocklists. Our outreach platforms run a DNS pre-flight check before go-live and use a warm-up ramp that freezes and steps back when the bounce rate rises.
SMS gets read quickly and costs money per message, so use it for short, time-critical content: appointment reminders, delivery windows, pickup notices, verification codes. Promotional SMS falls under the same consent rule as email. We connect the SMS provider you choose through the same event layer as email, so both channels share consent and suppression data. To help with the choice, PingMyUsers, the directory of communication APIs we built, compares SMS, email and WhatsApp providers on sourced, dated facts.
Merge fields come from the CRM with fallbacks, so a missing first name never produces “Dear ,”. The language comes from the contact record, not from a guess. Templates are built in MJML so they render in Outlook as well as in Gmail and Apple Mail. Product blocks are filled from shop data at send time, so a sold-out item doesn’t appear. Every change goes to seed addresses before it goes to customers.
| Driver | Why it matters |
|---|---|
| Message types and languages | Each needs copy, a template and tests |
| Systems that trigger messages | Shop, CRM, booking tool or your own app each need an integration |
| List and consent history | Contacts without consent records can’t simply be imported into campaigns |
| Current deliverability | A domain with a damaged reputation needs repair before volume |
| SMS | Provider selection, sender ID setup and per-message costs |
| Reporting | Delivery and engagement data written back to the CRM |
After a short discovery we send a fixed-price or phased proposal. Sending-platform and SMS fees are separate and depend on your volume.
Email and SMS are the output channels for marketing automation and CRM automation. Order-driven messages depend on the data from your online shop, and events from other systems arrive through API integrations. For WhatsApp and chat, see AI chatbots and the customer communication solution.
We have written the sending side ourselves: SMTP sending with warm-up, IMAP reply and bounce tracking, suppression lists shared across instances, delivery status synced back from the email provider, and an MJML rendering pipeline. So we can tell whether a problem sits in your DNS, your list or your content. Sensaria AG is a Swiss company and works in English, Italian, German and French.
What's included
Order, invoice, account and appointment emails sent through an email API, with delivery status written back to your system.
Segmented campaigns with one-click unsubscribe, bounce handling and suppression shared with every other sending tool.
Welcome, onboarding, renewal, abandoned-cart and back-in-stock messages, each with a clear exit condition.
Reminders, delivery notices and codes through the SMS provider you choose; promotional SMS only to numbers with consent.
Double opt-in, consent records per channel with source, timestamp and wording, and one suppression list for all tools.
SPF, DKIM, DMARC with reporting, reverse DNS, separate streams for transactional and marketing mail, warm-up for new domains.
Events from the CRM, Shopify, WooCommerce or your own application trigger messages; opens, clicks and bounces flow back.
Responsive HTML templates built in MJML, in each of your languages, with merge fields that have safe fallbacks.
Bounce, complaint and unsubscribe rates per stream, with alerts when delivery drops or a trigger stops firing.
Typical scenarios
Order confirmation, shipping notice and a review request after delivery; product recommendations only with consent or on the existing-customer basis.
Booking confirmation by email, an SMS reminder the day before, and a rebooking link after a missed appointment.
Sign-up and activation emails triggered by what the user has or hasn't done in the product, not by fixed days.
Lists, consent history and templates migrated, so segments come from the CRM instead of manual exports.
An audit of DNS records, alignment, sending streams and bounce handling after a domain change or a sudden drop in delivery.
FAQ
Email marketing automation sends emails triggered by what a contact does, or by dates in your data, instead of by someone pressing send: a welcome series after sign-up, a reminder for an abandoned cart, onboarding tips after the first order, a win-back after months of inactivity. Content is personalized from CRM or shop data, and each sequence stops when its goal is reached or the person opts out.
In most cases, yes. In Switzerland, Art. 3 para. 1 let. o of the Unfair Competition Act (UCA) requires the recipient's prior consent for mass advertising by email or SMS, a correct sender identification and a free, easy way to opt out in every message, for B2B as well as B2C. EU countries apply similar rules under the ePrivacy Directive. The main exception is for existing customers, as the next answer describes.
Under the Swiss rule, yes, if three conditions are met: you received their contact details in the course of a sale of your products or services, the advertising concerns similar products or services of your own, and the customer was offered the chance to refuse such use when you collected the details. Each message must still identify you and include a free opt-out. The FDPIC notes that simply opening an online account does not count as a sale. The EU soft opt-in works in a similar way.
SPF lists the servers allowed to send mail for your domain. DKIM signs each message, so the receiving server can verify who sent it and that it wasn't altered. DMARC tells receivers what to do with mail that fails authentication and sends you reports. Gmail, Yahoo and Microsoft require all three from senders of around 5,000 messages a day, and smaller senders benefit as well.
Senders of roughly 5,000 or more messages a day to their users must pass SPF and DKIM and publish a DMARC policy aligned with the From domain. Gmail and Yahoo also require one-click unsubscribe for marketing mail, unsubscribes processed within two days and reported spam below 0.3%. Microsoft rejects non-compliant bulk mail to Outlook.com since May 2025, and Gmail has rejected non-compliant traffic since November 2025.
Use the same brand domain, but separate sending streams, for example one subdomain for marketing and another for transactional mail. Reputation is then tracked separately, so a complaint spike after a newsletter doesn't delay order confirmations or password resets. Both streams still need SPF, DKIM and DMARC aligned with the address customers see.
Compare coverage for the countries you send to, delivery reports, sender ID options, API quality, where data is processed and the price per message at your volume. Swiss and international providers both work; the right one depends on where your customers are. We connect the provider you choose through the same event layer as email, so consent and opt-outs apply to both channels.
Technology we use
TechnologyTransactional, lifecycle and campaign email plus SMS, triggered by events in your CRM, shop or app, with consent records that hold up under Swiss and EU rules and the authentication mailbox providers require.
