Slack notifications

Get a Slack message when a call ends or fails, a caller leaves a message or books, or your minutes run low.

Last updated November 3, 2026

Alerts do not have to arrive as email. Point your own Slack workspace at your account and a call that ends, a message a caller left or an appointment they booked shows up where your team already is. The Integrations page in the app menu shows whether Slack is connected and links here.

What you need: you have to own the account or be an administrator on it, your plan has to include integrations, and you need permission to add an app in the Slack workspace you want to post into. If your plan does not include it, the card says so and offers a link to billing.

Make an incoming webhook in Slack

An incoming webhook is an address Slack gives you that posts into one conversation. Slack has two ways to make one.

  1. In Slack, open the app directory and find Incoming WebHooks.
  2. Add it and choose where the messages should land.
  3. Copy the URL. It starts with https://hooks.slack.com/services/.

If your Slack workspace does not allow that app, build one of your own instead: turn on the incoming webhook permission, choose where it should post, and copy the URL from the same screen. The result is the same address.

Treat that URL as a password. Anyone holding it can post into your Slack workspace.

Connect it

  1. Open Settings > Notifications and scroll to Slack notifications.
  2. Paste the URL into Incoming webhook URL.
  3. Give it a Name. Only your team sees this, and it is what the remove dialog will ask you about later.
  4. Tick the events it should carry.
  5. Press Connect.
Suggested image Screenshot of the Slack notifications card at the bottom of Settings > Notifications with nothing connected yet: the Connect a destination heading, the Incoming webhook URL field, the Name field, the list of event checkboxes with Minutes running low, Message taken and Booking made ticked, and the Connect button.

We store the URL encrypted and never show it again, so keep your own copy. The card shows a shortened form of it, which is enough to tell two destinations apart.

What each event posts

A new destination starts with Minutes running low, Message taken and Booking made ticked. An agency starts with Minutes running low, Client waiting on credits and Client canceled. Change the ticks before you press Connect, or later on the destination.

  • Call ended. A call finished normally. On a busy line this is a message per call, so it starts unticked.
  • Call failed. A call could not be completed.
  • Message taken. A caller left a message.
  • Booking made. A caller booked an appointment.
  • Minutes running low. Your account crossed the warning level set further up the same screen.

An agency account gets six more about its clients: a client provisioned, a client waiting on credits, credits allocated, a price that is not tied to one of your plans, an email address that clashes with another account, and a client who canceled.

Call messages are sent after the call has ended, never while it is live. Calls at a location that belongs to one of your clients stay with that client and are not posted to your destinations.

Limit it to some locations

If your account holds more than one location, each destination carries a Locations this destination hears about list. Leave every box clear and it hears about all of them, including the ones you add later. Tick a few and it hears about only those, so one destination can belong to one client while another carries everything. Going back the other way is a button rather than an empty list: Send from every location says what it will do before it does it, because clearing the last box would quietly widen the destination to locations you have not added yet.

What a message carries

A message is one line saying what happened, the name of the location and the time, plus a button that opens the app. For a call it is the calls page. It carries no caller content: no names, no phone numbers, no message text and no booking details. A low minutes message adds your credits left and your monthly credits. For full call details, see Send calls to Zapier, Make or n8n.

Prove it works

Press Send test message on the destination. It posts one small message and shows you what Slack said underneath: accepted, refused with a code, or no answer at all. It is limited to one test every 30 seconds per destination.

Delivery log opens every attempt against that destination, newest first, with the answer, which try it was and how long it took. Attempts are kept for 30 days.

Suggested image Screenshot of one connected destination inside the Slack notifications card: the name call-alerts, the redacted address underneath, an Active badge on the right, the events checklist, and the row of Send test message, Delivery log and Remove buttons.

When it stops working

If Slack refuses everything for 24 hours the destination is switched off and the badge turns to Disabled. That usually means the webhook was revoked in Slack, or the place it posted into was archived.

Fix it on the Slack side, then press Reconnect. It starts posting again and keeps its name, its events and its delivery log. If the webhook itself is gone, remove the destination and connect the new URL as a new one: a webhook cannot be swapped underneath a running destination, because the log of one address would end up attached to another.

Remove a destination

Press Remove and confirm. It stops receiving alerts straight away and its delivery log goes with it.

The webhook itself still exists in Slack until you delete it there, so if you are removing a destination because the address leaked, revoke it in Slack as well.

Was this helpful?

Still stuck? Send us the profile and the comment you are looking at and we will answer with the fix rather than a link back here.

Contact Robofono support