Agency Client Notifications via Slack: Real-Time QR Activity Without Dashboard Logins

An agency running QR campaigns for several clients eventually faces the same request from more than one of them: "can we see what's happening with our campaign without you sending us a screenshot?" Handing out full SMLLR dashboard logins to client stakeholders isn't a great answer — it exposes other clients' data, requires managing access as client-side contacts change, and gives more control than most clients actually want. A live feed of just their own campaign's activity, delivered somewhere they already check, solves the actual need without any of that overhead.

SMLLR's Slack integration (Pro plan and above) posts a real-time message every time a subscribed QR event fires — a scan, a scan-limit rule crossing, a scheduled redirect firing — using nothing more than a pasted Slack Incoming Webhook URL, no app install or OAuth approval required. For an agency, the natural pattern is a dedicated, client-facing Slack channel (or a channel in the client's own workspace, if they'll add the Incoming Webhook) that shows that client's campaign activity live, giving them exactly the transparency they asked for without touching the SMLLR dashboard at all.

Here's the constraint worth understanding before promising this to a client: a SMLLR webhook or Slack endpoint is configured at the account level, not scoped to one client's QR codes specifically — the same "one connection per tenant" pattern SMLLR already uses for Meta Sync's ad-account connection and Email Marketing's sending domain. If an agency runs every client's QR codes from a single shared SMLLR account, there's no native setting that says "only send Client A's events to Client A's Slack channel and nothing else" — SMLLR doesn't have a per-client webhook routing feature built in.

The cleanest fix is also the most straightforward: give each major client — or at least each client important enough to warrant this level of transparency — their own SMLLR account (or workspace, if using SMLLR's white-label and client-scoped reporting setup), each with its own Slack endpoint. Since webhooks are account-wide, an account containing only that client's QR codes means every event routed to that client's channel is automatically theirs alone, with zero filtering logic needed. The tradeoff is cost and administrative overhead — running several separate accounts, each needing its own Pro-plan subscription, adds up quickly for an agency managing dozens of smaller clients, which is why this workaround tends to make sense only for clients large enough to justify a dedicated setup.

For an agency running many clients from one shared account, a generic webhook endpoint pointed at Zapier or Make instead of directly at Slack is the more scalable route. The event payload includes qrCodeId and campaignId, so a Zap or Make scenario can inspect the incoming event, check which client's QR code or campaign it belongs to, and route the message to the correct client-specific Slack channel from there — SMLLR fires one account-wide event stream, and the middleware does the per-client sorting SMLLR itself doesn't do natively. This requires actually building and maintaining that routing logic (a lookup table mapping QR/campaign IDs to client channels, kept in sync as new QR codes are created), which is real setup work but avoids running a separate paid account per client. See the Zapier and Make automation guide for how the underlying connection works.

A boutique agency with a handful of high-value clients is usually better served by dedicated accounts — the subscription cost per client is easily justified, and there's no routing logic to build or maintain. A volume agency running dozens of smaller clients from one shared account is better served by the Zapier/Make middleware route, accepting the one-time setup cost of building the routing logic in exchange for not multiplying SMLLR subscriptions. Either way, this sits alongside SMLLR's broader agency link-tracking and client reporting capabilities — Slack notifications add a real-time layer on top of the periodic client-scoped reports agencies already share.

Webhooks and Slack require SMLLR's Pro plan, ₹4,999/month, per account. The dedicated-account workaround means that cost multiplied by however many clients get their own account; the middleware workaround keeps it to a single Pro-plan subscription plus whatever Zapier or Make tier the routing logic needs (Zapier's own free tier covers a modest number of tasks a month, which may be enough depending on client volume).