---
title: "Site email: messages your site sends | Briks"
url: https://briks.dev/docs/site-email
description: "Let your site send confirmations and replies from its own address on emails.briks.live, choose where replies go, and track sending against a monthly allowance."
last_updated: 2026-10-08
---

# Site email: messages your site sends

Some features of a site need to send email themselves, such as a booking confirmation to the person who booked. Site email lets them. It's off until you switch it on, unless the site has accounts for its visitors, sends from an address Briks gives your site, and has one monthly allowance shared by all your sites.

7 minute read Checked against the studio on 8 October 2026

## 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:

| Email | Sent by | Uses the allowance |
| --- | --- | --- |
| A booking confirmation your site sends a visitor | Your site, through site email | Yes |
| A note your site sends you when a record is saved | Your site, through site email | Yes |
| Your own test email | Your site, through site email | Yes |
| A message sent through a contact form | Briks, to you | No |
| A question the chatbot passes on | Briks, to your chosen address | No |
| The weekly analytics email and traffic alerts | Briks, to you | No |

## Switch it on

Where

1. Projects
2. Your project
3. Settings
4. Emails

1. Open Emails

   Where: Settings, Emails

   It opens on the **Emails** view, with **Insights**, **Sent emails**, **Blocked addresses** and **Settings** beside it.

2. Turn on sending

   Where: Let the site send email

   Turn the switch on. The first time, Briks also gives your site a private key to send with, so there's nothing else to set up.

3. Check the sender

   Where: Sent from

   Your project's name, and an address made from your site's address on `emails.briks.live`.

4. Choose where replies go

   Where: Replies go to

   **The owner** by default, or any verified address in your workspace.

5. Send yourself a test

   Where: Send a test email

   Click **Send test**. It goes to you and nobody else, and only once your own email address is verified. Three tests an hour at most.

Builds don't switch it on, except for accounts

Briks turns sending on for you only when a site has accounts for its visitors, so their confirmation and reset emails can go, and only if you have not set the switch yourself. Otherwise, until you turn it on, anything the site tries to send is turned away and listed in **Sent emails** as **Refused**, with the reason “Sending email is turned off for this project.”

## 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.

A booking confirmation A pilates studio in Bristol takes class bookings

> Core and Calm asks in the Studio: When someone books a class, email them a confirmation with the class, the time and our address, and send me a note with their name and phone number.

With **Let the site send email** on, both messages go out as Core and Calm, from `corecalm@emails.briks.live`. Each counts once towards the month's allowance.

## 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](https://briks.dev/docs/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

| Plan | Emails a month, all sites together |
| --- | --- |
| Free | 300 |
| Starter | 2,000 |
| Pro | 5,000 |
| Studio | 15,000 |
| Agency | 50,000 |

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.

At the allowance

Once your sites have used the allowance between them, every further message that month is refused, from any of them, not held for later. The feature that tried to send gets an error, and **Sent emails** shows a reason such as “This month's 300 emails, shared by all your sites, are used up. Sending starts again on the 1st.” If you're getting close, an Owner can move to a larger plan in [Billing](https://briks.dev/docs/billing).

## 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.

### Can I send from my own domain?

No. Site email always sends from an address on emails.briks.live. Replies can still reach your own inbox through **Replies go to**.

### Can I send a newsletter?

Not through site email. The same message to 20 or more people in a day is refused. Use a mailing service for newsletters.

### Do refused or failed messages use the allowance?

No. Only sent messages count, your tests included.

### Who can change these settings?

Owners, Admins and Editors can turn sending on or off, set replies, send tests, read **Sent emails** and block addresses. Viewers see the **Emails**, **Insights** and **Settings** views.

## Read next

- [Your site's features **Forms** Add a form to your Briks site, test it in preview, find every entry in the studio, get each one by email in production and pass them on with a webhook.](https://briks.dev/docs/forms)
- [Your site's features **Chatbot** Switch on a chat that answers visitors from your published pages, passes what it cannot answer to a verified email, and keeps every chat for you to read.](https://briks.dev/docs/chatbot)
- [Working on a project **Your site's code** Browse, edit and publish your site's code in the File Explorer on every plan. On a paid plan, download any version as a zip, and see what it leaves out.](https://briks.dev/docs/code)
- [Getting started **Credits and plans** How Briks credits work: holds of 50 and 5, charges for the work done, estimates and builds that wait, what happens at zero, and what each plan includes.](https://briks.dev/docs/credits-and-plans)

Still stuck?

Write to [hello@briks.dev](mailto:hello@briks.dev) with your project's name and what you expected to see. A screenshot helps.