Users can see the following for emails they've sent out through Breeze:
Email addresses that their message was successfully delivered to
Email addresses that opened their message (and an overall open rate percentage)
Email addresses that clicked a link in their message (and an overall click rate percentage)
Email addresses that failed to receive the email
This information can be helpful in making sure the email addresses you have within Breeze are accurate and getting a sense on how engaged your readers are as well as being able to improve your email content for greater engagement. To access this information:
Navigate to "More" > "History" > "Emails."
Select a previous email to view its details.
Click either "Delivered" or "Failed" on the left to view additional information.
If you're having trouble with an email going through, view your deliverability report to look into the status of a specific email. While status messages can vary based on email provider, you should find a status below similar to that listed in the report.
Delivered Your message was successfully delivered to the recipient.
Previously Reported as Spam This recipient previously reported a message from Breeze as spam. We honor that request by no longer attempting to send them emails. To remove this restriction and to email them again:
Navigate to "More" > "History" > "Email"
Find the email that did not send and select "Failed" from the lefthand side.
Find the email marked as "Previously Reported as Spam"
Invalid The recipient's email account does not exist. Check the spelling of the address and try again. Breeze will not attempt to send to this address in the future.1
Bounced Address This message can mean one of two things:
This most often means the recipient's email account does not exist. We recommend double checking that the address is correct. Breeze will not attempt to send to this address in the future.
This error can also mean that the recipient's email provider rejected the email as being potential spam. To resolve this, see "Improving Deliverability" (below).
If you have updated the email address on file there is no additional action required. If you have not edited the email address on file and have verified that it is indeed correct, and you would like to remove this restriction and email them again, please email us with the email address that is not receiving the messages.
When a user sends an email out of Breeze, our backend can see how the receiver interacted with it (open, sent, etc.). It also tells if the recipient marked the email as spam. When a person marks an email that has been sent from Breeze as Spam, that generates a quick scan of the church's account. In the last 30 days, it will determine what percentage of their messages were marked as spam. If it meets a specific percentage, Breeze will block the church's account from sending emails. What are the ranges?The industry standard for Spam is 0.15% — if it’s more than that the church will be blocked. Alternatively, The church will be marked as spam if the church has more than 50 static spam emails in the last 30 days. Breeze will begin monitoring the spam count at 0.05% to see if they can find the root of the issue before 0.15% is reached. What happens when emails are blocked? Primary users will receive an email indicating that their church account has been blocked. Breeze will run an investigation as to the nature of the block and remove the block or take further action as necessary. Best practices for email deliverability and not being marked as spam Unsubscribe option in the email Email only people you know Have an opt-in policy to receive emails from the church/organization.
Users can take steps to improve email deliverability, depending on what provider they are using:
I'm sending from a publicly-available account (e.g. Gmail, Yahoo, AOL, Comcast, Charter, etc).
When Breeze sends email messages as if those messages were coming from a Gmail, Comcast, or another publicly-available email account, the messages are more likely to be flagged as spam. This is because the recipient's mail server can see that even though the message says it's coming from firstname.lastname@example.org, the message didn't actually come from Gmail's servers (because it really came from ours). This is true for any third party emailing on behalf of an address like this.
If you find deliverability begins to suffer because of this, there are two options available:
Move your email account to a private domain name (e.g. change from email@example.com to firstname.lastname@example.org). By having a private domain name, you can tell the domain name that Breeze is allowed to send on its behalf.
Alternatively, you can tell our support team that you would like to enable "Alternate Sending" on your account.1 This will force messages to be sent from a Breeze-owned domain name. Replies will still go to your correct email address.
I'm sending from a private account (e.g. email@example.com, firstname.lastname@example.org, etc.)
If you are sending your messages from a private domain name (e.g. email@example.com), you'll need to adjust the domain's settings to essentially tell it that Breeze is allowed to email on its behalf. To do this, contact your technical administrator and ask them to add the following SPF record to the domain name:
v=spf1 include:email.breezechms.com ~all
Note that if you already have an SPF record, you'll want to add this address to the existing record. Do not create a separate record. Adding a record to an existing record might look something like this (the below example assumes the Google record already existed):
That will inform recipients that our mail server is allowed to email on behalf of your domain name (e.g. firstbaptistchurch.com).
"Alternate Sending" causes mail that you send from Breeze to actually come from a Breeze address. For instance, if your email account is firstname.lastname@example.org, with alternate sending enabled, the address your message actually comes from might be email@example.com. We set the reply-to address to be your actual address (firstname.lastname@example.org) so when recipients reply, those replies go to your inbox as expected.
Here are some things to remember in the community:
Be sensitive to differing political, cultural, denomination and theological beliefs
Be respectful, friendly, and sincere
Use appropriate tone and language
Encourage others, especially new users
Share what you know
Ask for help and help others
Provide constructive, helpful answers and feedback
Read through the “how to post” directions and follow them
Here are some things we do not permit in the community:
Do not post or link to content that violates any person’s privacy rights, including information that directly or indirectly identifies anyone other than yourself;
Do not post or link to information that is deceptive, fraudulent, threatening, libelous, harassing, hateful, offensive or inappropriate;
Do not post or link to content that promotes or encourages illegal activities;
Do not post or link to viruses, bots, worms, trojan horses or other malicious software, or utilize the community to post, link to, generate, distribute or promote any kind of spam;
Do not post or link to content that violates anyone’s intellectual property rights (including copyright, patent, trademark, publicity, moral and other property or proprietary rights) or which you do not have the right to post or link to. You may link to other community content or publicly available Breeze documentation if appropriately attributed and relevant;
Do not misrepresent yourself or lie about your identity or affiliation or falsely imply any association or sponsorship by Breeze;
Do not solicit community members for any commercial purpose;
Do not solicit community members to interact with you outside of the community to obtain support;
Do not solicit community members for their personal or contact information for any reason;
Do not post or link to content that disparages Breeze, its vendors, partners, or affiliates;
Do not spam the community with advertisements or self-promotion;
Do not provide inaccurate answers to questions; if you don't know the answer, it's better not to comment.
We reserve the right to immediately remove any posts that do not conform to our Community Guidelines, without warning. We also reserve the right to temporarily or permanently suspend or bar a user who violates these Community Guidelines.
To report behavior or content that violates or is inconsistent with these Community Guidelines, please contact us.
Feeling conflict? Having a hard time articulating an issue in the Community forum? Feel like things are getting lost in translation? -- Take your question offline, email our Support Heroes directly, we are here to help.