An employee you can audit.
Trust in an AI teammate comes from knowing exactly what she can’t do. Here is Eko’s full permission surface, and the guarantees behind it.
No auto-posting. Ever.
Eko has no code path that publishes to social platforms. She drafts responses; a human copies, edits and sends. This isn’t a toggle you could misconfigure. The capability doesn’t exist.
She only reads the channel you invite her to
Eko reads messages only in the channel you explicitly invite her to, so you can talk to her there like a colleague. She processes them in the moment to answer you and never stores your team's conversations. DMs, private channels she isn't in, and every other channel stay invisible to her.
Listening happens outside your workspace
Everything Eko reports about your brand comes from public conversations on the web, gathered by Buska's engine. Your Slack is where she talks with you and delivers, not a source she mines.
Commercial data goes to Buska only when you press the button
The Send to Buska handoff is always human-initiated. Nothing is forwarded to Buska’s lead-gen pipeline automatically.
Slack scopes she requests
The minimum needed to deliver briefs and take assignments.
chat:writePost briefs, digests and signal cards in channels she’s invited to.
commandsRespond to /eko slash commands and Ask Eko questions.
channels:readKnow which channels she’s a member of, to deliver to the right place.
channels:historyRead messages in the single channel you invite her to, so you can ask her questions without an @mention. Processed transiently, never stored.
users:readResolve @-mentions when a signal is assigned to a teammate.
im:writeDM a teammate when a signal is assigned to them, with their name only.
groups:historyim:historympim:historyfiles:readEko still requests no groups:history, im:history, mpim:history or files:read: your DMs, private channels she isn't in, and your files stay invisible to her.
Data handling
- Signals are public web content plus Eko’s analysis. They live in your Slack and in your Eko workspace, and are deleted when you offboard her.
- Feedback actions (ignore, mark as noise) train only your workspace’s filters, never a shared model across customers.
- The Buska handoff transmits the signal, its source URL and Eko’s context, nothing else from your Slack workspace.
Rules of engagement
The operating rules Eko ships with. On the Business plan they’re customizable; the guarantees above are not.
Humans send, Eko drafts
Eko never posts publicly or replies automatically. She drafts responses for a human to review, edit and send.
Commercial intent goes to Buska
If a signal looks like a buying opportunity, Eko surfaces a 'Send to Buska' action instead of engaging. Lead gen is Buska's job.
Reputation risk escalates immediately
Negative signals gaining traction are flagged as critical, posted in-channel and recommended for assignment within minutes, not batched into the digest.
Competitor threads stay classy
On competitor complaints, Eko drafts helpful, non-disparaging responses. She never recommends trashing a competitor.
Noise teaches Eko
'Mark as noise' trains Eko's filters. Two similar dismissals and that pattern stops reaching your channel.
Digest by default, alert by exception
Routine signals batch into the daily digest. Only high-urgency signals interrupt the channel in real time.
Every claim has a source
Each signal links to the original post. Eko never asks the team to act on something it can't verify.