• About us
Log inDemo

SMS Marketing · Marketing

Send the SMS from the record it is about. Read the reply on it.

From the segment to what it did, in five steps.

The message starts from a segment, or from a record

A campaign goes to a segment: a filter on the contacts you already hold, bought in the last twelve months, booked this quarter, opted in. A reminder goes from one appointment, a delivery notice from one order, and the record's fields are in the text before anyone types.

From the segment to what it did, in five steps.

  1. A campaign goes to a segment: a filter on the contacts you already hold, bought in the last twelve months, booked this quarter, opted in. A reminder goes from one appointment, a delivery notice from one order, and the record's fields are in the text before anyone types.

  2. Before the message is queued, the contact's SMS consent is read: opted in, when, from where, and whether a STOP came back since. A contact that fails the check is listed with the reason, not dropped in silence, and the segment does not get a vote.

  3. The message leaves through the SMS provider connected to your workspace, under your sender name, and comes back with a delivery receipt on each contact: delivered, pending, failed. The campaign shows the count; the contact shows its own line.

  4. "YES" lands on the appointment and confirms it. "Wednesday instead?" lands on the same appointment as a message to the host. A reply to a delivery notice lands on the order. The person who reads it sees the record, not a thread that could be about anything.

  5. Delivered, replied, confirmed, rescheduled, ordered: read on the campaign and on each contact, from the records the replies landed on, not from a click counter's guess. The month's reminders say how many no-shows they left.

Consent is a field on the contact, not a list you keep somewhere else.

Opt-in with its date and its source, opt-out with its date, and the STOP a contact texted back are fields on the contact record, with their history. Every send reads them first, the campaign and the single reminder alike: a contact who texted STOP on Tuesday is out of Wednesday's segment without anyone editing a list, and the reminder rule skips them too. A contact is exported with its consent history, and a request to be forgotten is one action on one record.

See it on your own data

What a campaign needs.

Which records send, what the text says and what a reply does are yours to set.

See it on your own data

A segment on your own records

Bought in the last twelve months, booked this quarter, an invoice open more than 30 days: a segment is a filter on the contacts you already hold, refreshed the moment you send.

Scheduled, or fired by a record

Thursday at 10:00, the morning of the appointment, or when the order is marked loaded: the trigger is a time or a change on a record.

Held for approval

A campaign to a segment waits for the person who signs it off; a reminder from a rule does not. Who approves is a rule on the campaign.

One message, from the record

From the appointment, the order or the contact: one text, typed by hand, with the record's fields offered as you type.

A short link that comes back to the contact

The booking link in the text is short, and the click is written on the contact that clicked, not on a dashboard nobody opens.

Delivery receipts on the contact

Delivered, pending, failed, per contact, from the provider, next to the reply and what the reply did.

The same SMS, for a grooming salon and for a food distributor.

What adapts: the record the message is sent from (an appointment, an order, a contact), the fields in the text, what fires it, what a reply is allowed to do, where consent was collected, and where the reply lands. Two businesses can run SMS Marketing and disagree on every one of those.

See it on your own data

A pet grooming salon sending appointment reminders

The message goes from the appointment 24 hours before, with the pet's name, the service and the groomer in the text. YES confirms the appointment; any other text lands on it as a note for the front desk. Consent came from the booking form, and the reply lands on the appointment.

A food distributor sending delivery notices

The message goes from the order when it is marked loaded, with the order number, the delivery window, the number of crates and the driver's first name. A reply ("back door, after 7") lands on the delivery and the driver sees it on the route. Consent is per contact, collected with the customer agreement, and the reply lands on the order.

The reply lands on the appointment it answers.

"Wednesday instead?" is not a ticket, not an inbox item, not a task for someone to match against a calendar. It is a message on the site survey of 22 Sep at Delcourt & Fils, under the reminder that asked, and Thomas answers it from there. When he moves the survey, the next reminder goes out with the new time, from the same record.

See it on your own data

This is the room.

One campaign as a list of contacts: consent as it was read, delivery as the provider reported it, the reply, and the record the reply landed on. The totals at the bottom are the ones that cost or made money.

See it with your own contacts

