# SMS marketing for events: the channel that bills you for a bad list

> SMS charges at the moment you send, not the moment you store. That single difference turns an unqualified list from a slow problem into a line on an invoice.

Source: https://hiipe.io/blog/sms-marketing-for-events
Published: 2026-09-24

SMS marketing bills you at the moment you send, not at the moment you store. That
one difference decides what counts as a good list. On email, a contact you should
never have collected costs you deliverability, slowly and invisibly, over months. On
SMS it costs you a real charge, on a real invoice, the first time you press send.

**Key takeaways**

- SMS prices the mistake immediately. Email defers it and hides it.
- Consent for email is not consent for SMS. It is given per purpose, not per contact.
- For an event, SMS rewards precision and punishes reach, which is the opposite of the retail playbook.

## What SMS marketing actually charges for

Every message. Not every contact.

This inverts the model most marketers have internalised from email, where the
subscription is indexed on how many people you keep and the sending is effectively
free at the margin. We wrote about that inversion at length in [what a 10,000 contact
list really costs](/blog/what-a-10000-contact-list-really-costs).

On SMS the meter runs the other way. Holding a number costs nothing. Using it costs
something every single time, and the charge does not care whether the number is
current, whether the person remembers giving it to you, or whether they were ever
asked in the first place.

That is not a flaw in the pricing. It is the most honest feedback loop in marketing.
A list that was scraped, bought, imported from a ticketing export or inherited from a
previous promoter produces an invoice that is exactly as large as a good list, and a
response that is not. The gap between the two is visible in one campaign rather than
in a year of declining open rates.

## Why the retail playbook does not transfer

Most SMS advice on the internet is written for retail, and it is written by tools
built for retail. The assumptions underneath it are specific: a low basket, a
repeatable purchase, a customer who buys again in six weeks, and therefore a case for
contacting people often.

An event has none of those properties. The purchase is a hundred euro decision made
once, tied to a date, in a city, on an evening when the person has to be free. There
are perhaps four moments in a campaign that justify a text, and twenty that do not.

| | Retail SMS | Event SMS |
|---|---|---|
| Purchase frequency | Every few weeks | Once per edition |
| Ticket value | Low, repeatable | High, single decision |
| Sending cadence | Weekly or more | Four to six moments per campaign |
| What drives response | Discount and urgency | Timing, city and whether they came last time |
| Cost of over-sending | Unsubscribes | Unsubscribes, plus the cost of every message |

Applying a retail cadence to an event list does two kinds of damage at once. It burns
the permission, which is the expensive part, and it bills you for the privilege,
which is the visible part.

## The consent you have is not the consent you need

This is the part that catches operators out, and it is a legal point rather than a
best practice.

