> ## Documentation Index
> Fetch the complete documentation index at: https://docs.servicebooked.ca/llms.txt
> Use this file to discover all available pages before exploring further.

# Form notifications

> Decide who hears about new submissions and how — email, Slack, in-app, or all three.

By default, every form submission creates a notification in your in-app bell for your org's owners and admins. You can also wire up email and Slack notifications per form for finer-grained control.

## In-app notifications

Automatic. When a submission lands, the **bell** in the top-right of your dashboard shows a new dot. Click it to see what came in. Owners and admins all get notifications by default; team members can opt in via [Settings → Notifications](/settings/notifications).

## Email notifications

By default, submission emails go to **all org owners and admins**. To override that for a specific form (e.g. a "service area check" form should only ping a specific teammate, not everyone):

1. Open the form in **Forms → \[your form] → Settings**.
2. Find the **Notify emails** section.
3. Add the specific email addresses that should be notified for this form.

Once you set notify emails on a form, ONLY those addresses are emailed for that form's submissions — the default fan-out to all admins is replaced.

Format: comma-separated, plain email addresses (`alex@example.com, support@example.com`). Up to 20.

## Slack notifications

If you've connected Slack at **Settings → Integrations → Slack**, you can route form submissions there too:

1. Pick a channel from the channel selector (defaults to #general).
2. Enable **Form submission** under "Notify on" in the Slack section.

Every submission posts to your chosen channel with the form name, the contact's name, and a link back to the dashboard. Doesn't replace email — runs in parallel.

[More on Slack integration →](/settings/integrations)

## Disable notifications for a form

If a form is purely internal (e.g., a feedback survey you don't need real-time alerts on), leave the notify emails empty and disable the form in your team's notification preferences. Submissions still save; you just don't get pinged.

## Per-user preferences

Each team member can manage their own notification preferences in **Settings → Account → Notifications**. They can opt out of email notifications, in-app notifications, or both — without affecting what other admins receive.

## Webhook notifications (advanced)

If you want submissions delivered to your own backend (a Zapier-style trigger, a custom CRM sync, an internal system), use **outgoing webhooks** at **Settings → Integrations → Webhooks**. Subscribe a webhook URL to the `form.submitted` event and you'll get a JSON POST per submission.

[More on webhooks →](/settings/integrations)

## Common setup

Most owners do:

* **In-app**: on (default).
* **Email**: configure notify emails for a few critical forms; let everything else fall back to admins.
* **Slack**: on for high-volume forms (so the team sees them in flow) and off for low-volume ones.

That gives you a real-time pulse during the day and a central inbox to clear at end-of-day.

## Next

You're done with Forms. Next:

<Card title="Connect your calendar" icon="calendar" href="/calendar/google-calendar">
  So the AI Receptionist can book real appointments from form submissions and conversations.
</Card>