Want to know how much website downtime costs, and the impact it can have on your business?
Find out everything you need to know in our new uptime monitoring whitepaper 2021
Here at CakeHQ we do try to please everyone, but that is a difficult task when everyone has a different idea of what is idea for them. The single thing we get the most comments about is our outward email alert templates – some people want to have them in a pretty table, some prefer just the details and nothing else. Some would like to put their company logo on the emails and others want no images at all. With this in mind we got thinking – how can we solve this seemingly unsolvable problem?
It’s simple – Email Templating!
From today all our superior and business plan users can design how their email alerts look using the full power of HTML. This means you can design the emails exactly how you want them to look and even ensure they keep with your companies branding when your team gets an alert.
To edit a template simply go to your “Account Details” tab within StatusCake and select the new “Email Templates” button on the top row. The Email Templates page will list all current email templates we use along with their status (“Edited” or “Not Edited”). You can then jump right into a HTML editor with a live preview of what your email will look like.
In the past few hours we’ve also pushed forward a wide range of improvements, bug fixes and general tweaks to ensure a great service. If you have any comments or questions on this latest feature then please do get in touch!
James Barnes
Share this
More from StatusCake
Alerting Is a Socio-Technical System
3 min read In the previous posts, we’ve looked at how alert noise emerges from design decisions, why notification lists fail to create accountability, and why alerts only work when they’re designed around a clear outcome. Taken together, these ideas point to a broader conclusion. That alerting is not just a technical system, it’s a socio-technical one. Alerting
James Barnes
February 25, 2026
Designing Alerts for Action
3 min read In the first two posts of this series, we explored how alert noise emerges from design decisions, and why notification lists fail to create accountability when responsibility is unclear. There’s a deeper issue underneath both of those problems. Many alerting systems are designed without being clear about the outcome they’re meant to produce. When teams
James Barnes
February 18, 2026
A Notification List Is Not a Team
3 min read In the previous post, we looked at how alert noise is rarely accidental. It’s usually the result of sensible decisions layered over time, until responsibility becomes diffuse and response slows. One of the most persistent assumptions behind this pattern is simple. If enough people are notified, someone will take responsibility. After more than fourteen years
James Barnes
February 11, 2026
Alert Noise Isn’t an Accident — It’s a Design Decision
3 min read In a previous post, The Incident Checklist: Reducing Cognitive Load When It Matters Most, we explored how incidents stop being purely technical problems and become human ones. These are moments where decision-making under pressure and cognitive load matter more than perfect root cause analysis. When systems don’t support people clearly in those moments, teams compensate.
James Barnes
February 4, 2026
The Incident Checklist: Reducing Cognitive Load When It Matters Most
4 min read In the previous post, we looked at what happens after detection; when incidents stop being purely technical problems and become human ones, with cognitive load as the real constraint. This post assumes that context. The question here is simpler and more practical. What actually helps teams think clearly and act well once things are already
James Barnes
January 28, 2026
When Things Go Wrong, Systems Should Help Humans — Not Fight Them
3 min read In the previous post, we explored how AI accelerates delivery and compresses the time between change and user impact. As velocity increases, knowing that something has gone wrong before users do becomes a critical capability. But detection is only the beginning. Once alerts fire and dashboards light up, humans still have to interpret what’s happening,
James Barnes
January 21, 2026