How does the reply land on the appointment or the order?

The message is sent from the record, so the reply is matched to the message that asked and lands under it. A keyword you define (YES, OK) can move the record's status; any other text is a message on the record for the person who owns it. Replies need a two-way number rather than a sender name; which numbers and sender names are available per country ⟨to confirm⟩.

How is consent handled?

Opt-in, its date and its source, opt-out and the STOP a contact texted are fields on the contact, with their history. Every send reads them first. A STOP received by reply sets the field the moment it arrives, and no rule or segment overrides it. What your opt-in must say is decided with your adviser; the default wording ⟨to confirm⟩.

Which provider sends the messages, and where?

The messages leave through an SMS provider connected to your workspace, and the delivery receipt for each message is written on the contact. The provider, the sender-name rules per country and the countries delivered ⟨to confirm⟩.

Can a message go out by a rule, without a campaign?

Yes. A reminder the day before an appointment, a notice when an order is marked loaded, a nudge when an invoice is thirty days open: the trigger is a change on the record, the consent check runs the same way, and Marketing Automation chains it with an email or a task.

Who can send a campaign?

Whoever you decide. A campaign to a segment can be held for approval by a named person; a single message from a record is sent by the person on the record. Both are rules you can read.

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.

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.

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 need	A spreadsheet	An SMS tool	A suite module	Enobase
A campaign to a segment	No	Yes, to an imported list	Yes	Yes, a filter on your contacts
Consent and STOP kept per contact	A column	Yes, on their list	Yes, on their contact	Yes, on the contact, read before every send
A reminder sent from the appointment	Copied	By file or API	Sometimes	Yes, from the appointment itself
The order's fields in the text	Copied	From list columns	Partly	Yes, the record's own fields
The reply on the record it answers	No	In their inbox	In their inbox	Yes, on the appointment or the order
What it did, read from the records	No	Clicks	Partly	Yes, confirmed, rescheduled, booked
Time to live	A day	A day	Weeks	One 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.

See Enobase on your operation.

30 minutes, your real events on screen. We'll show you exactly where Enobase saves your team time, no slides.

Have a quick chat

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

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

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.