Slack
Get LimeCall notifications in a Slack channel.
Connect
Open Settings → Integrations.
Choose Slack and Connect.
Authorise LimeCall in your Slack workspace.
Choose the channel notifications should post to.
What you can be notified about
A missed call.
A new callback request.
A high-scoring lead.
A new inbound message.
A voicemail left.
AI usage approaching its limit.
Choose a channel deliberately
Post to a channel the right people actually read. A dedicated channel like #limecall-leads works better than a busy general channel where notifications scroll away in minutes.
If your team is large, separate channels by purpose — missed calls to the team who can call back, usage alerts to whoever owns billing.
Do not notify on everything
This is the most common mistake. A channel that fires on every inbound call becomes noise within a day, and then gets muted — at which point the alerts you actually needed are also unread.
Notify on the things requiring a human decision:
missed calls, because someone should call back,
high-scoring leads, because speed matters,
usage alerts, because running out is expensive.
Ordinary answered calls do not need a Slack message. They are in the dashboard.
Acting from Slack
Notifications link back to the conversation or lead in LimeCall, so someone can pick it up in one click.
Missed calls are the highest-value alert
If you configure only one thing here, make it missed calls.
A missed call is a person who wanted to speak to you and could not. Getting it in front of a human within minutes — while they are still thinking about the problem — converts dramatically better than a callback the next morning.
Usage alerts
Route AI minute and credit alerts to Slack as well as email. Running out of AI minutes silently stops your receptionist answering — see AI minutes & usage.
Disconnecting
Disconnecting stops all notifications to the workspace. If alerts stop unexpectedly, check whether the authorising user has left or the app was removed from the workspace.