Will Cooper
Will Cooper
September 10, 2026
Stay in the know
Get helpful videos

Four rules separate a SharePoint alert email that gets acted on from one that gets archived unread: put the key information in the subject line, keep the body to what happened and what happens next, end with a single next-step link, and format that link to look like a button. None of them require code or special tools, they are writing and formatting decisions made once, when the alert is configured, and they pay on every email the alert ever sends. This article explains each rule and walks through the button formatting step by step.

The configuration of an alert determines whether it sends. The writing determines whether it works.

Your emails are being ignored

Everyone knows that forms trigger emails, and when setting up email alerts for SharePoint we spend almost no time thinking about the content. Something gets thrown together quickly, a link goes at the bottom, done. That is exactly the problem: we give alert emails little thought, and the people receiving them give them even less. Most SharePoint notifications look boring and unimportant, and in inboxes already buried in email, boring and unimportant means ignored.

The cost is not cosmetic. An ignored approval notification is an approval that waits; an ignored task alert is a deadline missed quietly. The process moves at the speed of the people who know it is their turn, and the email is how they find out. (Our companion piece, Nobody's Reading Your Stupid Automated Emails, makes the same argument with less diplomacy.) The good news is that the fix is a matter of craft, not technology, and the craft reduces to four rules.

Rule 1: The subject line is the email

Many users only read the subject line, so the subject line must carry the payload: clearly define what happened, to what, and what is expected. Compare "Item modified in Purchase Requests" with "PR-1174 approved: order laptops by Friday." The first requires opening the email to learn anything; the second has already communicated even if the email is never opened.

The practical technique is to build subjects from column values rather than static text: the request number, the requester, the amount, the new status. An alert configured once with dynamic values produces a specific, scannable subject on every send, and specific subjects also make emails findable in search a month later, which generic subjects never are.

Rule 2: Cut out the fat

Respect the time of your users. The body should describe only what happened and what happens next; everything else lives in SharePoint, one click away. The instinct to dump the whole item into the email, every field, every value, produces a wall the recipient skims past, and you lose your audience along with the result you wanted. The detailed information is in SharePoint; it does not belong in your email.

A useful discipline: draft the body as two short lines, what changed, and what the recipient should do about it, then stop. If a field's value is essential to the decision (the amount on an approval, the deadline on a task), include that field and no others. When the audience genuinely needs a lot of information regularly, the answer is not a longer email but a different format entirely, a daily summary that consolidates many changes into one organized message.

Rule 3: Every email is a call to action

Each alert email exists because someone should do something, so make the next step effortless: always end the email with a link that performs it. Usually that is a link to the edit form or display form of the item in question; sometimes it is a link to the SharePoint list. What matters is that the recipient never has to figure out where to go, the email did that thinking for them.

One link, singular, is the discipline. An email offering three links makes the recipient choose, and choice is friction. Decide which single action the process wants and give that action the spotlight.

Rule 4: Make the link look like a button

Why format the link? Because we are borrowing a technique from email marketing: we are conditioned to take action by clicking a button. A styled button-look draws the eye, signals "this is the point of this email," and measurably improves response over a bare text link, which reads as optional.

Here is a typical unformatted link at the bottom of an alert email. It is not eye catching, and it seems skippable:

Unformatted link

Turning it into a button takes a few steps in the content editor:

  1. Highlight the link and set the font size to 24px.
  2. Set the text as bold.
  3. Choose a background color for the link.
  4. Add three spaces before and after the link text to provide padding.

Formatting in editor

A few extra seconds of formatting produces a button-style link that stands out and pulls the eye exactly where you want the click:

Formatted button

Choose the background color deliberately: your brand color for routine actions, and reserve anything alarming for alerts that are genuinely urgent, so color keeps meaning. And when you are ready to go one step further, Ultimate Forms alerts support real action buttons that perform the update directly from the inbox, approve without even opening SharePoint, which is the same principle carried to its conclusion.

The fifth rule nobody writes down: send less

The four rules make each email better; the surrounding discipline makes the whole system credible. Every unnecessary email an alert sends teaches recipients that your notifications can be skimmed, and that lesson transfers to the necessary ones. Use conditions so alerts fire on the changes that matter, a status reaching a threshold, an assignment changing, not on every edit of every field. Use digests where volume is inherent. The recipient who gets three sharp emails a week from your system reads all three; the one who gets thirty vague ones reads none. Writing better and sending less are the same project: raising the value of the average email that carries your name.

For the design half of the story, branding, layouts, reusable templates shared across the organization, see our guide to designing alert email templates; the four rules here govern what the words say, and the template governs how they look. In summary, for best results: put all key information in the subject line, include only essential information in the body, provide a next-step link at the bottom, and format that link to stand out. Your users will appreciate the streamlined information, and your emails will get the results they were sent for. Remember, all the information is already in SharePoint; your users will click the link when they need more.

Frequently asked questions

Q: How do I make SharePoint alert emails more effective?
A: Four rules: carry the key information in the subject line, keep the body to what happened and what happens next, end with one next-step link, and format that link as a button.
Q: What should an alert email subject line contain?
A: What happened, to what, and what is expected, built from column values: the item number, the person, the amount, the new status. Many recipients read nothing else.
Q: How much detail belongs in the email body?
A: Only what the recipient needs to act: the change and the next step, plus at most the one or two field values essential to the decision. Everything else is one click away in SharePoint.
Q: How do I make a link look like a button in an alert email?
A: In the content editor: highlight the link, set 24px font size, make it bold, choose a background color, and add three spaces before and after the text for padding.
Q: Should an alert email contain more than one link?
A: One action link is best. Multiple links force a choice and dilute the response; decide the single next step the process wants and feature it.
Q: What if recipients need updates on many items?
A: Use a scheduled summary that consolidates changes into one organized email instead of many individual messages, and reserve individual alerts for changes that demand immediate action.
Loading...

Add your comment

Comments are not meant for support. If you experiencing an issue, please open a support request.
General
Relationships between two or more SharePoint lists has always been a major core concept in Ultimate Forms. Using our special Associated Items column, it's easy to set up such relationships. The child items show up inside the parent item form. You can work with them within the parent, adding new ones, modifying and deleting existing ones. One of...
General
Vladi Gubler | March 05, 2025
Need to send data from your SharePoint form directly to your email? This article will guide you through setting up a SharePoint form to email. The form sends collected information straight to your inbox. You’ll learn ways to create the form, configure email notifications, and customize email content. Understanding SharePoint...
General
Will Cooper | September 10, 2026
The key to professional-looking Word print templates in Ultimate Forms is tables. You design an ordinary Word document, place your SharePoint fields in double square brackets like [[Field Name]], and use Word tables to control exactly where every piece of data lands on the page: columns for side-by-side content, merged cells for headers, and...
Build powerful business applications in SharePoint using only your browser.
100% No-Code Solution
It’s never been easier to create, innovate, and share. All you need is your web browser!
Cost-Effective
Address business process pain points immediately. Save time and money.
Fantastic Support Team
In addition to our responsive support team, a wide variety of resources, documentations, tutorials, blogs and webinars is available to you
Popular Solution Templates
Sales Quote Generator
Create, manage and print sales quotes
Guestbook
Structured visitor feedback covering service, facilities, and experience with open-ended comments
Course Enrollment Management System
Real-time seat tracking, automatic enrollment counts, and centralized records
Microsoft partner logo
© 2005-2026 Infowise Solutions Ltd. All rights reserved.
Privacy | Cookie Policy | Accessibility | Cloud SLA