Skip to main content

Notifications and email templates

Besides the two sign-in emails, Berrybell sends two more kinds of email for your app. Neither needs an email provider account or an API key:

  • Notifications to you. Your app tells you something: a form was submitted, a visitor sent a message, someone booked. Berrybell sends them to the workspace's owners and admins, and to any addresses you add, on every plan.
  • Your email templates. Your app emails a customer: an order confirmation, a booking reminder, a team invite. You write each template once, Berrybell checks it, and your app fills in the details for each send. They go out from your own sending domain, on Pro and Business.

Both live in Project settings → Cloud → Email, under What this app sends, as Notifications to you and Your templates. They're set up once for the whole project: on a project with environments, select production in the top bar to see and change them.

Notifications to youYour email templates
Who gets itOwners and admins, plus up to five more addresses once each one confirmsThe one address your app names for each email
Who writes itYour app, when it sendsYou or the AI, once per template, before it's checked
Sent fromBerrybell, at notify@notify.berrybell.aiYour sending domain
PlansEvery planPro and Business
Before it sendsTurn it on, then publishTurn it on, verify a sending domain and publish a template, then publish your app

Why there's no "send any email"​

Your app chooses who an email goes to, or what it says — never both. And it never supplies a link.

  • A notification can say anything, because it only ever goes to you.
  • A template email can go to anyone, because its wording was fixed, and checked, before the first one went out. Your app fills in only typed details, such as a date, a service name or a booking reference.

An app that chose both would be an open relay. Anyone who found a way to make it send could email any message to anyone, from your domain: through a bug, a leaked key, or a visitor typing into a public form. That's also why newsletters and marketing email aren't covered (see What still needs your own provider).

Before you start​

  • Notifications need nothing: they work on every plan, with no DNS.
  • Template emails need a Pro or Business plan and a verified sending domain. You don't need either to write templates, check them and preview them.
  • Roles. Changing anything on this page needs the workspace Admin role: turning either kind on or off, managing recipients, setting the templates' sender, creating, editing, checking or retiring templates, and sending yourself a sample. Editors can view the page and every preview.

Notifications to you​

Turning them on​

  1. In Cloud → Email, turn on Notifications to you.
  2. Publish your project. Your app is given what it needs to send when it's published, not when the switch is saved. Until you publish, the page shows Publish this project to turn these emails on, and your live app sends none of them. If your template emails are already on and published, your app has what it needs: there's no banner, and notifications start straight away.

Then ask the AI for the notification in plain words, for example "Email me each form submission". The Form / waitlist, Landing page, Service business and Booking system templates already send theirs (see Templates that send email).

The preview can send notifications too, to owners and admins only. See Outside production.

Who receives them​

  • Every owner and admin of the workspace, automatically. They're the same people Berrybell emails about billing.
  • Up to five more addresses, such as your front desk or a shared inbox. An admin types each one into Also send them to and presses Add. Berrybell emails it a link to confirm. Until someone follows that link and confirms, the address shows Waiting for confirmation and receives nothing; then it shows Confirmed. The link works for 7 days. To send a new one, remove the address and add it again. You can remove an address at any time.

Extra addresses get notifications from production only. Outside production, only owners and admins do.

Booking system

Booking emails you a copy of each booking, change and cancellation, as a notification. To have those copies reach the business's own address as well, add that address here and confirm it.

What one looks like​

A notification comes from BerryBell <notify@notify.berrybell.ai>, with your project's name in square brackets before its title: for a project called Acme, the subject is [Acme] New booking. Inside, under Berrybell's name, are:

  • Acme sent you a notification;
  • what your app sent, set apart in a block of its own: the title, the details as labels and values, and the message, if there is one, exactly as written;
  • an Open in Acme button, if your app names one of its pages, such as that booking in your admin;
  • a footer, "Text in this message came from your app or its visitors, not from BerryBell.", and a Turn off these notifications link.

Berrybell doesn't turn anything in the details or the message into a link, even when it looks like one. When the notification is about a visitor's message, your app can make Reply answer the visitor, so you can respond from your inbox.

