LimeCall + Slack:
Real-Time Call Alerts in Slack
Get instant LimeCall notifications in Slack. New callback requests, missed calls, and call summaries delivered to your sales or support channels automatically — so your team never misses a lead.
How a callback becomes a Slack alert
From the moment a visitor requests a callback to the Slack message landing in the right channel — every step is automatic.
Visitor requests callback
Clicks LimeCall widget on your website
LimeCall routes alert
Evaluates routing rules against page URL and UTM
Slack message fires
Alert lands in the right channel within 3 seconds
Rep takes action
Picks up call or follows up on missed callback instantly
Add LimeCall to Slack via OAuth
Go to LimeCall → Integrations → Slack. Click "Add to Slack" and authorise via OAuth. Grant LimeCall permission to post to your workspace channels. The connection is live in under 30 seconds — no API tokens or webhooks to configure manually.
Configure channel routing
Set up routing rules to send different notification types to different channels. Pricing page callbacks to #sales-leads, missed calls to #missed-calls, enterprise leads to #exec-alerts. Set a default channel for any callback that matches no specific rule.
Set notification preferences
Choose which events send Slack alerts — callback requested, call completed, missed call, voicemail received. Configure digest frequency and target channel. Make a test callback and verify the Slack message arrives in the right channel within seconds.
Everything the LimeCall + Slack integration does
Six notification and routing capabilities that keep your team in sync with every call — without leaving Slack.
Real-time callback request alert to Slack channel
The moment a visitor submits their number in the LimeCall widget, a Slack message fires to your configured channel — caller name, phone, page URL, UTM source, and assigned agent — before the call even connects.
Missed call notification with caller details and page URL
When a callback attempt goes unanswered, LimeCall sends a missed call alert to your #missed-calls channel — or whichever channel you configure. Includes caller details, page URL, and a link to the LimeCall dashboard for immediate follow-up.
Call completed summary with duration, outcome, and caller
After every call, LimeCall posts a completion summary to Slack: call duration, outcome as marked by the rep, caller name, and any disposition notes. Your team has a real-time log of every call in Slack without opening a separate dashboard.
@mention specific team members on high-value leads
Configure @mention rules so the right rep is tagged the moment a high-value lead calls. Enterprise pricing page visitor? @mention the enterprise AE. Returning customer with a large open deal? @mention the account owner. Rules fire automatically.
Daily and weekly call digest in Slack
LimeCall sends a formatted call digest to any channel on a daily or weekly schedule — total callbacks, answer rate, missed calls, average duration, top pages, and per-agent breakdown. Management visibility with zero manual reporting.
Route notifications to different channels by lead source or page
Configure routing rules to send callbacks from your pricing page to #sales-leads, support page callbacks to #support-queue, and enterprise landing page callbacks to #enterprise-deals. Each rule matches on URL, UTM, or widget name.
Popular LimeCall Slack channel setups
The most common channel routing configurations our customers use from day one.
Every new callback request fires here instantly — caller details, page URL, UTM campaign. The sales team sees every new lead in real time without checking a dashboard or email.
Unanswered callbacks route here automatically with full caller details and a direct link to listen to any voicemail. Ensures no lead falls through because someone was on another call.
Callbacks from enterprise landing pages or visitors matching high-value criteria (large company, known account) route here with @mention of the AE. Leadership stays informed without watching every channel.
LimeCall posts a formatted call digest every morning — total calls, answer rate, missed rate, average duration, top pages. Management gets call data without asking for it.
Who uses LimeCall + Slack and how
See every new lead in #sales-leads instantly
Sales reps no longer need to check the LimeCall dashboard to know when a new lead has requested a callback. The Slack alert fires before the call connects — so reps have context before they pick up, and they never miss a lead while between calls.
No-answer callbacks flagged in #follow-up immediately
Support teams use the missed call channel as their follow-up queue. The Slack notification includes the caller's number, page, and time — enough to make a proactive outbound call or send an email within minutes of the missed callback.
Daily call summary without asking for it
The daily Slack digest gives managers total call volume, answer rate, missed rate, and per-agent performance every morning. No manual reports, no dashboard logins — the data arrives in the channel they already check.
Real-time call data as the source of truth
RevOps teams use the Slack integration to monitor callback volume against targets in real time. When the #sales-leads channel goes quiet, they know immediately — not at end of day when the damage is done.
LimeCall + Slack vs the alternatives
| Feature | LimeCall + Slack | Email alerts | Other callback tools |
|---|---|---|---|
| Real-time callback alert to Slack | Yes | Delayed | Partial |
| Missed call notification with page URL | Yes | No | No |
| Channel routing by page / UTM / lead source | Yes | No | No |
| @mention on high-value lead criteria | Yes | No | No |
| Call completed summary with outcome | Yes | Delayed | Partial |
| Daily / weekly digest to Slack channel | Yes | true | No |
| OAuth connect — 2 clicks | Yes | N/A | No |
Frequently asked questions
Does the LimeCall Slack integration work with Slack Free? +
Yes. LimeCall connects to all Slack plans including Slack Free. The OAuth connection and core notification features — real-time callback alerts, missed call notifications, and call summaries — work across all Slack tiers. Channel routing to multiple channels and @mention functionality require that those channels exist in your Slack workspace, but there is no Slack plan restriction imposed by LimeCall. The LimeCall side of the integration is included on Pro plan and above.
Can I route LimeCall notifications to different Slack channels based on the page a visitor called from? +
Yes. LimeCall supports channel routing by lead source and page URL. You configure routing rules in LimeCall → Integrations → Slack → Channel Routing. For example, callbacks from your pricing page route to #sales-leads, callbacks from your support docs route to #support-queue, and callbacks from enterprise landing pages route to #enterprise-deals. Each rule can match on exact URL, URL path prefix, UTM campaign, or UTM source. Multiple rules can be active simultaneously, and a callback matching no rule falls back to a default channel you configure.
What data is included in LimeCall Slack notifications? +
LimeCall Slack notifications include: caller name and phone number, the page URL they called from, UTM source and campaign, the LimeCall widget that triggered the call, the time of the callback request, and the assigned agent (if round-robin or rule-based routing is configured). For completed call notifications, the message also includes call duration, call outcome as set by the rep, and any disposition notes. For missed call notifications, the message includes a direct link to the LimeCall dashboard to listen to the voicemail if one was left.
Can I @mention specific team members in Slack when a high-value lead calls? +
Yes. LimeCall supports @mention routing in Slack notifications. You configure @mention rules based on lead characteristics — for example, if the callback is from your enterprise pricing page, @mention the enterprise AE. If the caller is a returning contact with a deal over a threshold value (pulled from your connected CRM), @mention the account owner. @mentions appear inside the Slack notification message, so the right person is alerted the moment the lead calls — even if they are not actively watching the channel.
Does LimeCall send daily or weekly Slack digests? +
Yes. LimeCall can send a daily or weekly call digest to any Slack channel you configure. The digest includes: total callbacks received, total calls answered, total missed calls, average call duration, top pages that generated callbacks, and a breakdown by agent. Daily digests are sent at a time you set in LimeCall → Integrations → Slack → Digest Settings. Weekly digests are sent on Monday morning by default. Digest messages are formatted as Slack Block Kit messages for clean, scannable summaries.
How is this Slack integration page different from the existing LimeCall for Slack page? +
The LimeCall for Slack page provides a general overview of how LimeCall works with Slack, including the basic setup and use cases. This integration page goes deeper into the technical configuration: channel routing rules, @mention logic, notification payload details, digest setup, and the full list of trigger events that generate Slack notifications. If you are evaluating whether LimeCall and Slack work together, start with the general page. If you are setting up the integration and need configuration detail, this page has everything you need.
How long does the Slack integration setup take? +
Most teams complete the LimeCall Slack integration setup in under 10 minutes. The OAuth authorisation takes two clicks and under 30 seconds. Configuring your first channel routing rule takes 2 minutes. Setting notification preferences — which events trigger alerts and which channels receive them — takes another 5 minutes. After configuration, make a test callback from the LimeCall dashboard and verify the Slack message arrives in the correct channel within seconds. The average setup time from start to first verified notification is under 10 minutes.
Ready to connect LimeCall with Slack?
2-click OAuth · Real-time alerts · Free trial included