Notifications

What it does

The Notifications page is where you tell your AI receptionist where to send alerts when something important happens on a call — a message was left, a call completed, or a caller was connected (or not connected) to one of your contacts.

You can set up any combination of four notification channels: email, Slack, Microsoft Teams, and webhooks. Each channel works independently, so you can use one, several, or all four at the same time. Every channel has a test button so you can confirm it is working before a real call comes in.

Looking for SMS? SMS notifications are configured per contact, not on this page. See SMS notifications below.

What triggers a notification:

• A caller left a message for someone on your team
• A call completed
• A routing event occurred (caller was connected or not connected to a contact)

How to get there

In the left sidebar, click Settings, then click Notifications in the settings submenu. The URL will be /tenants/[your-id]/settings/notifications.

Step-by-step

The page shows four channel cards. Each card has the same basic structure: an Enabled toggle at the top, configuration fields in the middle, and a Send Test Notification button at the bottom. Flip the toggle on to activate a channel, fill in the required fields, then use the test button to verify everything is connected.

Each channel saves independently — click Save Configuration on a channel card to save that channel’s settings. Changes take effect immediately for future calls.

Email

Email is the simplest channel to set up — no external accounts or integrations required.

1. Toggle Enabled on.
2. Enter the address you want notifications sent to in the Recipient Email field. This does not have to be your login email — you can use a shared inbox, a team alias, or any address you have access to.
3. Optionally, enter a Sender Name. This is the display name that appears in the “From” field in the recipient’s inbox. If you leave it blank, it defaults to “AI Receptionist.”
4. Click Send Test Notification to send a test email immediately. Check your inbox (and spam folder) to confirm it arrived.
5. Save your changes.

Slack

Slack notifications let your team receive alerts directly in any Slack channel. Setting up Slack requires an OAuth connection — a one-time authorization step that lets Azumo post to your workspace.

Connecting Slack:

1. Toggle Enabled on.
2. Click Connect Slack. Your browser opens the Slack consent screen.
3. Review the permissions Azumo is requesting, then click Allow. You are redirected back to the Notifications page.
4. Once connected, a Select Channel dropdown appears. Choose the Slack channel where notifications should be posted — for example, #receptionist-alerts or #front-desk.
5. Click Send Test Notification to confirm a message appears in your selected channel.
6. Save your changes.

Disconnecting Slack:

If you want to remove the Slack connection, click the Disconnect button that appears after connecting. This removes Azumo’s access to your workspace. You can reconnect at any time.

Automatic contact linking:

When Slack is connected, Azumo automatically looks up each contact’s email address against your Slack workspace. If there is a match, that contact is linked to their Slack account — you will see a “Linked” badge in the Slack column on your Contacts page. This link is what allows the AI receptionist to send a contact a direct Slack message when a caller asks for them. The link happens when you save a contact, so existing contacts may need to be re-saved if they were added before Slack was connected.

Microsoft Teams

Teams notifications use an incoming webhook — a URL you create inside Teams and paste here. No login or OAuth is required on Azumo’s end.

Creating the webhook in Teams:

1. In Microsoft Teams, open the channel where you want notifications to appear.
2. Click the ... (More options) menu next to the channel name and select Connectors (or Manage channel → Connectors, depending on your Teams version).
3. Search for Incoming Webhook and click Configure.
4. Give the webhook a name (for example, “AI Receptionist”) and optionally upload an image.
5. Click Create. Teams generates a webhook URL — copy it.

Connecting Teams in Azumo:

1. Toggle Enabled on.
2. Paste the webhook URL you copied from Teams into the Webhook URL field.
3. Click Send Test Notification to confirm a card appears in your Teams channel.
4. Save your changes.

Webhook

The Webhook channel is for sending notifications to your own software — a CRM, a custom app, a Zapier workflow, or any service that can receive HTTP POST requests. Webhook URLs must use HTTPS.

