Key takeaways
- The word update covers three different mails. A price change, a note that your autumn is nearly full, and a link to something you wrote all travel to different people on different triggers. Bundling them into one monthly send is why clients stop opening.
- Only one of the three lanes belongs on a calendar. Announcements fire when the thing happens, availability news fires when capacity moves, and the reading lane is the one that earns a fixed rhythm.
- An announcement without a date and an action isn't an announcement. Clients need to know what changes, from when, and what they have to do, in the first three lines.
- One issue, one next step. When the next step is a conversation, a booking link does more work than three links of equal weight, because the reader never has to choose.
Most newsletter updates get judged on one number, the open rate, and that number hides the problem. The word update covers three mails that behave nothing alike: a price change your clients are affected by whether they open it or not, a note that your September is nearly booked out, and a link to a piece you wrote. Different audiences, different triggers, different consequences for being missed.
Sorting them before you write is what separates a client newsletter that gets read from one that gets archived. What follows is that sort: what belongs in each lane, how to pick what makes this issue, how often each lane should fire, and how to close an update with a single next step.
The three lanes a client newsletter carries
Every update you'd ever send a client fits one of three lanes. The lane decides the audience, the timing and the tone, which is why picking it first saves you the usual argument about whether something is "newsletter-worthy".
Announcements that have to land
Price changes, new opening hours, a holiday closure, a policy change, a team member leaving, a service you're retiring. These are the mails where being unread is a real cost: the client turns up on a day you're closed, or sees a higher invoice they never agreed to.
Two consequences follow. First, an announcement gets its own send, not a slot in the monthly roundup. Second, it reads differently: what changes, from when, and what the client needs to do, inside the first three lines. Everything else goes below.
Announcements also sit in a different place legally and technically than your reading lane. Google's email sender guidelines require one-click unsubscribe on marketing and promotional mail and exclude transactional messages from that rule. A note telling an existing client their rate changes in 30 days is closer to the second category than the first, and treating it as a campaign is what gets it filed with the campaigns.
Availability, capacity and scheduling news
This lane is underused by service businesses and it's the one clients act on fastest. You've opened January slots. Two Thursday afternoons came free after a cancellation. You're away for three weeks in August. A second consultant has joined and the waiting time dropped from four weeks to one.
The audience here is narrower than your full list, which is the point. A message about Tuesday morning slots is relevant to the clients who book Tuesday mornings. If you're closing for a period, the out of office setting should reflect it before the mail goes out, so a reader who clicks through doesn't book a slot you're not there for.
Useful reading, the part clients tolerate
Tips, a short case study, an explanation of something you keep getting asked, an industry change that affects them. This is the lane most advice about newsletters is really about, and it's the only one with no deadline attached.
That makes it the filler, in the good sense. It's what keeps a monthly send from being empty in a month when nothing changed. It's also the lane where the honest failure rate is highest, so keep it short and keep it specific to work you actually did.
A four-question test for what goes in this issue
Before anything goes into a draft, answer four questions about it. If you can't, it isn't ready, and you'll find that out faster here than after the send.
- Who is affected? Not "the list". Name the group: clients on the old rate, clients who book in-person, everyone with an appointment in the next three weeks. If the answer really is everyone, say so deliberately rather than by default.
- What changes, and from when? A date turns an announcement into something a client can act on. Without one you'll get replies asking for it, which costs you more time than writing it did.
- What does the reader have to do? Nothing is a valid answer, and saying it explicitly ("no action needed, your existing bookings are unaffected") prevents a wave of worried replies.
- What happens if they never open it? This is the question that sorts the lanes. If the answer is a surprise invoice or a wasted trip, it's an announcement and needs its own send. If the answer is nothing much, it can wait for the monthly issue.
The fourth question is the one worth arguing about internally. A lot of service businesses discover that half of what they'd planned to announce has no consequence at all, which is a useful thing to learn before writing 400 words about it.
Cadence: only one lane belongs on a schedule
Announcements fire when the thing happens, minus the notice period. Availability news fires when capacity moves. The reading lane is the only one that earns a fixed rhythm, and monthly is the honest default for most service businesses, because that's roughly how often something worth reading actually accumulates.
Notice periods are where announcements go wrong most often. A 10-comment discussion in r/petsitting on how much notice to give before a rate increase converges on at least 30 days and a mail that states the old rate, the new rate and the effective date plainly. A 70-comment thread in r/smallbusiness on explaining a price increase pushes in the same direction: the long apologetic justification reads worse than the short factual one, and the clients who leave were usually going to leave.
For the reading lane, the frequency debate is mostly a proxy for a content problem. In a recent 10-comment thread in r/Emailmarketing on keeping a client list warm, the practical advice is to start slower than you think and let the archive prove you can sustain it. Monthly that you keep is worth more than weekly you abandon in March.
One rule holds across all three lanes: never let an announcement wait for the newsletter date. If the price changes on 1 November, the mail goes out on 1 October, not in the issue scheduled for the 20th.
Give every update one next step
A client update with four links of equal weight gets no clicks, because a reader who has to choose usually chooses nothing. Pick the one action the issue is for and make everything else plain text.
When the next step is a conversation, a booking link beats "reply to this email" by a wide margin, because reply-to-book costs the client two messages and you a scheduling thread. An annual review invitation is the clearest case: one paragraph on why now, one button to pick a time, nothing else. The same applies to a capacity announcement, where the button is the point of the mail.
If you don't have a page to point at yet, build it before the content calendar. Our guide to creating a booking page that converts covers what belongs on it, and adding it to your website makes it reusable outside the newsletter. A personal booking link is enough to start with.
Two things that are not the next step: the unsubscribe link, which belongs in the footer and stays easy to find, and a reminder about an existing appointment, which should be an automated appointment reminder rather than newsletter content.
Sending updates without keeping a second contact list
Most service businesses run this from a standalone email tool, with Mailchimp and Brevo the common starting points, and the contacts copied over from wherever they actually live. That import is the tax: consent recorded in one system, bookings in another, and a segment that's out of date the week after you built it. Our comparison of email marketing tools covers that category on its own terms.
The alternative is sending from the system that already holds the contacts. The meetergo Newsletter app is built that way: there's no separate subscriber list, every contact in the CRM with an email address can receive a campaign, and the tags written by bookings, imports and forms are the segmentation. Audiences come from 16 filter fields, including tag, language, country, consent and whether someone opened or clicked an earlier campaign, so "clients who haven't clicked the event invite" is a filter rather than a spreadsheet.
Three details matter for the announcement lane specifically. Campaigns leave through your own SMTP mailbox, so the mail comes from your address and your domain reputation stays yours. Consent is checked on every individual send against the record on the contact, and the rule applied is stored per send. And sequences start from a tag, so a form submission can trigger a welcome series without a separate automation tool in between. The same workflow engine handles confirmations and reminders around bookings.
The honest limitation: Newsletter is in beta and unlocked per workspace, so a workspace admin has to request access from the in-app catalog rather than switching it on themselves, and the plan assignment is set at launch rather than now. Campaigns cap at 20,000 contacts and 200 mails per hour by default, which means a large send runs over a few hours instead of landing at once. And opens are an estimate in any tool, so build your next audience on clicks.
Common mistakes
Putting the price change in the monthly roundup. It gets the roundup's open rate, which is not the open rate an announcement needs. Send it separately, then mention it once more in the next issue.
Sending campaigns from the same domain as your invoices. One badly targeted send can damage the reputation your booking confirmations depend on. A subdomain such as news.your-company.com keeps the two apart.
Announcing a change without a date. "We're updating our rates soon" produces replies, not acceptance. Give the effective date and the old and new figures.
Treating a newsletter unsubscribe as a blanket opt-out. Someone who leaves the reading lane still needs their appointment confirmations and their policy changes. Keep operational mail separate, and if your cancellation policy changes, that reaches everyone.
Writing the issue before deciding who it's for. Content assembled first tends to end with several links of equal weight and no clear audience. The four-question test takes two minutes and saves the draft.
Create a free meetergo booking page and make it the one button in your next client update. No credit card required.
Booking + video conferencing in one tool.
Booking + video conferencing in one tool.
FAQs
Do I need consent to email existing clients about a service change?
Operational mail to an existing client about the service they're buying sits on different ground than promotional mail, but the line is jurisdiction-specific and worth checking for yours. The practical rule: keep the announcement factual and free of offers, and it stays an announcement. Add a promotion to it and you've turned it into marketing.
How long should a client update be?
Short enough to read on a phone without scrolling twice. For announcements, three lines carry the substance and the rest is context. For the reading lane, aim for something a client finishes in under two minutes.
What do I send when nothing has changed?
Skip the send, or send the reading lane alone. An issue padded to fill a slot trains clients that yours isn't worth opening, and that habit is expensive to reverse. The electronic newsletter guide covers how to build a content stock so this happens less often.
Should availability news go to the whole list?
No. Filter to the people it applies to, by service, location or booking history. A full-list send about two free Thursday slots teaches most of your list that your mails aren't about them.
How do I get people onto the list in the first place?
A form at the point where the client is already dealing with you, with a line that says what arrives and how often. Our piece on newsletter signup calls to action has the wording that works better than "sign up to our newsletter".
Can the same tool send both the newsletter and my booking reminders?
Yes, and there's an argument for it: the reminder and the campaign then read the same contact record, so someone who cancelled last week doesn't get an invitation to book. Reminder emails and campaigns are different mails with different rules, but they don't need different contact lists.
What if my capacity is the constraint rather than demand?
Then the announcement lane is mostly about setting expectations, and a waitlist does more for you than a campaign. Tell clients the current waiting time and let them queue rather than chase.
