Curve, in the channel your team already uses.
Mention Curve in Slack and get an answer with sources in the thread. Recommendations arrive as cards in the channel you pick, with Approve on them. Nothing ships without a yes.
No credit card required.
Installed from Supercurve in one click. Public channels only, and every action from Slack is made as the person who clicked.
Two things, done well.
From a channel, Curve reads and answers, and brings the Inbox to you. Drafting, facts, and settings stay in Supercurve.
Answers in the thread
Mention Curve with a question. It answers in a thread, with the numbers, their time window, and the sources. Follow-ups in that thread need no mention.
Sessions were up 14% week over week (GA4, Aug 25 to 31). Almost all of it is organic: the pricing comparison post moved from position 9 to 4 for “marketing automation pricing” and brought 610 new sessions.
Sources: GA4 · Search Console · Inbox item “Pricing comparison post”
Inbox cards, buttons included
Pick one channel and every new recommendation and the daily report arrive as cards. Approve, view, or archive from Slack; the card turns into the outcome the moment it is handled.
New recommendation for acme.com
LinkedIn post: what the last three pricing pages we fixed had in common
Why: the pricing comparison post is your best organic page this month and nobody has posted about it. Draft ready in your voice.
Plain words are enough.
Curve reads the thread it was mentioned in, then its own data, memory, and Inbox.
- Ask
@Curve what changed in our traffic last week, and why?
GA4 and Search Console numbers with their window and sources, in the thread.
- Ask
@Curve why did the pricing page drop in search?
The page's queries and positions, what changed on it, and what to look at next.
- Read
@Curve what is waiting for us in the Inbox?
Open drafts, reports and heads-ups by title, each with a link.
- Read
@Curve which prompts do AI assistants mention us for?
The tracked prompts and each one's mention rate.
- Ask
@Curve what did this thread decide about the launch date?
Curve reads the thread it was mentioned in and answers from what was said there.
- Ask
@Curve for shop.acme.com, how did last week's LinkedIn post do?
When a workspace serves several websites, naming the site picks it.
Four steps, no keys.
A workspace admin installs it once. Everyone else just mentions Curve.
- 01
Add to Slack
From the Slack page in Supercurve, one click installs Curve in your workspace. A workspace admin approves it once.
- 02
Invite Curve to a channel
Type /invite @Curve in any public channel. Curve only ever sees the channels it is invited to.
- 03
Pick a channel for cards
Choose one channel and turn Inbox items on. New recommendations and the daily report arrive there as cards.
- 04
Link your account, once
The first time you click Approve, Curve sends a link only you can see. Open it signed in, and every later click is yours.
Built for the channel, not the archive.
Curve is a teammate in the room, not a copy of your workspace.
Never private channels, direct messages, or channels shared with other companies. Curve reads only the channels it is invited to.
On, Curve keeps 90 days of the channels it is in so answers have context, and forgets on request. Off, it reads only the thread it was mentioned in.
Approvals from Slack are made as the person who clicked, with the permissions they have in Supercurve. Someone outside the team gets a refusal, not a result.
Remove the app from Slack and every stored message, connection, and account link is gone. Your messages never train a model.
Questions, answered.
Every plan, while the app is in beta. Install it from the Slack page in Supercurve; the credits an answer uses are the same as asking Curve in the app.
Only what you set it to: cards for new Inbox items and the daily report, in the one channel you choose. Nothing is published to LinkedIn, your site, or anywhere else from Slack without a click on a card, and every click is the person who made it.
Yes. One workspace can serve several websites. Name the site in the question and Curve answers for it; each website picks its own channel for cards.
No. It answers when mentioned in a public channel it has been invited to, and replies inside threads it has already answered in. Private channels, direct messages, and Slack Connect channels are never read or stored.
Answers come from an AI model reading your connected data, and everyone in the channel can see them. Curve cites its sources so you can check the numbers in Supercurve before acting on them.