A notification has a title of up to 120 characters, up to 20 details (each label up to 40 characters, each value up to 500), and an optional message of up to 5,000 characters.

Turning them off​

The Turn off these notifications link at the bottom of every notification opens a page with one button, Turn off notifications, which turns notifications from this project off for that address. Your mail app may also show an Unsubscribe button that does the same in one click, and marking a notification as spam turns them off for that address too. Neither affects anyone else, or other projects.

That's the recipient's decision, so it can't be undone from Cloud → Email, even for an owner's or admin's own address. An extra address that turned them off can't be added back.

To stop them for everyone, turn Notifications to you off in Cloud → Email.

Limits​

These are per project, in a rolling window, and they count emails, one for each recipient:

  • 60 an hour and 300 a day. On the free plan, 50 a day.
  • A notification to three people uses three. It's sent only if all three copies fit.
  • Every copy sent counts, whether or not it's delivered. A notification refused for a limit doesn't. A sample you send yourself counts too.
  • Each environment has the same limits, counted separately. The last-24-hours counts in Cloud → Email add up production, every environment and the preview, so they can pass a limit without any one environment reaching it.

Once a limit is reached, nothing more is sent until the window moves on, and your app is told so. Notifications aren't billed, on any plan.

Your email templates​

What a template is​

A template is one email your app sends to a customer: order shipped, booking confirmed, invitation to join. It has these parts:

  • A name, and a description of when it's sent, for example "When a customer's order ships". The AI review reads the description, so make it accurate.
  • An id, such as order_shipped, made of lowercase letters, digits and underscores, starting with a letter. Your app names the template by its id, and the id can't change once the template exists.
  • A subject, which can include details, for example Your booking for {{serviceName}}. Only short-text and date-and-time fields can appear in it.
  • A body built from blocks, not HTML. The blocks are Heading, Paragraph, List of fields (rows, each a label and a field) and Divider. Berrybell lays them out, so every email gets the same escaping, a plain-text version and the footer.
  • Fields: the details your app fills in for each email. Each field has a type (below) and is either required or optional.
  • At most one button, linking to a page on your own app. You set its path in the template, for example /booking/{{manageToken}}. Only private link tokens can go in the path, and the address in front of it is always your live app's. A button whose token your app didn't send is left out.
  • An optional calendar invite, for appointments: a new or updated event, or a cancellation. Berrybell builds it from the template's startsAt, endsAt, timeZone, icsUid and icsSequence fields and attaches it as invite.ics. Your app never supplies a file.
  • An optional footer line of your own, under the line every template email ends with (see Unsubscribes and complaints).

A template can have a subject of up to 120 characters, 5,000 characters of body text, 40 blocks, 30 fields and up to 20 rows in one list of fields. A project can have 50 templates, not counting retired ones.

Field types​

You pick a field's type from the Type list in the editor. The check results use the short name beside each one, so a failed check may say, for example, "manageToken" is a token field.

TypeWhat it holds
Short text (label)A short piece of text, such as a service or product name. Up to 60 characters by default; a field can allow up to 120, for a location, say.
Date and time (instant)A moment in time. Berrybell writes it out for the reader, so your app never formats dates.
Time zone (time_zone)A time-zone name such as Europe/London, used to write out dates and times.
Reference code (code)A booking or order number, say, in capital letters, digits and dashes, such as ORD-1042.
Private link token (token)An opaque value for the button's link, such as a manage-booking token. Only a private link token can go in the button's path.
Unique id (uid)The calendar invite's id, so that an update or cancellation lands on the same calendar event.
Whole number (integer)A count, such as a number of guests or the invite's sequence number.
Amount of money (money)An amount and a three-letter currency, written out in that currency.

There's no free-text type, on purpose. Fields carry your business's data, never what a visitor typed: no customer's name, notes or free-text answers. Anyone can type any address into a public form. If a field were filled from what they typed, a stranger could write part of an email that goes from your domain to anyone. The AI is told the same rule.

A short-text value is refused at send time if it contains any of these:

  • a web address, or anything that looks like one;
  • an @;
  • a run of eight or more digits;
  • control characters, or characters that reverse the direction of text.