The SMS tool you would otherwise buy holds the number and the text, never the appointment.

  • A campaign to a segment

    A spreadsheet
    No
    An SMS tool
    Yes, to an imported list
    A suite module
    Yes
    Enobase
    Yes, a filter on your contacts

  • Consent and STOP kept per contact

    A spreadsheet
    A column
    An SMS tool
    Yes, on their list
    A suite module
    Yes, on their contact
    Enobase
    Yes, on the contact, read before every send

  • A reminder sent from the appointment

    A spreadsheet
    Copied
    An SMS tool
    By file or API
    A suite module
    Sometimes
    Enobase
    Yes, from the appointment itself

  • The order's fields in the text

    A spreadsheet
    Copied
    An SMS tool
    From list columns
    A suite module
    Partly
    Enobase
    Yes, the record's own fields

  • The reply on the record it answers

    A spreadsheet
    No
    An SMS tool
    In their inbox
    A suite module
    In their inbox
    Enobase
    Yes, on the appointment or the order

  • What it did, read from the records

    A spreadsheet
    No
    An SMS tool
    Clicks
    A suite module
    Partly
    Enobase
    Yes, confirmed, rescheduled, booked

  • Time to live

    A spreadsheet
    A day
    An SMS tool
    A day
    A suite module
    Weeks
    Enobase
    One week
What you needA spreadsheetAn SMS toolA suite moduleEnobase
A campaign to a segmentNoYes, to an imported listYesYes, a filter on your contacts
Consent and STOP kept per contactA columnYes, on their listYes, on their contactYes, on the contact, read before every send
A reminder sent from the appointmentCopiedBy file or APISometimesYes, from the appointment itself
The order's fields in the textCopiedFrom list columnsPartlyYes, the record's own fields
The reply on the record it answersNoIn their inboxIn their inboxYes, on the appointment or the order
What it did, read from the recordsNoClicksPartlyYes, confirmed, rescheduled, booked
Time to liveA dayA dayWeeksOne week

Questions about SMS Marketing

Yes. On its own it is a contact with a consent field, a segment, a campaign and the replies. Turn Appointments on and a reminder goes from the booking and the reply confirms it; turn CRM on and a reply from a campaign can become an opportunity on the contact.

Enobase Email MarketingThe email to the same segment, from the same contacts and the same consent fields.ExploreMarketing AutomationThe rule that sends the SMS the morning of the appointment, and the email the day before.ExploreCRMThe contact the message went to, and the opportunity a reply can become.Explore

See Enobase on your own contacts.

Book a demoGet access
Solutions
  • Finance
  • Quotes
  • E-Invoicing
  • HR & Payroll
Industries
  • Catering
  • Construction Company
  • Private Equity
  • All industries
Platform
  • Data Model
  • Knowledge & Collaboration
  • AI & Workflows
  • Analytics
  • Integrations
Company
  • About us
  • Hiring policy
  • Press & Brand
  • Download
  • Privacy
  • Terms
  • Subprocessors

© 2025 Enobase, Inc. All rights reserved.

  • LinkedIn
  • X
  • GitHub
