Crafting a better work experience

At Missive, we're not fans of meetings. However, we’ve just started doing all-hands, few times a year, to keep in sync.

The idea is, prior to each, I send a written memo about our vision, challenges, strategies, and roadmap – a snapshot of our current status.

After writing the first one, I decided why not share it with our customers. Here it is, memo numero uno.

👋 Hello team,

Things have changed a lot in the last few months for us at Missive. It's important that we all share a common understanding of our journey, our goals, and the path ahead.

Instead of lengthy all-hands meetings where only I talk, I'll capture our vision, challenges, strategies, and roadmap in writing first so you can participate and ask questions.

I wrote each section of this memo to convey specific insights or updates, designed for clarity and brevity. While some sections are brief, each is important. Feel free to engage with each part as it resonates with your role and interests, but I encourage a thorough read to grasp the full picture of where we stand and where we're headed.

On origins

In 2013, Rafael, Etienne, and I started working together on a product called ConferenceBadge, a simple name badge designing tool for event organizers. The product quickly gained traction, allowing us to work full-time on it. However, early on, regardless of sales increasing, we decided that was not what we wanted to do with most of our time.

We wanted to work on a more ambitious project, Missive. The initial idea, devised by Etienne, was: Could we create a collaborative email draft editor? This idea quickly morphed into the first Missive prototype, a full-fledged collaborative email client merged with team chat.

From its inception, Missive was a bold move. By rejecting a safe path for something more ambitious — discarding a successful, revenue-generating, bootstrapped product like ConferenceBadge to work on an unproven idea — many called us crazy.

There, I see two guiding principles, which I think we all should keep and apply forward:

1. Level up: Build a foundation, a quick win, something achievable with your current means/skills. Then use this as a foundation to propel yourself to the next level.
2. Long-term thinking: Do not limit yourself or your ambitions to your current situation, think long-term where you want to be, and start acting now.

ConferenceBadge was our foundation, it gave us the means and de-risked our path to working on a product normally built by teams massively funded.

On our long journey

For much of Missive's history, we were a small team of three, ruthlessly prioritizing listening to and delighting our customers.

Our process to decide what to work on next was simple: do customer support ourselves and set out to improve some of the bigger pains our customers were experiencing at that moment. This shows on our changelog, a long list of incremental improvements.

This process worked magically at first, we could fix issues at a speed unmatched by our competitors and ship innovative features at a blistering pace.

After 8 years and more than 3500 paid customers, it started to show its limitations. As we've grown, so has our to-do list. Not too long ago, I found myself knee-deep in customer support, with Rafael and Etienne tackling bug reports that seemed to multiply overnight.

The three of us, juggling everything, had become too big of a liability. We didn't have enough time to do anything meaningful.

Working on a project like Missive can be extremely satisfying when you have the space and time to experiment. Lately, we were more and more heads down, just trying to make things work.

After a couple of attempts at scaling the team unsuccessfully, we were exhausted.

Then, on a rainy November day at a microbrewery near the office, we each took turns, Rafael, Etienne, and I, discussing what we wanted and where we wanted to go. What transpired was that we were absolutely not exhausted from working on Missive, but mostly we were exhausted from doing it alone. On that day, we laid down a plan.

1. Hire someone to help us hire. (Janie)
2. Move from our gloomy shared office to a nice HQ. (in construction…)
3. Hire someone to help us with customer support. (Philippe, Luis)
4. Hire experienced developers. (Louis-Michel, Grzegorz, Denys)
5. Hire a talented designer. (Arnaud)

Fast forward 5 months later and I believe we are on track. The team has grown, each of you brings something unique to the table, be it from past collaborations, as a customer, or through your work experiences. Your fresh perspectives and skills are exactly what Missive needs to leap forward. With more hands on deck, we're not just looking to distribute the workload; we're aiming to multiply our capabilities.

I’m confident in saying we are extremely talented and we have what it takes to make a big impact.

I personally set a high bar for ourselves, aspiring to be mentioned in the same breath as Notion and Linear; products known not just for their utility but for their innovative edge and the quality of their user experience.

We were a tiny team, now that we are a bit bigger, we are still going to punch far above our weight.

On mission

We have the ambition of being a meeting-less culture, that’s even why some of you were interested to apply to a job at Missive. Now to be meeting-less, there's a requirement, we need alignment, we need to agree on where we are going. To that effect I wrote this mission statement:

We are toolmakers. Our tools improve communication by breaking silos and ease collaboration. They are built for teams having an outsized impact on the world, like us.

Toolmakers love their craft. They are obsessed with the end result. They build in service of others. They don’t get lost in convoluted processes. They are always focused on creating the best possible product, in the end it’s the only thing that matters.

Missive 3.0

With more time to think, one of our goals this year is to redefine what Missive is. Aiming to make it not just a shared inbox app but a platform that helps small and medium-sized businesses plan around all the work that revolves around their communications.

This is how we’ve been using Missive at Missive for years now. But it’s not just us, our hubris, it’s also what our most fanatic users have wanted for years:

Etienne and Arnaud will spearhead this project and work together on UI improvements and improvements around task management.

Let me give you an example, a freight transportation broker using Missive will exchange hundreds of emails a day with businesses wanting to deliver parcels.

From these emails, hundreds of tasks need to be completed by different people. Currently, such a customer might use the basic task functionality in Missive to achieve this, but it's not an ideal experience.

They are most likely to fall back on using a platform like ClickUp or Asana to manage those tasks, alongside Missive. The feedback we've consistently received is clear: such users would prefer a seamless experience within Missive, where task management is integrated directly into the communication flow. The current task's implementation is too simplistic and conversation-centric. Once tasks are created, they are lost in the sea of conversations and there is no accountability possible.

I believe there's a significant market opportunity here, as virtually every business that relies heavily on daily communication via email or any other text communication channels could benefit from such a built-in way to manage tasks around communication.

We need to make this vision a reality on the product side but also to clearly articulate this via our brand and our different marketing initiatives. This will set us apart from traditional help desks.

On AI

AI is on everyone’s radar; it’s the new hot thing. To me, it would be a mistake to market ourselves as an AI product or define all of our roadmap around it. Of course, short-term it would be great, free media and a lot of attention. But long term all products will have AI built-in. This won’t be a differentiator at all. There is no moat in AI.

Now, I’m not saying it's not important, it is, what I’m trying to articulate it’s that AI should not be the main part of our DNA. We will experiment with it, we will create buzz with it, it’s just not what will set us apart.

On collaboration

As I wrote before, we were a small team, for a long time. We know we’ve developed ways of working that are not compatible with collaborating with more people. With the help of Louis-Michel, Denys and Greg on the tech side of things, we already started changing some of our practices.

I expect you, the new team members, to teach us, the original three, how to work and collaborate in a bigger team. But I expect us to teach you how to be mighty efficient. This will create tensions, it’s good and expected.

As toolmakers, our goal is to create the best product, not implement the best processes. The processes are only good if they help us achieve the best product.

On growth

Growth is the consequence of a great product. There is no shortcut. Any growth initiative should be about putting fuel on an already strong fire.

Historically, growth has been around 2%-6% month over month. We always had a solid stream of new inbound users.

This nice consistent growth, hides a darker reality, for every new users and existing ones who grow with us (seat expansion) we have a lot of users who churn, and usually, after a short period of time.

In this graphic, subscriptions = paid organizations. Above purple is good, orange is bad.

To increase our growth rate we need to work on that orange part and better nurture our inbound users. The recipe is simple:

1. Better product (make it simple, reduce the confusion)
2. Better support
3. Better documentation
4. Better onboarding
5. Yearly plan
6. Impactful brand/marketing
7. Better product metrics

We need to be more deliberate and eloquent about what Missive is by simplifying the product and the message.

On our changelog

I got curious writing this memo and parsed the data from our changelog and generated a graph showing the number of release elements either tagged as New, Improved or Fixed per quarter over the years.

The trends of both New and Improved features are decreasing faster than the Fixed one. With more and more technical debt and customers to care for, a tiny team can’t forever beat the odds.

On our tool stack

We use Missive, more than anything else, even when it’s not the best fit. We stick to it, we live with its weaknesses… then we improve it. This experience is our fuel; it guides us into creating a better product from a first hand experience.

We avoid using too many tools. Having a simple stack has more advantages than using the perfect tool for every job. The cognitive cost of learning and maintaining many platforms is high. Let’s not fall into this trap.

On the upcoming price increase

On Feb 28th, we announced a price increase. One goal is to make monthly plans more expensive and attract more customers to the new yearly plans.

The announcement email was sent to all ~6k+ admins and owners of paying organizations. We received 124 replies, with 34% neutral, 40% positive, and 26% negative, but none were hyper-negative. So technically, only 0.25% of users replied negatively, which is not bad.

Most of the replies inquired about the possibility of getting their grandfathered seats rolled up into a yearly subscription with a 20% discount. Originally, it was decided that if you upgraded to a yearly subscription, you would move to the new pricing. We decided it would be fair game not to do so. This change allowed me to reply with the following message, to which most responded extremely positively.

I expect to see a lot of customers switching to the yearly subscription next April and May.

On competitors

Who are our competitors? Missive being a pretty general email/collaboration solution, there are a lot of them. From Front to Spark, Superhuman and even to Intercom and Slack.

Should we care? No, we should always refrain from being obsessed with one or listen to only people who switched over to Missive from one of them. We are not copy cats chasing a space with a discounted product.

A lot of our users come from Front, just search for Front on this page to see. Because of this there are strong demands for us to implement their exact feature set. We sometimes do but most of the time we don’t.

We need to find our way.

――――

The end. That's it, this is the starting point, what are we going to achieve together? See you all, tomorrow, at the 🙌 all-hands!

Philippe Lehoux

‍

An auto-reply email is a pre-written message your email client sends automatically when someone emails you, usually to let them know you’re out of office, to confirm receipt of a support request, or to acknowledge a business inquiry. Below are seven proven templates for the most common situations, plus the steps to set them up in Missive, Gmail, and Outlook.

Emails take up more than a quarter of the average workweek, so it makes sense that people dread coming back from vacation to a full inbox. A good auto-reply sets expectations for the sender, tells them who to contact in the meantime, and buys you a little breathing room when you’re back.

The catch is writing one that doesn’t make you look unreachable, confused, or unprofessional. Nobody wants an auto-reply like this one that said she might never answer, or the classic example where one auto-reply replied to another auto-reply in an infinite loop.

This guide covers what an auto-reply is, seven ready-to-use templates for different situations, and step-by-step setup instructions for Missive, Gmail, and Outlook.

What is an automatic email reply?

An automatic email reply (sometimes called an out-of-office reply, autoresponder, or canned response) is a message your email client sends on your behalf when an incoming message meets certain conditions. Common triggers:

• Time-based: dates you’re away on vacation, leave, or at a conference.
• Sender-based: emails from specific addresses, like a job applications inbox.
• Content-based: emails with certain subject lines or keywords, often used for support ticket confirmations.

Most email clients support auto-replies natively. Missive, Gmail, and Outlook all handle the basics, though each has different strengths, which you’ll see in the setup sections below.

7 auto-reply email examples for every situation

Each of these templates uses Missive’s variable syntax to auto-fill the recipient’s name and other details. If you’re not using Missive, just replace the curly-brace variables with plain text.

1. Out-of-office auto-reply (general template)

Whether you’re on vacation, a local holiday, or taking time off for family reasons, this template works for any out-of-office situation. The {{ user.status }} variable pulls in your current Missive status automatically, so one template covers every occasion.

2. Out-of-office auto-reply for maternity or paternity leave

A longer leave needs a longer-horizon reply. Give a clear date range, point to a reliable backup contact, and set expectations about whether you’ll check email at all during the leave.

3. Auto-reply for someone no longer with the company

When someone leaves, their inbox doesn’t stop receiving emails. A well-written auto-reply redirects the sender to the right person and keeps the door open for future business.

4. Out-of-office reply with an alternative contact method

If your email isn’t the best way to reach you for urgent matters, this template gives senders a backup channel (phone, text, or a teammate) without inviting every non-urgent sender to call.

5. New support request auto-reply

Customer support is the most common use case for auto-replies. An instant “we got your message” acknowledgment goes a long way toward reducing anxiety and cutting down on duplicate follow-ups from the same person.

6. General business inquiry auto-reply

For info@ or contact@ inboxes, a quick auto-reply confirms the message landed and sets a response expectation. This prevents the sender from assuming their email got lost and emailing three more times.

7. Job application auto-reply

