Author: Dan Birchmore

  • Notifying every customer: a digital-first letter process for terms, billing and account changes

    Some letters have to reach every customer: a change to your terms and conditions, a new price or billing arrangement, a different payment date, or news that the business has been acquired or renamed. Posting them to your whole customer base is slow and expensive, and tells you nothing about who read them. This guide sets out a digital-first process, based on the approach we use with financial services clients, that reaches every customer, proves it, and posts letters only where it has to.

    In short: create one letter per customer, invite each customer by SMS and email to read it on a secure, branded portal after a simple identity check, and automatically print and post the same letter to anyone who isn’t reached or doesn’t read it. Make the message easy to recognise as genuine, release it in batches, and use the results to clean your contact data for next time.

    1
    Step 1Invite

    The customer receives a branded SMS and/or email saying an important letter about their account is ready, with a personal link.

    2
    Step 2Verify

    They confirm details you already hold, such as their account number and postcode. No app, account or password needed.

    3
    Step 3Collect

    They read and download the letter on a secure portal with your branding, at your own web address.

    4
    Step 4Track & follow up

    Every step is recorded. Letters not viewed trigger a reminder, then are printed and posted automatically.

    Notifications that must reach everyone

    The same process works for any letter you need to send to a large part of your customer base:

    NotificationTypical content
    Terms and conditions changeWhat’s changing, when it takes effect, and the customer’s options if they don’t agree
    Price or billing changeNew prices, charges or billing frequency, and the date they apply from
    Payment changeA new payment date, Direct Debit details or collection arrangements
    Acquisition, merger or rebrandWho the customer now deals with, and reassurance that their account carries on
    Annual and regulatory noticesStatements, summaries and notices you’re required to send each year
    Service changesBranch or office closures, new contact details, changes to how accounts are managed

    Why these letters need care

    • You need proof. Many changes must be notified a set time in advance, and you may later need to show that each customer was told. Post gives you no evidence unless it’s tracked or signed for.
    • Customers need clarity. Most will want to know one thing: does this affect me, and do I need to do anything? The letter should answer that clearly.
    • Links can look like scams. An unexpected message asking customers to tap a link and confirm who they are can look like phishing, so how you send it matters.
    • Post is slow and costly at volume. Printing and posting to everyone takes days and costs the most per letter, with no idea who opened it.
    • It’s a chance to go digital. A letter every customer receives is the ideal moment to confirm mobile numbers and email addresses for the communications that follow.

    The process, step by step

    1. Prepare the letters. Your systems create a personalised, print-ready PDF for each customer and hand it over through secure shared storage or an API, with a record listing each customer’s contact details and the details used to verify them.
    2. Choose the channels for each customer. The platform checks what you hold. Customers with a mobile number or email address get a digital invite; anyone with neither goes straight to print.
    3. Send the invites together. Where you hold both, the SMS and the branded email go out at the same time, each with a personal link. Sending both at once gives the best chance of the letter being read quickly.
    4. The customer verifies and reads. The link opens a branded portal on your own web address. The customer confirms details they already know, such as their account number and postcode, then views or downloads the letter. No app, account or password is needed.
    5. Remind, then post. If the letter hasn’t been viewed after an agreed number of days, an optional reminder goes out. If it’s still not viewed, or neither invite could be delivered, the same PDF is printed and posted automatically.
    6. Report every step. Each delivery, click, identity check, view, download and posting is recorded and sent back to your systems in real time, or as reports, giving you evidence for every customer.
    A customer views the everymessage secure portal on their phone, with a button to view an important document
    The customer’s view: a branded portal, no app needed.

    The decision flow

    Digital-first notification flowLetters and records are received. Customers with a mobile or email get an SMS and email with a personal link. If neither is delivered, or no contact details are held, the letter is printed and posted. Otherwise the platform waits, with an optional reminder; if the letter is viewed the journey ends digitally, if not the same letter is printed and posted.Letters and records receivedCheck the contact details heldMobile or emailheld?NoYesSMS with personal linkEmail with personal linkDelivered on atleast one channel?NoYesWait an agreed number of days(optional reminder)Letter viewed?NoPrint and post thesame letterYesViewed digitallyPrinted and posted
    Every customer ends in one of two places: letter viewed digitally, or printed and posted. Both are reported.

    Digital letter, email attachment or post?

    Posted letterEmail attachmentDigital letter
    CostPrint, envelope and postage for every letterLowLow; print and postage only for letters that revert to post
    SpeedDaysSecondsSeconds
    SecurityCan be lost or opened by someone elseCan be forwarded or interceptedReleased only after an identity check
    ProofNone, unless tracked or signed forLimitedDelivered, opened, verified and downloaded, all recorded
    If it isn’t readYou don’t knowYou don’t knowAutomatic reminder, then a printed letter

    Making sure it’s recognised as genuine

    This decides whether customers engage. Plan it with your brand and compliance teams:

    • Use the name customers know. If the business has been acquired or renamed, co-brand during the transition, for example “Old Brand, now part of New Brand”, in the SMS, the email and on the portal.
    • Use a recognisable sender. A clear SMS sender name and email display name. Generic names such as “Verify” or “Alert” are blocked by UK networks anyway: see UK SMS sender ID rules. Consider registering your sender name with the UK SMS SenderID Protection Registry so it can’t be spoofed.
    • Authenticate your email. Send from a dedicated subdomain of your own domain, set up with SPF, DKIM and DMARC: see SPF, DKIM and DMARC explained.
    • Put a notice on your website. Tell customers the letter is coming, what it will look like and how to check it’s genuine.
    • Never ask for anything sensitive. No bank details, passwords or payments in the message, and identity checks only on information the customer already knows.

    Running it smoothly

    • Work back from the notice date. Start early enough for the whole cycle, including reminders and any letters that revert to post, to finish within the notice period you need to give.
    • Release in batches. Spread the sends over several days, so calls and messages from customers arrive at a pace your contact centre can handle. Outbound sending can be paused at any time if inbound contact spikes.
    • Send a reminder before posting. One reminder to customers who haven’t read the letter lifts digital uptake and reduces the number of letters printed.
    • Fix contact data as you go. Failed texts and bounced emails are reported back, so you can correct contact details before the next notification.
    • Test with your own team first. Send to a seed list of staff phones and inboxes to check the wording, links, identity check and letter before customers see anything.

    What you’ll need to set up

    ItemWhat’s involved
    Portal addressA subdomain of your own website for the secure portal, with an SSL certificate, so customers see your name in the address bar.
    Email sending domainA dedicated subdomain for sending, with SPF, DKIM and DMARC records added to your DNS.
    BrandingLogos, colours and approved wording for the email, SMS and portal.
    Identity checkThe details customers will confirm, such as account number, postcode or date of birth, supplied with each record.
    LettersOne print-ready PDF per customer, uniquely named, unprotected (the portal controls access) and laid out for a window envelope, so the same file works online and in the post.
    Hand-overA record file uploaded to secure shared storage, or an API call from your systems.
    RulesHow many days before a reminder and before posting, the batch schedule, and how long data is kept.

    With those agreed, a first project typically runs in a few weeks: set-up, building the templates and workflow, testing with your seed list, then a phased go-live.

    One set-up, every notification

    The portal, domains, branding and integration you set up for the first notification can be reused for every one after it, adding only new templates and rules. The same platform also sends simpler messages that don’t need the portal:

    Digital letterSimple branded email or SMS
    Best forTerms and price changes, statements, notices of change, arrears and collections letters, important account documentsService updates, contact detail changes, reminders, general news
    How it’s readOn the secure portal, after an identity checkIn the message itself
    ChannelsSMS and email, with automatic fallback to postEmail or SMS
    TrackingFrom invite to viewed, downloaded or postedDelivered, bounced, opened and clicked

    Every mobile number and email address confirmed along the way increases the share of later letters that can be delivered digitally, so the savings grow with each notification. See how one 2025 project cut posted letters to about a tenth of the total in our article on digital-first mail.

    Frequently asked questions

    What is the best way to notify all customers of a change?

    Send each customer a personal letter that explains what is changing, when, and whether they need to do anything. Deliver it digitally first, by SMS and email with a secure link, and post it only to customers who can’t be reached digitally or don’t read it within an agreed time.

    Can terms and conditions or price changes be notified digitally?

    In many cases, yes, provided the customer can easily read, download and keep the notice and you can show it was delivered. Check the rules that apply to your sector and your existing terms, and keep post as the fallback for anyone who isn’t reached digitally.

    Why not just email the letter as an attachment?

    Attachments can be forwarded, intercepted or opened by the wrong person, and you can’t see whether they were read. A digital letter is released only after the customer verifies their identity, and every step is tracked.

    What happens to customers who don’t open the digital letter?

    After an agreed number of days, and optionally a reminder, the same letter is printed and posted automatically. Every customer is reached, and you have a record of whether each letter was viewed online or posted.

    Won’t customers think the message is a scam?

    Some might, so make it recognisable: use the brand name customers know, a familiar SMS sender name and email display name, a notice on your website, and never ask for bank details or passwords. Identity checks should only use information the customer already knows.

    Do customers need an app or an account?

    No. They tap a personal link, confirm a couple of details they already know, such as their account number and postcode, and view or download the letter.

    Need to notify all your customers?

    Tell us what you need to send and to whom, and we’ll show you how a digital-first letter would work for your customers.

  • UK SMS sender ID rules: why generic names like Verify and OTP are blocked

    The sender ID is the name or number a text message appears to come from. In the UK, generic sender IDs such as Verify, OTP or Delivery are blocked by the mobile networks, because scammers use them to look official. This guide explains which sender IDs are restricted and why, what to use instead, and how the everymessage platform checks sender IDs when your account is set up, so a blocked name can’t become the sender your messages go out with.

    In short: use your own brand name as your sender ID, up to 11 characters, or a mobile number if customers need to reply. Generic words and other organisations’ names are blocked by UK networks. everymessage won’t let a restricted or over-length sender ID be saved, so you find out at set-up, not when messages fail.

    Why generic sender IDs are blocked

    Text message scams, often called smishing, rely on looking official. A message from Verify or Delivery is easy to trust and says nothing about who really sent it. To make that harder, BT and EE began blocking a list of generic sender IDs on 10 July 2023, including spelling tricks such as V3RIFY or V_ERIFY. They also protect the names of well-known brands and public bodies, so only those organisations, or senders they authorise, can use them.

    The direction of travel is clear: in October 2025 Ofcom consulted on further guidance asking providers to check who their customers are and to stop scam messages, including the misuse of sender IDs. Sender IDs are expected to identify a real, accountable organisation.

    Which sender IDs are restricted?

    There are two kinds of restricted sender ID.

    Generic terms

    Words that describe a type of message rather than a sender. Some examples:

    OTP 2FA Verify Code Login Secure Alert Info SMS Bank Payment Refund Delivery Parcel Tracking Reminder Appointment Support Update NoReply

    Protected names

    Names and abbreviations of well-known organisations, such as banks, delivery companies, tax and benefits services, government departments and major brands. They can only be used by that organisation or someone it authorises.

    Our list holds over 190 restricted terms, based on UK network guidance, and we update it as the networks change their rules.

    What to use instead

    Instead ofUseWhy
    OTP or VerifyBrightCareYour customers know who sent the code, and it’s delivered.
    DeliveryBrightShopThe brand they ordered from.
    ReminderBrightDentRecognisable, and harder for scammers to copy.
    NoReplyA mobile numberIf replies matter, send from a number customers can text back.
    • Up to 11 characters for a name. Letters, numbers, full stop, hyphen, underscore, space and ampersand only.
    • Your brand, not a description. Names that combine a generic word with your brand can still be filtered, so your brand name on its own is safest.
    • No look-alikes. Swapping letters for numbers or adding punctuation to get round the rules is treated as an attempt to evade them.
    • A number for two-way. Customers can’t reply to a name. Use a mobile number when you want replies, for example to confirm appointments.
    • Protect your brand. If your name is a target for scammers, consider the UK SMS SenderID Protection Registry, which blocks unauthorised senders using it.

    How everymessage controls sender IDs at set-up

    A sender ID is set when a company or user is created or edited, in the portal or through our admin API. We check it there and then, so problems show up immediately instead of as failed messages later.

    1. Restricted terms are refused. The company default sender, the passcode (OTP) sender and each user’s sender are checked against our restricted list when they’re saved. Capital letters don’t matter: verify, Verify and VERIFY are all refused, with a message explaining why.
    2. Over-length names are refused. An alphanumeric sender ID longer than 11 characters can’t be saved. Networks would cut it short, so the name customers saw wouldn’t match the one you chose. We’d rather tell you than shorten it quietly.
    3. Numbers are tidied when you send. If your sender is a mobile number, stray spaces and a leading + are removed before the message goes out, so the number customers see, and reply to, is exactly the one on your account.
    4. The list is kept up to date centrally. Our administrators maintain the restricted list as network rules change, and changes apply the next time a sender ID is saved, across every account.
    5. Resellers are covered too. The same checks apply when a reseller sets up customer accounts, so restricted names can’t be configured anywhere on the platform.

    If you set a different sender for an individual message through the API, the same network rules apply. Use your brand name or one of your numbers, and avoid generic terms.

    Frequently asked questions

    Why was my SMS sender ID rejected?

    If it’s a generic word such as Verify, OTP, Alert, Info or Delivery, UK networks block it to stop scammers impersonating real organisations, so everymessage won’t let you save it. Use your brand name instead.

    Can I add my brand to a generic word, such as BrandOTP?

    Networks look for generic terms and their variations, so the safest choice is your brand name on its own. A sender ID should clearly identify your organisation without relying on a generic word.

    How long can a UK SMS sender ID be?

    An alphanumeric sender ID can be up to 11 characters. A numeric sender, such as a mobile number, can be longer. Customers can only reply to a number, not to a name.

    Which characters can a sender ID use?

    Letters, numbers and a small set of punctuation: full stop, hyphen, underscore, space and ampersand. Avoid look-alike spellings, such as replacing letters with numbers, which networks treat as attempts to get round the rules.

    Can I use a bank’s or government department’s name as my sender ID?

    Only if you’re that organisation, or are authorised by it. Well-known brand and public-sector names are protected, and messages using them without permission are blocked. Contact us if you need to use one.

    Do I need to register a sender ID in the UK?

    Not with the networks, but you should only use a name you have the right to use. Brands that are often impersonated can also join the UK SMS SenderID Protection Registry, so messages using their name from unauthorised senders are blocked.

    Need help choosing a sender ID?

    We’ll help you pick a sender name that’s recognisable and delivered, and set up a mobile number if you need replies.