marketing/asset-status-roll
widget: marketing/asset-status-roll family: widget kind: run frame: sticker subject: one contact's SMS consent field re-read over time, each reading on top of the one it replaced move: the STOP reading stacking onto the opt-in, the field's current value settling to Opted out neighbour: asset-status-roll · reused; the field is SMS consent and the readings are consent events content: Maison Berger, reception · SMS consent · 3 Feb 2026 Opted in, source: order form · 22 Sep 2026 Campaign sent, consent read: opted in · 22 Sep 2026 STOP received by reply, source: the contact · now: Opted out, excluded from every segment props: the contact, the readings not: a legal register static: yes
Open asset editor
marketing/asset-workflow-node
kind: record, sticker; three filter lines "Bought since 1 Oct 2025", "SMS consent: opted in", "Country: BE, FR" and the count "321 contacts"
Open asset editor
marketing/asset-workflow-node
with trigger "Order marked loaded", if "SMS consent = opted in" then "Send delivery notice", else "Note on the order, not sent"
Open asset editor
marketing/widget-mail-approval
with "Autumn opening, showroom · 318 recipients · held for Mathilde Renard · Approve, Edit"
Open asset editor
marketing/widget-actions
with Send SMS, Send reminder now, Copy booking link
Open asset editor
marketing/widget-experience-detail
kind: record, sticker; "eno.be/k7Q2" resolving to "Book a walkthrough", clicked by Léa Dumont 22 Sep 10:04, on the contact
Open asset editor
marketing/asset-activity-list
with "Reminder sent 08:00 · Delivered 08:00:14 · Reply YES 08:03 · Appointment confirmed 08:03"
Open asset editor
marketing/widget-experience-detail
widget: marketing/widget-experience-detail family: widget kind: record frame: sticker subject: one business's version of the unit of work, its own fields visible move: the fields that differ from the other case landing last, marked neighbour: widget-case-card · reused; the content is this case content: Grooming salon · Message: appointment reminder · From: the appointment, 24 h before · Fields: pet, service, time, groomer · Reply YES: confirms · Other reply: note on the appointment, front desk notified · Consent: booking form · Lands on: the appointment · marked fields: Fired 24 h before, Reply confirms, Booking form consent props: the business label, the object, the marked fields not: a filled operational record; this is the shape one business gave it static: yes
Open asset editor
marketing/widget-experience-detail
widget: marketing/widget-experience-detail family: widget kind: record frame: sticker subject: one business's version of the unit of work, its own fields visible move: the fields that differ from the other case landing last, marked neighbour: widget-case-card · reused; the content is this case content: Food distributor · Message: delivery notice · From: the order, when marked loaded · Fields: order no., window, crates, driver · Reply: free text, on the delivery, driver notified · Consent: customer agreement, per contact · Lands on: the order · marked fields: Fired by a status, Reply to the driver, Agreement consent props: the business label, the object, the marked fields not: a filled operational record; this is the shape one business gave it static: yes
Open asset editor
marketing/widget-invoice-issued
widget: marketing/widget-invoice-issued family: widget kind: record frame: sticker subject: a two-way SMS exchange held on the appointment it is about, the host answering from the record move: the client's reply arriving under the reminder, the host's answer typed from the record, the appointment date changing behind both neighbour: widget-reply-on-record (S2) · reused; the reply is free text and the exchange continues rather than a keyword closing it content: Site survey, Delcourt & Fils · site office · 21 Sep 08:00 reminder "Karim will be on site on 22 Sep at 09:00" · 08:07 reply "Wednesday instead?" · 08:21 Thomas Peeters "Wednesday 23 Sep at 09:00 works, I have moved it." · survey now 23 Sep 09:00, Karim Haddad, status Rescheduled · next reminder: 22 Sep 08:00 props: the record, the two sides, the change made not: a shared inbox static: no
Open asset editor
marketing/screen-events-table
screen: marketing/screen-events-table family: screen view: list nav: Inbox, AI Assistant, Dashboards, Contacts, Segments, Email campaigns, SMS campaigns (active), Automations, Bookings, Opportunities subject: one SMS campaign's recipients as rows, each with its consent, delivery, reply and the record the reply landed on content: SMS-2026-0114 Autumn opening, showroom · segment "Bought since 1 Oct 2025, SMS opted in, BE and FR" · 318 recipients · sent 22 Sep 10:00 · columns Contact, Company, Consent, Delivery, Reply, Landed on; rows Léa Dumont, Atelier Nord, Opted in 12 Mar, Delivered 10:00:08, "Coming with a colleague", Walkthrough 26 Sep 14:00 · reception, Maison Berger, Opted in 3 Feb, Delivered 10:00:09, STOP, contact opted out · reception, Delaunay Group, Opted in, Failed (number invalid), none · reception, Studio Ferrand, Opted in, Delivered 10:00:11, no reply · footer: 321 in the segment · Not sent, no consent 3 · Delivered 309 of 318 · Replies 41 · Bookings from the link 23 · STOP 2 neighbour: screen-events-table · same live table with roll-ups over one set of records; recipients instead of services, and a record link in the last column tags: modules=sms-marketing · categories=marketing · capabilities=compliance,integrations · industries= · sections=full-screen,swipe · reusable=yes
Open asset editor

© 2026 Enobase, Inc. All rights reserved.

Log in
All systems normal