Connect Lumos to Slack: Weekly AI Visibility Digest

Why Slack is the right surface for AI visibility data

Most teams don't log in to a monitoring dashboard daily. Even great dashboards lose to the inertia of a busy week. The Lumos Slack integration solves that by inverting the access pattern: instead of asking the team to come to the data, the data goes to the team — once a week, on Monday, in the channel where they already plan.

The weekly digest is short on purpose. Long status messages get scrolled past. The Lumos digest is structured to be glanceable in 30 seconds (score, direction, headline) and actionable in 5 minutes (top 3 backlog items, top mover prompts, competitor flags). Everything beyond that links back into the dashboard for the team member who wants to dig deeper.

What's in the weekly digest

Every Monday morning at 9 AM local time (configurable), the digest posts to your chosen Slack channel:

• This week's visibility score. The current score, the change from last week, the trend over the past 4 weeks. Color-coded so you can read it at a glance.
• Top movers. The 3-5 prompts that gained or lost the most rank this week. Each shows the prompt, the engine, and the delta. The biggest losses get a flag — that's the signal to act.
• Top 3 backlog items. The three highest-leverage actions from this week's GEO backlog, with expected lift and a one-click 'create ticket' button if you have Linear/Jira/Asana connected.
• Competitor moves. If a tracked competitor changed rank significantly on a prompt you care about, it shows here. Especially useful for catching a competitor's content launch within days instead of weeks.
• Citation changes. New high-impact domains citing you, or top domains that stopped citing you. The latter is rare but worth knowing about fast.
• Link to the full dashboard. One click goes back into Lumos with the digest's context preserved.

How to connect Lumos to Slack

Setup takes about 30 seconds.

1. Open Lumos Settings → Integrations → Slack. You'll see a "Connect to Slack" button.
2. Authorize via OAuth. Click connect; you're redirected to Slack's standard OAuth flow. Pick the workspace you want to install Lumos into. If your workspace restricts third-party app installs, you may need a workspace admin to approve — the Lumos OAuth screen shows exactly what's requested so they can audit it.
3. Pick a channel. Choose the channel for the weekly digest. Most teams use a dedicated #geo or #growth-data channel; some send it to #marketing-weekly.
4. Configure frequency and sections. Default is weekly Monday 9 AM with all sections enabled. You can switch to daily or alert-only, and toggle individual sections.
5. Done. The next digest posts on the next scheduled run. You can also fire a test digest manually to see what it looks like.

The connection is workspace-scoped — you can connect a single Lumos workspace to multiple Slack channels (e.g., a leadership digest in one channel and an operational digest in another).

Permissions and security

The Lumos Slack app requests minimum permissions. The full scope list:

• chat:write — to post the digest and alerts.
• commands — so /lumos slash commands work inside Slack (e.g., /lumos score returns your current visibility score; /lumos rank "best GEO tool" looks up your rank on a specific prompt).
• channels:read — to list available channels in the setup UI when you pick where the digest goes.

The app does not request: message history read access, file access, DM access, user-list access beyond channel members. You can review the exact scopes during the OAuth approval screen.

The integration is fully revocable. Disconnecting from inside Lumos (Settings → Integrations → Slack → Disconnect) immediately stops all posts. Revoking the app from Slack's app directory has the same effect.

Real-time alerts (beyond the weekly digest)

The weekly digest is the default, but Lumos can also fire real-time alerts to Slack on configurable triggers:

• Visibility score drop. Alert when your visibility score drops by N points or more in a single day. Most teams set this at 3-5 points.
• Competitor crossover. Alert when a tracked competitor crosses you on a key prompt — either gaining rank past yours or pulling away when you were closing.
• New citation. Alert when a new high-impact domain starts citing you. Useful for catching the moment a major publication picks you up.
• Citation drop. Alert when one of your top 10 cited domains stops citing you. Rare but important — usually signals a content change on their end or an algorithm shift.
• Schema or robots.txt regression. Alert when a structural change on your site breaks AI crawler access. Caught early, these are 30-minute fixes; caught late, they're week-long visibility drops.

Each alert type can route to a different channel — you might want score drops in #growth-leadership and schema regressions in #engineering.

Slash commands

/lumos inside any channel where the app is installed gives you on-demand queries without leaving Slack:

• /lumos score — current visibility score and weekly change.
• /lumos rank "<prompt>" — your rank on a specific prompt across all engines.
• /lumos backlog — top 5 items from this week's GEO backlog.
• /lumos competitors — current competitor rankings.
• /lumos help — full command list.

Slash commands are scoped to the user who runs them, so a teammate without Lumos access still gets a useful response but with the appropriate auth prompt.

Connect Lumos to Slack

The Slack integration is available on every Lumos plan including the free tier. Sign up or, if you're already on Lumos, head to Settings → Integrations → Slack.

• See related: Connect Lumos to ChatGPT.
• See related: Weekly GEO Backlog.
• Read the strategy: Why GEO is a competitive advantage.