The calm advantage
At Fernand, we spend a lot of time talking with support teams. Not VP of Operations, Team Leads or metrics folks, but the people on the front lines: those who open their laptops each morning, sip their coffee, and dive into a queue of unresolved questions, complaints, and confusion.
Many of these teams work at fast-growing SaaS companies. They have good tools. They care deeply. And yet, they often feel like they’re drowning.
A support agent recently told us, “I can’t remember the last time I felt like I was ahead. It always feels like we’re catching up.”
That’s not just tiring. It’s costly. For morale, for performance, and for the long-term health of the team.
What if the answer isn’t to go faster, but to go calmer?
The hidden cost of stress in support
Customer support has a stress problem, and most of us are too busy to talk about it.
In a recent industry survey, 92 percent of support agents reported experiencing anxiety at work. That’s not surprising when you consider the environment. Conversations pile up with no natural end in sight. Notifications ping constantly. Every interaction is measured, timed, categorized, and scored. And somewhere in all of that, a human being is just trying to help another human being.
It’s no wonder so many people burn out. Support can feel less like problem-solving and more like treading water in a storm, head just above the surface, inbox never really empty.
And yet, this pressure is often invisible. The stress shows up in small ways: shorter replies, dropped threads, that creeping sense of resentment or detachment. In the long run, it leads to churn. Customer churn, but even more terribly: team churn.
Why calm matters more than we think
Calm isn’t the absence of productivity. It’s the environment in which good work can actually happen.
Picture this: You’ve just opened your inbox. It’s quiet. You know what to focus on first. Your workspace is simple, almost spartan. There’s no noise competing for your attention. You open the next conversation. A customer is confused about their invoice. You take a breath, respond with clarity, and even add a touch of kindness. The customer replies, grateful. You resolve the case and move on.
Now compare that to the more common experience: jumping between tabs, glancing at Slack every ten seconds, toggling between tools, wondering which ticket to prioritize next, and replying just fast enough to stay afloat.
Calm doesn’t just feel better. It makes people better at their jobs. When agents aren’t constantly distracted, they can actually think. And when they can think, they can help. This philosophy echoes what Jason Fried and David Heinemeier Hansson argue in “It Doesn’t Have to Be Crazy at Work”: that chaos and urgency are not prerequisites for success, but symptoms of poor systems. They make the case for a calm company, where focus, clarity, and reasonable expectations lead not only to better work, but to a better life. The same holds true in support. When calm becomes the norm, quality follows.
The everyday chaos that gets in the way
Despite the best intentions, most support setups are not built for focus. They are built for throughput.
Recommended by LinkedIn
Agents often deal with bloated interfaces filled with widgets, tags, SLAs, timers, clunky integrations and dashboards. There’s rarely a clear sense of progress, just a stream of incoming noise.
This leads to a culture of constant triage where urgency replaces clarity and where people are incentivized to work fast, not well.
Cultivating calm in a noisy world
The good news? Calm doesn’t require a full systems overhaul. In fact, it starts with mindset and small shifts in how we design support work.
One of the simplest changes is to embrace visible progress. Something as basic as a queue that shrinks as you move through it, or a confirmation that says “well done, this is resolved,” can go a long way in restoring a sense of control
Another shift is tone. Many teams are moving away from robotic scripts and embracing more human, conversational language. It sounds counterintuitive, but taking the time to write one thoughtful, clear message often leads to faster resolution than three templated ones.
Expectation-setting is another calm lever. When customers know when they’ll hear back, even if it’s in a few hours, they relax. So do the agents.
And finally, less is more. The fewer tools, tabs, and notifications involved, the easier it becomes to focus. This is where design and product choices matter deeply.
When we built Fernand, our goal wasn’t to reinvent support from scratch. It was to remove the noise, and finally empower the people spending 8 hours a day answering customer conversations to have an experience truly dedicated to empowering them, not their managers.
One of our favorite features is the Bonjour screen. Each morning, agents are greeted with a fresh view, no lingering leftovers from yesterday, no noisy ticket numbers, just the conversations that need attention today. Like asking a colleague how support is doing today. It sets the tone, gently, for focus.
We also designed Fernand around the principle of one thing at a time. No chaotic multiviews. No toggling between half-replied tickets. You work through one conversation, with full context, until it’s done. Then, and only then, do you move to the next.
To close the loop, progress in Fernand is always visible. Teams know exactly what’s pending, what’s resolved, and what might need a second look. Once all conversations in the current session are handled, agents are rewarded with a clean, elegant inbox zero moment ; reminiscent of the clarity-focused experience in Superhuman. It’s a subtle design choice, but a powerful one. Because when progress is visible, the mind can rest. And with clarity comes calm.
It’s not just a gimmick or a nicer interface. It’s a shift in how support can feel.
The ripple effect of Calm
When calm becomes part of your support culture, everything changes, and not just for your team.
Customers notice. They feel the clarity and presence in your responses. They trust you more. They stay longer. And internally, your team becomes more resilient, more thoughtful, and less likely to burn out.
In the end, calm is not a luxury. It’s a strategy. A quiet one, maybe. But a powerful one.
Nice work, this looks interesting and thoughtfully built.
Great read!
I enjoyed reading this. Sometimes, it feels like it takes 30 minutes to write a simple 5-minute email. We’re so busy trying to sound professional or over-relying on AI that we lose our own voice. We end up spending more time and energy on tweaking prompts—"use my voice," "make it more polite," "be more personable"—and after so many tries, we just settle for something that doesn’t quite feel right because "we’ve taken too long anyway." This whole cycle makes you wonder: where’s the fine line between using AI to remove manual processes and just doing the work ourselves? In customer service, I believe it's a critical question. I think another powerful way to introduce calm is through Expectation Management. It’s all about proactively creating simple, clear documentation like FAQs and SOPs. These documents do more than just provide information; they reduce customer complaints by telling them exactly what they’re paying for and what to expect. If something goes wrong, the documentation explains why and what they should do to fix it. It also gives support agents a solid reference point, making the entire process feel much calmer and more predictable.