1. Toggle Enabled on.
2. Enter your endpoint’s URL in the Webhook URL field. The URL must start with https://.
3. Optionally, enter a Signing Secret. When a signing secret is set, Azumo includes a signature header with each request so your endpoint can verify the request is genuine and was not tampered with. If you do not need request verification, you can leave this blank.
4. Click Send Test Notification to send a test payload to your endpoint. Use your endpoint’s logs or a tool like webhook.site to inspect the payload.
5. Save your changes.

SMS notifications (per contact)

SMS notifications are not configured on this page. They are set per contact, on the Contacts page.

When SMS is enabled for a contact, that person receives a text message at their saved phone number any time the AI receptionist takes a message for them. The SMS is sent from your Azumo phone number (the same number callers dial in). A contact must have a phone number saved before SMS can be turned on. You will see an “SMS” badge in the contacts table for contacts with this enabled.

Tips

• Test before your next call. Use the Send Test Notification button on each channel you set up. It takes 30 seconds and tells you right away whether the configuration is correct — much better than finding out during a real call.
• You can enable more than one channel. For example, you might send email to a shared inbox for record-keeping and also post to Slack so your team sees alerts in real time. All enabled channels fire on the same events.
• Slack channel selection matters. Pick a channel your team actually monitors. A high-traffic general channel may cause notifications to get buried. A dedicated channel like #calls or #receptionist is easier to keep an eye on.
• The Sender Name field affects how email looks in the inbox. Setting it to your business name (for example, “Acme Plumbing Receptionist”) makes notifications easier to recognize in a busy inbox.
• Webhook signing secrets are recommended if you are using the webhook channel in a production app. Without one, any system that knows your endpoint URL could send fake requests. The signing secret ensures only Azumo’s notifications are accepted.

Troubleshooting

I clicked Send Test Notification and nothing arrived. Check that the Enabled toggle is on and that you have saved the page since entering your configuration. For email, check your spam folder — some email providers flag automated messages. For Slack, confirm that the channel still exists and that the Azumo app has been granted access to post to it.

Slack shows “Connected” but the channel picker is empty. This usually means the Azumo app was added to your Slack workspace but does not have access to any channels. In Slack, go to the channel you want and type /invite @Azumo (or use Channel Settings → Integrations → Add an App) to give the app posting access. Then return to the Notifications page and refresh — the channel should appear in the dropdown.

I disconnected Slack and reconnected, but notifications stopped going to the channel I selected. After reconnecting, the channel selection resets. Open the Notifications page, choose your channel from the Select Channel dropdown again, and save.

The Slack column on my Contacts page does not show “Linked” for a contact. Two things to check: (1) confirm Slack is connected on this page, and (2) confirm the contact’s email exactly matches their Slack account email. The link is created when you save the contact — try opening that contact’s record and saving it again with no changes. If the emails match, the “Linked” badge should appear within a few seconds.

Teams notifications are not appearing in the channel. Confirm the webhook URL you pasted matches the URL Teams generated — it must be the complete URL, including the https:// prefix. Also check that the incoming webhook connector is still active in Teams; connectors can sometimes be removed by a Teams admin. Recreate the webhook in Teams if needed and update the URL on this page.

The Webhook test returned an error. Make sure your endpoint URL starts with https:// — plain http:// URLs are not accepted. Also confirm your endpoint is reachable from the public internet (local development servers behind a firewall will not work). If you need to test locally, use a tunneling tool like ngrok to expose your endpoint temporarily.

I am not getting notifications for messages taken, but my channel is enabled. Notifications fire after a call ends and the AI receptionist has finished processing it (usually within a few seconds of the call completing). If a call ended but no notification arrived, check your channel’s test button to confirm the connection is still live. If the test works but real notifications are missing, contact support@azumo.com with the Call SID from your Call History page.

Related

• Contacts — enable SMS notifications per contact and see which contacts are linked to Slack
• Call History — review call outcomes and use Call SIDs when contacting support about a missing notification
• Business Hours — control when your receptionist takes messages vs attempts to reach a contact
• Agent Configuration — adjust how your receptionist handles messages and routing