Candidates often apply to dozens of roles at once and have no idea whether their application was received. A simple acknowledgment with a realistic timeline respects their time and reflects well on your company.

How to write a professional auto-reply

The seven templates above cover most situations. When you’re writing your own, keep these principles in mind.

• Keep it short. The sender should know three things within a few seconds: (1) why you’re not replying right now, (2) how long they should expect to wait, and (3) who to contact if it’s urgent. Anything beyond that is fluff.
• Stay professional. You don’t need to explain why you’re away or where you’re going. “Out of office” is enough. Avoid detailed stories about the vacation you’re on or the medical situation you’re dealing with.
• Warn the person you’re redirecting to. Before naming a coworker as the backup contact, make sure they know they’re the backup contact. Surprise coverage duties breed resentment.
• Be explicit about the alternative. If you’re saying “for urgent matters, contact X,” be clear about what counts as urgent. Otherwise every sender will decide their issue qualifies.
• Proofread. An auto-reply sends to hundreds of people while you’re not looking. A typo in your out-of-office reply is visible to everyone you correspond with for two weeks straight.
• Include a signature. Even for an auto-reply, your normal email signature tells the recipient how to verify they’ve reached the right person.

A few common mistakes worth avoiding:

1. Forgetting to turn it off. Nothing undermines “I’m back from vacation and ready to work” like an auto-reply still saying you’re away until next Monday.
2. Inviting “urgent” contact when you don’t want to be disturbed. If you offer an escape hatch, expect it to be used. If you genuinely don’t want interruptions, say so.
3. Trying to be funny. A joke that lands in person rarely lands in text, and it definitely doesn’t land the two-hundredth time a stranger receives your auto-reply.

How to set up auto-replies in Missive

In Missive, auto-replies are built with rules and canned responses. The combination gives you far more control than a simple out-of-office toggle.

1. Create the response. Go to Settings > Responses and write your template using variables for personalization.
2. Create a rule. Go to Settings > Rules > Create rule, pick Email as the channel and Incoming message as the trigger.
3. Add conditions. Filter which incoming emails trigger the auto-reply (all emails, specific senders, emails to a specific account, emails containing certain keywords, etc.).
4. Add the action. Choose “Send response” and select the template you just created.
5. Optional: throttle. Set “Send at most once every X per conversation” so the same sender doesn’t get the auto-reply 10 times on the same thread.
6. Save.

For personal out-of-office replies, Missive also has a dedicated personal auto-response feature tied to your status. Set your status to “Out of office,” define the date range, and Missive handles the rest.

How to set up auto-replies in Gmail

Gmail’s vacation responder is the simplest option for a basic out-of-office reply.

1. In Gmail, click the gear icon > See all settings.
2. Scroll to Vacation responder at the bottom of the General tab.
3. Turn it on, set the start and end dates, and write your subject and message.
4. Optionally, limit the reply to people in your Contacts or to your organization only.
5. Click Save Changes.

For more targeted auto-replies (specific senders, specific keywords), you’ll need to combine Gmail templates with filters:

1. Enable Templates in Settings > Advanced > Templates.
2. Compose your message, then click the three dots > Templates > Save draft as template.
3. Create a filter (in the search bar, click Show search options) with your criteria, then select Send template as the filter action.

How to set up auto-replies in Outlook

Outlook splits between the new and classic versions; the steps are slightly different.

New Outlook and Outlook on the web:

1. Click the Settings gear in the top right, then go to Accounts > Automatic replies.
2. Toggle Turn on automatic replies.
3. Set a time range if you only want the reply to run during specific dates.
4. Write your reply. You can set a different message for people outside your organization.
5. Click Save.

Classic Outlook for Windows:

1. Go to File > Automatic Replies.
2. Select Send automatic replies.
3. Check Only send during this time range and set the dates if applicable.
4. Write your reply in both the Inside My Organization and Outside My Organization tabs as needed.
5. Click OK.

Microsoft’s setup guide covers the older and Mac versions as well.

FAQ

What should an auto-reply email say?

At a minimum: why you’re not responding (out of office, out of hours, reviewing a support ticket), how long the sender should expect to wait, and who to contact in the meantime if the issue is urgent. Three sentences is usually enough. Long auto-replies signal that you have too much to say about your absence; short ones signal you’ve got it handled.

How long should an out-of-office message be?

Two to four sentences. Any longer and the sender stops reading. Any shorter and you haven’t set expectations. The seven templates above are all in this range and can be used as a length benchmark.

Can I set up an auto-reply for specific senders only?

Yes, in every major email client. In Missive, add a condition to your rule filtering by sender address or domain. In Gmail, combine a filter with a template. In Outlook, use rules (File > Manage Rules & Alerts > New Rule) rather than the simple Automatic Replies toggle, which applies to everyone.

What’s the difference between an auto-reply and a canned response?

An auto-reply sends automatically based on rules you’ve set up, without any human action. A canned response is a saved template you insert manually into an email you’re about to send. The two overlap, most auto-replies are built from canned responses, but the key difference is whether a human is in the loop when it sends.

How do I set up an auto-reply for a shared inbox?

This depends on the client. In Missive, shared inboxes (like support@ or sales@) can have rules that send auto-replies on behalf of the team, so responses don’t get sent from a specific individual. In Gmail and Outlook, shared mailboxes usually need the auto-reply configured by an admin at the mailbox level, not the individual level; personal out-of-office replies don’t apply to shared addresses.

What should I write in an away message for Outlook?

Any of the templates in this guide will work. Outlook lets you set one message for people inside your organization and a different (usually more formal) message for people outside. The “out-of-office general template” and the “alternative contact method” template are the two most common picks for Outlook away messages.

Can auto-replies hurt customer relationships?

They can, if they’re poorly written. The most common complaints: auto-replies that don’t say when the person will be back, auto-replies that promise a follow-up that never comes, and auto-replies with no alternate contact for urgent situations. Done well, they set expectations and reduce anxiety. Done badly, they feel like being put on hold.

Should I include a link to my FAQ or help center?

For support auto-replies, yes. A linked help center deflects common questions and often resolves the sender’s issue before anyone on the team has to reply. For personal out-of-office replies, usually no; it adds clutter without helping.

Missive is a collaborative email client with rules, canned responses, and personal auto-responses that work across email, SMS, WhatsApp, Instagram, and more. Try Missive free.

The best property management email templates cover the five moments that repeat every month: applications (auto-reply, approved, declined, waitlist), move-in, maintenance requests, rent reminders, renewals, and move-outs. Save them as canned responses in your email tool so your team can fire off a polished, on-brand reply without rewriting it each time.

Managing properties comes with a lot of communication. Whether you’re emailing potential tenants or resolving maintenance issues, there’s only so much you can handle one-off.

To help you build and maintain good landlord-tenant relationships, we’ve put together email templates that make it quicker to respond to maintenance requests, send rent reminders, follow up with applicants, and more. Let’s jump in.

The best property management email templates for your rentals

We’ve pulled together the templates you’ll actually use in daily property management work, with variable placeholders you can fill in.

If you’re using Missive, a collaborative email client for teams, you can copy/paste these directly into your canned responses and share them with your team so everyone sends the same clean message.

Application communication

First impressions matter, especially when it comes to attracting and retaining quality tenants. The application process sets the tone and often influences whether a tenant decides to move into one of your properties.

You might be thinking:

Wait, I don’t need an email template for applications; most of my leads come from Facebook Marketplace. I don’t do email marketing.

The good news is that these templates save time whether you’re sending via email or Facebook Messenger. With Missive, you can manage your Facebook Messenger account alongside email and reuse the same templates across both.

New application auto-reply

A template for an auto-reply when you receive a rental application:

Approved application

When an applicant passes the credit check and is approved, here’s a follow-up email template to use:

Declined application

Some applicants won’t be approved. Here’s a template to make declining straightforward and respectful:

Application on the waitlist

Last one for applications: for when you need to tell an applicant they’re on the waiting list.

Move-in communication

A welcoming email with all the info new tenants need for their move-in kicks off the relationship well. A good message makes them feel valued and cuts down on the “wait, what time?” questions.

Maintenance requests

Most of the emails filling up your inbox as a property manager are maintenance requests. Replying quickly and letting the resident know you’re taking care of the issue is how you keep them happy.

Receiving a maintenance request

Acknowledge the request right away so the resident knows it’s on your radar:

Issue resolved follow-up

Once the issue is fixed, a quick follow-up shows you care about the resident’s experience:

Two messages (acknowledge + resolution follow-up) set the right expectation and cut down on the “any update?” emails.

Rent payment reminder emails

If a resident is late on rent, a firmer reminder is in order. A few tips:

• Keep the tone warm and professional: this is a friendly nudge.
• Don’t sound accusatory. Assume they forgot or lost track of time.
• Give them the benefit of the doubt on the first reminder.
• Spell out the exact late fees that apply under the lease.
• Say when late fees will start accruing if the balance remains unpaid.
• Explain next steps if it stays unpaid past the late fee date (e.g., notice to pay or quit).
• Offer to discuss payment plans or assistance programs if relevant.
• Include account balance, where to pay, and who to contact with questions.

Here’s a template:

Renewals

Timely renewal notices are how you retain residents and avoid vacancies. Start at least 90 days before the lease expires (adjust for your local laws). The email should spell out any changes and give a clear deadline for notice to vacate.

A template:

Move-out communication

When a resident decides to move out, you’ll need to communicate all the info they need for the process. It can feel like a lot, especially if you manage many properties, but templates handle most of it.

A few tips before the template:

• Send a move-out inspection reminder 30 days before the move-out. Flag that inspections look for damages beyond normal wear and tear.
• Include the date/time of inspection and whether residents need to be present. Offer to reschedule if the proposed time doesn’t work.
• Attach your move-out cleaning checklist so residents can prepare the unit. Mention any charges for major cleaning or repairs.
• Thank the resident for their tenancy and confirm you’re processing their security deposit return, along with your policy timeline.

With those in mind, here’s the template:

Best practices for property management emails

Being a good property manager isn’t just about caring for brick and mortar, it’s also about nurturing relationships. Whether you’re a manager or a landlord, a few email best practices save time and avoid misunderstandings:

• Personalize your communication. Use the resident’s name in the greeting instead of a generic “Hello.” It goes a long way.
• Use clear, descriptive subject lines. Subject lines should tell the resident what the email is about at a glance. Skip vague lines like “Lease Question” that could apply to anyone.
• Optimize for mobile. Most people read email on their phone. Use a single-column layout, larger fonts, and short paragraphs so your messages are easy to read on a small screen.
• Keep it professional. Even friendly greetings should stay polite with a business-like tone. Forget everything you learned in school about writing like Shakespeare: be clear and concise. And proofread; sloppy emails hurt your image fast.

Master property management email communication and you’ll deliver five-star service, operate efficiently, and support your team.

FAQ

How do I manage property management emails across a team?

Use a shared inbox tool so your whole team can see every tenant conversation, assign the right person, and avoid duplicate replies. Missive, for example, lets multiple leasing agents and maintenance staff work the same inbox without forwarding or sharing passwords.

What’s the best way to save property management email templates?

Save them as canned responses in your email client. That way, any team member can pull up the right template in one click and personalize the variables before sending. If you’re using Missive, you can share templates across your team so everyone sends the same polished message.

How quickly should I respond to tenant emails?

Same-day acknowledgment for anything, even if full resolution takes longer. For maintenance issues, acknowledge within a few hours and set a clear expectation for when you’ll follow up. For applications, reply within 24-48 hours. For response-time SLAs, 4 business hours is a solid benchmark for tenant communication.

Should I automate reminders for rent and lease renewals?

Yes, where you can. Rent reminders, late payment notices, and renewal notices all follow the same pattern every month or year, which makes them perfect for automation. Use your property management software’s built-in reminders, or set up rules in your email tool to handle the routine nudges and free your time for the stuff that actually needs a human.

How do I handle tenant complaints over email?

Acknowledge the complaint quickly (within a few hours), validate their frustration, and give a clear timeline for resolution. For anything complex or emotional, switch to a phone call after the first email response. Written channels are better for records; voice is better for tone. Missive lets you track every step of a complaint across email, SMS, and calls in the same thread so nothing falls through the cracks.

Emails end up in spam for four main reasons: poor list management (sending to unengaged or unconsented addresses), low-quality or keyword-stuffed content, weak DNS authentication (missing or misconfigured SPF, DKIM, DMARC, and BIMI records), and poor sender reputation monitoring. Fix all four and your deliverability improves substantially, even without any content changes.

