How to Add the Promptwatch Agent to Slack
How we add the Promptwatch agent in Slack: org owner from Settings, one channel per client project, and briefings that skip when nothing changed.
Slack is where the account already talks. We add the Promptwatch agent so GEO does not die in an unread login. We do not dump it into #general. One client project, one channel. If nothing changed, the scheduled briefing skips. That is the whole point.
The org owner connects Slack. Analysts do not run a second OAuth on a personal workspace.
Who clicks, and where it lands
Settings → Slack, from the org owner. After Slack is connected, we map a channel to a Promptwatch project. The map is one-to-one. Two clients in one channel is how a mention for Brand A gets actioned on Brand B.
A strategist who is not the org owner cannot connect Slack in our process. Org owner does Settings → Slack. Then we map channels. If the owner is slow, we wait. We do not connect a personal Slack app and call it the agency install. Connect the workspace the account actually uses, then create one private channel per client and invite the people on the retainer. Stay out of #general.
We never use #general. We never use the agency-wide #seo channel. We make a quiet channel named for the client and we invite the people who already get the monthly. If the client's own Slack is in the SOW, we map there instead of ours. Still not their #general.
Scheduled briefings are optional. We turn them on when the client asked for a pulse and we know they will not open Looker. The briefing skips if nothing changed. We would rather send silence than a "still the same" ping that trains everyone to ignore the bot. Accept that it will skip quiet weeks.
If the client wants a daily ping even when nothing moved, we explain the skip. A daily "no change" trains mute. If they still want a standing meeting, that is a meeting, not a bot.
This is not instant alerts. If you need a person watching errors, that is a human on Agent Analytics, not a Slack firehose.
What we say in the channel
We ask the agent about the prompts on that project. Mention vs citation. Which URL got used. Whether a persona row moved. We do not ask it to invent a win for the next status email.
Looker still holds the QBR. Slack holds the mid-cycle check. MCP in Claude is for the analyst who is already in an editor. Three surfaces, one project. See MCP and Looker. Keep Looker for the monthly, including Google's generative AI performance reports when Overviews are in the SOW. Keep Slack for questions on that project.
Kick-off at $199/mo is how we run this across accounts: unlimited projects and prompts, 10 seats. Essential is $95/mo, one project, fine for a single brand Slack. Professional is $245/mo. Business is $579/mo. Explore is free, 10 ChatGPT prompts, and is not a Slack program. G2: 4.7/5.
We refuse a briefing in a channel that also has memes and deploy pages. Nobody will read the GEO line. We also refuse mapping one Slack workspace to every Kick-off project without naming channels first. Connect Slack once (org owner). Then map, project by project. And we do not post crawler tokens, API keys, or draft CMS credentials in the Promptwatch channel. Keys belong in the password manager. The agent does not need them in chat.
FAQ
Who can connect Slack?
The org owner, from Settings. A strategist who is not the org owner cannot connect Slack in our process. We do not connect a personal Slack app and call it the agency install.
Why does the scheduled briefing skip some weeks?
It skips when nothing changed. A daily "no change" ping trains people to mute the bot. If the client still wants a standing meeting, that is a meeting, not a bot.
Is this the same as instant alerts?
No. If you need a person watching errors, that is a human on Agent Analytics, not a Slack firehose.
If you want the map done, hello@1001seomedia.com. Send the workspace name and the project list. Do not add us to #general.