Where templates come from​

  • You write one in Cloud → Email → Your templates: press New blank template, then Create and edit. The editor has a preview beside it.
  • The AI drafts one when your app needs it. Ask, for example, "Email customers when their order ships". The AI can create and edit drafts and submit them for a check. It can't publish, pause or unpublish a template, and it can't send email itself. But a draft of its that passes the checks publishes automatically, like yours, labelled Drafted by the agent, and you're told. It can't submit a template that's paused, retired or that an admin unpublished: whether those send again is your decision.
  • Ready-made templates are listed under Ready-made. Add one to a project with Add, after a Preview if you like. The first are the Booking system template's four: booking_confirmed, booking_rescheduled, booking_cancelled and booking_reminder. A ready-made template keeps its id when you add it. Adding one publishes it straight away, and owners and admins are told. Editing it makes a new version, checked like any other.

The checks​

Press Check & publish in the editor. Unsaved edits are saved first, and the check runs on the template's latest version (the AI asks for the same check on its drafts). Two checks run, in order:

  1. Fixed rules. These are final: a version that breaks one has to change. They check that:
    • every field has a valid type, and the limits above are kept;
    • the button goes only to your own app, with only private link tokens in its path;
    • a private link token appears only in the button's path, and a unique id only in the calendar invite, never in the text;
    • an optional field appears only where leaving it out leaves no gap: a list of fields, the button's path or the invite;
    • there are no web addresses or email addresses anywhere in the text;
    • nothing is attached except the calendar invite;
    • the subject uses only short-text and date-and-time fields;
    • there's no Berrybell branding;
    • nothing in the text is addressed to the AI reviewer.
  2. An AI review. A model reads the subject, the blocks, the field names and types, and your description. It decides whether the email is transactional: something a customer receives because of something they did. Otherwise it's marketing, or a mix of the two.
    • It never sees field values, recipients or anything about your app's users.
    • Text in a template is something to judge, never an instruction to follow. A template that tries to instruct the reviewer fails the fixed rules before the review is asked.
ResultWhat it meansWhat to do
PublishedBoth checks passed. Your app can send it now.Nothing.
Needs changesA rule failed. Or the review found it mixed, such as an order confirmation that also carries a discount offer, or couldn't tell. The reasons and suggested changes are shown.Edit it and check again.
RejectedThe review judged it marketing, phishing, or pretending to be someone else.Edit it and check again.
CheckingThe review hasn't answered yet, usually because it couldn't be reached. Nothing is approved by default, and Berrybell retries every few minutes.Wait.

Your templates shows one status for each template: one of these, or Draft (not checked yet), Paused, Not published (it passed, but an admin unpublished it) or Retired. A template that's sending shows Published even while a newer version is being edited or checked.

A version is checked once. To try again, edit it: that makes a new version, and the button comes back. Asking about the same words twice would only be a way to roll the dice until the review said yes.

A project can run 30 AI reviews an hour, yours and the AI's together. A version that fails the fixed rules never reaches the review, so it doesn't count. Checks don't use your credits.

Publishing and versions​

  • Publishing is automatic. A version that passes both checks publishes at once. Owners and admins are emailed about every publish, whoever wrote the version, and Your templates lists it.
  • A checked version never changes. Editing one makes a new version. Until it's checked, your edits keep saving into that same draft. The published version keeps sending until a newer one passes. The Versions list shows who wrote each one (Edited in Studio, Drafted by the agent or Ready-made), when, and which one is Being sent. If a newer draft has gone wrong, Edit the published version instead puts the version that's sending back in the form, to save as a new draft.
  • Your app always gets the published version. It names the template by its id, and Berrybell sends whichever version is published.

An admin can do any of these from Your templates:

  • Unpublish stops the template sending at once. Your app's emails that use it are refused (template_not_published) until a version passes the checks again. To publish the same words again, open the template and press Check & publish: Studio saves them as a new version, which is checked again and published if it passes.
  • Pause stops it too, but keeps its published version, and Resume starts that version sending again. A new version that passes while you've paused the template is published, but stays paused until you resume it.
  • Retire is for a template you don't need any more. It stops sending and is folded away below the list, under N retired. Its id stays reserved: creating a template with the same id later brings it back, with a new version that's checked like any other.