Every day, approximately 350 billion emails are sent and received. Of those, more than 45% end up in spam. That’s a massive hit for businesses: marketing emails don’t reach subscribers, transactional emails don’t inform customers, and teams struggle to communicate effectively.

Email deliverability is something of a black box, much like SEO. The rules change often and aren’t fully disclosed by major Email Service Providers (ESPs) like Google, Apple, and Microsoft.

Sometimes they are disclosed, as with Google and Yahoo’s enforcement of stricter sender authentication requirements starting in February 2024 and tightened further since. More often, the rules stay opaque.

The good news: even with that uncertainty, you can significantly improve your email deliverability. If your messages are getting lost in the spam folder, read on; we’ll cover why emails end up there and how to prevent it.

What is email deliverability?

Before we dive into why your emails end up in spam, let’s start with a distinction that trips up most people:

Just because your emails show as “delivered” in your sending tool (bounce rate, delivery rate) doesn’t mean they’re actually reaching the recipient’s inbox.

Email deliverability is the odds that your email makes it to the inbox and not to spam. “Delivered” just means the recipient’s server accepted it; spam filtering happens after that.

Why do emails end up in spam?

Emails trigger spam filters for many reasons, but the story usually comes down to four pillars:

1. List management: Sending emails to unsubscribed or dormant addresses is a major red flag. Your list should be built organically with permission-based opt-ins. If you’re still emailing old, inactive accounts that keep bouncing, your reputation takes a hit.
2. Content and engagement: Excessive exclamation points, ALL CAPS, misleading subject lines, or irrelevant keywords can trigger spam filters and route your email to no man’s land.
3. DNS configuration: Not implementing email authentication protocols like SPF, DKIM, and DMARC is another red flag for ESPs. These act like digital IDs, verifying that you’re who you say you are and preventing impersonation by spammers.
4. Monitoring and optimization: Not regularly tracking deliverability metrics like spam rate, open rate, and click-through rate means you’ll miss signals about what needs to change, whether that’s content, list hygiene, or technical setup.

Avoid these red flags and your emails will land in the inbox far more often.

Best ways to prevent emails from going to spam

List management

Opt-in

How you collect emails and build your subscriber list matters a lot. If you use a deceptive method to grab email addresses and then send unsolicited messages, those recipients will be unhappy, and unhappy recipients mark you as spam.

Use an opt-in form that clearly tells users they’ll receive content from you by checking a box or a similar mechanism. Be clear, not sneaky.

Unsubscribe

Make it easy to unsubscribe. Don’t hide the link in gray-on-white at the bottom of your template. People who can’t unsubscribe flag your email as spam, which damages your reputation.

Google and Yahoo now require an unsubscribe button directly in the header of bulk email. Here’s what it looks like:

Cleaning your lists

Deprecated emails

Use a third-party tool to remove deactivated or banned accounts from your list. Those create hard bounces, and hard bounces hurt your reputation.

We like Neverbounce for this.

Sunset policy

If a group of subscribers hasn’t opened a single email in the last six months, send them a message asking if they’re still interested. Emails that consistently get ignored are likely to be flagged as spam, which isn’t good for your sender reputation and isn’t a great final touchpoint with your brand either. Be kind and warm about it; let them sail into the sunset if that’s their wish.

Content

The content you send matters more than almost anything else. People’s time is valuable, so when you ask for their attention, make sure what you’re sending is worth the read.

A quick checklist before hitting send:

• Is the content relevant and interesting?
• Is it well-written and to the point?
• Is it well-designed and easy to scan?
• Is it actually meant for my audience?
• Does it use any words that could trigger a spam filter?
• Would I want to receive this email if I were the reader?

Infrastructure configuration

Authenticating and securing your emails is a crucial step in making sure they reach the inbox. It’s often overlooked and one of the easiest wins for deliverability.

There’s a tight link between security and compliance here. ESPs want to reduce spam, scams, and phishing. To support that, they favor domains with well-configured security and authentication protocols in their DNS.

This part is tricky to set up but incredibly valuable. It can mean the difference between a +39% open rate and a +34% purchase likelihood.

So what are these authentication and security protocols?

Understanding DNS

DNS is the address book of the internet. Computers use DNS to look up domain names and find the corresponding IP addresses needed to connect to websites, servers, and other resources.

DNS is also where ESPs like Google, Apple, and Microsoft check how your emails are secured and authenticated:

• Who is authorized to send emails on behalf of your domain? (SPF)
• What signature should they look for to confirm the content is authentic? (DKIM)
• Is your domain protected by a policy? (DMARC)
• Is your sender identity verified with a logo? (BIMI)

Let’s go through each one.

Authorized senders list (SPF record)

SPF records are like a guest list for sending emails. An SPF record is a line of text that specifies which domains or IP addresses are permitted to send emails on behalf of your domain. It lives in your DNS manager, under TXT records.

Here’s an example SPF record:

v=spf1 ip4:192.0.2.0/24 ip6:2001:db8::/32 include:_spf.example.com ~all

If an email from your domain is sent to a recipient server from an IP not on your SPF list, deliverability takes a hit.

A quick tip: to check whether your DNS is configured properly and your email has a good chance of reaching the inbox, use Palisade’s free Email Deliverability Score tool. It audits your DNS configuration and suggests improvements.

Digital signature (DKIM records)

DKIM records add a digital signature to your emails that proves they’re authentic when they arrive at the recipient server. Think of it like the signature on the back of your credit card.

Each third-party service you use with your domain typically needs its own DKIM key and record.

Here’s an example DKIM record:

v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAgAS4QZzH+/iM5ilpxexFK7uVnX5OasDMW61p7IvUjM+488QnpLqDTlsvGdJtG/oHgwRpXcNSxKKhtX3R4zg0MoSdLJYTEMiirr8UdeuGng/ZKM2XtLa+qGve6kp3H5NBx2uYHVj+E0WANeRT3bK5sMVRTYSAywN/m9ugX5T5PkbvJ2HRTmrX00ov4/VoVFSbfHZzaA/FDX/hyFnWEiOb1JihArP2+cMs+CYgIi7u8t+p0FqR/37kuEh5PLxOct/fnhqjn35XPn8C1s2fAC5J2WZjmmC5QM2qYV90isu03jeCI7Vap9ocKj5P+qJAlooYNujICd84ZmcHeA2UJqj22QIDAQAB

Defended domain (DMARC)

DMARC protects your domain from people trying to send fake emails (phishing, spam) on your behalf.

The DMARC policy is central to deliverability and security. It tells recipient servers what to do if the emails they receive from you aren’t authenticated properly through your SPF or DKIM (often called alignment).

Here’s an example DMARC record:

v=DMARC1; p=none; rua=mailto:dmarc@palisade.email; ruf=mailto:dmarc@palisade.email; fo=1;

Google and Yahoo have been enforcing DMARC policies for bulk senders since early 2024, and their requirements have continued to tighten since. If you’re sending any volume of email, DMARC alignment is non-negotiable.

Brand display and verified checkmark (BIMI)

BIMI was adopted by Google, Apple, Yahoo, and most major ESPs (still waiting on Outlook) back in May 2023. It’s now the standard way to verify your identity via email, display your brand logo in the inbox, and get a verified checkmark. You’ll see this rolled out by large brands like LinkedIn and Google:

Here’s an example BIMI record:

v=BIMI1;l=https://images.palisade.email/brand/bimi-logo.svg;a=https://images.palisade.emai/brand/certificate.pem

Monitoring

Monitoring your sender reputation is a big part of keeping deliverability high. Sender reputation is like a person’s reputation: it takes time to build and is easy to damage.

There’s no single tool that does it all, but several tools can give you partial visibility into your deliverability health.

Domain reputation, IP reputation, and spam rates

One of the best tools available, even if it only monitors your reputation from Google’s perspective, is Google Postmaster.

It gives you three key data points on sender reputation:

• Domain reputation: How Google views your domain holistically. All emails from all apps combine into one reputation.
• IP reputation: How the third-party app’s IP reputation affects your sender reputation.
• Spam rate: The number of users reporting your emails as spam.

Wrapping up

Email deliverability isn’t set-and-forget; it’s ongoing work, but worth it.

Many companies spend significant time A/B testing funnels and producing content but skip the critical step of making sure their emails actually reach the inbox. If your users aren’t seeing your content, what’s the point of investing so much in creating it?

It’s not easy. List management best practices change. Content engagement shifts with trends. DNS compliance evolves. Reputation monitoring is sensitive. After reading this, you should have a better understanding of email deliverability basics (and the difference between “delivered” and “in the inbox”), and know where to focus your attention first.

FAQ

Why do my emails keep going to spam?

The most common causes are missing or misconfigured SPF, DKIM, and DMARC records; sending to a dirty list with unengaged or invalid addresses; using content patterns spam filters flag (all caps, misleading subject lines, spam-trigger words); and poor domain or IP reputation. Start with DNS authentication; it’s the most impactful fix and often the most overlooked.

What’s the difference between delivered and inbox placement?

“Delivered” means the recipient’s email server accepted the message. Inbox placement means the message actually made it to the inbox instead of spam, Promotions, or other filtered folders. Your ESP will typically show you delivered rates but not inbox placement. For that you need deliverability tools like Palisade or Google Postmaster.

Do SPF, DKIM, and DMARC really matter?

Yes. Since Google and Yahoo’s 2024 enforcement changes, bulk senders (over 5,000 emails a day to Gmail or Yahoo addresses) that don’t have proper SPF, DKIM, and DMARC alignment see their messages quietly dropped into spam or rejected outright. Even for smaller senders, proper authentication measurably improves inbox placement.

How do I check if my email is set up correctly?

Free tools like Palisade’s Email Deliverability Score, MXToolbox, and Google Postmaster will audit your DNS configuration, flag missing records, and highlight issues with SPF, DKIM, DMARC, and BIMI. Run a check before you send any big campaign.

Does BIMI actually improve open rates?

Early data suggests yes, in the +10% to +39% range for open rates, because a verified logo in the inbox increases trust at a glance. The tradeoff is that BIMI requires a Verified Mark Certificate (VMC) from a certifying authority, which costs several hundred dollars per year and requires a trademarked logo.

Can I improve deliverability without changing my content?

Often yes. Proper DNS authentication (SPF, DKIM, DMARC), list cleaning (removing hard bounces and long-inactive subscribers), and consistent sending volume can all improve inbox placement without any content changes at all. If your content is reasonable and your deliverability is bad, the technical setup is usually the culprit.

Customer service goals are specific, measurable targets that define what success looks like for a support team. They translate strategic priorities into concrete numbers like first-response time, customer satisfaction (CSAT), ticket deflection rate, or team engagement, so individual agents and managers know what they’re working toward and how they’re being measured.

If you’ve just taken over a new support team, or you’re leading one through a period of change (a reorganization, an acquisition, a leadership transition), one of the hardest parts of the job is setting goals that are actually useful. Especially if your company is trying to become more customer-first, the targets you set will shape what that means in practice.

Too vague, and nobody knows what success looks like. Too ambitious, and the team burns out chasing them. Too safe, and the team coasts. The skill is landing somewhere in between, with goals specific enough to guide daily decisions and realistic enough to feel achievable.

This guide covers what SMART goals look like applied to customer service, how to set them for different levels of the team, and how to adjust when reality doesn’t match the plan.

Why customer service goals matter

Running a support team without clear goals is like sailing without a destination, you move a lot, but it’s hard to tell whether you’re getting anywhere. A few specific benefits of real goals:

It connects support to the business. Well-defined goals make it clear how your team is contributing to company outcomes. That helps when budget conversations come around and you need to justify headcount or tools.

It makes customer experience improvements traceable. When you’re targeting a specific CSAT number or response time, you can measure whether the change you made actually moved the needle. Without a target, improvement is vibes.

It makes your team happier. This one gets underestimated. People want to know what “good” looks like. Ambiguity about performance is stressful, and it makes it hard to have meaningful career conversations. Clear goals give individual team members something to work toward and something to be measured fairly against.

SMART goals for customer service (the framework)

You’ve probably seen the SMART framework before. The acronym stands for:

• Specific
• Measurable
• Achievable
• Relevant
• Time-bound

It’s useful because vague goals are the enemy of accountability. “Improve response times“ is a wish. “Send a first response to 80% of chat inquiries within 60 seconds by the end of Q2” is a goal.

5 SMART customer service goals examples

If you need something to copy and adapt right now:

1. Response time: Respond to 80% of incoming emails within 4 hours during business days by end of Q2 2026.
2. CSAT: Maintain an average CSAT score of 88% or higher across all channels through 2026.
3. Self-service deflection: Reduce ticket volume on the top 10 FAQ topics by 20% by end of Q3 2026 by launching a help center.
4. Team engagement: Reduce voluntary support team turnover by 20% year over year through monthly 1:1s and quarterly team events.
5. Voice of customer: Ship at least one product improvement per quarter based on support-surfaced feedback starting Q2 2026.

Let’s walk through each piece in the context of a real support goal.

Specific

Get precise. “Answer customers faster” doesn’t tell anyone what channel, what threshold, or what counts as “faster.”

Better: “Send a first response to customers within 60 seconds of their initial chat message.”

Better still: “Send a first response to order-status chat inquiries within 60 seconds during business hours.”

The more specific the goal, the clearer the path.

Measurable

You need a number you can check against. Our chat goal gets measurable with a percentage: “80% of chat customers will receive a response within 60 seconds.”

Pick metrics you can actually track in your tool. If it takes engineering time to instrument, the goal won’t survive contact with reality.

Achievable

This is where the assessment work before goal-setting pays off.

“80% in 60 seconds” might be a stretch goal for a small chat team seeing hundreds of conversations a day. Might be easy for a larger team with capacity to spare. Without an honest look at your starting point, you either set goals that demotivate (too hard) or ones that don’t move the team (too easy).

If the realistic starting point is 30% in 90 seconds, a reasonable Q1 goal might be 50% in 90 seconds, and a stretch Q2 goal might be 70%. You’ll get further with escalating goals than with one aspirational target the team gives up on in week three.

Relevant

The goal has to connect to something bigger. Is it aligned with the customer service values your company operates on? Does it support the company’s strategic priorities?

A chat response time goal makes sense if customer speed is a differentiator. It matters less if your customers are mostly asynchronous and prefer email follow-ups. Matching the goal to the actual priority prevents wasted effort.

Time-bound

Without a deadline, measurement never happens. “By the end of Q2 2026, we’ll be responding to 80% of chat customers within 60 seconds” gives you a specific checkpoint.

Pick deadlines long enough to drive meaningful change but short enough that feedback loops are useful. Quarter-long goals usually work well. Annual goals tend to drift and get revisited only once, too late.

Setting goals requires an honest assessment first

Before you write a goal, spend time understanding where the team actually is. A few questions that help:

• What’s our current team capacity (hours available, per-agent load)?
• What’s our incoming volume by channel, tickets, chats, calls, DMs?
• What are our current baselines for response time, resolution time, CSAT, and NPS?
• What’s our team’s budget, and what tools do we use?
• What company-level goals are we supposed to be contributing to? (Your broader customer service strategy should set the direction.)
• What did last quarter’s data actually show, trends, bottlenecks, wins?

Answer those first, and your goals will land somewhere sensible. Skip this step and you’ll end up with goals pulled from industry averages that have nothing to do with your team’s reality. (For teams just starting out, a set of general customer service tips is a fine baseline to work from.)

3 examples of department-level goals

Improve customer self-service

Customers increasingly want self-service options. A help center with good coverage deflects tickets before they’re ever created.

Example goal: “By end of Q3 2026, launch a help center covering our 15 most frequently asked support questions, with the goal of reducing tickets on those topics by 20%.”

Measure success through help center analytics (view counts, search terms, time on page) and ticket volume trends on the covered topics.

Implement a quality assurance program

A QA program is one where managers regularly review a sample of agent conversations against a scorecard. It improves consistency, surfaces training opportunities, and gives individual feedback a data foundation.

Example goal: “In Q2 2026, finalize a QA scorecard based on 100 ticket reviews from the previous quarter, and begin monthly calibration sessions with the team in Q3.”

Success is measured by whether the scorecard ships on time and calibration sessions actually happen monthly. Secondary measures include QA score trends once the program is running.

Improve customer satisfaction

CSAT is a direct customer-voice metric. Moving it is slow work, but improvement shows up in retention and referrals over time.

Example goal: “Maintain an average CSAT of 88% or higher across email and chat each month in 2026, with no month below 85%.”

Collect CSAT through a post-resolution survey. Most modern support tools have this built in. Some teams also use AI rules to route low-scoring surveys to a manager for immediate follow-up.

2 examples of manager-level goals

Improve team engagement

Engaged support teams stick around longer and do better work. Attrition in support is expensive, both the direct cost of hiring and the indirect cost of losing institutional knowledge.

Example goal: “Hold a monthly 1:1 with each direct report, run one team social event per quarter, and reduce voluntary turnover by 20% year over year.”

Turnover is the measurable outcome. 1:1 cadence and social events are the inputs.

Become the voice of the customer

Support managers sit at the clearest vantage point in the company for what customers are actually saying. Translating that into product, engineering, and marketing decisions is a high-use part of the job.

Example goal: “Establish a bi-weekly Voice of the Customer meeting with product leadership in Q2 2026, with the goal of influencing at least one product release and one bug fix per quarter based on support insights.”

Measure through meeting cadence and the count of shipped changes attributable to support-surfaced feedback.

2 examples of individual agent goals

Improve a specific skill

Every agent has strengths and growth areas. A good performance system identifies those and builds specific goals around them.

Example goal: “Complete the company’s de-escalation training by end of Q2, and reduce my escalation rate on tier-1 tickets by 15% in Q3.”

Measurable through training completion and escalation-rate data.

Take more ownership of customer experience

The more agents take ownership of their customers’ end-to-end experience, the better the outcomes, for customers and for the agents’ own growth.

Example goal: “Respond to every CSAT rating I receive (positive and negative) within 24 hours for the next quarter, using the responses to identify at least three improvement areas by end of Q2.”

Ownership isn’t always numerical, but activity-based goals like this work well as a way to build habits that compound over time.

Making goal-setting a habit, not an event

The real trap with goal-setting isn’t picking the wrong goals. It’s picking goals once, putting them in a document, and never looking at them again.

Goals need a rhythm:

• Set them at the start of the quarter.
• Check in mid-quarter, are we on track? What’s getting in the way?
• Review at quarter end, what did we hit, what did we miss, what did we learn?
• Carry forward what worked, rewrite what didn’t.

The teams that run this cycle consistently tend to outperform the teams that treat goal-setting as an annual planning ritual. It’s not magic. It’s just doing the work.

One more thing: goals aren’t a substitute for judgment

SMART goals are useful because they force specificity. They’re not a replacement for thinking.

If a goal starts pushing the team toward behavior that hurts customers (agents closing tickets too fast to hit handle-time targets, for example), the goal is the problem, not the team. Rewrite it. Goals should serve outcomes, not the other way around.

The teams that do this well treat goals as hypotheses: “we think hitting this number will lead to this outcome.” When the number moves but the outcome doesn’t, they change the goal instead of doubling down.

Missive is a collaborative email client for teams that care about customer experience. Shared inboxes, assignments, internal chat, and rules that work across email, SMS, WhatsApp, and live chat. Free for up to 3 users, try it free.

Ah, unhappy customers. The not-so-silent killer of business.

Your team can deliver, innovate, and grow. But if customers aren’t happy, none of that matters for long. And you can’t fix what you don’t measure.

So how do you actually measure customer happiness?

With customer satisfaction metrics. There are dozens of them, which is both good and bad — good because you can pick the ones that fit your business, bad because it’s easy to get lost in a sea of acronyms. This guide covers the nine that actually matter, when to use each, and how to interpret what the numbers are telling you.

What are customer satisfaction metrics?

Customer satisfaction metrics are the numbers companies use to understand how happy customers are with their product, service, and overall experience. They give you a feedback loop — without one, you’re just guessing about what customers think.

Some metrics shed light on specific interactions (a support conversation, a product onboarding). Others capture the bigger picture (overall loyalty, retention, revenue impact). The best teams use a mix: one or two moment-to-moment metrics, one or two relationship-level metrics, and one financial metric.

Let’s dig in.

1. Net Promoter Score (NPS)

NPS is a customer satisfaction metric that gauges loyalty based on one question: how likely is a customer to recommend you?

If someone will enthusiastically tell their friends about your product, it’s a strong sign they’re happy with what you’ve built.

NPS is based on a single survey question:

How likely would you be to recommend X to a friend or colleague?

Respondents rate on a scale from 0 to 10. Based on their rating, they fall into one of three groups:

• Detractors (0–6) are customers who are not satisfied with your product. They’re often the most vocal group — negative experiences tend to travel.
• Passives (7–8) generally feel good about your product, but aren’t enthusiastic. The NPS model excludes them from the equation.
• Promoters (9–10) love your product. They’re highly satisfied and likely to spread the word.

How to calculate Net Promoter Score

Calculate the percentage of promoters and the percentage of detractors from your total responses. Then subtract detractors from promoters:

NPS = % of promoters − % of detractors

If you got 100 responses — 50 promoters, 30 passives, 20 detractors — your NPS is 30 (50% promoters minus 20% detractors).

What’s a good NPS?

NPS ranges from −100 (everyone’s a detractor) to 100 (everyone’s a promoter), but real-world scores sit in the middle. Anything above 0 means you have more promoters than detractors. According to recent benchmarking research, the overall NPS benchmark sits around 32. But the bigger signal is the trend — is your NPS rising or falling over time?

When to use NPS

NPS works as a KPI for overall customer satisfaction. In practice:

• Web apps typically send NPS surveys after onboarding and then quarterly.
• E-commerce stores send NPS surveys within a week of delivery.
• Brick-and-mortar businesses use QR codes at the exit or physical feedback kiosks.

Product and marketing teams often use NPS as a headline KPI. Customer success teams use it as an input for churn prediction and customer health scoring.

Pros and cons

The good: NPS gives you a single number that summarizes overall loyalty, easy to track over time.

The bad: “Likelihood to recommend” doesn’t always correlate with actual behavior. It also doesn’t tell you why — you need to pair it with open-text feedback to act on it.

2. Customer Satisfaction Score (CSAT)

CSAT measures how happy customers are with a specific interaction — a support conversation, a sales demo, a feature they just used. It’s a snapshot, not a long-term relationship metric.

The survey usually asks something like:

How satisfied were you with your recent experience?

Customers answer on a scale (1–5 is most common), and you measure the percentage who gave a positive rating.

How to calculate CSAT

Count the number of “satisfied” responses (usually 4s and 5s on a 5-point scale) and divide by total responses:

CSAT = (satisfied ratings / total ratings) × 100%

If 100 people respond and 80 of them rate 4 or 5, your CSAT is 80%.

What’s a good CSAT score?

CSAT ranges from 0% to 100%. Under 50% is a red flag — more people are leaving unhappy than satisfied. In competitive industries like SaaS and e-commerce, the benchmark is around 80%. A 95% CSAT is realistic for a high-performing team.

You should also see a 5–20% response rate on CSAT surveys. If fewer people are responding, rethink your survey timing, messaging, or channel.

When to use CSAT

CSAT works best as a follow-up after specific touchpoints:

• After a support conversation
• After a sales demo
• After a business review with your customer success team
• After an in-store purchase

Many teams use CSAT as a KPI for individual agents and entire customer-facing teams. Don’t send CSAT after every single interaction — it gets annoying, response rates crater, and the data becomes unreliable.

Pros and cons

The good: captures satisfaction at specific moments, actionable when you tie it to who handled the interaction.

The bad: “Satisfaction” is subjective. Cultural differences affect what a 4 vs. a 5 means. Response rates vary, so results don’t always reflect your full customer base.

3. Customer Effort Score (CES)

CES measures how easy it is for customers to do something — get their question answered, complete a task, find what they need. It’s based on research showing that reducing effort is a better predictor of loyalty than trying to “delight” customers.

Instead of asking about satisfaction, the survey asks:

How easy was it to [resolve your issue / find what you needed / complete your task]?

How to calculate CES

CES uses a 7-point scale. Divide the number of responses rating 5, 6, or 7 (easy) by total responses:

CES = (ratings of 5, 6, 7 / total ratings) × 100%

If 100 people respond and 60 rate 5 or higher, your CES is 60%.

What’s a good CES?

CES ranges from 0% to 100%, higher is better. Because it’s a relatively new metric (Gartner introduced it in 2010), benchmarking is less mature than NPS or CSAT. What matters more is your own trend over time.

When to use CES

CES works well after any interaction where “ease” is the thing you want to optimize:

• After a support conversation (how easy was it to resolve the issue?)
• After using a self-service resource (how easy was it to find the answer?)
• After first use of your product (how easy was it to get started?)

Timing matters — send the survey immediately, while the experience is fresh.

Pros and cons

The good: highly actionable. If CES is low, you know exactly where the friction is.

