Your marketing data, in the channel.
Ask a question where the team already is, and get the answer in thread. Anomalies, digests and scheduled reports arrive without anyone asking.
Ask next: Which campaign drove it? • Compare to last month
A step inside Cresva rather than a way to sign up. Not signed in? The link stops at login and brings you back.
Four things that show up on their own
These are scheduled jobs, not notifications you configure one by one. The cadence beside each is the schedule it actually runs on.
Anomalies, as they surface
A metric that moved further than its own history says it should. The message carries the z score, a severity, the brand and the company, and the UTC minute it was detected. Grouped per channel, so one post covers everything found in that window.
The daily spend digest
One company summary, then a line per brand. Each carries a freshness stamp in minutes, so you can tell at a glance whether you are reading this morning's numbers or a stalled pipeline.
Scheduled reports, delivered
When a report finishes, it arrives with a View Report button rather than a link buried in prose. The greeting is time aware, so a report that lands at 09:00 does not open by telling you it is the end of the day.
The weekly safety receipt
A week in one message: days all safe, total spend monitored, and every cap hit or failure worth naming. When there is nothing to report it says so plainly, which is the point of a receipt.
What you would actually ask
Mention the app in a channel or send it a direct message. It answers in a thread under your message, so a channel can hold several of these at once.
“What was our Meta spend last week?”
Mention the bot in a channel or send it a direct message. It posts a placeholder immediately and replaces that message in place once the answer is ready, so the thread never fills with progress noise.
“Why did ROAS drop on Tuesday?”
The same agent that answers in the dashboard answers here, with the same tools. It reads the data itself rather than searching for a saved report that happens to cover the question.
“Which campaigns are worth more budget?”
Answers arrive threaded under the message you sent, so a channel can hold several conversations at once without any of them turning into a wall of replies.
Where the line is
Answers in Slack are text. Charts, approving an action, and uploading a file are dashboard work, and Slack does not pretend otherwise. Slack is where the work is reported and where you can ask about it, and the dashboard is where you change something.
One command, /shield
Point the digests at a channel without going back to the dashboard. Replies are ephemeral, so running it does not clutter the channel for everyone else.
Tip: `@Shield last 7 days for BRAND`
Only visible to you
/shield brands
Lists the brands you can ask about, as buttons.
/shield summary-here
Makes the current channel the one that receives digests.
/shield set-channel BRAND
Records a channel for one brand by name.
A workspace, scoped to one company
Every request is verified
Every request Slack sends is checked against an HMAC-SHA256 signature over the raw body, inside a five minute replay window, before any of it is read. A request that fails is refused rather than logged and processed.
Thread replies are rate limited per brand per hour, so a busy channel cannot turn into an unbounded bill.
Tokens and tenancy
The workspace token is encrypted with AES-256-GCM before it is stored, and the column that holds it is classified as sensitive in the schema.
A Slack request can only act inside the company whose connection carries that workspace id. Nothing resolves a brand or a company globally, and a regression test holds that line.
Slack, Claude and ChatGPT reach the same intelligence layer
This page is the Slack door, where the team already works. The others put the same layer inside an assistant. They are ways in rather than separate products.
Questions
Do I need a Cresva account first?
Yes. Connecting Slack is a step you take from inside Cresva, not a way to sign up. The install flow requires an existing login and a company, and it has to finish in the same browser that started it. If you are not signed in, the connect link sends you to the login page first and returns you afterwards.
Which brand does it answer about?
The brand recorded on the Slack connection, which is the one that was open when the workspace was connected. Per channel brand routing is not wired yet: a question asked in one channel and the same question asked in another are answered about the same brand.
Can it post charts?
No. Answers in Slack are text. Charts are a dashboard feature.
Can I approve actions from Slack?
No. Approvals happen in the dashboard or through the links in approval emails. Slack is where the work is reported and where you can ask about it.
Does it remember the conversation?
Within a Slack thread it carries recent context, and a reply in a thread is read against the message it replies to. It does not share history with the dashboard: a question asked in Slack does not appear in your dashboard threads, and the reverse is also true.
Can one company connect two Slack workspaces?
No. Connecting a second workspace replaces the first. One workspace per company.
What can it see?
The same data the dashboard can see for that company, because it is the same agent behind both. It reads only the workspace it was installed into, and only within the company that installed it.
What does it need from Slack?
Permission to read mentions, post messages, list channels, register the slash command, and look up users. It does not request permission to read your channel history.
Ask in the channel. Answer in the thread.
Takes a minute, and needs an existing Cresva account.