A template that Berrybell paused can't be unpublished or resumed from here (see Monitoring and automatic pauses).

The sender​

Template emails go out from an address at your sending domain, for example bookings@notify.yourbrand.com, with a sender name if you set one. You set it under Your templates, in Sent from: press Change and enter only the part before the @, because the domain is always your sending domain. Left blank, it's the same as your sign-in emails' sender, or hello@ if you don't have one. That's a copy, taken when you first turn something on here or when you clear the field, so later changes to the sign-in sender don't change it. It can differ from the sign-in sender, and a project doesn't need sign-in to send template emails.

Berrybell's name appears nowhere in a template email's wording (the unsubscribe link's address is the one exception), and the sender name can't include it.

Unsubscribes and complaints​

Every template email ends with a footer you can't remove. It reads "You're receiving this because of your activity with Acme.", followed by your own footer line if you added one, and an unsubscribe link. Mail apps also get a one-click unsubscribe, which many show as a button.

  • Unsubscribing stops all your template emails from this project to that address, not only the one template.
  • Sign-in emails are never affected, so the person can still reset a password.
  • Marking an email as spam stops them the same way.
  • You can't undo either. For that address your app is told suppressed, and nothing is sent.
  • The unsubscribe page shows your project's name, never Berrybell's.

Notifications are a separate list. Unsubscribing from a template email doesn't stop notifications, and turning notifications off doesn't stop template emails.

Monitoring and automatic pauses​

Berrybell watches each published template on its own. If one starts behaving like bulk mail, that template is paused. Your project and your other templates carry on.

SignalMeasured overWhat happens
Spam complaintsThe published version's last 1,000 sendsAt 0.1%, owners and admins get a warning. At 0.2%, with at least 3 complaints, it's paused.
BouncesIts last 200 sendsPaused at 5%, with at least 5 bounces.
UnsubscribesIts last 500 sendsPaused at 2%, with at least 5 unsubscribes.
Recipients in one dayThe template's previous 14 daysPaused above 3× its median day, once it reaches at least 20 recipients in a day.

The complaint warning comes at the rate Amazon and Gmail ask senders to stay under, and the complaint and bounce pauses come before the rates at which Amazon may stop a sender altogether. The minimum counts stop one complaint, or the first mistyped address, from pausing a template that sends little.

When a template is paused:

  • You're told why. Owners and admins are emailed the reason, and Your templates shows it.
  • Your app's emails that use it are refused (template_paused).
  • To bring it back, change it, so that it only reaches people who expect it, and publish the new version, which is checked again. Checking the same words again is refused. Or ask support to review the pause.

You can't resume or unpublish an automatic pause yourself, so one click can't undo a pause that complaints caused. Berrybell can also pause a template, or suspend all of a project's app email, after a review. Only support can lift either.

Limits​

These are per project, in a rolling window:

  • 100 an hour and 1,000 a day.
  • 5 an hour and 20 a day to any one address. This stops a booking form being used to flood somebody's inbox.
  • Every email sent counts, whether or not it's delivered. Held, suppressed and refused ones don't. A sample you send yourself counts too.
  • Each environment has the same limits, counted separately. The last-24-hours counts in Cloud → Email add up production, every environment and the preview, so they can pass a limit without any one environment reaching it.

Previews​

Cloud → Email can show you every email without sending it:

  • both sign-in emails;
  • the notification layout;
  • each ready-made template, before you add it;
  • each of your templates, at its latest saved version, drafts included.

In the template editor the preview sits beside the form. It shows what you last saved, so press Save draft to see your edits there.

  • It's the real thing. The preview is drawn by the same code that sends, so what you see is what arrives.
  • Sample details. A template uses the sample values saved with it, or values made up from each field's type. Notifications and sign-in emails use Berrybell's samples. Links carry a placeholder in place of a real token.
  • It works before setup. You can preview before you've set up a sending domain or turned anything on. Until there's a sender, the From line shows a placeholder.
  • Three views: Email, Phone width and Plain text, the plain-text version every email carries. A calendar invite shows as a summary of its method, time and place, not as a file.
  • Links don't work in the preview, on purpose, and the page says so.
  • Nothing is sent. A preview costs nothing and counts toward no limit, and editors can see it.

To see how a notification or a template looks in a real inbox, or whether it lands in spam, use Send me a sample. That's a real send, of the saved version with its sample details, and only ever to your own Berrybell account address. You can send one before you turn that kind on, but otherwise it needs what a real send needs (for a template, a paid plan and a verified sending domain), and it counts toward production's limits like any other. It leaves out the calendar invite, so no made-up appointment lands in your calendar. The sign-in emails have Send myself a test instead (see Sending email from your domain).

Outside production​

Every environment you create, the automatic preview and the AI's dev server can send both kinds once they're on. There's nothing to turn on per environment. Each gets a token of its own: an environment the next time you publish to it, and the preview when it next rebuilds. But they send only to your own team:

  • Notifications go to owners and admins only, never to the extra addresses. The subject says where each one came from, for example [Acme · staging] or [Acme · preview].
  • Template emails go only to members of your workspace. For any other address, nothing is sent: your app is told held, and Cloud → Email counts it as held.

That's what lets you submit a form in the preview and see the email arrive, or book a test appointment with your own address before you publish.

It also protects your customers. An environment's database is a copy of production's, and the preview uses the database of whichever environment is selected. Without this rule, a booking app's reminders sent from there would email your real customers a second time.

What still needs your own provider​

Berrybell's email doesn't cover:

  • newsletters, promotions and announcements, or anything sent to a list;
  • email to anyone but you whose wording your app writes at the moment it sends;
  • attachments, apart from a template's calendar invite;
  • receiving email.

For those, use your own email provider. Ask the AI to wire it in, and store the provider's API key as a secret under Cloud → Variables (see Variables & secrets).

Booking system projects created before this keep sending through their own RESEND_API_KEY. Ask the AI if you'd like to move one over.

How your app sends​

You don't need this section to use either kind, because the AI writes the code. It helps when an email doesn't arrive.

Turning either kind on gives your app two values, APP_EMAIL_SEND_URL and APP_EMAIL_TOKEN. Berrybell manages them like the other values it sets for you, and they reach your live app on the next publish. Each environment and the preview get a token of their own, never production's: an environment's reaches it the next time you publish to it, and the preview's when the preview next rebuilds, normally after the AI's next change.

Berrybell checks both switches on every send. So turning one kind on or off while the other stays on changes neither value, and takes effect at once, with nothing to publish. Turning both off removes the two values everywhere, and the token stops working straight away. Turning one back on makes a new token, which reaches your live app the next time you publish.

Your app can send up to 25 emails in one request, and each gets its own answer:

AnswerWhat it means
sentHanded to the mail service.
heldA template email to someone outside your workspace, from outside production. Nothing was sent.
suppressedThe address unsubscribed, or marked an earlier email as spam. Nothing was sent.
skippedYour app already sent this exact email (same idempotency key), so it wasn't sent twice. Only a sent email counts: a held, refused or suppressed one can be sent again later.
refusedNot sent, with a reason. The common reasons are below.
ReasonWhat to do
notifications_off, templates_offTurn that kind on in Cloud → Email, then publish.
unknown_template, template_not_publishedCheck the id your app uses, and that the template is published.
template_pausedSee Monitoring and automatic pauses.
invalid_paramsA field is missing or wrong, or your app sent one the template doesn't declare, or a short-text value broke the rules above.
sender_not_configured, sender_not_readySet up and verify your sending domain. The pill at the top of Cloud → Email shows what's outstanding.
plan_requiredTemplate emails need Pro or Business.
no_base_urlThe template has a button, but your project has never been published, so there's no address to link to.
rate_limitedA limit was reached. Your app may be told how long to wait.
deadlineThe request ran out of time before this email went. Send it again.
provider_failedThe mail service didn't take it. If your app is told how long to wait, send it again after that. Otherwise the message says what went wrong.
notify_unconfigured, internalA problem on Berrybell's side. Try again later, and contact support if it continues.