The bad: can be misleading without context. A low CES might mean your product is genuinely hard to use, or it might mean you serve technical users working on complex problems.

4. Customer churn rate

Churn is the rate at which you lose customers. It’s the ultimate satisfaction metric — if customers are canceling, they’re telling you something, even if they never filled out a survey.

How to calculate churn rate

Divide the number of customers lost in a period by the number you had at the start:

Churn rate = (customers lost / customers at start of period) × 100%

If you start the month with 100 customers and lose 20, your monthly churn is 20%.

What’s a reasonable churn rate?

Lower is better. Ideally it should be below your growth rate, and under 7% annually for most subscription businesses. Much higher than that, and you’re filling a leaky bucket — every new customer you add is offset by one walking out the door.

When to use churn rate

Churn rate is critical for any subscription or recurring-revenue business. It’s also a lagging indicator — by the time you see it rise, customers are already gone. So pair it with leading indicators (CSAT, NPS, support ticket volume) that can warn you before churn happens.

Pros and cons

The good: directly ties customer satisfaction to business outcomes.

The bad: not actionable on its own. A high churn rate tells you there’s a problem, but not what the problem is.

5. Customer Retention Rate (CRR)

Retention is the flip side of churn — instead of measuring who leaves, you measure who stays. For some teams, framing it this way is more motivating and maps more cleanly to customer success work.

How to calculate retention rate

CRR = ((Customers at end of period − New customers acquired) / Customers at start of period) × 100%

If you start with 100 customers, gain 30 new ones, and end with 110, your retention rate is (110 − 30) / 100 = 80%.

When to use retention rate

Retention rate works especially well for customer success teams and account management teams, where the goal is keeping existing customers happy, expanding accounts, and preventing churn. It also surfaces issues earlier than churn rate alone, because it accounts for the fact that new customer acquisition can mask retention problems.

Pros and cons

The good: a positive framing that ties to customer success activity.

The bad: like churn, it’s a lagging indicator. You need leading indicators to act before it moves.

6. Customer Lifetime Value (CLV)

CLV estimates the total revenue you’ll earn from a customer across the entire relationship. It’s not a direct satisfaction metric, but it tells you whether your satisfaction efforts are paying off — happy customers stay longer and buy more.

How to calculate CLV

The simple version:

CLV = Average purchase value × Purchase frequency × Customer lifespan

For a SaaS business, it’s often calculated as average revenue per customer divided by churn rate. If your average customer pays $100/month and your monthly churn is 5%, CLV is roughly $2,000.

When to use CLV

CLV is most useful for decision-making — how much can you afford to spend acquiring a customer? How much should you invest in customer success? It also helps identify which customer segments are most valuable, so you can focus retention efforts where they’ll have the biggest impact.

Pros and cons

The good: connects satisfaction work directly to revenue. Easy to justify budgets.

The bad: calculation gets complex for businesses with varied purchase patterns. Also backward-looking — doesn’t tell you what customers think right now.

7. First Response Time (FRT)

FRT is how long it takes your team to send the first reply to a customer inquiry. It’s not satisfaction itself, but it correlates strongly with it — customers who wait hours or days for a first response are already unhappy by the time you write back.

How to calculate FRT

Measure the time between when a customer contacts you and when your team sends the first human response. Average it across a time period (daily, weekly, monthly).

What’s a good FRT?

Benchmarks vary by channel:

• Live chat: 30 seconds to 2 minutes
• Email: under 4 hours during business hours, under 24 hours overall
• Social media: under 1 hour
• SMS: 15–30 minutes during business hours

When to use FRT

FRT is a headline metric for customer support teams. It’s also a useful operational metric — if it’s getting worse, you need more staff, better automation, or better routing.

Pros and cons

The good: easy to measure, directly actionable. If FRT is high, you know what to fix.

The bad: fast responses don’t equal good responses. A two-minute reply that misses the question is worse than a ten-minute reply that solves it.

8. Average Resolution Time

Resolution time is how long it takes to fully resolve a customer’s issue — from the first message to the last. It captures the full experience, not just the first response.

How to calculate resolution time

Measure the time between when a conversation starts and when it’s marked closed/resolved. Average it across conversations.

What’s a good resolution time?

Varies wildly by issue type. Simple billing questions should resolve in minutes. Complex technical issues might take days. Track by category — a long average resolution time for password resets means something different than a long average for bug reports.

When to use resolution time

Resolution time is useful for identifying systemic issues. Is one category of problem taking dramatically longer than others? Is a particular agent’s resolution time an outlier (either good or bad)? Does resolution time correlate with CSAT scores?

Pros and cons

The good: captures the full experience, not just the opening exchange.

The bad: can push teams toward rushed closures. Make sure you’re not optimizing for speed at the expense of actually solving the problem.

9. Customer Health Score

Customer health score combines multiple signals into a single indicator of how a customer is doing overall. It’s less a metric and more a framework — you pick inputs that predict churn or expansion for your business and combine them into a score.

How to calculate health score

Every team calculates it differently. Common inputs:

• Product usage (login frequency, features used)
• Support ticket volume and sentiment
• NPS or CSAT scores
• Billing status
• Engagement with emails or check-ins
• Time since last meaningful interaction

Weight them by how predictive they are of your actual outcomes (churn, expansion), then combine into a 0–100 score or a red/yellow/green indicator.

When to use health scores

Health scores are most useful for customer success teams managing a portfolio of accounts. They help prioritize — which accounts need attention this week? Which ones are ripe for expansion?

Pros and cons

The good: early warning system. Health scores catch problems before they show up in churn.

The bad: garbage in, garbage out. If your inputs aren’t actually predictive, the score is just a number. Requires ongoing calibration.

Going beyond metrics

Metrics are great for spotting trends and setting KPIs. But a number on a dashboard never tells you the whole story.

The teams that really understand their customers pair metrics with open-ended feedback. Adding a free-text field to your CSAT survey, for example, often reveals that low ratings have nothing to do with your support team — they’re about a specific product issue that’s easy to fix. Without the text field, you’d be troubleshooting the wrong problem.

The opposite happens too. Customers might rate individual interactions highly while being broadly dissatisfied with your product. Or they might churn without ever leaving a negative review, because they were “too polite” to complain.

So treat metrics as a starting point. The number tells you that something is happening. Conversations with customers tell you why. The best customer satisfaction programs use both.

Missive is a collaborative email client that helps teams handle customer support, gather feedback, and automate follow-ups. If you’re trying to close the loop between metrics and actual customer conversations, Missive might be worth a look. Try it free.

“Customer experience” has become one of those phrases that means everything and nothing. Every company claims to care about it. Every vendor promises to help you improve it. Everyone agrees it matters.

But if you ask ten people at the same company what “customer experience optimization” actually involves, you’ll get ten different answers.

This guide tries to fix that. It covers what customer experience optimization actually is, why it matters for real business reasons, the practical pillars that make it work, and the seven things you can do this quarter to start improving. No abstract frameworks. No buzzwords. Just what works for teams that are trying to get this right.

What is customer experience optimization?

Customer experience optimization (CXO) is the ongoing process of improving every touchpoint a customer has with your company — from the first ad they see to the last support conversation they have.

The word “optimization” matters here. You’re not building customer experience from scratch each time. You already have one, whether you designed it or not. Every email you send, every signup flow, every support reply, every outage post-mortem — they all shape how customers perceive you.

The question is whether that perception is happening by design or by accident.

In today’s market, there isn’t much room to get this wrong. Research from Adobe shows that 86% of consumers are willing to pay more for a better experience. A study from Qualtrics found that 80% of customers have switched brands after a bad experience. The companies that get experience right pull ahead. The ones that don’t lose customers to competitors who do.

Unlike a one-time project, customer experience optimization is continuous. Customer expectations change. Your product changes. The tools and channels you use change. What counted as “great” three years ago is table stakes now. The teams that do this well treat it as ongoing work, not a quarterly initiative.

The four pillars of customer experience optimization

Most good customer experience work breaks down into four categories. You don’t have to master all of them at once, but you do have to be deliberate about each.

Personalization

67% of customers want a personalized experience, according to Adobe’s research. The one-size-fits-all approach stopped being competitive a while ago.

Personalization isn’t just about using someone’s name in an email. It’s about recognizing that different customers have different jobs to do with your product, and designing around that. A first-time user exploring what your tool does needs different onboarding than a power user coming back to recover their account. A small business has different support needs than an enterprise customer.

The practical version of personalization looks like this: your support team sees a customer’s history when they reply. Your onboarding adapts to what the customer said they wanted to do. Your emails reference their actual use of the product, not just their signup date.

Consistency

We’ve all had this experience: you call support, get transferred, and have to explain your problem from scratch to the next agent. Or you read a help article that contradicts what the salesperson told you last week.

Consistency is hard. You’ve got multiple people replying to emails, multiple writers producing content, multiple channels your customers reach out through. Getting all of them to sound like the same company is a real coordination problem — but it’s the difference between feeling like a cohesive brand and feeling like a random collection of departments.

The teams that do this well invest in shared context — shared style guides, shared canned responses, shared customer history, shared internal documentation. When everyone can see the same picture of the customer, consistency is easier to maintain.

Responsiveness

A Forrester study found that 77% of consumers say valuing their time is the single most important thing companies can do to deliver a great experience. Speed matters. Waiting four days for a reply to a simple question doesn’t feel like good customer experience, regardless of how thoughtful the reply eventually is.

Practical responsiveness looks like: a first response within minutes on live chat, within hours on email. A clear path to reach a human when AI or self-service can’t help. Automated confirmations that set expectations, even when a real reply takes longer.

AI has shifted what’s possible here. Tools that can draft first responses, categorize incoming messages, and route to the right person mean you can respond faster without adding staff. But AI that gives the wrong answer fast is worse than a slower human who gets it right — so the goal is speed with accuracy, not speed at all costs.

Accessibility

Accessibility is about making it easy for customers to get what they need. This includes:

• Finding your support channels. Is contact info buried in a footer? Is live chat available on pages where people have questions?
• Getting help without authenticating through three screens. How many clicks between “I have a problem” and “I’m talking to someone”?
• Using self-service when they prefer to. Is your help center actually helpful, or is it a dumping ground for old articles?
• Communicating in the channel they prefer. Some customers want email. Some want text. Some will only use chat. Serving all of them matters.

Removing friction is often the most impactful CXO activity for growing teams. The smallest annoyances compound into real dissatisfaction.

Why customer experience optimization matters

Good customer experience isn’t just a feel-good initiative. It shows up in the numbers:

Revenue. Deloitte found that customers who have positive experiences spend 140% more than those who have negative ones. Same product, different experience, nearly 2.5x the revenue per customer.

Retention. Happy customers stay longer. In subscription businesses, even a small reduction in churn has a compounding effect on revenue — a 5% improvement in retention can translate to 25–95% more profit over the customer’s lifetime.

Referrals. Every customer tells their friends something about you, one way or another. Make sure it’s something you want repeated.

Word of mouth resilience. When something goes wrong (and it will), customers with strong experience loyalty give you the benefit of the doubt. Customers who already felt mistreated use the incident as an excuse to leave.

The business case for CXO isn’t soft. It’s some of the hardest-dollar value work your team can do.

The hard parts (and how to handle them)

Customer experience optimization sounds straightforward on paper. In practice, three things consistently make it hard.

Getting to the data

You can’t improve what you can’t measure. But most teams discover that their customer data is scattered across five tools that don’t talk to each other — support tickets in one place, product usage in another, survey responses in a third, revenue data in a fourth.

The fix usually isn’t buying more tools. It’s getting the tools you have to share information. That might mean building a dashboard in Looker or Tableau that pulls from multiple sources. It might mean having your support team log context into your CRM. Or it might mean a weekly meeting where different teams share what they’re seeing in their corner of the customer experience.

Start with the data you actually have. You don’t need perfect data to start spotting trends.

Sustaining the effort

CXO isn’t a project that ends. It’s ongoing work that competes for attention against everything else on your team’s plate. The teams that sustain it do two things: they assign clear ownership (someone whose job includes CXO, not an initiative that’s everyone’s and therefore no one’s), and they build it into regular rhythms (monthly reviews, quarterly goals, standing meetings).

Without those structures, CXO becomes something everyone agrees is important and nobody gets around to.

Choosing the right tools

Tool selection matters more than it seems. The wrong tool creates years of friction. The right tool fades into the background and lets your team focus on the work.

When evaluating CXO tools, involve the teams who’ll actually use them. Your support lead knows what features matter for a shared inbox. Your data lead knows whether the analytics export is usable. Your customer success lead knows whether the CRM integration actually works.

