Author: Steve Purvey

  • Take card payments on any call, without the card ever touching your systems

    Every card payment taken over the phone is a risk you carry. A customer reads out 16 digits and a security code, a member of your team writes them down, and your phone system and call recordings now hold card data. That pulls people, systems and recordings into PCI DSS, the card industry’s security standard, with all the assessment, controls and audit work that follows. The alternative, “we’ll text you a link”, loses payments that should have been taken there and then.

    everymessage and Paytia fix both problems. Your customers pay by card on the call itself, inbound or outbound, with our AI voice assistant or with your team, and the card number never reaches you.

    In short: when it’s time to pay, the caller types their card details on their own phone keypad. Paytia captures and masks the keypad tones, so our AI voice assistant, your team and your call recordings only learn that digits were entered, never what they were. The payment goes through your own payment gateway, the result comes back within seconds, and the conversation carries straight on. It works in front of your phone system, behind it, or with no phone system at all.

    Every call, every setup

    Secure payments fit the way you already take calls, rather than the other way round.

    • Inbound calls. Customers ring to pay a bill, settle an arrears balance, book and pay a deposit, or renew. Our AI voice assistant answers 24 hours a day, or puts them through to your team.
    • Outbound calls. Our AI voice assistant or your team calls customers about overdue balances, renewals or unpaid bookings, and takes the payment there and then, instead of ending with “we’ll send you a link”.
    • In front of your phone system. everymessage answers first, takes payments, and passes everything else to your existing phone system as it does today.
    • Behind your phone system. Your phone system answers as normal, and sends payment calls, or a queue of them, to us.
    • Completely standalone. No phone system at all? We provide the numbers, the AI voice assistant and the payment line.

    It suits any business that takes money over the phone: collections and arrears, utilities, housing, bookings and deposits, subscriptions and renewals, and service desks.

    Customers who’d rather message than call? Secure card payments in text, WhatsApp and web chat are coming soon.

    How it works

    1. A customer calls your number. everymessage answers, either with our AI voice assistant or by putting the caller through to your team.
    2. It’s time to pay. We ask Paytia to start a secure card capture on that live call. Capture starts within a second or two of the assistant asking.
    3. The caller keys in their card details on their phone keypad. Paytia hears the tones and masks them, a technique known as DTMF masking. The assistant, your team and any recording only get confirmation that digits were entered.
    4. Paytia takes the payment through your own payment gateway, such as Stripe.
    5. The result comes straight back. Paytia sends the outcome to us by secure webhook, and the conversation picks up again: “Thanks, that’s gone through.”

    How Paytia connects

    Paytia sits in front of the call, between the caller and everymessage. When it’s time to pay, we switch on secure capture, and Paytia masks the keypad tones before the call audio reaches us. Card tones never reach the everymessage platform at all.

    How the call flows
    CallerKeys their card on the keypad
    PaytiaCaptures and masks the tones
    everymessageAI assistant or your team
    Paytia sits between the caller and everymessage, so card tones stop at Paytia.

    Fully integrated with Paytia

    everymessage is fully integrated with Paytia and ready to use.

    • Secure card capture starts within a second or two of the assistant asking for payment.
    • The outcome comes back automatically by secure webhook, including the address, postcode and security-code check results.
    • It works with our AI voice assistant and with calls routed to people, including team members on Microsoft Teams.

    Less PCI burden, more payments taken

    • Take card data out of your business. Card numbers never reach your staff, your desks, your phone system, your call recordings or our AI. With no card data in your environment, there’s far less to protect and assess: your business can become eligible for SAQ A, the shortest PCI DSS self-assessment, instead of SAQ C-VT or SAQ D.
    • Stop pausing and redacting recordings. No more “pause the recording while you read me your card”, and no card data hiding in recordings for someone to find later. Every call can be recorded in full.
    • Get paid on the call. Customers pay mid-conversation, while they’re ready to, instead of being sent a link they may never open. That matters most on collections and outbound calls.
    • Protect your team. Nobody hears or handles a card number, so nobody can mishear it, write it down or be accused of misusing it.
    • Keep your phone system. In front of it, behind it or instead of it: no rip-and-replace project.
    • Let AI take payments safely. The assistant handles the conversation and Paytia handles the card, so you can automate payment calls without the AI ever seeing card data. It pairs with AI appointment booking when you take a deposit at the time of booking.

    About Paytia

    Paytia is a PCI DSS service provider assessed to Level 1 merchant processing status. Paytia handles the capture and transmit of customer card holder and sensitive authentication data on behalf of merchants looking to remove all card data from their business, people, processes and technology.

    Find out more about Paytia’s AI payment security.

    Frequently asked questions

    Does the AI voice assistant hear the card number?

    No. The caller types their card details on their keypad, and Paytia masks the tones before they reach the assistant. The assistant only learns that digits were entered and, afterwards, whether the payment went through.

    Can we record calls where customers pay by card?

    Yes. With DTMF masking, recordings only capture masked tones, so you can record whole calls without storing card data. Without it, PCI DSS doesn’t allow card security codes to be kept in recordings, which is why many businesses pause recording while customers read out their card.

    What are the rules for taking card payments over the phone in the UK?

    Card payments taken by phone must follow PCI DSS, the card industry’s security standard. It covers anyone and anything that hears, sees, stores or passes on card data, including your staff, phone system and call recordings. Keeping card data out of all of them, as here, cuts down what you have to secure and assess.

    Can my team take payments this way too?

    Yes. A team member can start secure capture during a call, and the caller keys in their details in the same way. Your team never hears or sees the card number.

    Which payment gateways does it work with?

    Paytia takes the payment through the merchant’s own gateway. That includes gateways such as Stripe; ask us about the gateway you use.

    Do I need to change my phone system?

    No. everymessage and Paytia can sit in front of your phone system, behind it, or replace it entirely with numbers from us.

    Can we take payments on outbound calls?

    Yes. Whether our AI voice assistant or your team makes the call, the customer can pay during it in exactly the same way.

    Does this make us PCI compliant?

    It takes most of the burden away. With card data kept out of your people, systems and recordings, your business can become eligible for SAQ A, the shortest PCI DSS self-assessment, instead of SAQ C-VT or SAQ D. You still complete your own self-assessment, and your assessor confirms what remains in scope.

    See a secure payment on a live call

    Book a call and we’ll show you a card payment taken during a live call, by our AI voice assistant and by a team member, with the card number masked throughout. Then we’ll map out how it fits your calls, inbound or outbound, with or without your current phone system.

  • Automate appointment booking with AI: voice, SMS and WhatsApp

    Most appointment admin is the same few conversations repeated all day: “Can you still make Tuesday?”, “Have you got anything sooner?”, “I need to move my appointment.” Each one takes a member of staff a few minutes, often across several calls. Automating them frees your team for the conversations that need a person, and lets customers sort things out at any time of day.

    In short: an AI voice assistant or chatbot connected to your live calendar can book, confirm, reschedule and cancel appointments by phone call, SMS, WhatsApp and secure web chat, both when it contacts customers and when customers contact you. It only offers slots that are really free under your own booking rules, updates your diary the moment something changes, sends a confirmation straight away, and hands over to a person whenever the customer asks. It can even take a card payment, such as a deposit or booking fee, during the call, without anyone hearing the card details.

    Two directions: reminders out, bookings in

    Outbound: reminders that customers can answer

    Before each appointment, the customer gets a reminder on the channel that suits them:

    • An AI voice call that says who is calling, confirms the appointment and asks if it still suits. The customer can confirm, cancel or ask for another time in their own words, and the assistant replies in a natural voice, with a choice of UK accents and dialects.
    • An SMS they can reply to: YES to confirm or NO to cancel, with a link to a secure chat window if they’d like a different time.
    • A WhatsApp message using an approved utility template, with buttons to confirm or change. In the UK, Meta charges £0.0159 for a utility message, plus our usage fee.
    • An RCS message with your logo and tap-to-reply buttons, which falls back to a web page or SMS on phones that can’t show RCS.

    When a customer cancels or moves, the slot is freed in your calendar straight away, and can be offered to someone else on a waiting list.

    Inbound: customers book whenever suits them

    • They call your number and an AI voice assistant answers. It uses natural language recognition to understand what they say, in their own words and with a wide range of UK accents, then checks real availability, offers a couple of times and books the one they choose. If you take deposits, the caller can pay by card before they hang up.
    • They text or message you on WhatsApp, and get a link to a secure chat window, where the assistant checks availability, books the slot they choose and sends a confirmation.
    • They reply to an earlier message, for example “can I make it later?”, and get a link to the secure chat window to pick a new time.

    Whatever the channel, the booking lands in the same calendar, and the customer gets a written confirmation by SMS, WhatsApp or email.

    Why the live calendar matters

    The difference between a reminder service and a booking assistant is the connection to your calendar or booking system:

    • Only real slots are offered, so there’s no double booking and no “we’ll call you back to confirm”.
    • Changes happen immediately: a cancellation frees the slot the moment the customer says so.
    • Your rules are followed: you set how bookings and changes work, such as appointment lengths, buffers, opening hours, which staff do which job, how close to the appointment it can be moved and how many times. The same rules apply by phone, text, WhatsApp and chat.
    • Your team sees everything in the calendar they already use, with the conversation recorded against the booking.

    everymessage connects to Outlook and Google calendars, or to any CRM or booking system with API access, so the assistant books into the same place your team already works.

    Which channel for which customer?

    ChannelBest forGood to know
    AI voice callPeople who prefer to talk, older customers, last-minute changesNatural speech recognition and playback, with many UK dialects. Every call is transcribed and its outcome recorded. Customers can ask for a person at any point
    SMSEveryone with a mobileSend from a mobile number so customers can reply
    WhatsAppCustomers who have opted in to WhatsAppReminders use approved utility templates. Replies within 24 hours are free-form conversation
    RCSAndroid users, with a fallback for everyone elseBranded messages with tap-to-reply buttons

    Many organisations combine them: a WhatsApp or SMS reminder first, then an AI voice call to anyone who hasn’t replied.

    A worked example: a service engineer visit

    1. Two days before, the customer gets an SMS: “Your engineer visit is booked for Thu 16 Jan, 8am to 12pm. Reply YES to confirm or ask for another time.”
    2. The customer replies “can it be Friday instead?” and gets a link to a secure chat window.
    3. The assistant checks the calendar and offers the Friday slots your rules allow. The customer picks the afternoon.
    4. The calendar is updated straight away, Thursday’s slot is freed, and a confirmation is sent.
    5. On the morning of the visit, the customer gets a reminder with the engineer’s arrival window.

    Nobody in the office had to pick up the phone.

    Taking a deposit or payment while you book

    Many bookings need money up front: a deposit, a booking fee or payment for a missed appointment. The assistant can take it in the same conversation:

    1. The booking is agreed and the assistant confirms the amount.
    2. The caller is connected to a secure payment line run by our PCI DSS compliant payment partner, without having to call another number.
    3. They key in their card details on their phone’s keypad. Nobody hears them, and they never reach your call recordings or systems.
    4. The result comes straight back, the booking is marked as paid, and a confirmation is sent by text or email.

    Keeping it safe and human

    • A person is always available. The assistant hands over to your team when the customer asks, or when a request isn’t something it should handle.
    • Keep sensitive details out of messages. A reminder doesn’t need to say why someone has an appointment.
    • Everything is recorded: every message, call transcript and outcome, so your team can see what was agreed.
    • UK hosted and ISO 27001 certified.

    For ready-to-use reminder wording, see our appointment reminder text examples.

    Frequently asked questions

    Can AI book appointments over the phone?

    Yes. An AI voice assistant connected to your calendar can answer calls, check availability, book or move an appointment and send a confirmation by text, and it can hand over to a person whenever the caller asks.

    Does the AI voice assistant understand regional accents?

    Yes. It uses natural language recognition, so callers can speak normally rather than pressing buttons or using set phrases, and it handles a wide range of UK accents. Its replies are played back in a natural voice, with many UK dialects to choose from to suit your customers.

    Can customers reschedule by text message?

    Yes. Customers reply to confirm or cancel. To choose another time, they tap a link to a secure chat window, which books the new slot in your calendar within the rules you set.

    Can WhatsApp be used for appointment reminders?

    Yes, for customers who have opted in. Reminders use Meta-approved utility templates, which cost £0.0159 each in the UK plus our usage fee, and customers can reply in the same chat.

    Which calendars does it work with?

    Outlook and Google calendars, and any CRM or booking system with API access. Talk to us about the system you use.

    Can we set our own rules for booking and rescheduling?

    Yes. You set the rules for each channel and for changes, for example how close to the appointment a booking can be moved, how many times, and which slots and staff are offered. The assistant follows them by phone, text, WhatsApp and chat.

    Can the assistant take a deposit or payment?

    Yes. During the call, the customer is connected to a secure payment line run by our PCI DSS compliant payment partner and keys in their card details on their phone’s keypad. Nobody hears the card details, they never reach your call recordings or systems, and the booking is marked as paid as soon as the payment goes through.

    What happens if the AI doesn’t understand?

    It asks again or offers to pass the customer to a member of your team, so nobody gets stuck.

    See AI booking with your own calendar

    Book a free discovery call and we’ll show you an AI assistant booking, confirming and moving appointments in your calendar, by phone, text and WhatsApp.

  • Yeastar SMS: add two-way business texting to Yeastar P-Series with everymessage

    Yeastar P-Series is a business phone and contact centre system with omnichannel messaging built in, so agents can handle SMS alongside calls, WhatsApp and live chat in the Linkus client. To send and receive texts it needs an SMS provider, and everymessage can be that provider through Yeastar’s custom SMS channel. This guide explains how it works, what you need, the exact Yeastar settings and how to test it.

    In short: in Yeastar go to Messaging > Message Channel, add an SMS channel with ITSP set to General, and enter the everymessage API key and addresses below. Copy the webhook URL Yeastar gives you and send it to us. Texts from agents go to everymessage, and customer replies come back to Yeastar by signed webhook. No code and nothing to install.

    How the integration works

    When an agent sends a text, Yeastar posts it to everymessage with your API key, and we send it to the mobile networks. When a customer replies to your number, we sign the reply with your Secret and post it to your Yeastar PBX, which routes it to the extension, message queue or message flow you choose. Yeastar can also check the connection from time to time with a quick verification request.

    Outbound
    AgentSends a text from the Linkus client
    Yeastar PBXPosts it to everymessage with your API key
    everymessageSends it and tracks delivery
    Customer’s mobileReceives the SMS
    Inbound
    Customer’s mobileReplies to your number
    everymessageSigns the reply and posts it to your Yeastar webhook
    Yeastar PBXRoutes it to an extension, message queue or message flow
    Yeastar sends messages to the everymessage API; replies come back by signed webhook.

    What you need

    • Yeastar P-Series Software Edition, firmware 83.23.0.24 or later
    • A domain name for your PBX with a valid certificate. Yeastar notes the domain must not contain an underscore
    • An everymessage account with an API key, and a Secret for signing webhooks
    • An SMS-enabled number from everymessage for customers to text and reply to

    Setting it up in Yeastar

    1. Get your details from us. We provide your API key (your API username:password, Base64-encoded), a Secret, and your SMS number.
    2. Add the channel. In the Yeastar web portal go to Messaging > Message Channel, click Add and choose SMS.
    3. Fill in the Authentication tab. Enter a name, set ITSP to General, and enter the values in the table below.
    4. Send us the webhook URL. Choose a Webhook URL from the drop-down, copy it and send it to us. We set it against your number with your Secret, so replies are signed.
    5. Set the sending rate. On the Messaging Settings tab, set the message sending rate. Ask us if you need to send faster than your account allows.
    6. Add your number. In the Number section, add your everymessage number in E.164 format, for example +447700900456, and choose where inbound messages go: an extension, a message queue or a message flow. Then choose which extensions can start conversations, and save.
    7. Test. Check the channel shows as connected, send a text from Linkus, then reply from the mobile and check the reply reaches the right agent.
    Yeastar settingValue
    ITSPGeneral
    API KeyYour everymessage API key (username:password, Base64-encoded)
    SecretThe Secret we give you (recommended)
    API Address for Sending Messageshttps://api.everymessage.com/v1/pbx/messages
    API Address for Verifying Authenticationhttps://api.everymessage.com/v1/pbx/verify (optional)
    Webhook URLCopy it from Yeastar and send it to us

    Picture messages (MMS)

    When someone sends a picture, video or document from Yeastar, everymessage delivers it as an ordinary SMS with a personal, secure link. The link opens a page showing the message and the media, so it works on every phone and network. MMS itself is still patchy on many UK phones and networks.

    • Up to 10 files per message, each up to 6 MB: images (JPEG, PNG, GIF, WebP, HEIC), video (MP4, MOV, 3GP, WebM), audio (MP3, M4A, AAC, AMR, OGG, WAV), PDF and contact cards (vCard).
    • Private by default. Files are copied to UK storage and only shown through the recipient’s own link, which can’t be guessed. Links stay live for 30 days.
    • Text is optional. If a message has no text, we add a short line such as “You’ve been sent a picture. View it here:”.
    • Delivery reports work as normal, because the message itself is an SMS.
    • Simple pricing. A picture message is charged as an SMS plus a media hosting fee.

    If any file can’t be fetched or isn’t a supported type, nothing is sent and Yeastar gets error 10003 with the reason. A file over 6 MB gets error 10008.

    Picture messages need to be switched on for your everymessage account. If they aren’t, Yeastar gets error 10005: ask us and we’ll turn them on.

    Voicemail notifications by SMS

    Yeastar P-Series can tell people about a new voicemail by text, using the same everymessage SMS channel. On firmware 83.25.0.23 or later you can also attach the voicemail itself, so the recipient can listen to it straight from their phone.

    • No extra set-up with us. Voicemail texts use the SMS channel you’ve already added, so they go out from your everymessage number (or your sender name) like any other text.
    • The recording arrives as a link. When the voicemail is attached, we deliver it like a picture message: an SMS with a personal, secure link to a page with an audio player. There’s no app to install.
    • Picture messages need to be on. Attaching the recording uses picture messages, so they need to be switched on for your account. Without them, a voicemail text with the recording attached is refused with error 10005.
    • Keep recordings under 6 MB. A recording over the limit is refused with error 10008. Yeastar’s maximum voicemail length setting is the easiest way to stay within it.
    • Watch long custom messages. Yeastar lets you write a long notification template. Very long texts use more SMS parts, and a text over your account’s limit is refused with error 10002, so keep the template short or ask us to raise the limit.
    • Same pricing. A notification with the recording attached is charged as an SMS plus a media hosting fee. Without it, it’s a normal SMS.

    Sending from your company name

    Yeastar sends each text from the number on the SMS channel. If you’d rather customers see your company name, you can set a sender name of up to 11 characters on that number, for example BrightDent, in the everymessage portal (Numbers → edit the number → PBX sender name), or ask us and we’ll set it for you. Texts sent from that number then go out from the name instead, and Yeastar keeps the conversation under your number.

    • One-way only. Customers can’t reply to a name, so use it for numbers that send notifications, not conversations.
    • UK sender ID rules apply. Letters, numbers and spaces, at least one letter, and no restricted generic names such as Verify or OTP. See UK SMS sender ID rules.
    • Per number. Your other numbers keep sending from the number, so two-way conversations carry on as normal.

    API reference

    You don’t need this to use Yeastar, but it shows exactly what Yeastar and everymessage exchange, which helps when testing or troubleshooting. The full reference, with code examples, is in our developer docs: Phone systems (PBX) API.

    Verify the connection

    Yeastar sends a random challenge with your API key. A valid key returns HTTP 200 with the same challenge in the body.

    curl "https://api.everymessage.com/v1/pbx/verify?challenge=mAWpGnyeTZgguOPY" \
      -H "Authorization: Bearer YOUR_API_KEY"

    Send a message

    Yeastar posts each text as JSON. from, to and text are all required, and numbers are in E.164 format.

    curl -X POST "https://api.everymessage.com/v1/pbx/messages" \
      -H "Content-Type: application/json" \
      -H "Authorization: Bearer YOUR_API_KEY" \
      -d '{"from": "+447700900456", "to": "+447700900123", "text": "Your order is ready to collect."}'

    A successful request returns HTTP 200 with the message details, including the everymessage message id. Errors return a JSON errors list using Yeastar’s error codes, listed under common problems below.

    Send a picture message

    Add media_urls with up to 10 public file URLs. text is optional when media is included. The response is the same as for a text message.

    {"from": "+447700900456", "to": "+447700900123", "text": "Here's the quote you asked for.",
     "media_urls": ["https://files.example.com/quote-1042.pdf"]}

    Replies

    Customer replies are posted to your Yeastar webhook as a message.received event. When a Secret is set, the request carries an X-Signature-256 header: sha256= followed by the lowercase hex signature of the request body made with your Secret.

    {
      "data": {
        "event_type": "message.received",
        "record_type": "event",
        "payload": {
          "id": "123789",
          "direction": "inbound",
          "type": "SMS",
          "from": { "phone_number": "+447700900123" },
          "to": [ { "phone_number": "+447700900456" } ],
          "text": "Can I collect it tomorrow?",
          "received_at": "2026-10-13T09:15:04.511Z"
        }
      }
    }

    Common problems and fixes

    SymptomLikely causeFix
    Channel won’t connectAPI key or verify address wrongCheck the key is username:password, Base64-encoded, and the verify address ends /v1/pbx/verify
    Error 10004Authentication failedRe-enter the API key
    Error 10001Number can’t be sent toCheck the number is a valid mobile in E.164 format
    Error 10005No permissionCheck the from number is one of your everymessage numbers and your account has credit
    Error 10003A picture or file couldn’t be usedCheck each file is reachable and a supported type, with at most 10 per message
    Error 10008A file is too largeKeep each file to 6 MB or less
    Customers can’t replyThe number sends from a sender nameNames are one-way. Use a number without a sender name for conversations
    Error 10006Too many requestsLower the sending rate, or ask us to raise your daily limit
    Replies don’t arriveWebhook not set, or Secret mismatchSend us the webhook URL, and check the Secret in Yeastar matches ours
    Replies rejectedPBX domain issueUse a domain with a valid certificate and no underscore

    Why use everymessage for Yeastar SMS

    UK numbers

    Two-way UK numbers that customers can text and reply to, set up and supported by our UK team.

    Signed replies

    Every reply is signed with your Secret, so your PBX only accepts genuine messages from everymessage.

    Sent as typed

    Emoji and accented characters are kept, with Unicode used only when a message needs it.

    Built for volume

    Multiple carrier routes and sending that can burst to 1 million SMS per hour, for busy contact centres and message campaigns.

    Secure and UK-hosted

    Hosted in UK data centres with high availability across the UK and EU, and ISO 27001 certified since 2009.

    More than SMS

    The same platform provides RCS, WhatsApp, email and AI voice assistants.

    Using 3CX? The same everymessage PBX API works with it too: see 3CX SMS. For other platforms, see NetSapiens SMS, Amazon Connect and every way to connect on our Business SMS page.

    Frequently asked questions

    Can Yeastar P-Series send SMS through everymessage?

    Yes. everymessage works as a custom SMS channel in Yeastar P-Series Software Edition, so agents can send and receive business SMS on everymessage numbers from their Linkus clients.

    Which ITSP do I select in Yeastar?

    Select General. Then enter the everymessage API key, the address for sending messages and, optionally, the address for verifying authentication and the Secret.

    What is the Secret for?

    It lets Yeastar check that replies really come from everymessage. We sign every webhook we send to your PBX with it, and Yeastar rejects any request whose signature doesn’t match. It’s optional but recommended.

    Which Yeastar version do I need?

    Yeastar P-Series Software Edition firmware 83.23.0.24 or later, reachable on a domain name with a valid certificate. Yeastar notes the domain name must not contain an underscore.

    Does it support MMS?

    Yes. Pictures, videos and documents sent from Linkus are delivered as an SMS with a personal, secure link that opens the message and media on any phone. Up to 10 files per message, each up to 6 MB.

    Can we send from our company name?

    Yes. You can set a sender name of up to 11 characters on one of your everymessage numbers in the everymessage portal (Numbers, then PBX sender name), or ask us to, so texts sent from that number go out from your name instead. Customers can’t reply to a name, so use it for notification numbers.

    Can agents send emoji and accented characters?

    Yes. Messages are sent exactly as typed. Plain text uses the standard SMS alphabet, and a message with emoji or other characters is sent as Unicode automatically.

    Add SMS to your Yeastar system

    Get your API key, Secret and numbers, and we’ll help you set up the channel and test it end to end.

  • 3CX SMS: send and receive business texts in 3CX with everymessage

    3CX is a business phone system used by thousands of UK organisations, and it can send and receive SMS through a messaging provider. everymessage supports the 3CX generic SMS provider interface, so your 3CX users can text customers from the same web client and apps they use for calls, on UK numbers, with delivery reports and replies in the conversation. This guide takes you through the setup on 3CX V20 step by step, then shows how to test it and fix the common problems.

    In short: turn on SMS on a 3CX SIP trunk, enter our PBX messages URL and your API key, then point a PBX-format webhook at the URL 3CX gives you (or send it to us and we do it). Outbound texts go from 3CX to everymessage, and replies and delivery reports come back to 3CX by webhook. No code and nothing to install.

    How the integration works

    3CX sends each outgoing text to everymessage as a simple request with your API key. We send it to the mobile networks and track delivery. When the message is delivered, or a customer replies to your number, we post it straight back to your 3CX system, which shows it in the right conversation.

    Outbound
    3CX userSends a text from the 3CX web client or app
    3CXPosts it to everymessage with your API key
    everymessageSends it and tracks delivery
    Customer’s mobileReceives the SMS
    Inbound and delivery reports
    Customer’s mobileReplies to your number
    everymessagePosts the reply, and each delivery report, to your 3CX webhook
    3CXShows the reply and delivery status in the conversation
    3CX sends messages to the everymessage API; replies and delivery reports come back by webhook.

    Before you start

    You needWhere it comes from
    Your everymessage API username and passwordeverymessage support, or your account admin
    An SMS-enabled number on your everymessage accounteverymessage: a new number, or one ported in
    3CX V20 with a SIP trunk to hold the SMS settingsYour 3CX admin console
    Admin access to the everymessage portalOnly if you set up the webhook yourself (step 3)

    The SIP trunk can be the one that already carries your calls. Its SMS settings are independent of who provides the voice service.

    Step 1: Get your API key and number

    Your API key is your everymessage API username and password, joined with a colon and Base64-encoded. 3CX sends it as Authorization: Bearer <API key> on every message.

    1. Get your API username and password from everymessage.
    2. Join them with a colon, no spaces: username:password.
    3. Base64-encode the result. On Windows PowerShell: [Convert]::ToBase64String([Text.Encoding]::UTF8.GetBytes('username:password')). On Mac or Linux: printf 'username:password' | base64.
    4. Keep the result safe. It is the API key for step 2, so treat it like a password.

    Note the SMS number on your account in international format with a plus, for example +447700900123. 3CX must send from that exact number, or the message is refused.

    Step 2: Add everymessage as the SMS provider in 3CX

    In 3CX V20 the SMS settings live on a SIP trunk’s SMS tab.

    1. In the 3CX web client, click Admin (bottom left).
    2. Go to Voice & Chat and edit the SIP trunk that carries your number.
    3. Open the SMS tab and turn on Enable SMS.
    4. Fill in the fields below and save.
    5. Copy the Webhook URL that 3CX shows on the same tab. You need it in step 3.
    6. Make sure your SMS number is on that trunk, and route it to the user, ring group or queue that should receive texts.
    3CX fieldValue
    Provider URLhttps://api.everymessage.com/v1/pbx/messages
    API KeyThe Base64 key from step 1
    NumbersInternational format with a plus, for example +447700900123

    If you have no trunk yet, add a Generic SIP trunk to hold the SMS settings.

    Step 3: Send replies and delivery reports to 3CX

    Replies and delivery reports reach 3CX through a webhook in PBX format, pointed at the URL you copied in step 2. Send that URL to everymessage support and we set it up, or do it yourself in the everymessage portal:

    1. Open Webhooks and add a new webhook.
    2. Paste the 3CX webhook URL and set Payload format to PBX – 3CX / Yeastar.
    3. Leave Signing secret blank. 3CX doesn’t check signatures.
    4. Open Numbers, edit your SMS number, set reply handling to URL and select the new webhook. Replies to that number now go to 3CX.
    5. Select the same webhook as the delivery address for your API user (or company), so delivery reports reach 3CX too.

    Use the PBX format, not the standard everymessage format. 3CX rejects messages in the standard format, and the replies never appear.

    Step 4: Test it

    Three checks prove the whole loop: a send, a delivery report and a reply.

    • Send. From the 3CX app, text your own mobile from the SMS number. It should arrive within a few seconds.
    • Delivery report. Within a minute, 3CX should mark the message as delivered.
    • Reply. Reply from your mobile. The reply should appear in the same 3CX conversation.

    If the send fails, 3CX shows the error code we returned: see common problems and fixes. If the reply never arrives, check the webhook format and URL from step 3 first.

    Picture messages (MMS)

    When someone sends a picture, video or document from 3CX, everymessage delivers it as an ordinary SMS with a personal, secure link. The link opens a page showing the message and the media, so it works on every phone and network. MMS itself is still patchy on many UK phones and networks.

    • Up to 10 files per message, each up to 6 MB: images (JPEG, PNG, GIF, WebP, HEIC), video (MP4, MOV, 3GP, WebM), audio (MP3, M4A, AAC, AMR, OGG, WAV), PDF and contact cards (vCard).
    • Private by default. Files are copied to UK storage and only shown through the recipient’s own link, which can’t be guessed. Links stay live for 30 days.
    • Text is optional. If a message has no text, we add a short line such as “You’ve been sent a picture. View it here:”.
    • Delivery reports work as normal, because the message itself is an SMS.
    • Simple pricing. A picture message is charged as an SMS plus a media hosting fee.

    If any file can’t be fetched or isn’t a supported type, nothing is sent and 3CX gets error 10003 with the reason. A file over 6 MB gets error 10008.

    Picture messages need to be switched on for your everymessage account. If they aren’t, 3CX gets error 10005: ask us and we’ll turn them on.

    Sending from your company name

    3CX always sends from the number set on the extension. If you’d rather customers see your company name, you can set a sender name of up to 11 characters on that number, for example BrightDent, in the everymessage portal (Numbers → edit the number → PBX sender name), or ask us and we’ll set it for you. Texts sent from that number then go out from the name instead, and 3CX keeps the conversation under your number.

    • One-way only. Customers can’t reply to a name, so use it for numbers that send notifications, not conversations.
    • UK sender ID rules apply. Letters, numbers and spaces, at least one letter, and no restricted generic names such as Verify or OTP. See UK SMS sender ID rules.
    • Per number. Your other numbers keep sending from the number, so two-way conversations carry on as normal.

    API reference

    You don’t need this to use 3CX, but it shows exactly what 3CX and everymessage exchange, which helps if you’re testing or troubleshooting. The full reference, with code examples, is in our developer docs: Phone systems (PBX) API.

    Send a message

    3CX posts each text as JSON, with your API key as a Bearer token. from, to and text are all required, and numbers are in E.164 format.

    curl -X POST "https://api.everymessage.com/v1/pbx/messages" \
      -H "Content-Type: application/json" \
      -H "Authorization: Bearer YOUR_API_KEY" \
      -d '{"from": "+447700900456", "to": "+447700900123", "text": "Your engineer is on the way."}'

    Errors return a JSON errors list with a code, title and detail; the codes are listed under common problems below. A successful request returns HTTP 200 with the message details. The id is the everymessage message id, which 3CX uses to match the delivery report:

    {
      "data": {
        "record_type": "message",
        "direction": "outbound",
        "id": "123456",
        "type": "SMS",
        "from": { "phone_number": "+447700900456" },
        "to": [ { "phone_number": "+447700900123", "status": "queued" } ],
        "text": "Your engineer is on the way.",
        "encoding": "GSM-7",
        "parts": 1
      }
    }

    Send a picture message

    Add media_urls with up to 10 public file URLs. text is optional when media is included. The response is the same as for a text message.

    {"from": "+447700900456", "to": "+447700900123", "text": "Here's the quote you asked for.",
     "media_urls": ["https://files.example.com/quote-1042.pdf"]}

    Replies

    Customer replies are posted to your 3CX webhook as a message.received event:

    {
      "data": {
        "event_type": "message.received",
        "record_type": "event",
        "payload": {
          "id": "123789",
          "direction": "inbound",
          "type": "SMS",
          "from": { "phone_number": "+447700900123" },
          "to": [ { "phone_number": "+447700900456" } ],
          "text": "Thanks, see you soon",
          "received_at": "2026-10-13T09:15:04.511Z"
        }
      }
    }

    Delivery reports

    When a message is delivered or fails, a message.finalized event is posted to the same webhook. payload.id is the id returned when the message was sent, and to[].status is delivered or delivery_failed.

    Common problems and fixes

    Every refused send returns an HTTP status and a five-digit code, which 3CX shows against the message.

    HTTPCodeMeaningWhat to do
    40110004API key missing or wrongRebuild the key from step 1: username:password, no spaces, Base64-encoded
    400 / 42210002Invalid request, or text too long for your accountCheck the message; ask us to raise the parts limit for long texts
    42210001Recipient number invalid or not routableUse a full international number, for example +447700900456
    42210005Sender not allowed, or number blockedSend only from your everymessage numbers
    42210003A file couldn’t be downloaded or is an unsupported typeUse a supported, publicly downloadable file, at most 10 per message
    42210008A file is over 6 MBSend a smaller file
    40210005Not enough creditTop up your account
    40310005Picture messages not enabledAsk us to switch on Rich SMS
    42910006Daily sending limit reachedWait until midnight UK time, or ask us to raise the limit
    50010007Temporary fault on our sideRetry; contact us if it persists

    If sends work but replies never show in 3CX, the cause is almost always the webhook: the wrong URL, or the standard format instead of PBX. If messages stay unconfirmed, check the same webhook is set as the delivery address for your API user or company. And customers can’t reply to a sender name, by design.

    Why use everymessage for 3CX SMS

    UK numbers

    Two-way UK numbers that customers can text and reply to, set up and supported by our UK team.

    Delivery reports

    Every message is tracked, and its final status is sent back to 3CX so users can see what was delivered.

    Sent as typed

    Emoji and accented characters are kept, with Unicode used only when a message needs it, so nothing a user types is lost.

    Built for volume

    Multiple carrier routes and sending that can burst to 1 million SMS per hour.

    Secure and UK-hosted

    Hosted in UK data centres with high availability across the UK and EU, and ISO 27001 certified since 2009.

    More than SMS

    The same platform provides RCS, WhatsApp, email and AI voice assistants.

    Using Yeastar? The same everymessage PBX API works with it too: see Yeastar SMS. Using a different phone or contact centre platform? See NetSapiens SMS, Amazon Connect and every other way to connect on our Business SMS page.

    Frequently asked questions

    Can 3CX send SMS through everymessage?

    Yes. everymessage supports the 3CX generic SMS provider interface, so 3CX users can send and receive business SMS on everymessage numbers, with delivery reports shown in 3CX.

    What do I enter in 3CX?

    The everymessage PBX messages URL and your everymessage API key. 3CX sends the key as a Bearer token on every message, so there’s nothing else to install.

    How do replies reach 3CX?

    3CX gives you a webhook URL for the trunk. We set it against your everymessage numbers in the 3CX / Yeastar (PBX) format, and every customer reply and delivery report is posted to it.

    Where are the SMS settings in 3CX V20?

    On a SIP trunk. In the 3CX web client click Admin, go to Voice & Chat, edit the SIP trunk that carries your number and open its SMS tab. The trunk can be the one that already carries your calls.

    Why do texts send from 3CX but replies never appear?

    Almost always the webhook. It must point at the exact URL shown on the 3CX trunk’s SMS tab and use the PBX (3CX / Yeastar) payload format. 3CX rejects the standard everymessage format, so replies sent in it never appear.

    Does it support MMS?

    Yes. Pictures, videos and documents sent from 3CX are delivered as an SMS with a personal, secure link that opens the message and media on any phone. Up to 10 files per message, each up to 6 MB.

    Can 3CX send texts from our company name?

    Yes. 3CX always sends from a number, but you can set a sender name of up to 11 characters on that number in the everymessage portal (Numbers, then PBX sender name), or ask us to, so texts from it go out from your name instead. Customers can’t reply to a name, so use it for notification numbers.

    Can users send emoji and accented characters?

    Yes. Messages are sent exactly as typed. Plain text uses the standard SMS alphabet, and a message containing emoji or other characters is sent as Unicode automatically.

    What number format does 3CX use?

    3CX sends and expects numbers in international E.164 format with a leading +, for example +447700900123. everymessage accepts and returns numbers in that format.

    Add SMS to your 3CX system

    Get your API key and numbers, and we’ll help you connect 3CX and test it end to end.

  • NetSapiens SMS: add two-way business SMS with everymessage as your carrier

    NetSapiens is a unified communications (UCaaS) platform used by service providers to deliver voice, video and messaging to their business customers. Its SMS Advanced API lets you plug in your own SMS carrier, and everymessage can be that carrier. This guide explains how the integration works, what you need, how it’s set up and how to test it, so your NetSapiens users can send and receive business SMS through a UK messaging platform.

    In short: add everymessage as a carrier in your NetSapiens SMS Advanced API configuration. Outbound texts are posted to the everymessage send API, and inbound replies are forwarded to your NetSapiens server by webhook. It’s configuration only, with no code, and works with NetSapiens v43 and later.

    How the integration works

    NetSapiens treats everymessage like any other SMS carrier. When a user sends a text, NetSapiens posts it to the everymessage gateway, which sends it to the mobile networks and records delivery. When a customer replies to one of your everymessage numbers, we forward the message to your NetSapiens server, which routes it to the right user.

    Outbound
    NetSapiens userSends a text from their NetSapiens app or portal
    NetSapiens coreSMS Advanced API posts it to the everymessage carrier
    everymessageChecks, sends and tracks delivery
    Customer’s mobileReceives the SMS
    Inbound
    Customer’s mobileReplies to your everymessage number
    everymessageReceives the reply and calls your webhook
    NetSapiens coreReads the message and routes it
    NetSapiens userSees the reply in the conversation
    Outbound SMS uses the NetSapiens SMS Advanced API; inbound replies arrive by webhook.

    What you need

    • NetSapiens v43 or later with the SMS Advanced API enabled (v44 or later if you want to keep the + on inbound numbers)
    • An everymessage account with API credentials
    • CLI or SSH access to your NetSapiens core server, where the carrier settings live
    • SMS-enabled numbers provisioned on everymessage, for customers to text and reply to

    Setting it up

    The integration is a short block of carrier settings on the NetSapiens core server, plus a webhook we set against your numbers. These are the steps; the complete configuration follows.

    1. Choose a carrier name. NetSapiens carrier names must be lowercase and 16 characters or fewer, for example everymessage. A name with capital letters makes outbound messages fail silently.
    2. Point the carrier at everymessage. Set the carrier URL to the everymessage send endpoint we give you, with form-encoded requests.
    3. Map the outbound fields. NetSapiens’ from, to and text values map to the everymessage sender, numbers and message fields.
    4. Add your API key. Your everymessage API key is added as a custom outbound field, so it’s included in every request.
    5. Set the number format. everymessage expects international numbers without a leading +, for example 447700900123, so the outbound plus options are turned off.
    6. Set up inbound. Send us your NetSapiens inbound webhook URL, including your carrier name, and we’ll set it against your numbers. On the NetSapiens side, map the inbound number, sender and message fields, and tell NetSapiens where to find them in our payload.
    NetSapiens settingeverymessage fieldWhat it holds
    outboundFromsenderYour sender ID or number
    outboundTonumbersThe recipient’s number
    outboundTextmessageThe message text
    inboundToinboxNumberYour everymessage number that received the reply
    inboundFromsenderThe customer’s mobile number
    inboundTextcontentThe reply text

    Carrier API configuration

    This is the complete carrier configuration. Add it to /etc/netsapiens/api_config.php on your NetSapiens core server (or nsconfig_include.php, depending on your deployment), and replace the values in capitals:

    • FQDN in the URL: the everymessage API address we give you.
    • BASE64_ENCODED_USERNAME_PASSWORD: your everymessage API key, which is your API username and password in the form username:password, Base64-encoded.
    // everymessage SMS carrier configuration
    
    // API endpoint
    Configure::write('NSCarrier.everymessage.url',
      "https://FQDN/send");
    
    // Content type
    Configure::write('NSCarrier.everymessage.content_type',
      'application/x-www-form-urlencoded');
    
    // Outbound parameter mapping
    Configure::write('NSCarrier.everymessage.outboundFrom', "sender");
    Configure::write('NSCarrier.everymessage.outboundTo', "numbers");
    Configure::write('NSCarrier.everymessage.outboundText', "message");
    
    // Number formatting (no plus prefix)
    Configure::write('NSCarrier.everymessage.outboundToPlus', false);
    Configure::write('NSCarrier.everymessage.outboundFromPlus', false);
    
    // Authentication via apiKey form field
    Configure::write('NSCarrier.everymessage.customOutboundJsonFields',
      "apiKey");
    Configure::write('NSCarrier.everymessage.customOutboundJsonFields.apiKey',
      "BASE64_ENCODED_USERNAME_PASSWORD");
    
    // Inbound: messages arrive inside a "list" array
    Configure::write('NSCarrier.everymessage.customNestedInboundFields',
      ["list", 0]);
    
    // Inbound parameter mapping
    Configure::write('NSCarrier.everymessage.inboundTo', "inboxNumber");
    Configure::write('NSCarrier.everymessage.inboundFrom', "sender");
    Configure::write('NSCarrier.everymessage.inboundText', "content");

    Inbound sender numbers arrive in international format with a +, for example +447700900123. If your deployment expects the +, NetSapiens v44 and later can keep it:

    // Keep the + on inbound numbers (v44 and later)
    Configure::write('NSCarrier.everymessage.inboundToPlus', true);
    Configure::write('NSCarrier.everymessage.inboundFromPlus', true);

    Inbound webhook URL

    Send us your NetSapiens inbound webhook URL and we’ll set it against your everymessage numbers. Replace FQDN with your NetSapiens server’s address, and use the same carrier name as in your configuration:

    https://FQDN/ns-api/?object=sms&action=create&inboundSMS=true&nsCarrier=everymessage

    Replies are delivered inside a list array, which is why the configuration tells NetSapiens to read the first item with ["list", 0]:

    {
      "list": [
        {
          "type": "INBOUND_MESSAGE",
          "messageId": 987,
          "sender": "+447700900123",
          "inboxName": "support",
          "inboxNumber": "447700900456",
          "content": "Yes, please book me in",
          "dateTime": "2026-10-13T09:15:04.511Z"
        }
      ]
    }

    Test your credentials

    Before testing through NetSapiens, check your API key with a direct request in test mode. test=true validates the request without sending the message or using credit, and a successful response includes "status": "success".

    curl -X POST "https://FQDN/send" \
      -d "apiKey=BASE64_ENCODED_USERNAME_PASSWORD" \
      -d "sender=YourCompany" \
      -d "message=Test from NetSapiens" \
      -d "numbers=447700900123" \
      -d "test=true"

    Then send a text from NetSapiens and check the messaging log (tail -f path-to-api/tmp/logs/messaging.log) for NS_SMS200. For replies, look for (Messages.dispatch) create1, which shows the webhook arrived.

    Common problems and fixes

    SymptomLikely causeFix
    Outbound fails with no errorCarrier name has capital lettersUse an all-lowercase carrier name
    Outbound fails with HTTP 401API key is wrongCheck the API key in the custom outbound field
    Outbound fails with HTTP 400A field is missingCheck the from, to and text mappings
    Numbers rejectedWrong number formatSend international numbers without a +
    Replies don’t arriveWebhook URL incompleteCheck the URL includes your carrier name and server address
    Replies arrive emptyInbound fields not mappedCheck the nested inbound setting and the inbound field mappings

    Why use everymessage as your NetSapiens SMS carrier

    UK numbers and sender IDs

    Two-way UK numbers for replies, and branded sender IDs for one-way messages, checked against UK network rules at set-up.

    Built for volume

    Multiple carrier routes and sending that can burst to 1 million SMS per hour, for everything from one-to-one conversations to large campaigns.

    Delivery tracking

    Delivery reports for every message in the everymessage portal and through the API, so you can see what reached each customer.

    Secure and UK-hosted

    Hosted in UK data centres with high availability across the UK and EU, and ISO 27001 certified since 2009.

    More than SMS

    The same platform also provides RCS, WhatsApp and email, so you can grow your messaging with one supplier.

    UK support

    Our own UK team helps you configure the carrier, set up your numbers and test the integration.

    Using a different platform? See our Business SMS page for every way to connect, including the SMS API, SMPP, email-to-SMS and Amazon Connect.

    Frequently asked questions

    Can NetSapiens send SMS through everymessage?

    Yes. NetSapiens v43 and later can use everymessage as an SMS carrier through the NetSapiens SMS Advanced API. Outbound messages are sent to the everymessage gateway, and inbound messages are forwarded to NetSapiens by webhook.

    Which version of NetSapiens do I need?

    NetSapiens v43 or later with the SMS Advanced API enabled. Keeping the + on inbound numbers needs v44 or later.

    Does it support two-way SMS?

    Yes. Customers’ replies to your everymessage numbers are forwarded to your NetSapiens server by webhook, so users see them in NetSapiens alongside their outbound messages.

    Do I need to write any code?

    No. The integration is configuration only: a block of carrier settings on the NetSapiens core server, plus an inbound webhook URL that we set against your numbers.

    What number format does everymessage use?

    Outbound numbers are sent in international format without a leading +, for example 447700900123. Inbound sender numbers arrive in international format with a +, for example +447700900123.

    Can I test without sending messages?

    Yes. The everymessage send API has a test mode that checks a request is valid without sending the message or using credit, so you can confirm your credentials and settings before going live.

    Add SMS to your NetSapiens platform

    Get your API credentials, numbers and our full NetSapiens integration guide, and we’ll help you test it end to end.

  • Forget MMS, here is RCS: picture messages that work for marketing

    For years, the only way to put a picture in a text message was MMS. It never caught on for business: it was expensive, images arrived squashed and blurry, and there was no branding, no buttons and no way to see what happened next. In our experience, the organisations that used MMS marketing most were the mobile networks themselves, promoting their own offers. RCS changes that. This guide explains why MMS didn’t work, what RCS does instead, and how to use images in RCS marketing that customers actually respond to.

    In short: forget MMS. RCS Business Messaging sends sharp images, swipeable carousels and tap-to-act buttons from a verified, branded sender, straight into the phone’s own messaging app. Phones that can’t receive RCS can get the same rich message, images included, as a branded web page by SMS link, so every customer sees your pictures.

    Why MMS never worked for business

    Too expensive

    An MMS cost many times more than an SMS, which ruled it out for campaigns to large customer lists. That’s why most MMS marketing came from the networks, who weren’t paying the same rates.

    Poor image quality

    Networks and handsets shrink MMS images to small file sizes, so photos often arrived compressed, cropped or blurry, which is the opposite of what a marketing image needs.

    No branding

    An MMS comes from a number, with no logo, brand name or verification, so customers can’t easily tell a genuine offer from a scam.

    Unreliable delivery

    MMS depends on mobile data and the right handset settings. Some customers saw a download link or nothing at all instead of the picture.

    No interaction

    There were no buttons. To act on an offer, customers had to type a long web address or reply with a keyword.

    Little to measure

    With limited delivery reporting and no tap tracking, it was hard to know whether a campaign worked.

    Here is RCS: picture messaging done properly

    RCS (Rich Communication Services) is the upgrade to SMS built into modern phones’ default messaging app. With RCS Business Messaging, your messages arrive from your verified brand, with your logo and colours, and can include images, video, rich cards, carousels and buttons. Customers don’t need an app, and they reply or tap in the same place they read their texts.

    BrightShop ✓ Verified
    Summer sale
    20% off garden furniture, SarahYour member discount is ready. Offer ends Sunday at midnight.
    Shop the saleFind my nearest store
    Remind me FridayStop offers
    An RCS rich card: verified brand, image, personalised text and buttons, in the phone’s own messaging app.
    MMSRCS Business Messaging
    SenderA phone numberYour verified brand name, logo and colour
    ImagesSmall, compressed filesSharp images and video, in cards sized for the screen
    LayoutA picture and some textRich cards and swipeable carousels with titles and descriptions
    ActionsType a web address or replyTap to open a link, call, see a map, add to calendar or reply
    TrustEasy to imitateBrand verified before you can send
    ReportingLimitedDelivery reports, replies and button taps
    Phones without itMessage may not arriveeverymessage sends a web version by SMS link, or a plain SMS

    Ways to use images in RCS marketing

    Product carousels

    Show several products in a swipeable carousel, each with its own picture, price and “Buy now” button. Ideal for new ranges, sales and back-in-stock alerts.

    Personal offers

    A single eye-catching card with the customer’s name and offer, and buttons to shop online or find the nearest store.

    Events and launches

    An event image with the date and venue, plus buttons to book, add to calendar or get directions.

    Property and vehicles

    New listings or stock with photos, key details and a button to arrange a viewing or test drive.

    Travel and leisure

    Destination images, last-minute deals and upgrade offers, with a button straight to booking.

    Loyalty and renewals

    A branded card showing points, rewards or a renewal offer, so customers can act in one tap instead of searching for a login.

    Tips for image campaigns that work

    • One clear image, one clear action. Uncluttered pictures with one focal point work best on a small screen, with a single main button.
    • Keep the important words out of the picture. Put the price, date or offer in the card’s title and description, so it’s always readable and works with screen readers.
    • Size for mobile. Use images made for a phone screen and keep file sizes light, so cards load quickly on mobile data.
    • Personalise. Merge the customer’s name, nearest store or offer into each card from your data.
    • Use a carousel for choice, a single card for focus. Carousels suit browsing; a single card suits one offer or reminder.
    • Get consent and offer an opt-out. RCS marketing follows the same UK rules as SMS marketing. Only send to customers who’ve agreed, and include an easy way to stop.
    • Measure and adjust. Compare delivery, replies and button taps between images and offers, and send more of what works.

    Every customer sees your pictures, even without RCS

    Not every phone can receive RCS yet. Where MMS simply failed on those phones, everymessage checks each recipient and picks the best channel automatically.

    1. RCS phones get the full branded message with images, carousels and buttons in their messaging app.
    2. Other phones get an SMS with a personal short link on rcsview.uk, our secure viewing domain. Tapping it opens the same rich message, images, carousel and buttons included, as a branded web page in the phone’s browser. Button taps still come back to you as replies.
    3. Or plain SMS if you prefer a simple text fallback for that send.
    BBrightShop
    Text message · Today 10:02
    BrightShop: Sarah, your 20% summer discount is ready. See your offer: rcsview.uk/k7Qm2
    Plain SMS, works on every phone
    🔒 rcsview.uk/k7Qm2
    BrightShop
    Summer sale
    20% off garden furniture, SarahYour member discount is ready. Offer ends Sunday at midnight.
    Shop the sale Find my nearest store
    The same rich card, as a branded web page
    No RCS? The customer gets an SMS with a personal rcsview.uk link (left), which opens the same rich message in their browser (right).

    Each link is unique to the customer, so the web page shows their personalised card, and the platform records when each link is first opened. Unlike MMS, the pictures don’t depend on handset settings: if the phone can open a web page, the customer sees your images.

    You see what was delivered by RCS, by web link and by SMS in the portal and through the API. Read more about RCS Business Messaging and how it compares in RCS vs SMS vs WhatsApp.

    How to get started

    1. Brand verification. We set up your RCS agent, your branded sender, and take it through verification with Google and the mobile networks.
    2. Design your cards. Build rich cards and carousels with your images in the everymessage Template Designer, with a live preview and no coding.
    3. Choose your audience and fallback. Send to a group from the portal or through the RCS API, and choose a web version or SMS for phones without RCS.
    4. Measure. Track delivery, replies and taps, and refine your next campaign.

    Frequently asked questions

    Is RCS the same as MMS?

    No. MMS sends a picture or short video from a phone number, with no branding or buttons. RCS Business Messaging sends from a verified brand, with your logo, rich cards, swipeable carousels and tap-to-act buttons, and reports what was delivered.

    Can I still send MMS picture messages to UK customers?

    MMS still exists on UK networks, but it was always expensive per message, images are heavily compressed and it carries no branding or buttons. For business picture messages, RCS does everything MMS did and much more.

    What happens if a customer’s phone can’t receive RCS?

    everymessage can send them an SMS with a personal short link on rcsview.uk that opens the same rich message, images and buttons included, as a branded web page. You can choose a plain SMS instead if you prefer.

    Can I send marketing by RCS?

    Yes, under the same UK rules as SMS marketing: you need the customer’s consent, you must identify yourself, and every message needs a simple way to opt out. everymessage can add an opt-out link to rich messages.

    What kind of images work best in RCS cards?

    Clear, uncluttered images with one focal point, sized for a phone screen and kept light so they load quickly. Put key information such as the price or date in the card text rather than inside the image, so it’s always readable.

    Do customers need an app to see RCS picture messages?

    No. RCS messages arrive in the phone’s built-in messaging app, in the same place as their text messages.

    Ready to send your first picture campaign?

    We’ll help you verify your brand, design your first rich cards and choose the right fallback for every customer.

  • Two-way SMS in Amazon Connect: your options and how to set it up

    Customers would often rather send a text than wait on hold. If your contact centre runs on Amazon Connect, you can let them: texts arrive in the agent workspace, agents answer alongside calls and chats, and replies go back to the customer’s phone. This guide explains the two ways to add two-way SMS to Amazon Connect, how each works, and how to choose.

    In short: you can add SMS to Amazon Connect natively, using phone numbers from AWS End User Messaging SMS, or connect your SMS provider so customer texts become Amazon Connect contacts and agent replies go out as SMS. Native suits teams building everything in AWS from scratch. A provider integration suits organisations that already have numbers, sender names and messaging on another platform.

    Why add SMS to your contact centre?

    • Customers already text. Every mobile phone can send an SMS, with no app, login or data connection needed.
    • Fewer calls, shorter queues. Offering “text us instead” in your phone menu or on your website moves simple queries to messaging, where an agent can handle several conversations at once.
    • Replies to your own messages. Customers can reply to an appointment reminder, delivery update or bill, and the reply reaches someone who can help.
    • Asynchronous by nature. Customers reply when it suits them, without staying on a call.

    Two ways to do it

    Native: AWS End User Messaging SMSConnect your SMS provider
    Phone numbersRequested in your AWS account, then imported into Amazon ConnectThe numbers you already use with your provider
    In the agent workspaceAn SMS contactA chat contact, routed by your contact flow
    Set-up in AWSNumber request, registration where required, two-way settings, leaving the SMS sandbox, spend quotaAn access role for the provider, and a message stream for agent replies
    UK sender namesRegistered with AWSManaged with your provider
    BillingThrough AWSThrough your provider, alongside your other SMS
    Other channelsEach configured separately in AWSDepends on your provider; with everymessage, SMS, RCS, WhatsApp and email run from one platform
    Best forNew set-ups built entirely in AWSOrganisations that already send SMS and want to keep their numbers and messaging in one place

    Both approaches let agents answer texts in Amazon Connect, and both let your contact flows route them. The difference is where your numbers, registrations and messaging live.

    Option 1: native SMS through AWS

    AWS End User Messaging SMS provides SMS numbers that you import into Amazon Connect. In outline:

    1. Request a number in the AWS End User Messaging SMS console for the country you’ll message, with two-way messaging switched on. Some countries need the number or sender ID registered first, which AWS says can take up to 15 business days.
    2. Enable two-way SMS on the number, with Amazon Connect as the destination, and import it into your instance.
    3. Update your flows to recognise SMS contacts and route them to the right queue.
    4. Go to production: move your account out of the SMS sandbox and check your spending limit.

    Points to know: a number can’t be shared between voice and SMS, and opt-out keywords such as STOP are handled by AWS unless you set up your own opt-out handling. In the UK, AWS supports two-way SMS on long codes and short codes, and alphanumeric sender IDs must be registered.

    Option 2: connect your SMS provider

    If you already send texts through a messaging provider, you can connect it to Amazon Connect instead. With everymessage it works like this:

    1. A customer texts one of your numbers. The number is set to send its replies to Amazon Connect.
    2. A chat contact starts in Amazon Connect, using the contact flow you choose, so your routing, opening hours and bots apply. Further texts from the same customer join the same conversation while it’s open.
    3. The agent replies in their usual workspace. Amazon Connect streams the reply to a notification topic in your AWS account, which is shared with everymessage.
    4. The reply goes out as an SMS from the same number, so the customer just carries on texting.

    Access is through a role in your AWS account, protected by an external ID, with only the Amazon Connect permissions the integration needs. No AWS keys are shared, and you can withdraw access at any time. See SMS for Amazon Connect (currently in Beta).

    Sending texts from your contact flows

    Whichever option handles inbound texts, your flows can also send SMS. Add an “Invoke AWS Lambda function” block, and have the function call an SMS API. Common uses:

    • After a call: a confirmation, reference number or summary of what was agreed.
    • Instead of waiting: a callback link or a link to self-service while the customer is in the queue.
    • Payments: a secure payment link, so card details are never read out over the phone.
    • Feedback: a short satisfaction survey when the contact ends.

    The everymessage SMS API takes a single HTTPS request and returns a message ID you can store against the contact. Delivery receipts can be sent to your systems by webhook.

    Good practice for SMS in a contact centre

    • Use a number customers can reply to. Messages from a sender name such as your company name can’t be replied to.
    • Set expectations. Tell customers your messaging hours and how quickly you reply, and use an automatic reply outside hours.
    • Keep sensitive details out of texts. Send a secure link instead of account numbers or personal data. See digital letters.
    • Honour opt-outs. Make sure STOP requests are recorded and respected across every system that sends texts.
    • Keep messages short. Long replies are split into several parts and cost more. See SMS character limits explained.
    • Think beyond SMS. For customers who prefer them, RCS and WhatsApp offer richer conversations. Compare them in RCS vs SMS vs WhatsApp.

    Which should you choose?

    Choose native AWS SMS if…

    you’re setting up messaging from scratch, want numbers, registration and billing all in your AWS account, and only need SMS inside Amazon Connect.

    Connect a provider if…

    you already send SMS through a provider, want to keep your existing numbers and sender names, or want SMS, RCS, WhatsApp and email managed and reported in one place, with UK-based support.

    Frequently asked questions

    Can Amazon Connect send and receive SMS?

    Yes. You can add SMS to Amazon Connect natively through AWS End User Messaging SMS, or connect an existing SMS provider such as everymessage, so customer texts arrive as contacts your agents can answer and agent replies go back as texts.

    Does two-way SMS in Amazon Connect work in the UK?

    Yes. AWS supports two-way SMS on UK long codes and short codes, and alphanumeric sender IDs for UK messages must be registered. With everymessage you can use UK mobile numbers you already have with us.

    Do customers need an app to text a contact centre?

    No. Customers use the normal messaging app on their phone. Their texts reach your agents, and the replies arrive as ordinary text messages.

    Can a contact flow send an SMS?

    Yes. A flow can call a Lambda function, and the function can send a text through an SMS API. That’s how flows send confirmations, callback links, payment links and surveys.

    Can customers reply to a sender name such as a company name?

    No. Texts sent from an alphanumeric sender name can’t be replied to. For two-way conversations, send from a mobile number or short code.

    Should I use AWS’s own SMS or an SMS provider?

    If you’re starting from scratch and want everything inside AWS, the native option works well. If you already send SMS through a provider, want to keep your numbers and sender names, or want SMS, RCS, WhatsApp and email managed together, connecting your provider can be simpler.

    Add SMS to your Amazon Connect contact centre

    Our Amazon Connect integration is in Beta. Tell us about your contact centre and we’ll set it up with you.

  • SPF, DKIM and DMARC: a practical guide to email security

    Anyone can send an email that claims to come from your domain. SPF, DKIM and DMARC are three DNS records that let inbox providers check whether it really did. Set up properly, they stop criminals impersonating you, keep your genuine email out of spam folders, and protect the reputation of your domain. This guide explains each one, shows example records, and sets out a safe plan to reach full protection.

    In short: use SPF to list the servers that send your email, DKIM to sign every message with your domain, and DMARC to require that one of them matches the From address and to tell providers to reject what fails. Start DMARC in monitoring mode, fix every legitimate sender, then move to p=reject. Gmail, Yahoo and Microsoft now require all three from bulk senders.

    Why email authentication matters

    • Fraud: phishing and invoice fraud often use a real company’s domain in the From address. Without DMARC enforcement, nothing tells the receiving server to refuse it.
    • Deliverability: inbox providers trust authenticated mail. Unauthenticated email is more likely to be filtered as spam or rejected outright.
    • Reputation: providers build a reputation for your domain from the mail it sends. Authentication ties that reputation to you, so spoofed mail can’t damage it and your good sending history counts.
    • Visibility: DMARC reports show every service sending email as your domain, including ones you didn’t know about.

    What the big inbox providers require

    Since 2024, Gmail and Yahoo have required senders of more than 5,000 messages a day to their users to meet these rules, and Microsoft introduced similar requirements for Outlook.com in 2025:

    • SPF and DKIM set up for the sending domain;
    • a DMARC record, at least p=none, with SPF or DKIM aligned to the From domain;
    • one-click unsubscribe in marketing email, with unsubscribes honoured within two days;
    • a spam complaint rate kept well below 0.3%;
    • valid forward and reverse DNS for sending servers, and TLS encryption.

    Smaller senders benefit from the same rules: the requirements describe what good, trusted email looks like.

    How the three work together

    SPFDKIMDMARC
    What it doesLists the servers allowed to send for a domainAdds a digital signature to each messageRequires an aligned SPF or DKIM pass, sets a policy, sends reports
    What it checksThe sending server’s IP address against the envelope sender (Return-Path) domainThe signature against a public key in the signing domain’s DNSThat the passing SPF or DKIM domain matches the visible From domain
    Where it livesexample.com TXTselector._domainkey.example.com TXT_dmarc.example.com TXT
    Survives forwarding?Usually notYes, if the message isn’t changedYes, through DKIM
    On its ownDoesn’t protect the From address people seeDoesn’t say what to do with failuresNeeds SPF or DKIM to work

    SPF: who is allowed to send

    An SPF (Sender Policy Framework) record is a single TXT record on your domain listing every service that sends email for it: your own mail servers, your office email provider, and any platform that sends on your behalf, such as a CRM, helpdesk, billing system or email platform.

    RecordNameValue (TXT)
    SPFexample.comv=spf1 include:_spf.google.com include:spf.example-esp.net ip4:203.0.113.10 -all
    • One record only. A domain must have exactly one SPF record. Two records make SPF fail. Add new services to the existing record.
    • Stay under 10 lookups. Each include, a, mx and redirect costs a DNS lookup, including the ones nested inside other includes. More than 10 makes SPF fail. Remove services you no longer use, and move bulk senders to their own subdomain.
    • End with -all or ~all. -all (hard fail) says anything not listed is unauthorised. ~all (soft fail) is gentler while you’re still finding senders. Never use +all, which allows anyone.
    • Know its limits. SPF checks the hidden envelope sender, not the From address your recipients see, and it normally fails when a message is forwarded. That’s why you need DKIM and DMARC as well.

    DKIM: a signature on every message

    DKIM (DomainKeys Identified Mail) adds a cryptographic signature to the headers of each email. The sending service signs with a private key; you publish the matching public key in DNS. Receiving servers check the signature, which proves the message was authorised by the signing domain and hasn’t been changed in transit.

    RecordNameValue (TXT)
    DKIMs1._domainkey.example.comv=DKIM1; k=rsa; p=MIIBIjANBgkqh...IDAQAB
    • Sign with your own domain. The signature’s domain (d=) should be your domain, not your provider’s. Only then does DKIM count towards DMARC.
    • One selector per service. The selector (s1 above) lets each sending service have its own key, so you can change or remove one without affecting the others.
    • Use 2048-bit keys where your DNS host and provider support them, and avoid 1024-bit keys for new set-ups.
    • Rotate keys every 6 to 12 months, and straight away if a key may have been exposed. Publish the new selector before switching, then remove the old one.

    DMARC: policy, alignment and reports

    DMARC (Domain-based Message Authentication, Reporting and Conformance) ties SPF and DKIM to the From address people actually see. A message passes DMARC when SPF or DKIM passes and the domain that passed matches the From domain. This matching is called alignment. DMARC then tells receivers what to do with mail that fails, and asks them to send you reports.

    RecordNameValue (TXT)
    DMARC_dmarc.example.comv=DMARC1; p=none; rua=mailto:dmarc-reports@example.com; fo=1
    TagMeaning
    p=The policy for failing mail: none (monitor only), quarantine (send to spam) or reject (refuse it).
    rua=Where to send daily aggregate reports, summarising who sent mail as your domain and whether it passed.
    pct=The percentage of failing mail the policy applies to, so you can roll out quarantine or reject gradually.
    sp=A separate policy for subdomains. Without it, subdomains follow p=.
    adkim= / aspf=Alignment mode: r (relaxed, the default) allows subdomains of the same organisation to match; s (strict) needs an exact match.

    A safe path to p=reject

    1. List your senders. Find every system that sends email as your domain: office email, marketing, CRM, invoicing, helpdesk, website forms, scanners and devices.
    2. Publish p=none with reports. Nothing is blocked, but within a day you start receiving reports.
    3. Fix every legitimate sender. Add it to SPF and turn on DKIM signing with your domain. Read the reports for two to four weeks until all genuine mail passes.
    4. Move to quarantine. Start with p=quarantine; pct=25 and increase to 100 while watching the reports.
    5. Move to reject. Set p=reject. Mail that fakes your exact domain is now refused.
    6. Keep watching. New services get added over time. Check reports regularly, and before you add a new sender, set up its SPF and DKIM first.

    Protecting your sender reputation

    Authentication proves who you are; reputation decides whether providers want your email. Both matter for reaching the inbox.

    • Separate your streams. Send marketing from one subdomain (for example news.example.com) and transactional email from another (mail.example.com). A complaint-heavy campaign then can’t delay password resets or invoices.
    • Warm up new domains and IP addresses. Start with small volumes to your most engaged recipients and increase gradually over a few weeks.
    • Only email people who asked. Use confirmed opt-in for marketing, never buy lists, and make unsubscribing one click.
    • Remove bounces and inactive recipients. Stop sending to addresses that hard bounce or complain, and stop marketing to people who haven’t opened or clicked in months.
    • Watch your complaint rate. Keep spam complaints below 0.1%, and never let them reach 0.3%. Google Postmaster Tools and Microsoft SNDS show how providers see your domain.
    • Be recognisable. Use a consistent From name and address, avoid link shorteners, and send email people expect. See transactional email template best practices.

    Preventing spam and fraud

    • Enforce DMARC. p=reject is the single most effective step against criminals using your exact domain.
    • Lock down unused domains. For every domain or subdomain that doesn’t send email, publish the records below.
    • Watch for lookalikes. DMARC doesn’t cover lookalike domains such as examp1e.com or example-billing.com. Register obvious variants and monitor new registrations that resemble your brand.
    • Add your logo with BIMI. Once DMARC is at quarantine or reject, BIMI can show your verified logo next to your email in supporting inboxes. Gmail requires a verified mark certificate.
    • Encrypt mail in transit. MTA-STS and TLS reporting make other servers use encrypted connections when sending to you, and tell you when that fails.
    • Don’t put sensitive details in email. Send a notification that links to a secure portal instead. See digital letters.
    • Train your staff to check the real sender address, not just the display name, and to verify payment changes by phone.
    RecordNameValue (TXT)
    SPFparked.example.comv=spf1 -all
    DMARC_dmarc.parked.example.comv=DMARC1; p=reject;

    Add a null MX record (MX 0 .) to show the domain receives no email either.

    Checklist

    1. One SPF record per sending domain, listing every service, under 10 lookups, ending -all or ~all.
    2. DKIM signing with your own domain on every service, using 2048-bit keys, rotated regularly.
    3. A DMARC record with reporting, moved from p=none to p=reject once all genuine mail passes.
    4. Separate subdomains for marketing and transactional email.
    5. One-click unsubscribe, automatic bounce and complaint suppression, and a low complaint rate.
    6. SPF -all, DMARC p=reject and a null MX on every domain that doesn’t send email.
    7. Regular review of DMARC reports and provider reputation dashboards.

    How everymessage helps

    • Authenticated from the first send. Every sending domain on our business email platform is set up with SPF, DKIM and DMARC, and we help you add the records.
    • Reputation protected automatically. Hard bounces, spam complaints and unsubscribes are suppressed, so you don’t keep emailing people who can’t or don’t want to receive it.
    • Email to SMS checks too. Our email to SMS service only accepts mail that passes SPF, and can require DKIM, so nobody can send texts by faking your address.

    Frequently asked questions

    What is the difference between SPF, DKIM and DMARC?

    SPF lists the servers allowed to send email for your domain. DKIM adds a digital signature that proves the message came from your domain and wasn’t changed. DMARC checks that SPF or DKIM passed for the domain in the visible From address, tells inbox providers what to do with mail that fails, and sends you reports.

    Do I need all three?

    Yes. Gmail, Yahoo and Microsoft now expect bulk senders to use SPF, DKIM and DMARC, and each one covers gaps in the others. SPF breaks when email is forwarded, DKIM alone doesn’t tell providers what to do with failures, and DMARC needs at least one of the other two to pass.

    Should my SPF record end in -all or ~all?

    Once DMARC is in place, either works, because DMARC decides what happens to failing mail. -all (hard fail) is the stricter choice when you’re sure every sending service is listed. ~all (soft fail) is safer while you’re still finding services that send for you.

    Will DMARC p=reject stop my own emails?

    Only if a legitimate service sends as your domain without passing aligned SPF or DKIM. That’s why you start with p=none, read the reports for a few weeks, fix every legitimate sender, and only then move to quarantine and reject.

    Does DMARC stop all phishing?

    No. It stops criminals sending email that uses your exact domain. It doesn’t stop lookalike domains, such as examp1e.com, or free email accounts with your company name in the display name. Monitor lookalikes and train staff to check the real sender address.

    What about domains we don’t send email from?

    Protect them too. Publish an SPF record of v=spf1 -all, a DMARC policy of p=reject and a null MX record, so nobody can send convincing email from them.

    Want a second opinion on your email set-up?

    Tell us about your domains and sending services, and we’ll help you get SPF, DKIM and DMARC right.

  • Email to SMS (email to text): how to send texts from your email

    Email to SMS, also called email to text, lets you send a text message from any email account, such as Outlook or Gmail, with no software to install. Write an email, address it to a mobile number at @emsg.me.uk, and we deliver it as an SMS. This guide covers how to address your email, what gets sent, how to keep disclaimers and signatures out of your texts, the account settings that control length and delivery receipts, and how replies come back to your inbox.

    In short: send an email to 07700900123@emsg.me.uk and the message body arrives as a text on that mobile. Your account settings decide whether the subject or the body is sent, how long a message can be, and whether you get a delivery receipt. Send from a two-way mobile number and replies come back to you as emails.

    How it works

    1. Register your email address. Your email address is your everymessage login. We only accept email to SMS from registered addresses, so your credit can’t be used by anyone else.
    2. Address the email to a mobile number. Put the number in front of @emsg.me.uk. Add as many numbers as you need in To, Cc or Bcc.
    3. Write your message. We take the email body (or the subject, if your account is set up that way), remove signatures and quoted replies, and send it as an SMS.
    4. Get receipts and replies by email. Delivery receipts and replies from the mobile come back to your inbox, if your account is set up for them.

    Addressing your email

    The part of the address before the @ is the mobile number. Use digits only. We convert UK numbers to international format for you.

    You send toWe send the SMS toNotes
    07700900123@emsg.me.uk+44 7700 900123UK mobile in national format.
    447700900123@emsg.me.uk+44 7700 900123UK mobile in international format.
    33612345678@emsg.me.uk+33 6 12 34 56 78International: start with the country code. A leading 00 also works.
    sales@emsg.me.ukEvery member of your sales contact groupUse a contact group’s name or email alias from the portal. Members who have unsubscribed are skipped.
    credits@emsg.me.ukNothing is sentWe reply with your account’s remaining credit (pay-as-you-go accounts).
    • Several recipients: add each number as a separate address. To, Cc and Bcc all work, so you can Bcc mobiles without the others seeing them.
    • Other email addresses: you can copy in colleagues on ordinary email addresses. They get the email as normal; only the @emsg.me.uk addresses are sent as texts.
    • Avoid the + sign and spaces in the address. Some email programs change or reject them.

    Body or subject: what gets sent

    By default, the email body becomes the SMS and the subject is ignored. If you’d rather type short messages in the subject line, turn on Use subject as SMS for your account. The subject is then sent, and the body is ignored.

    Use subject as SMS: off (default)Use subject as SMS: on
    Sent as the SMSThe email bodyThe subject line
    Best forLonger messages, and messages sent by business systemsQuick one-line messages from a phone or email client
    Signatures and disclaimersRemoved using the options belowNot an issue: the body isn’t sent
    Maximum lengthSet by your account’s Max segments (see below)

    When we read the body, we:

    • use the plain-text version of the email, or convert HTML email to plain text;
    • stop at the first quoted reply or signature break: a line starting --, -----Original Message-----, On ... wrote:, From:, a line of underscores, or a line starting >;
    • tidy up extra spaces and blank lines.

    Attachments are not sent. For the best results, send plain-text email and keep to standard characters: see SMS character limits for why that matters.

    Choosing the sender

    Your texts come from your account’s default sender, which is a sender name (up to 11 letters and numbers) or one of your mobile numbers. To use a different sender for one message, add sender= at the end of the subject line:

    To07700900123@emsg.me.uk
    SubjectAppointment reminder sender=BRIGHTCARE
    BodyYour appointment is tomorrow at 10:30. Call 01234 567890 to change it.

    Put the sender= token last, because everything after it is read as the sender. The sender must be a name you’re allowed to use, or a number on your account.

    Keeping disclaimers and signatures out of your texts

    Most business email adds a signature or legal disclaimer. Signatures that start with a standard -- line are removed automatically. For anything else, there are two ways to stop it reaching the text.

    1. The Email disclaimer setting

    In the portal, enter the first few words of your disclaimer in Email disclaimer, exactly as they appear in your emails, for example This email is confidential. We cut the message at the first place that text appears, so the disclaimer and everything after it are removed.

    The setting holds up to 50 characters and must be at least 3. Capital letters don’t matter. Enter * or leave it blank for no disclaimer.

    2. Custom end tags

    Wrap your message between #%# and ##. Only the text between the tags is sent, whatever comes before or after it.

    This is the most reliable option when a disclaimer is added by your mail server after you press send, or when an automated system writes the email and you can’t control the rest of the body.

    To07700900123@emsg.me.uk
    Body#%#Your engineer will arrive between 10:00 and 12:00 today.##

    Kind regards,
    Service team
    This email and any attachments are confidential…

    The text above sends only Your engineer will arrive between 10:00 and 12:00 today. Don’t use ## inside the message itself, because the first ## ends it.

    A third option is Use subject as SMS: the body, and any disclaimer in it, isn’t sent at all.

    Account settings for email to SMS

    An administrator sets these for each user in the portal (Users, then Edit).

    SettingWhat it does
    Max segmentsThe longest message the user can send, from 1 to 6 SMS parts. One part holds 160 characters; six joined parts hold 918. A longer message isn’t sent. Keeping this low means a long email thread sent by mistake can’t use up your credit.
    Daily limit (£)The most the user can spend in a day. Messages over the limit are rejected and the sender is told why.
    Email receiptWhen on, every email to SMS message asks for a delivery receipt. When off, you can still ask for one per message by turning on a read receipt (return receipt) in your email client.
    Delivery ruleWhere delivery receipts go: Via Email, Via URL (to your system’s webhook), Via Email & URL, or Collect / Portal (held for you to collect through the API or portal).
    Use subject as SMSSends the email subject instead of the body.
    Email disclaimerThe text at which the email body is cut, to remove a disclaimer.
    OriginatorThe user’s default sender: a sender name, or a two-way mobile number if you want replies.

    Delivery receipt emails

    With the delivery rule set to email, you get an email when the network confirms the outcome. The subject says whether the message was delivered, expired or rejected, and the original message is quoted underneath.

    Each receipt comes from the mobile number itself, for example 447700900123@emsg.me.uk. Reply to the receipt and your reply is sent to that mobile as a new text.

    Replies: SMS back to your email

    People can’t reply to a sender name such as BRIGHTCARE. To have a conversation, send from a two-way mobile number on your account:

    1. Set the user’s Originator to your two-way number, or add sender= with the number to the subject.
    2. Set the number’s Reply handling to Email (or Email & URL, to also send replies to your system).
    3. Replies arrive in your inbox, sent to the email address of the user who sent the original message. Each one comes from the mobile, for example 447700900123@emsg.me.uk, with your original message quoted below.
    4. Reply to the email to answer. Your reply goes back to the mobile as a text. The quoted history in your reply is removed automatically, so only your new words are sent.

    A text that isn’t a reply to a recent message, such as a customer texting your number first, is emailed to the number’s owner with the subject Incoming SMS. You can reply to it in the same way.

    Security

    • Registered senders only. Email from addresses that aren’t registered users is rejected.
    • Checked at the door. Incoming email must pass SPF, and can also be required to pass DKIM, so messages pretending to come from your domain are refused.
    • Spam and viruses are filtered before anything is read. Automatic replies, out-of-office messages and bounces are ignored, so they never become texts.
    • Whole-domain sign-up (optional). Your administrator can let anyone at your company’s email domain send without being added one by one. New senders get your company’s default settings.

    If a message isn’t sent

    We email the sender with the reason. The common ones:

    ReasonWhat to do
    No valid mobile recipientCheck the number before the @: digits only, starting 07, 44 or another country code.
    No group foundCheck the group name or alias in the portal. Groups are per company.
    Message body was emptyEverything was removed as signature or disclaimer, or Use subject as SMS is on and the subject was blank. Check your Email disclaimer setting, or use end tags.
    Insufficient credits / daily limit reachedTop up your account, or ask your administrator about the user’s daily limit.
    Message authentication (DKIM) failedYour company requires DKIM. Ask your email administrator to check DKIM signing for your domain.
    Message too longThe message needs more SMS parts than your Max segments allows. Shorten it, check that a long signature or reply thread isn’t being included, or ask your administrator to raise the limit.

    Frequently asked questions

    Is email to SMS the same as email to text?

    Yes. Email to SMS, email to text and mail to SMS all mean the same thing: you send an email to a mobile number and it arrives as a text message. With everymessage, you address the email to the number at @emsg.me.uk.

    What email address do I send to?

    Put the mobile number in front of @emsg.me.uk, for example 07700900123@emsg.me.uk. You can use UK numbers starting 07 or 447, or any international number starting with its country code.

    Can I send one email to several mobiles?

    Yes. Add each number as its own address in To, Cc or Bcc. Every number receives the same message. You can also send to a contact group by using the group’s name as the address.

    Is the email subject sent?

    Not by default. The message body becomes the SMS. If you turn on Use subject as SMS for your account, the subject line is sent instead and the body is ignored.

    How do I stop my email disclaimer appearing in the text?

    Enter the first words of your disclaimer in the Email disclaimer setting, and everything from that point is removed. Or wrap your message in #%# and ## so only the text between them is sent.

    How do I know my message was delivered?

    Turn on Email receipt for your account, or request a read receipt in your email client. You’ll get an email when the network confirms delivery or failure.

    Can people reply to my texts?

    Yes, if you send from a two-way mobile number on your account and its replies are set to Email. Replies arrive in your inbox, and you answer them by replying to the email.

    Who can send email to SMS?

    Only email addresses registered to your account. Mail from anyone else is rejected, so nobody can spend your credit by sending to our address.

    Start sending texts from email

    We’ll set up your users, sender names and two-way numbers so you can send and receive texts from the email you already use.

  • Royal Mail’s blocked price rise: what it means for your mailings

    Royal Mail’s planned October 2026 increase in bulk mail prices was blocked at the last minute. But postage is still going up: revised prices are due in December, and the final increase isn’t clear yet. Here’s what happened, what it means for your mailings, and how organisations are cutting the volume they need to post.

    In short: Ofcom suspended Royal Mail’s proposed access (bulk) mail price rises in September after a complaint from the industry, and Royal Mail withdrew them on 5 October 2026. Revised, lower increases are now intended for early December. Prices will still rise, so it’s a good time to move to digital-first delivery and post only what you have to.

    What happened

    DateEvent
    23 July 2026Royal Mail notifies access customers of price increases (Contract Change Notice 129), due on 5 October. Reported rises include around 36% for some access business letters and 11 to 12% for some advertising mail.
    4 September 2026Ofcom accepts a dispute from the Mail Competition Forum, acting for 17 access customers, to decide whether the increases are fair and reasonable. The increases are suspended while it does.
    Late September 2026Royal Mail issues revised access prices under a new notice, which it says are lower than the original proposal, intended for early December 2026.
    5 October 2026No increase takes effect. Royal Mail withdraws the original notice and Ofcom closes the dispute.

    Source: Ofcom, Dispute between Mail Competition Forum and Royal Mail.

    Prices will still rise: we’re waiting to see by how much

    The October increase was stopped, not cancelled. The revised prices are still increases, and they could take effect in December unless there are further complaints to Ofcom. How much more any particular mailing will cost depends on the format, weight, service level and how the mail is sorted and presented, so there is no single percentage that applies to everything.

    The dispute only covered access mail, the route most bulk business mail takes. Other Royal Mail services, including stamps, are priced separately.

    We’re reviewing the revised prices as the detail is confirmed and will update our print and post customers on what it means for their mailings. In the meantime, plan for higher postage in 2027 budgets, and book autumn and Christmas mailings early.

    Post less: digital first, paper where needed

    The most reliable way to protect yourself from postage increases is to send less post. A digital-first approach works like this:

    1. Send a secure digital letter. Each customer gets an email or SMS inviting them to view their letter or document online.
    2. Protect the content. The document sits in a secure, branded portal behind two-factor verification, so only the right person can open it.
    3. Track every invite. You see whether each invite was delivered, and whether the document was opened.
    4. Post only the rest. Where an email bounces or an SMS fails, the letter is printed and posted automatically, so everyone still receives it.

    Digital letters arrive in minutes rather than days, cost a fraction of a posted letter, and come with proof of delivery and opening that post can’t give you. Some notices must still go by post, and some customers need paper. A digital-first approach keeps the post for them.

    In practice: two projects from 2025

    A UK council

    The council delivered its customer mailings as secure digital letters. Residents received a link to a branded portal, where each document sat behind two-factor verification. For council billing, residents also confirmed their postcode, a further check before any billing details were shown.

    A finance house

    A finance house needed to send updated terms and conditions to its customers. Every invite was tracked through to delivery, opening or failure. Only the customers whose email or SMS invite failed were sent a printed letter: about 10% of the overall volume. The other 90% received their terms digitally, with a record of delivery.

    Making the post you do send cost less

    • Use bulk mail services, not stamps. Access mail through a mailing partner costs far less per item than a stamp.
    • Qualify for marketing discounts. Mailings planned to Royal Mail’s advertising mail requirements can attract lower postage. Talk to us before you design the mailing.
    • Clean your data. Every letter sent to a wrong or out-of-date address is wasted postage and print.
    • Choose the right format and weight. A small change in size or paper weight can move a mailing into a cheaper price band.

    How everymessage helps

    • Digital letters: secure, branded documents delivered by email or SMS, behind two-factor verification, with tracking from delivery to opening.
    • Print and post: printing, enclosing and postage handled for you, including Royal Mail marketing discounts on mailings that qualify.
    • Automatic fallback: letters are posted only where digital delivery fails, from one platform.
    • Your brand throughout: our AI branding tool styles your forms and documents in your own brand, online and on paper.

    Frequently asked questions

    Did Royal Mail’s October 2026 price rise go ahead?

    No, not for access (bulk business) mail. Ofcom accepted a dispute over the proposed increases on 4 September 2026, which suspended them, and Royal Mail withdrew the notice on 5 October 2026. Revised access prices, which Royal Mail says are lower, are intended to take effect in early December 2026.

    Will postage still go up?

    Almost certainly. The revised access prices are still increases, and other Royal Mail products are priced separately. The size of the rise for any mailing depends on the format, weight, service and sortation used.

    What is access mail?

    Bulk business mail that is collected and sorted by a postal operator or mailing house before being handed to Royal Mail for final delivery. It’s how most large mailings reach a lower price per item than stamps.

    Can every letter be sent digitally instead?

    Not always. Some notices must be sent by post, and some customers prefer or need paper. A digital-first approach sends a secure digital letter where it can be delivered and tracked, and posts a printed copy to everyone else.

    How much post can a digital-first approach save?

    It depends on how complete and accurate your email and mobile data is. In one 2025 project for a finance house, only about 10% of the total volume needed to be printed and posted.

    Find out how much post you could save

    Tell us about your mailings and we’ll show you how a digital-first approach would work for your customers.