Consent under European law is given for a defined purpose. The GDPR sets out the
[conditions for valid consent](https://gdpr-info.eu/art-7-gdpr/), including that it
be specific and demonstrable, and the ePrivacy Directive adds the rule that governs
marketing messages directly: unsolicited electronic communications to individuals
[require prior consent](https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32002L0058).
The United Kingdom applies the same logic through PECR, and the regulator's
[direct marketing guidance](https://ico.org.uk/for-organisations/direct-marketing-and-privacy-and-electronic-communications/)
is explicit that the permission has to cover what you actually intend to do.

Read that against how phone numbers usually arrive. A ticketing checkout collects a
mobile number because it needs to send an order confirmation. That is a contractual
necessity, not a marketing permission. The number is in your export. The right to
text it is not.

So the file that looks like a forty thousand contact SMS list is frequently a forty
thousand contact liability, and the way you discover which one it is, on SMS, is by
paying to send to it.

There is a cheaper way to find out, which is to audit the file before it becomes
a campaign rather than after. That is what an import should actually do: resolve
every domain rather than trust its spelling, set aside the masked relay
addresses that will never belong to anyone reachable, merge the duplicates,
reject the disposable domains, and above all treat consent as a gate rather than
a column, so an explicit refusal is never carried across. It should also be
legible: nothing removed in silence, every decision written down, the whole
changelog handed back to the person who owns the list. An import that quietly
drops rows to look good is the same failure as a send that quietly bills for
them.

That audit runs on every list before it enters HIIPE, and it is deliberately a
separate step from sending. The point is simple: the first campaign on an
inherited list should not be the thing that tells you what the list was.

## The number you can see and cannot use

There is a second version of the same problem, and it is structural.

Ticketing platforms and social networks sit between an operator and their audience by
design. Sometimes they will send on your behalf. They will not usually hand over the
number with a consent trail attached, because the consent was given to them.

You cannot send an SMS through someone else's permission. Email can be laundered
through an intermediary's sending domain and it mostly works. A text message cannot:
there is a number, it belongs to a subscriber, and either you hold a record of that
subscriber agreeing to hear from you or you do not. This is why SMS is the channel
that reveals, faster than any other, who actually owns an audience. The long version
of that argument is in [the receipt is the part nobody
owns](/blog/first-party-fan-data-and-the-receipt).

## Where SMS is actually a mainstream channel

Demand for SMS marketing is not evenly distributed, and an operator running the same
campaign in five countries should not expect the same channel mix in each.

|  | searches/month |
|---|---|
| France | 590 |
| United Kingdom | 480 |
| Brazil | 320 |
| Italy | 210 |
| Spain | 170 |

France is the outlier, and it shows up in the adjacent terms too: the query for an
SMS campaign draws a thousand searches a month there on its own. If you promote in
Paris and in Madrid, SMS is a first-choice channel in one of those cities and a
second-choice one in the other, and the budget should say so.

The same caution applies to the tooling. Almost every SMS platform on the
market was designed and priced for enterprise retail, and a tool built for that
buyer will push you toward volume, because volume is what its own economics
reward. An event does not need volume. It needs four messages that land on the
right two thousand people.

## What a good event SMS list looks like

Three properties, and none of them is size.

**It was asked for by channel.** The moment of capture recorded a separate permission
for text messages, with a timestamp and a source, not a single tick box covering
every future use.

**It is recent.** A number collected at a show two years ago is a number that has
changed hands, changed operator, or changed owner. Recency matters more on SMS than
anywhere else because you pay for the guess.

**It is segmented before it is sent to.** Proximity to the venue, attendance at the
previous edition, and whether the person already holds a ticket are the three cuts
that turn a broadcast into something worth its unit cost.

A list with those three properties will be smaller than the export. It will also be
the only version of the list that makes economic sense to text.

## What comes after SMS is not email

RCS is the carrier-level successor to SMS, and it is worth understanding before you
build a channel strategy around the older format. It carries images, buttons and
delivery receipts, it renders inside the same native inbox, and it is being rolled
out by handset makers and operators rather than by an app anyone has to install.

The important part for an operator is that RCS inherits the economics and the
permission model of SMS rather than those of email. It is billed per message. It
reaches a phone number. It needs the same channel-level consent, obtained the same
way. Anyone who builds a clean, per-channel, timestamped SMS list today is building
the asset that RCS will run on tomorrow, and anyone who imports a ticketing export
and hopes is building neither.

That is why we treat email, SMS, RCS and social DMs as one permission problem with
four delivery surfaces, rather than four products. The consent record is the thing
that has to be right. The transport is a detail that changes every few years.

## How this shapes the way we built it

HIIPE meters sending, not storage. Contacts are unlimited on every plan including the
free one, email sends are included on the paid plans, and SMS is billed at
professional rates on top, with RCS and social DMs in beta on the same basis. The
[plans](/pricing) are on one page.

The part that matters more than the price is where the permission comes from. Capture
happens on surfaces you own, the channel consent is recorded at the moment it is
given, and the export carries that trail with it. That is what makes a phone number
an asset rather than a row in a file, and it is the same argument as the rest of the
[product](/features): the list is only yours if the proof travels with it.

**Read next** : [Email marketing cost: what a 10,000 contact list really bills you](/blog/what-a-10000-contact-list-really-costs) · [What a fan CRM is, and what it is not](/blog/what-is-a-fan-crm)
## Citable facts

- Consent to receive email is not consent to receive SMS. Under the EU ePrivacy Directive, unsolicited electronic marketing to individuals requires prior consent, and that consent is given for a defined purpose rather than for a contact record.
  Source: Directive 2002/58/EC, Article 13, and GDPR Article 7 on conditions for consent
- SMS is billed per message sent rather than per contact stored, so the cost of an unqualified list appears at the first send instead of degrading deliverability over months.
  Source: Standard SMS carrier billing model, verified against public operator pricing, September 2026

## FAQ

### Is an email opt-in enough to send someone an SMS?
No. Consent is given for a purpose and a channel, not for a contact record. Someone who ticked a box to receive your newsletter has not agreed to receive a text, and a ticketing export that carries a phone number rarely carries a separate permission to use it.

### How many SMS should an event actually send?
Far fewer than a retailer. The retail playbook assumes weekly contact against a low basket. An event has a handful of decisive moments: announcement, presale opening, last release, and the day itself. Four well-timed messages to a qualified segment beat twenty to everyone.

### Is SMS more expensive than email?
Per message, yes, by a wide margin. Per result, it depends entirely on the quality of the list, because SMS charges you the same amount for a number that converts and a number that should never have been in the file.

### What happens to my SMS list if I change platform?
That depends on whether you can export the numbers with their consent trail. A phone number without a record of when, where and for what the person agreed is not a list you can legally send to, whatever the file says.