Seven ways to start optimizing your customer experience

Here’s what to actually do, in the order that usually works best.

1. Map your customer journey

Start by drawing out every touchpoint a customer has with your company — from the first ad or blog post they see, through signup, onboarding, regular use, support interactions, renewal, and churn. Include the emotions they likely feel at each stage.

This sounds basic, but most teams have never actually done it. The exercise alone surfaces gaps. “Wait, what happens between day 3 and day 10 of the trial? Nothing?”

2. Collect both quantitative and qualitative data

Quantitative data tells you what is happening — response times, survey scores, churn rates, feature usage. Qualitative data tells you why — verbatim customer feedback, recorded support calls, user interviews, open-text survey responses.

You need both. The numbers tell you where to look. The words tell you what to do about it.

3. Understand the job customers are hiring you to do

The Jobs to Be Done framework is a useful lens. Every customer bought your product to do a specific job — make their team more productive, save time on a recurring task, solve a specific problem. When you understand the job, you can design experiences around helping them get it done faster.

Useful questions to ask real customers:

• What were you trying to accomplish when you signed up?
• What would you have done if we didn’t exist?
• What’s the first real “aha” moment you had using us?

4. Personalize where it matters most

Don’t try to personalize everything. Pick the two or three touchpoints where personalization has the biggest impact:

• Using the customer’s actual use case in onboarding instead of generic tips
• Having support reps see a customer’s full history so they don’t have to re-explain
• Adapting email content based on how the customer uses the product

Small, well-targeted personalization beats broad, shallow personalization every time.

5. Audit your content

Every web page about your company is a touchpoint. Your help center. Your pricing page. Random blog posts from 2019. Community forum threads. If any of it is outdated or wrong, it’s shaping customer perception.

Pick the top 10 pages by traffic and read them honestly. Update what’s wrong. Archive what’s obsolete. Make sure what’s live reflects your current product, positioning, and policies.

6. Run small experiments

You don’t need permission to run experiments. Try two different onboarding email sequences and see which gets better activation. Try two versions of your out-of-office autoresponder and see which gets fewer angry follow-ups. A/B test your help center search.

The goal isn’t statistical significance. The goal is building a habit of trying things, measuring them, and learning.

7. Make consistency a team norm

Consistency isn’t a feature you add. It’s a cultural norm you build and maintain.

Practical moves:

• Shared style guide for tone of voice, word choices, and brand elements
• Shared canned responses so common questions get the same quality answer regardless of who replies
• Shared customer context so anyone responding to a customer can see the full history
• Weekly examples of good replies shared in team channels so everyone calibrates to the same bar

The role of good tools

The best customer experience optimization happens when your team isn’t fighting their tools.

Missive is an email client built for team collaboration. When customer messages — email, SMS, WhatsApp, live chat — all land in one inbox with shared context, a few CXO things get easier:

Consistency becomes the default. Shared canned responses, shared labels, shared history. Anyone can pick up any conversation and continue it like they’ve been handling it all along.

Personalization is trivial. The customer’s full conversation history is right there. The last support issue, the last sales exchange, the internal notes from customer success — all visible to whoever’s replying.

Response time drops. Team inboxes, assignments, and rules get messages to the right person fast. AI-drafted replies for common questions cut response time without sacrificing accuracy.

Cross-channel visibility improves. A customer’s email from last week and their chat from today live in the same conversation. No more asking “did they mention this somewhere else?”

None of this is a replacement for CXO strategy. But good tools remove the friction between strategy and execution.

Customer experience optimization is table stakes

Ten years ago, “customer-centric” was a differentiator. Today, every company claims to be customer-centric. The ones that mean it are the ones investing in real, ongoing optimization work — mapping journeys, collecting both types of data, personalizing smartly, staying consistent, moving fast.

The companies that don’t do this work eventually lose customers to the ones that do. Not all at once, but steadily — one difficult interaction at a time, one friction point at a time, one missed opportunity at a time.

The good news is you don’t have to do everything today. Pick one or two pillars. Pick two or three tactics from this guide. Make them part of how your team works. Then pick the next ones.

Missive is a collaborative email client that helps teams deliver consistent, personalized customer experiences. Shared inboxes, internal chat, assignments, and AI-powered automation — all in one place. Try it free.

CC (carbon copy) sends an email to additional recipients who can all see each other. BCC (blind carbon copy) sends the same copy but hides those recipients from everyone else. Use CC for visibility; use BCC for privacy or for emailing large groups without exposing every address.

Both fields were borrowed from paper-era business letters. “CC” originally referred to a literal carbon copy made on a typewriter. The mechanics have changed and AI has reshaped what teams use these fields for, but the etiquette still holds in 2026: “To” is for action, “CC” is for visibility, “BCC” is for discretion.

Key takeaways

• CC is for visibility, BCC is for privacy. CC lets all recipients see each other. BCC hides the recipient from everyone else. That’s the only functional difference; everything else is etiquette.
• “To” means “please act,” CC means “FYI.” If you need someone to do something, put them in the To field. CC signals they’re being kept in the loop, not that they need to respond.
• BCC has a reply-all trap. If a BCC’d person hits Reply All, their response goes to the sender and all visible recipients, but nobody sees the BCC’d person’s address. This can create confusion if the BCC’d person reveals context they shouldn’t have.
• For teams, shared inboxes beat CC chains. CC was designed for individuals. If you’re CC’ing coworkers on every customer email just to keep them informed, you’ve outgrown it; a shared inbox gives everyone visibility without the clutter.

What does CC mean in email?

CC stands for carbon copy. It’s a field in the email header that lets you send a copy of an email to additional recipients. When someone is CC’d, they can see the full email thread and every other recipient, including other CC’d people.

It’s a common way to keep people informed about a conversation without making them the primary audience. For example, a sales rep at a marketing agency might email a prospect and CC their manager. The manager sees every reply, but isn’t expected to weigh in. They’re there for context.

The technical difference between “To” and “CC” is almost nothing. The difference is convention: “To” is for the people the email is addressed to, CC is for people you want looped in.

What does BCC mean in email?

BCC stands for blind carbon copy. The mechanics are the same as CC, with one change: BCC’d recipients are invisible to everyone else on the thread. Nobody in the To or CC fields knows a BCC recipient exists.

This makes BCC useful in two situations:

1. Mass emails where recipients don’t need to see each other. A company announcing a policy change to 200 customers doesn’t need every customer seeing everyone else’s address. BCC protects everyone’s privacy and prevents the awkward reply-all chains that follow.
2. Privately looping someone in. You might BCC a manager on an email to a difficult client, so they have visibility without the client knowing they’re being watched.

BCC should be used carefully. Using it to quietly include a third party in a private conversation can erode trust if it comes out later, and in some industries (legal, regulated communications) it raises compliance questions.

What’s the difference between CC and BCC?

The main difference is visibility. CC recipients are visible to everyone; BCC recipients are hidden.

When should you CC someone?

CC is the right tool when you want someone to see the conversation, but you don’t need anything from them. Three common cases:

To share context without demanding a response. If you’re emailing a vendor about a billing issue and your coworker in finance should know it’s happening, CC them. They don’t have to reply; they just have a record.

To introduce a new person to an existing thread. When looping someone new into an ongoing conversation, CC’ing them is standard. They see the history and can jump in if they want.

To build a paper trail inside your company. CC’ing a project lead or manager on client communications keeps them informed and creates a reference for later. This is common at accounting firms like KPMG or law firms where project leads want visibility into junior staff’s client-facing emails without taking over.

When should you BCC someone?

BCC has fewer legitimate use cases than CC, and most of them come down to privacy.

Emailing a large group where recipients shouldn’t see each other. Event invites, newsletter blasts, or announcements to a client list. Putting everyone in BCC (and yourself in To) protects privacy and prevents reply-all disasters.

Sending a copy to yourself at another address. If you want a copy of an outgoing email in a separate personal or archive inbox without the recipient seeing it, BCC is the cleanest option.

Quietly looping in a supervisor. Use this one carefully. Occasionally a manager needs visibility on a conversation for oversight reasons (HR, compliance, escalation tracking). BCC keeps them informed without changing the dynamics of the conversation.

When should you not use CC or BCC?

There are three situations where reaching for CC or BCC is a mistake.

When you need a reply or action. CC’d recipients usually assume they don’t need to respond. If you actually need input from someone, put them in the To field. Anything else invites confusion and missed responses.

When you don’t have consent. If the thread contains sensitive information, adding new recipients without checking first is a fast way to lose trust. When in doubt, ask the original sender before looping anyone in.

When you’re CC’ing the same people over and over. If you find yourself CC’ing the same three coworkers on every customer email just so they have visibility, CC is the wrong tool. You’re trying to do shared work through a tool built for point-to-point communication, and everyone’s inboxes are paying for it. More on the alternative below.

What are the alternatives to CC’ing your team?

CC works fine for one-off visibility. It falls apart when “keeping the team in the loop” is a constant, not an exception.

Common symptoms that CC has outgrown its usefulness:

• Every customer email has four people CC’d, and none of them read most of them.
• Coworkers miss important messages because they’re buried under CC clutter (the inverse of inbox zero: everyone’s drowning in mail nobody asked for).
• When someone’s out, nobody knows which CC chains still need a reply.
• Reply-all threads spiral into side conversations that are impossible to follow.

The underlying problem is that CC was designed for individual senders. When a team shares responsibility for an inbox (support@, sales@, info@, or a partner address for a small firm), you need a tool built around shared work, not one that mimics it with CC. Our team email management piece goes deeper on what that shift looks like in practice.

The option most teams settle on is a shared inbox.

Shared inboxes: how they replace CC

In a shared inbox, every member of a team sees the same conversations automatically. Nobody has to CC anyone because everyone already has access. Instead of replying-all to coordinate a response, you discuss the thread internally, where the discussion stays attached to the email itself.

Missive is a collaborative email client built around this pattern. It works like a regular email client for your personal inbox, and then layers shared conversations, internal chat, and assignments on top for the addresses your team handles together.

What that looks like in practice:

• Connect shared addresses alongside personal ones. Your support@, sales@, and info@ addresses live next to your own inbox. Anyone on the team can see incoming emails without forwarding or CC’ing.
• @mention instead of CC. If you want a coworker’s input on a thread, @mention them in an internal chat attached to that conversation. They get notified and join the thread automatically. Nobody else on the email sees the mention; it’s not part of the visible email, just a layer of team discussion.
• Assign responsibility. Instead of “can you take this one?” in a CC’d reply, you assign the conversation to a specific person. It moves to their inbox, and everyone can see it’s theirs.
• Reuse team replies. Common responses live in a shared canned response library the whole team draws from, instead of forwarding old emails or CC’ing someone “for the template.”
• One inbox for every channel. If your team handles customer conversations over SMS, WhatsApp, Instagram, Messenger, or live chat alongside email, they all show up in the same place with the same team collaboration features.

The result is that CC goes back to being what it was originally for: an occasional FYI to someone outside the immediate conversation. Day-to-day team communication stops routing through the CC field entirely.

How are AI email tools changing CC and BCC use in 2026?

The biggest shift in 2026 isn’t about CC etiquette. It’s that AI tools are quietly replacing many of the patterns CC was invented to solve.

Three of those patterns are dissolving:

CC for visibility is becoming "AI summary on demand." Historically, you CC’d a manager so they could see how a client conversation was going. Now an AI email assistant can read every thread in a shared workspace and summarize what’s happening on request: “Brief me on the open conversations with this client.” The manager skips reading 30 CC’d threads and gets the picture in one shot. The CC was a low-bandwidth signal; the AI summary is a high-bandwidth one.

CC for routing is becoming "AI triage." Teams used to CC the person who probably should handle an inbound message, hoping they’d pick it up. Now AI Rules classify incoming mail by intent and assign it to the right teammate without anyone having to add a CC. The routing logic moves from the sender’s discretion to a system the team configures once.

CC for context is becoming "AI search across past threads." Looping someone new into a thread used to mean CC’ing them and forwarding the history. Now the AI can pull relevant prior conversations and contact context directly into the current thread, on demand. Less forwarding, less cluttering of other people’s inboxes.

BCC is changing less because its core use case (privacy and mass sending) doesn’t have an AI alternative. But the “quiet visibility” form of BCC, covertly looping in a manager, is also getting replaced by audit logs and AI summaries in collaborative inboxes. If a team operates in a shared workspace where the AI can summarize on request, there’s less reason to BCC anyone for oversight.

