Site email: messages your site sends

#What site email is for

Site email carries the messages your site's own features write, one person at a time: a confirmation after someone books, a note to you when a new record is saved, a reply to an application. The switch itself says it: “Not for newsletters or mailings.”

Several other emails around your site come from Briks itself and don't touch the allowance:

#Switch it on

#The sending address

Every site sends from an address on emails.briks.live named after its site address, with your project's name as the sender's name. Mail can't be sent from your own domain, even once you've connected it.

#Why replies should reach your own inbox

Nobody reads the sending address. When someone replies to a booking confirmation (“Can I move to Thursday?”), that reply goes wherever Replies go to points. Left on The owner, it reaches the person who created the project, or the first Owner if they've left. For a business with a shared inbox, add that inbox as a verified address and choose it.

The list holds the same verified addresses as the chatbot's Hand off to: members' sign-in addresses, and outside addresses confirmed on the Chatbot tab. When a message sets its own reply address, such as a note to you that should reply to the visitor, that one is used instead.

#Your monthly allowance

The allowance is one for the whole workspace, shared by all its sites. The count starts again on the 1st of each month (UTC), and only sent messages count. This month, all your sites, on the Emails view, shows how many your sites have sent of the allowance and how many came from this site, and the bar turns red at 90 percent.

#Other reasons a message is turned away

• More than 30 messages from the site in one minute: “Too many messages in the last minute. Send fewer at once.”
• More than 3 messages from this site to the same address in an hour, or more than 10 from all your sites to it in a day.
• The same message sent to 20 or more other people in a day. That's a mailing, and site email is for one person at a time.
• An address on your workspace's block list, or on Briks's own list, which takes in addresses that bounced or marked mail as spam. The site is only told the address can't receive email.
• An address whose domain can't receive email.
• Addresses reserved for examples and tests.

Each refusal is recorded with its reason, except the 30 a minute rule, which turns messages away before anything is written. Messages stopped for going too fast are listed as Held; the others as Refused.

#Sent emails

Sent emails lists every email sent for this site in the last 90 days, newest first, 200 to a page: the site's own messages and the ones Briks sends you about it, such as form entries, chat questions, weekly reports and traffic alerts. Each row shows When, its Kind (such as Site email, Test email or Form entry), To, Subject and Status. Refused, held or failed messages show their reason under the status.

• Narrow it. Filter by Status (Sent, Refused, Held or Failed) and by Kind, or search Address or subject.
• Block from a row. The menu at the end of a row blocks that address, or every address at its domain, for the whole workspace.
• Never the words. Only who a message went to, its kind, its subject and what happened are kept.

#Blocked addresses

Blocked addresses apply to every site in your workspace: nothing is sent to them. Under Block an address or domain, type an Email address or domain, add a Reason and an end date in Ends if you like (left empty, it stays until removed), and press Block. The list shows each entry with Blocked by, Reason and Added, and the bin removes it so email can be sent to it again. Addresses Briks itself has blocked that your sites tried to email are listed too, tagged Blocked by Briks, with no reason given.

#Insights

Insights shows this month at a glance: Sent this month, Left this month, Refused and Failed. Under them, Sent each day covers the last thirty days, and Why messages were refused lists this month's reasons, most common first. A sudden run of refusals for one reason is usually the quickest way to spot a feature that's misbehaving.

#Settings

• Download what was sent: when each email was sent, what kind it was, to whom, its subject and whether it went, for the last 90 days, as a file (Download JSON).
• Replace the site's key: New key stops the current key at once. A published site gets the new one straight away; otherwise it gets it at its next publish.
• No clearing. The record of what was sent is kept for 90 days and then removed on its own, so it has no clear button.

The Emails view also has a section headed For the site's code, with the Relay key and Relay address the site sends through. It's there for anyone editing the site's code by hand; when Briks builds a feature that sends email, it connects all of this for you.