Author: Steve Purvey

  • RCS vs SMS vs WhatsApp: which should your business use?

    SMS, RCS and WhatsApp all put a message on your customer’s phone, but they reach different people, show different things and cost different amounts. This guide compares them side by side and shows which to use for common jobs, and when to use more than one.

    In short: SMS reaches every mobile phone, with or without data, so it’s the safe choice for critical alerts and passcodes. RCS turns a text into a branded, verified, interactive message in the same inbox, with SMS as a fallback. WhatsApp is best for conversations with customers who use it and have opted in. Most organisations get the best results by combining them.

    At a glance

    SMSRCSWhatsApp
    Where it arrivesThe phone’s messaging appThe phone’s messaging appThe WhatsApp app
    Who can receive itEvery mobile phoneAndroid phones and iPhones on iOS 18 or later, where the network supports RCSPeople who use WhatsApp and have opted in to your messages
    Needs mobile data or wi-fiNoYesYes
    Sender shownA sender name (up to 11 characters) or a phone numberYour verified brand name, logo and colourYour verified business profile
    ContentPlain textText, images, video, rich cards, carousels and buttonsText, images, documents, video, audio and buttons
    Message length160 characters per part; longer messages are joinedUp to 3,072 characters of textUp to 4,096 characters of text
    Starting a conversationAny time (with consent for marketing)Any time (with consent for marketing)Approved templates only, unless the customer messaged you in the last 24 hours
    ReceiptsDeliveredDelivered and readDelivered and read
    If it can’t be delivered–Fall back to SMS or a web versionFall back to SMS or another channel
    Best forUniversal alerts, passcodes, critical messagesBranded, interactive journeys in the native inboxConversations and customer service with opted-in customers

    SMS: reaches everyone

    SMS works on every mobile phone in the country, old or new, and doesn’t need mobile data, wi-fi or an app. Messages arrive in seconds, and almost all are read. That makes SMS the dependable choice when a message simply has to get through: passcodes, outage and emergency alerts, delivery and appointment reminders.

    • Strengths: universal reach, no app or data needed, fast, simple, and supported by every business system.
    • Limits: plain text only, 160 characters per message part, and a sender that can be imitated by scammers. In the UK, the SMS SenderID Protection Registry helps stop criminals using registered brand names.
    • Cost: charged per message part, typically a few pence in the UK. Long messages and emoji use more parts, so it pays to understand SMS character limits.

    RCS: SMS, upgraded

    RCS (Rich Communication Services) Business Messaging arrives in the same messaging app as SMS, but the sender is a verified brand with your name, logo and colours. Messages can include images and video, rich cards with buttons, swipeable carousels, and suggested replies such as “Confirm” or “Reschedule” that customers tap instead of typing.

    • Strengths: a trusted, branded sender that is hard to imitate; rich, interactive content in the inbox customers already use; and read receipts, so you know a message was seen, not just delivered.
    • Limits: the phone, the network and a data connection all need to support it. Android phones support RCS through Google Messages, and Apple added it to iPhone with iOS 18.
    • Fallback: anyone who can’t receive RCS gets an SMS instead, or an SMS with a link that shows the same rich message as a branded web page, so nobody misses out.
    • Cost: charged per message, with plain-text RCS usually close to the price of an SMS and rich messages costing more. Fallback messages are charged as SMS.

    Read more about RCS Business Messaging with everymessage.

    WhatsApp: built for conversation

    WhatsApp Business messages arrive in the WhatsApp app, from your verified business profile. They support text, images, documents, voice notes and buttons, and they suit two-way conversations: customer service, bookings and support.

    • Strengths: very widely used in the UK and worldwide, great for back-and-forth conversations, and inexpensive for reminders, passcodes and replies to customers who message you first.
    • Limits: customers must use WhatsApp and opt in to messages from you. To start a conversation you must use a template approved by WhatsApp, and free-form messages are only allowed for 24 hours after the customer’s last message.
    • Privacy: Meta runs the platform and handles message content, so avoid sending medical or financial details by WhatsApp.
    • Cost: Meta’s fee per message, which depends on the message category, plus our usage fee. See WhatsApp message types and pricing explained.

    Which channel for which job?

    JobBest choiceWhy
    One-time passcodesSMS, or WhatsApp with SMS fallbackSMS reaches every phone instantly. WhatsApp authentication messages can cost less for customers who use it.
    Appointment remindersRCS with SMS fallbackBranded reminder with “Confirm” and “Reschedule” buttons, while SMS covers everyone else.
    Delivery updatesRCS or WhatsApp, with SMS fallbackImages, tracking buttons and maps make updates clearer.
    Marketing campaignsRCS with fallback, or SMSCarousels and images from a verified brand stand out; SMS is simple and reaches everyone. WhatsApp marketing costs more and needs opt-in.
    Customer serviceWhatsApp, or RCSCustomers can start a chat from your website, an email or an SMS link, and replies in the 24-hour window cost little.
    Emergency and outage alertsSMSWorks without data or an app, on every phone, even when networks are busy.
    Sensitive informationSMS or RCS with a secure linkSend a notification and link to a secure portal rather than the details themselves.

    Using them together

    You don’t have to choose one channel. The most effective set-ups use each where it’s strongest:

    1. RCS first, SMS fallback. Send a branded, interactive message; anyone who can’t receive RCS automatically gets an SMS or a web version, so you reach everyone.
    2. WhatsApp where customers prefer it. Use WhatsApp for customers who have opted in, and for conversations they start.
    3. SMS for the critical path. Keep SMS for passcodes and urgent alerts, where reaching every phone matters more than looks.
    4. Journeys across channels. With Workflow, follow an unread message with a reminder on another channel, or an email, or a call.

    everymessage runs SMS, RCS, WhatsApp and email from one platform, one inbox and one API, with delivery reporting for every channel.

    Frequently asked questions

    What is the difference between RCS and SMS?

    SMS is plain text from a number or sender name and works on every mobile phone. RCS arrives in the same messaging app but comes from a verified brand with your logo, and can include images, rich cards, carousels and buttons. It needs a phone and network that support RCS and a data connection; when it can’t be delivered, an SMS can be sent instead.

    Is RCS available on iPhone?

    Yes. Apple added RCS to iPhone with iOS 18, and Android phones support it through Google Messages, where the mobile network supports it. Phones that can’t receive RCS can get an SMS or a web version instead.

    Is WhatsApp cheaper than SMS for businesses?

    For utility and authentication messages, such as reminders and passcodes, usually yes in the UK. Marketing messages on WhatsApp cost more, and every recipient must have WhatsApp and have opted in to hear from you.

    Which channel is best for one-time passcodes?

    SMS reaches every phone without needing data or an app, so it remains the safest default. WhatsApp authentication messages can cost less for customers who use WhatsApp, with SMS as the fallback.

    Can I use more than one channel?

    Yes. With everymessage you can send by RCS with automatic SMS fallback, use WhatsApp for customers who have opted in, and run all three from one platform, inbox and API.

    Not sure which channel to use?

    Tell us what you need to send and to whom, and we’ll recommend the right mix.

  • Transactional email templates: best practices for design and delivery

    Order confirmations, receipts, password resets and appointment reminders are the emails customers actually wait for. This guide covers how to design transactional email templates that look right in every inbox, reach the inbox in the first place, and meet UK requirements.

    In short: keep transactional emails single-purpose, single-column and around 600 pixels wide; put the key fact and one clear action at the top; make them readable with images off and in dark mode; authenticate your domain with SPF, DKIM and DMARC; include your company details; and keep marketing out of them.

    What makes an email transactional

    A transactional email is sent because of something the recipient did, or something that affects their account: a purchase, a booking, a password reset, a change of address, a delivery update, an invoice or a security alert. People expect it, often within seconds, and they act on it.

    That changes the design brief. A marketing email competes for attention; a transactional email has the attention already and must not waste it. Success means the customer finds the information quickly, trusts that the email is genuine, and can do the one thing it asks.

    Anatomy of a good transactional template

    1. A recognisable sender. Your brand as the sender name (for example “Example Ltd” or “Example Ltd Orders”), from an address on your own domain.
    2. A specific subject line. Say what happened and include the reference: “Your order A1042 is confirmed”, not “Thank you!”.
    3. Preheader text. The preview line after the subject. Use it for the next most useful fact, such as the delivery date.
    4. A headline that states the purpose. The reader should know why the email arrived within a second.
    5. The key details. Order number, amount, date and time, address: laid out so they can be scanned, not buried in paragraphs.
    6. One primary action. Track the order, reset the password, confirm the appointment. One button, clearly labelled.
    7. Help and contact. How to get support, in the email itself.
    8. A footer with your business details. UK companies must show their registered name, company number, place of registration and registered office address in business emails.

    Design and layout

    Build to a standard width

    Design at 600 to 640 pixels wide. That fits the reading pane in desktop clients, and a single media query lets the layout fill the screen on a phone. A wider template is either shrunk or scrolled sideways, and both make it harder to read.

    Use one column

    Single-column layouts read naturally on phones, where most transactional email is opened, and avoid the column-collapsing problems that multi-column designs bring. Give elements generous spacing so buttons and links are easy to tap.

    Lead with the key information

    Put what the customer needs first: the order is confirmed, the code is 482913, the appointment is on Tuesday at 10:30. Everything else is secondary.

    Have one clear call to action

    Make the main action a proper button, at least 44 pixels tall, with a label that says what happens (“Reset your password”, “Track your order”). Secondary links can be plain text.

    Stay on brand, but keep it simple

    Use the same logo, colours and tone across every template, so customers recognise genuine emails from you, which also helps them spot phishing. Resist heavy imagery: a transactional email should still make sense with every image blocked.

    Write plainly

    Short sentences, everyday words, no internal jargon or system codes. If something needs action, say exactly what and by when.

    Built to render everywhere

    Email clients don’t render HTML like browsers. Desktop Outlook on Windows uses a word-processor engine, Gmail removes some styles, and every phone app behaves slightly differently. Build defensively:

    • Use tables for layout and inline CSS for styling. Keep a small <style> block only for media queries and dark-mode tweaks.
    • Use web-safe font fallbacks. A custom web font is fine where it’s supported, but always list Arial, Helvetica or similar after it.
    • Make buttons from padded table cells with a link inside, not images, so they display even with images off.
    • Give every image alt text and fixed dimensions, and host images on HTTPS. Many inboxes block images until the reader allows them.
    • Keep images light. Compress them, use PNG for logos and JPEG for photos, and supply them at twice the display size for sharp screens.
    • Add a static fallback for animated GIFs. Some versions of Outlook show only the first frame.
    • Keep the HTML under about 100 KB. Gmail clips larger messages and hides the rest behind a “View entire message” link, which can hide your footer.
    • Send a plain-text version too. A multipart email with a plain-text part is more accessible and looks less like spam.

    Dark mode

    Many people read email in dark mode, and clients handle it differently: some leave your colours alone, some invert them fully, and some only partly. To stay readable:

    • Use logos with a transparent background and a light outline or padding, so they don’t vanish on a dark background.
    • Avoid text that is part of an image; it can’t adapt.
    • Declare color-scheme support and add prefers-color-scheme styles where they’re supported.
    • Check contrast in both modes, not just light.

    Accessibility

    • Set the language (<html lang="en">) and use real headings and paragraphs, so screen readers can navigate.
    • Mark layout tables with role="presentation", so they aren’t read out as data tables.
    • Keep text contrast at 4.5:1 or more, and body text at 14 to 16 pixels.
    • Write link text that makes sense on its own, such as “View your invoice”, rather than “Click here”.
    • Don’t rely on colour alone to show status: write “Payment failed”, don’t just show red.

    Personalisation

    Templates should be built around fields that are filled in for each message: name, reference, amounts, dates, addresses, links. Plan for missing data: a greeting should still read well if the first name is blank (“Hello” rather than “Hi ,”), and long values such as addresses shouldn’t break the layout.

    Never put passwords in an email. Make links that act on an account, such as password resets, single-use and short-lived, and show only partial details for sensitive information: the last four digits of a card, not the full number.

    Keep marketing out

    It’s tempting to add offers to emails with high open rates. In the UK, a genuine service message doesn’t need marketing consent under PECR, but once you add promotional content the ICO may treat the whole email as direct marketing. That means it needs consent or a valid soft opt-in, and an unsubscribe link, and it can’t be sent to people who have opted out. It also distracts from the purpose of the email and can make it look less trustworthy.

    If you do include anything beyond the transaction, keep it small, relevant to what the customer just did, and below the main content.

    Getting delivered

    A perfect template is no use in a spam folder. Gmail and Yahoo (since 2024) and Microsoft’s consumer mail (since 2025) all set firm requirements for anyone sending in volume, and authenticated mail does better at every provider.

    • SPF lists the servers allowed to send for your domain.
    • DKIM signs each message so it can’t be altered on the way.
    • DMARC tells inboxes what to do with mail that fails those checks, and sends you reports. Start with a monitoring policy and move to quarantine or reject once you’re confident.
    • Use a sending subdomain for system email, for example mail.example.com, so its reputation is separate from your staff mailboxes and marketing.
    • Use a monitored reply-to address. Customers reply to order and booking emails; a “no-reply” address frustrates them and gets ignored.
    • Keep complaints low. Google asks bulk senders to stay under a 0.3% spam rate. Clean, expected transactional mail helps your whole domain.

    Test before you send

    • Preview in the clients your customers use: Outlook on Windows, Gmail on web and phone, Apple Mail and Outlook on iPhone.
    • Check with images turned off, in dark mode, and at phone width.
    • Click every link, and check that personalised fields fill correctly, including when data is missing.
    • Send test messages to real inboxes at the major providers, and check they arrive in the inbox rather than spam.

    Measure what matters

    Open rates are no longer reliable: Apple’s Mail Privacy Protection loads images automatically, so many emails show as opened when they weren’t. For transactional email, track:

    • Delivery and bounce rates, split into hard bounces (bad addresses to clean up) and soft bounces (temporary problems).
    • Time to inbox, especially for passcodes and password resets, which are useless if they arrive late.
    • Spam complaints.
    • Clicks on the main action, and the outcome you care about, such as appointments confirmed or fewer calls to your contact centre.

    Test one change at a time, such as the subject line or the button wording, and compare the results.

    A starter template

    A minimal responsive transactional template with a preheader, a single-column card, a button that works in Outlook, dark-mode support and a UK company footer. Replace the example details with your own.

    <!DOCTYPE html>
    <html lang="en">
    <head>
    <meta charset="utf-8">
    <meta name="viewport" content="width=device-width, initial-scale=1">
    <meta name="color-scheme" content="light dark">
    <meta name="supported-color-schemes" content="light dark">
    <title>Your order A1042 is confirmed</title>
    <style>
      @media (max-width: 620px) { .container { width: 100% !important; } .pad { padding: 24px 20px !important; } }
      @media (prefers-color-scheme: dark) {
        .bg { background: #111318 !important; } .card { background: #1f2430 !important; }
        .text { color: #e6e9ef !important; } .muted { color: #9aa3b2 !important; }
      }
    </style>
    </head>
    <body class="bg" style="margin:0; padding:0; background:#f2f4f7;">
    <!-- Preheader: the preview line shown after the subject in most inboxes -->
    <div style="display:none; max-height:0; overflow:hidden;">Arriving Thursday 13 November. Track your parcel any time.</div>
    <table role="presentation" class="bg" width="100%" cellpadding="0" cellspacing="0" style="background:#f2f4f7;">
      <tr><td align="center" style="padding:24px 12px;">
        <table role="presentation" class="container" width="600" cellpadding="0" cellspacing="0" style="width:600px; max-width:600px;">
          <tr><td style="padding:0 0 16px;">
            <img src="https://example.com/logo.png" width="140" height="36" alt="Example Ltd" style="display:block; border:0;">
          </td></tr>
          <tr><td class="card pad" style="background:#ffffff; border-radius:8px; padding:32px 40px;">
            <h1 class="text" style="margin:0 0 12px; font:bold 24px/1.3 Arial, Helvetica, sans-serif; color:#111827;">Your order is confirmed</h1>
            <p class="text" style="margin:0 0 20px; font:16px/1.6 Arial, Helvetica, sans-serif; color:#374151;">Hi Sam, thanks for your order A1042. It will arrive on Thursday 13 November.</p>
            <!-- Button: a padded table cell, so it works in every client including Outlook -->
            <table role="presentation" cellpadding="0" cellspacing="0"><tr>
              <td style="border-radius:6px; background:#0b5cad;">
                <a href="https://example.com/orders/A1042" style="display:inline-block; padding:14px 28px; font:bold 16px Arial, Helvetica, sans-serif; color:#ffffff; text-decoration:none;">Track your order</a>
              </td>
            </tr></table>
            <p class="text" style="margin:24px 0 0; font:14px/1.6 Arial, Helvetica, sans-serif; color:#374151;">Questions? Reply to this email or call 0344 000 0000.</p>
          </td></tr>
          <tr><td class="muted" style="padding:20px 8px; font:12px/1.6 Arial, Helvetica, sans-serif; color:#6b7280;">
            Example Ltd, registered in England and Wales, company number 01234567.<br>
            Registered office: 1 High Street, Anytown, AB1 2CD.<br>
            You're receiving this because you placed an order with us.
          </td></tr>
        </table>
      </td></tr>
    </table>
    </body>
    </html>

    How everymessage helps

    • Delivery you can see. Detailed reporting on every email: submitted, delivered and bounced.
    • Set up properly from the start. We help you put SPF, DKIM and DMARC in place for your sending domain.
    • Templates with personalisation, filled from your data for each customer, in single sends or bulk runs of millions.
    • Journeys across channels. With Workflow, send an email and follow up by SMS or a call if there’s no response, or if the email bounces.
    • Branded landing pages. Our AI branding tool turns any web form or PDF into a page in your own brand, so the link in your email lands somewhere that looks like you.

    Find out more about business email with everymessage.

    Frequently asked questions

    What is a transactional email?

    An automated email sent because of something a person did or something that affects their account: an order confirmation, receipt, password reset, appointment reminder, delivery update or security alert. It gives information they need rather than promoting anything.

    Do transactional emails need consent under UK law?

    Genuine service messages don’t need marketing consent under PECR. But if you add promotional content, the ICO can treat the email as direct marketing, which does need consent or a valid soft opt-in, plus an unsubscribe option.

    What width should an email template be?

    600 to 640 pixels is the safe standard. It fits desktop reading panes, and with a simple media query the layout scales down to full width on phones.

    Do I need SPF, DKIM and DMARC for transactional email?

    Yes. Gmail, Yahoo and Microsoft expect authenticated mail, and without SPF and DKIM aligned to a DMARC policy, important emails such as password resets are much more likely to be filtered or rejected.

    Should transactional emails use a no-reply address?

    It’s better not to. Customers reply to order and booking emails with questions. Use an address that someone reads, or at least tell people clearly how to get help.

    Talk to us about transactional email

    We’ll help you design, authenticate and send emails your customers can rely on.

  • SMS character limits explained: GSM-7, Unicode and long messages

    Why does one text cost one SMS and a slightly longer one cost two? And why can a single emoji double the price? This guide explains SMS character sets, long messages and how to keep every message to as few parts as possible.

    In short: one SMS holds 160 characters from the standard GSM alphabet, or 70 if any character needs Unicode. Longer messages are split into parts of 153 (GSM) or 67 (Unicode) characters, joined back together on the phone, and each part is charged as one SMS.

    Try it: count your message

    Paste or type a message to see which character set it needs and how many parts it will use.

    Two character sets

    GSM-7

    The standard SMS alphabet: A–Z, a–z, 0–9, common punctuation, the £, $ and @ signs, a few accented letters and some Greek capitals. Each character takes 7 bits, so 160 fit in one SMS.

    Unicode (UCS-2)

    Used when a message contains anything outside GSM-7: emoji, Chinese, Arabic, Cyrillic or Polish letters, and many accented characters. Each character takes 16 bits, so only 70 fit in one SMS.

    The whole message uses one character set. A single Unicode character anywhere in it switches every character to Unicode.

    How long messages are split

    An SMS carries 140 bytes. A longer message is sent as several SMS, each with a small header (the user data header) telling the phone how to rejoin them in order. The header takes 6 bytes, leaving less room for text in each part:

    Character setSingle SMSEach part of a long message2 parts3 parts4 parts6 parts
    GSM-7160153up to 306up to 459up to 612up to 918
    Unicode7067up to 134up to 201up to 268up to 402

    The parts may arrive at slightly different times, but the phone waits for all of them and shows one message. You are charged for every part.

    Characters that catch people out

    In GSM, but count as two

    These come from the GSM extension table and need an escape character, so each one counts as two:

    € [ ] { } \ ^ ~ |

    Not in GSM: switch the message to Unicode

    CharacterOften comes fromGSM alternative
    ’ ‘ “ ”Word, Outlook and phone keyboards (curly quotes)‘ and “
    – —Word and web pages (en and em dashes)–
    …Autocorrect (ellipsis)…
    Emoji 😀 👍 🎉Phones and marketing copyRemove, or use words
    ê, á, ç, í, ó, ú, ł, őNames and non-English wordse, a, c… (é, è, à, ù and Ç are in GSM)
    Non-breaking spaces, tabsText copied from websites and spreadsheetsOrdinary space

    An emoji also counts as two Unicode characters, so one emoji uses 2 of the 70.

    Good news for UK senders

    The £ sign, $, @, é and è are all standard GSM characters and count as one.

    Worked examples

    MessageCharacter setParts
    160 plain charactersGSM-71
    161 plain charactersGSM-72 (153 + 8)
    159 characters plus a € signGSM-7 (€ counts as 2)2
    150 characters with one curly apostropheUnicode3 (instead of 1)
    120 characters plus one emojiUnicode (emoji counts as 2)2 (instead of 1)
    400 plain charactersGSM-73

    On a large send, a single pasted apostrophe can triple the bill. That’s why the default matters.

    How everymessage handles it

    • Standard text by default. Through our REST API, messages are converted to the GSM alphabet unless you ask for Unicode. Curly quotes and dashes become plain ones, accented letters become their plain letter where GSM doesn’t have them, and emoji are removed. Your message always goes at 160 characters per SMS.
    • Unicode when you want it. Set "unicode": true to keep emoji and non-Latin text. If a message turns out to be plain GSM text after all, we still send it as GSM, so you don’t pay for Unicode you didn’t need.
    • Accurate part counts and prices. Every message is counted and priced by its real number of parts before it is sent.
    • A limit on message length. Each user account can be limited to between 1 and 6 parts per message: from 160 up to 918 standard characters (70 to 402 in Unicode). It stops one long message using up your credit, for example when someone forwards a whole email thread to email-to-SMS.

    See the Send SMS API reference for the unicode option, or business SMS for everything else we offer.

    Tips for writing SMS

    • Write or paste your message into a plain text editor first, or check it with the counter above.
    • Aim for 160 characters. If you need more, use the space up to the next part boundary (306, 459) rather than going just over it.
    • Use Unicode only when it adds something, such as a customer’s name in their own alphabet or a message in another language.
    • Put a link to a web page in the message for long or detailed information, instead of sending many parts.
    • If you send rich content often, consider RCS or WhatsApp, which have far higher limits and support images and buttons.

    Frequently asked questions

    How many characters can one SMS hold?

    160 characters using the standard GSM alphabet, or 70 characters if the message needs Unicode, for example because it contains an emoji or non-Latin text.

    Why is a long SMS split into 153-character parts?

    Each part of a long message carries a small header so the phone can put the parts back together in the right order. The header uses 7 characters of space, leaving 153 for your text (67 with Unicode).

    Does the pound sign £ need Unicode?

    No. The £ sign is part of the standard GSM alphabet and counts as one character. The euro sign € is in GSM too, but counts as two.

    Why did my message cost three times as much as expected?

    Usually one character outside the GSM alphabet, such as a curly quote pasted from a document or an emoji, switched the whole message to Unicode, which fits less than half as much text per part.

    What is the longest SMS I can send?

    On everymessage, each user account can be set to allow between 1 and 6 parts per message, which is up to 918 standard characters or 402 in Unicode. The limit protects your credit if a long email is sent to email-to-SMS by mistake.

    Are long messages delivered as one message?

    Yes. The parts travel separately but the phone joins them and shows one message. Each part is charged as one SMS.

    Send SMS with everymessage

    UK business SMS with accurate part counts, character set conversion and a full API.