The practical implication: CC isn’t going away, but its centrality is fading. The teams running AI email well in 2026 use CC for what it was originally meant for (the occasional FYI to someone outside the immediate conversation) and let AI handle the routing, summarizing, and context-pulling that CC was getting overloaded with.

FAQ

What’s the purpose of CC in an email?

CC (carbon copy) lets you send a copy of an email to additional recipients who don’t need to take action, but benefit from seeing the conversation. It’s a way to keep people informed, create a paper trail inside a company, or loop in someone new without making them the primary audience.

What’s the difference between CC and BCC with an example?

CC and BCC both send a copy of an email to additional recipients. The difference is visibility. If you CC your manager on an email to a client, the client can see your manager is on the thread. If you BCC your manager on the same email, the client has no idea your manager is included.

Example: You email a vendor asking for an updated quote. You CC your procurement lead so they can follow along (the vendor sees them). You BCC your manager so they have a record for budget approvals (the vendor has no idea).

When should I avoid using CC?

Avoid CC when you actually need a response or action; CC’d people usually assume they don’t have to reply. Also avoid CC’ing the same coworkers repeatedly on routine team communications. That pattern is a sign you need a shared inbox, not more CC chains.

Should I use CC or BCC in email?

Use CC when transparency matters and you want all recipients to see each other. Use BCC when privacy matters, you’re emailing a large group of people who shouldn’t see each other’s addresses, or you need to discreetly loop someone in.

What happens if someone I BCC’d replies to all?

Their reply goes to the sender and every visible recipient (everyone in To and CC). The BCC’d person’s address still doesn’t appear in the message headers, but the content of the reply can give them away. If they reference something only the original email contained, other recipients will realize someone was quietly copied.

Can I tell if I’ve been BCC’d on an email?

Usually no. When you receive a BCC’d email, it arrives like any other message, but your address doesn’t appear in the To or CC fields. Some email clients show a small note like “bcc: you” in the headers, but only you can see it, not the other recipients. If you don’t see your address anywhere in the visible fields but you still got the email, you were BCC’d.

Is it rude to CC someone’s manager?

It depends on context. CC’ing a manager to keep them informed on routine updates is normal at most companies. CC’ing a manager specifically to escalate or pressure someone into responding (sometimes called “CC’ing the boss”) is usually seen as passive-aggressive. If the goal is accountability, a direct conversation is almost always a better move.

Does CC or BCC affect email deliverability?

Not directly, but very large recipient lists in CC or BCC can trigger spam filters or get flagged by your email provider. For sending to big groups (hundreds of recipients), a proper email marketing tool or mailing list is a better option than stuffing addresses into BCC. It also gives you unsubscribe handling and bounce tracking, both of which matter for staying out of spam folders.

Does CC work the same way in Gmail and Outlook?

Yes, the mechanics are identical across every modern email client. CC and BCC are part of the underlying email protocol (defined in RFC 5322), so Gmail, Outlook, Apple Mail, and any IMAP-based client all handle them the same way: CC recipients are visible in the headers, BCC recipients are not. The differences are interface-level. Gmail and Outlook both hide the CC and BCC fields by default and require you to click to reveal them, which is partly why people forget those fields exist. Other clients put them on screen by default.

What happens to someone after you CC them?

The CC’d person receives the email in their normal inbox, just like the people in the To field. They can see every other recipient (To and CC) and can reply or reply-all. Most email clients don’t visually distinguish a CC’d email from a directly addressed one in the inbox list. Convention says CC’d recipients aren’t expected to respond, but the email itself doesn’t enforce that; if they hit Reply or Reply All, their reply behaves like any other.

How do AI email tools handle CC and BCC in 2026?

AI email assistants treat CC and BCC the same way humans do: they read the conversation, see who’s on it, and consider that context when drafting replies or routing. The bigger change is that AI tools are reducing the need to CC at all. AI Rules can route mail based on intent (no need to CC the right person), AI assistants can summarize ongoing conversations on demand (no need to CC for visibility), and shared inboxes with AI search can pull context from prior threads (no need to CC for history). The AI tools don’t change what CC does; they make many of the reasons to use it less necessary. Our guide to using AI in your email inbox covers the patterns in more detail.

Missive is a collaborative email client built for teams that have outgrown CC. Connect your team’s shared addresses, discuss conversations internally, and handle email, SMS, WhatsApp, and more from one place. Try Missive free.

Not long ago, I came across a company whose support team was drowning in tickets.

Their solution to handling the overwhelming volume of customer requests was… particular.

All incoming tickets received outside business hours were automatically closed, with an auto-reply asking the customer to contact the support team again during business hours.

That’s a sure way to a negative experience for your customers, and it reflects horribly on your brand.

Bad customer service is still far more common than it should be, which got us asking: what are some examples of horrible customer service?

Sometimes it’s easiest to learn about what your customer service team should do by looking at times when other teams made the wrong call. Negative examples, if you will.

So if you’re curious to learn how your business can be customer-centric and consistently deliver excellent customer service, read on for examples of terrible customer service interactions, and tips on how to turn them around.

What is bad customer service?

Bad customer service is a support interaction that doesn’t meet a customer’s expectations. Excessive delays in responding to an inquiry, rude or unhelpful behavior from customer service representatives, mishandling customer complaints, and not fully resolving a problem are all examples of inadequate customer support.

That’s a subjective definition, and there’s no way around that. Whether an interaction with a customer service rep is good or bad depends on what a customer expects.

But on the other hand, some customer interactions are just flat out bad. Take obscenely long hold times or rude agents, for example.

These things are bad for business, but they happen all the time.

And that’s despite the considerable impact that customer service has on business. 68% of customers will willingly pay more for products from brands known to offer a great customer experience. Great experiences increase revenue, boost retention, and improve customer satisfaction.

Or look at it the other way: 65% of customers have switched to a different brand after a bad experience. Bad customer support increases churn and hurts your bottom line.

That’s why you need a sound customer service strategy: because in today’s competitive landscape, your company can’t afford poor customer service.

5 clear examples of bad customer service

Below, five common examples of poor customer service along with tips on how to make them better:

1. Support agents not addressing a customer’s real concern
2. Prioritizing company policy over customer needs
3. Displaying a lack of empathy or rude behavior
4. Making customers wait too long
5. Making it hard to access support channels

1. Support agents not addressing a customer’s real concern

In an ideal world, customers would ask for exactly what they need in terms your support agents can understand.

That’s not what usually happens in a real interaction.

Customers describe situations based on their own understanding. They share the symptoms as they see them, and your support team has to play the role of a doctor identifying the root cause of their pain.

That’s why learning to ask good questions and read between the lines are key customer service skills.

Here’s an example from a recent support ticket at a bank:

A worried customer contacted her bank’s customer service department. Her card purchases were being declined, despite having a positive balance in her account. She feared her money was blocked or, worse, lost.

In response, the customer service rep shared a knowledge base article about existing limits on the number of card transactions. The article wasn’t exactly wrong, she had exceeded the number of transactions, but the agent completely missed the real pain point. The source of the customer’s concern was whether she’d lost access to her money, and some reassurance would have transformed the interaction.

How to fix or avoid this issue:

Train agents to use critical thinking and ask great questions. That’s how they’ll pick up on what customers need, even when they don’t say it directly. In the interaction above, the bank employee should have addressed the primary concern, reassured her that the money wasn’t blocked, and informed her when the transaction limit would reset.

Other tactical tips to improve in this area:

• Monitor customer conversations through a quality assurance program to ensure they meet your standards. If agents are failing to identify root causes or address all of a customer’s concerns, give them extra coaching or try role-playing complicated customer scenarios.
• Encourage frontline staff to truly listen. This often means your customer service KPIs, like handle time or resolution time, shouldn’t be overly aggressive. Spending extra time to ensure an issue is fully resolved pays off in customer loyalty and fewer follow-up conversations.

2. Prioritizing company policy over customer needs

Bruce Lee famously encouraged his students to “Be water, my friend.” He recognized the importance of adapting based on the situation at hand.

Sure, policies and guidelines are there to be followed. They’re crucial in keeping departments on the same page and making operations run smoothly.

But a strict or inflexible process can also be harmful.

Let’s say one of your biggest customers contacts you because they need to make a return, but they happened to miss the deadline by a week. They’ve spent a lot of money with your brand, and they also happen to be an influencer in your industry.

But their call gets routed to a new support rep, who opts to follow the return policy by the book, explaining that the customer is ineligible for a refund. That puts the customer in an awkward spot: they can push for an exception, share the bad experience publicly, or suffer in silence.

A knowledgeable agent would recognize that keeping this particular customer happy is more important than following the standard process.

How to fix or avoid this issue:

Empower your frontline staff. Knowledgeable customer service reps can recognize outdated processes that no longer serve the business. They can also identify situations that are the exception to the rule.

Other ideas:

• Regularly audit your existing policies to adjust or eliminate ones that no longer serve your business well.
• Segment customers in your CRM so you can identify customers needing a VIP experience and route their tickets to specific team members.

3. Displaying a lack of empathy or rude behavior

Frontline staff should never demean customers or display brash or sarcastic attitudes. The same goes for showing apathy or simply displaying no interest in solving a customer’s issues.

Unfortunately, it happens.

A full 73% of customers surveyed by chatbot and AI solution provider Netomi reported being on the receiving end of rudeness from a customer service agent.

This actually happened to me personally. My wife ordered a new area rug online. It ended up being the wrong size, so she initiated a return. The rug was so large that it needed to be picked up by a third-party logistics service, and she waited two weeks to hear from them.

Silence.

After calling the logistics service, she was told there was no record of her request. She tried again, and after several more days of silence, she called back the company she’d purchased from.

The customer service rep gave her the runaround, ultimately telling her it was her fault the return had stalled because she had waited too long, even though their system had failed to notify the logistics service of the request.

How to fix or avoid this issue:

The moment a customer takes the time to contact your support team, they’re already frustrated. Opening the conversation with empathy and communicating a willingness to resolve their problem goes a long way.

To help with this:

• Focus on hiring people who display a high degree of emotional intelligence and communicate with empathy. Role-playing difficult conversations can help surface these skills.
• Equip your support team with strategies to keep calm when dealing with rude customers.

4. Making customers wait too long

Long wait times are a classic example of subpar customer support. They’re a great way to create frustrated customers and build a negative brand reputation.

If you’re curious how it plays out, there are entire Reddit threads about how long consumers have waited on hold.

You’ll read about a customer trying to cancel their phone company and waiting 85 minutes on the phone. Or the 42 minutes it took to book a doctor’s appointment.

That’s about 84 minutes and 41 minutes longer than customers should be waiting.

An excessive response time is only made worse by having to repeat yourself across multiple agents. In a recent survey, almost two-thirds of US adults said valuing their time is the most important thing a brand can do to provide a good customer service experience.

How to fix or avoid this issue:

Reduce your hold times and respond faster. The right approach depends on your situation. A few ideas:

• Find and improve processes slowing your team down. Intelligent conversation routing is essential to speedy service. Use support automation to improve speed and efficiency, for example, by routing specific tickets to qualified agents without manual work.
• Use canned responses or templates. Missive lets you reply faster with pre-written snippets or templates that still allow for personalization through custom variables.
• Offer a callback option. Long hold times are never ideal, but offering a callback at least gives customers the option of getting off the phone and moving on with their lives while they wait to hear from your team.
• Adjust your hours or staffing. When your agents are spread too thin, customers wait longer. Reducing operating hours might sound negative, but if it dramatically improves the experience during those hours, it often goes over well. Alternatively, hiring more agents or adjusting shifts can make a big difference.

5. Making it hard to access support channels

Is anything worse than struggling to reach a business when you need help?

Comcast/Xfinity is infamous for this, as Reddit threads like this show. Here’s a snippet from one user:

“I asked to cancel (which took 4 tries as it ‘accidentally’ kept hanging up on me in the process..) and I said the same to them. They offered $75 at first and I said no. They then offered $45. I thought about it, but they said that’s only for a year then it’s back to the ‘regular rate’ I told them to cancel it then. Had my fiancée sign up immediately after that, and now we are locked in at $30 for two years.”

Is it possible that the phone system hung up on them four times? Technically, yes. But it’s highly unlikely.

Whether it’s unhelpful support agents, a chatbot that gets users caught in a loop, or burying your contact form deep in your help center, situations like these are incredibly frustrating. While offering good self-service is a critical part of a modern customer service strategy, always make it easy for users to get human help when they need it.

How to fix or avoid this issue:

Whatever communication channels your support team offers, make them easy to find and access. Customers contact you when they have problems, don’t create additional problems by making it hard to reach your team.

Tactical tips:

• Use software that enables teamwork. Your support team can handle tickets much faster by working on a collaborative platform like Missive, which includes features like tagging teammates as observers and real-time collaboration on replies.
• Offer support where your customers are. If most of your sales come through social media, offer support on social. If you have a mobile app, embed support channels right in your app.

The underlying causes of poor customer service

We’ve seen examples of inadequate customer support and how to improve it. It’s tough to deliver a consistently great experience. It takes hard work and intentionality.

Across the board, there are a number of underlying reasons why bad customer experiences are still so prevalent:

• Inadequate training. Without properly training frontline staff, you risk agents offering lousy service. Your team might even be providing insufficient support without you knowing, which is why quality assurance is such a crucial part of support operations.
• Low employee morale. Don’t expect excellent customer support from unmotivated employees. In a survey, about 75% of employees said that workplace culture affects their ability to serve customers.
• Operational inefficiencies. Cumbersome processes and outdated systems impact your team’s ability to serve customers quickly and reliably.
• Lack of automation. Excessive reliance on manual work isn’t scalable. Companies often deliver great service when their customer base is small, then struggle to maintain that quality when they grow.
• Lack of omni-channel support. Forcing users to use a specific contact channel risks creating frustration and increases customer effort.
• Poor customer feedback handling. Ignoring or mishandling customer feedback leads to customer resentment and negative reviews. It also robs your organization of an opportunity to learn and improve.

Great customer service is a game-changer

Negative customer experiences are damaging to your business. Your customers are your company’s most important resource, and building out systems that enable you to support them well won’t happen by accident.

At the same time, your customer service processes will always be evolving. This work is never done, so don’t focus on getting across a finish line that doesn’t exist.

Instead, make it a regular part of your routine to audit your customer experience and analyze customer feedback. By creating feedback loops that enable you to continually improve, you’ll build a flexible customer service operation that your customers can rely on.

Frequently asked questions

What are the main types of bad customer service?

The most common forms of bad customer service are: long wait times, unhelpful or rude agents, rigid policy enforcement over customer needs, support channels that are hard to find or use, and agents who don’t address the customer’s actual problem. Most specific bad experiences fall into one of these five buckets.

What’s the biggest cause of bad customer service?

Inadequate training and poor staffing are usually the root causes. Agents can’t deliver great service without the skills to read between the lines, the authority to make judgment calls, or enough time in the day to actually handle the queue well. Most “bad agent” stories are actually “bad system” stories in disguise.

How do you recover from a bad customer service interaction?

Acknowledge the issue directly, apologize sincerely (without making excuses), fix the root problem, and offer a tangible gesture of goodwill where appropriate. The recovery itself can sometimes produce a more loyal customer than a smooth original experience, but only if it’s handled with genuine accountability.

What’s the real cost of bad customer service?

Research consistently finds that about 65% of customers switch brands after a bad experience. The direct cost is lost revenue from that customer, but the compounding cost is everyone they tell, and increasingly, everything they post online. One bad review often costs more than the revenue from the original interaction.

How do you train agents to avoid these mistakes?

The highest-leverage moves are: role-playing difficult conversations, coaching on listening skills (not just scripts), empowering agents to make exceptions to policy when warranted, and setting response-time KPIs that don’t penalize spending extra time on genuinely hard cases. Most bad service comes from agents following process correctly; the process itself is usually the problem.

There’s a saying in the support world: no one majors in customer service.

There’s no single educational or career path that prepares you specifically for this kind of work. Most of us take a winding professional journey before landing in a support role, and we pick up the soft skills that define great customer service along the way, sometimes formally but often through direct exposure to customer-facing jobs.

Whether you’re new to support or a career customer service professional, this piece covers the skills that matter most, why they matter, and how to build them.

What are soft skills, really?

Soft skills are usually described as the counterpart to “hard” skills, things like communication, empathy, and emotional intelligence as opposed to technical competencies like coding or accounting. The common framing is that hard skills are measurable and soft skills are abstract.

That framing doesn’t hold up well when you actually look at customer service.

There’s nothing soft about the skills a support agent needs to defuse an angry customer on a phone call, guide a non-technical user through a troubleshooting process without condescension, or stay composed through a sixteen-email thread about a billing error. Many software engineers would not last a single shift on a support queue.

And the measurement argument falls apart too:

• A high customer satisfaction (CSAT) rating is a measurement of your team’s empathy, care, and communication skills.
• A high bug-fix-and-ship rate traceable to customer reports is a measurement of your support team’s ability to advocate effectively with engineering.
• A strong Net Promoter Score (NPS) reflects your team’s listening skills and their ability to anticipate what customers need.
• A forgiving customer base after a major outage? That’s a measurement of the goodwill your support team has built through positive attitude and de-escalation work during the normal times.

Soft skills are measurable. They’re also the skills that most directly shape customer perception of your brand.

Why soft skills matter commercially

A few numbers that hold up consistently across years of customer experience research:

• Customers who have a good customer experience are likely to spend meaningfully more than customers who have a bad one.
• The vast majority of customers cite customer service as a factor in their loyalty to a brand, most studies put it above 90%.
• Roughly two-thirds of customer churn comes down to poor service, not product problems.
• A significant share of customers have ended a service conversation mid-flow out of frustration at some point.

All of these are direct consequences of soft skills in action, or their absence. Great agents calm frustrated customers; mediocre ones inflame them. Skilled listeners catch the real issue; rushed ones miss it.

What are the top 5 soft skills for customer service?

If you only have time for five, these are the ones to hire for and train on:

1. Empathy: the ability to genuinely understand what the customer is experiencing.
2. Active listening: picking up on what’s said and what isn’t, and responding to the real question.
3. Clear communication: explaining complex things in plain language, adjusted to the customer’s level.
4. Patience: staying steady through slow, frustrating, or repetitive conversations.
5. Problem-solving: turning curiosity about a problem into a resolution, not just a response.

The deeper list below goes further, but if you’re setting up hiring criteria or a training curriculum from scratch, these five cover most of what matters.

The 8 soft skills that matter most

1. Empathy, compassion, and patience

These three are so tightly linked that separating them is artificial. Customers contacting support are often in moments of real frustration or need. They’re not at their best, and they’re not obligated to be.

Empathy lets you understand the problem from their side. Compassion gives you the patience to stay in that headspace even when the problem is your tenth of the day. Patience lets you guide a customer through a solution without condescension, no matter how technical the gap.

The customer doesn’t care about your metrics. They care about whether they feel heard. Empathy is the skill that makes them feel heard.

2. De-escalation and conflict resolution

Most customers aren’t hostile. They’re frustrated, stressed, or dealing with something underneath the surface that you’re not privy to. If they’ve had bad experiences with other companies, they may arrive conditioned to expect the same from you.

De-escalation is the skill of absorbing someone’s emotional state without absorbing the anger. It’s staying calm, acknowledging frustration genuinely, and redirecting toward a path forward without making the customer feel dismissed.

The quieter version of this skill, and maybe the more important one, is not taking it personally. When a customer is sharp with you, it’s almost never about you. Knowing that lets you respond to the situation instead of reacting to the tone.

3. Positive attitude and friendliness

Customer perception forms fast. When customers are frustrated or a problem can’t be solved immediately, a friendly tone can turn an interaction around more than almost anything else.

A concrete example: reframing from negative to positive.

Instead of “I’m sorry, I can’t offer you a refund,” try “I can get that product replaced for you, would that help?”

The second version offers a path forward and invites collaboration. The first leaves the customer at a dead end with nowhere to go.

The same applies to channel. Warmth in your voice on a phone call, or a well-placed emoji in a chat message, genuinely lands. Customers can tell when you’re engaged versus going through the motions.

4. Effective verbal and written communication

This is the job. Clear communication means your message gets across without the customer needing to interpret it. It means pacing your explanations to the customer’s level. It means knowing when to use a reply template as a starting point and when to write fresh. It also means following basic email etiquette on the channels where customers expect professionalism.

Whatever channel you’re on (phone, chat, email, SMS, WhatsApp), communication skills are what turn intent into outcome. A technically correct answer delivered poorly will leave the customer more confused than before. A plain-language answer from someone who clearly understood the problem lands cleanly.

5. Active listening and attentiveness

There’s a difference between hearing and listening. Active listening means paying attention not just to what the customer says but to what they’re not saying, how they phrase things, and what’s under the surface of the question.

Active listeners ask fewer but better questions. They don’t make customers repeat themselves. They notice when a question is standing in for a bigger problem.

A common tell of passive listening: the agent who immediately starts troubleshooting the wrong thing because they heard a keyword and pattern-matched. Active listeners wait until they actually understand the problem before offering a solution.

6. Curiosity, adaptability, and resilience

Support agents regularly run into situations they’ve never encountered. A new bug, an edge case, a feature used in a way no one thought of. The difference between a good agent and a great one is how they respond to not knowing.

Curious agents dig in. They approach unfamiliar problems with “let me figure this out” rather than “let me deflect this.” Adaptable agents adjust when their first theory turns out to be wrong. Resilient agents stay functional at the end of a long day when a P1 lands in their queue.

You can’t train curiosity exactly, but you can hire for it and reinforce it by celebrating the deep dives.

7. Problem-solving and resourcefulness

Curiosity gets you interested in a problem. Problem-solving gets it resolved.

The best agents have a methodology, a reliable way to narrow down what’s happening when something goes wrong. They know which tools to check, which logs to read, which teammate to ask. They know when to try a quick fix versus when to escalate to engineering.

Resourcefulness is the adjacent skill: knowing where information lives, who holds it, and how to get to it without burning an hour on Slack.

8. Ownership and advocacy

Support agents handle dozens of conversations a day. Each customer, though, only interacts with you once (or rarely). What’s routine for you is rare for them.

Ownership means the agent treats each customer’s issue as their issue, not just a ticket. It means following up on escalated issues instead of marking them closed and moving on. It means representing the customer’s experience internally when you share feedback with product or engineering.

Advocacy is the outward version of ownership. Great support teams don’t just solve customer problems, they make sure the company knows about patterns that matter. The agent who flags that ten customers asked about the same bug this week is doing advocacy work. That’s how support teams become engines of product improvement instead of ticket-closing machines.

How to build soft customer service skills

If you’re looking at this list and thinking “I want to work on some of these,” you’re in good company, everyone at every level of customer service has growth areas here.

A few ways that actually work:

Structured courses and training. Platforms like LinkedIn Learning, Coursera, Udemy, and Skillshare have solid content on empathy, active listening, and conflict resolution. They’re not magic, but they give you vocabulary and frameworks for practicing.

Books that hold up. A few that still get recommended:

• Never Lose a Customer Again by Joey Coleman
• The Service Culture Handbook by Jeff Toister
• Exceptional Customer Service by Lisa Ford

Peer feedback and mentorship. The people you work with are often your best resource. Regular peer review of customer conversations, low stakes, high candor, builds pattern recognition fast. Role-playing tough customer scenarios in a safe setting lets you try new approaches without a real customer on the line.

Shadowing and reverse-shadowing. Watching senior agents handle calls or chats teaches what you can’t get from a book. Having senior agents watch you teaches what you can’t see in yourself.

Recording and reviewing your own work. With permission and for training purposes, reviewing your own customer conversations surfaces habits you don’t know you have. Most agents who do this find at least one pattern they wish they hadn’t.

The hard skills / soft skills balance

The last word on this: there’s no real boundary between hard and soft skills in customer service. They feed each other constantly.

• You keep customers happy by understanding their problems, solving them, and listening to their feedback. That’s a mix of communication (soft), product knowledge (hard), empathy (soft), and troubleshooting (hard) on every single ticket.
• You keep engineering happy by translating customer needs into bug reports and feature requests that are technically actionable. That requires product depth and the ability to communicate it.
• You keep your team happy by being someone worth working with. That’s soft skills through and through.

The best support professionals have both. Looking at any great support team, the people who stand out combine technical fluency with the human skills to deploy that fluency well.

That’s not a nice-to-have. That’s the job.

A quick note on the “7 Cs of customer service”

You’ll occasionally see lists of the “7 Cs of customer service” floating around: clarity, consistency, care, competency, choice, courtesy, and communication. It’s a useful mnemonic if it helps, but don’t get hung up on matching a specific framework. The actual work is building the underlying skills (the ones covered above), not memorizing the acronym. Pick whichever framework helps your team internalize the point.

Missive is a collaborative email client built for teams that take customer service seriously. Shared inboxes, internal chat on every conversation, and multi-channel support across email, SMS, WhatsApp, and live chat. Free for up to 3 users, try it free.