Slack

Ask where you already talk.

Ask @anedai in any Slack thread and it answers there, as you; and workflows post updates to your channels.

A Slack thread in #payments: Lena asks @anedai what's blocking Payments this sprint, and anedai answers with the two blocked issues and who's on them

Why Slack

Why it saves time.

  1. 01

    No tab switch for a quick answer.

    “Who's on PAY-142?” gets answered where it was asked.

  2. 02

    The right people hear about the right things.

    A Bug from an Enterprise customer lands in #support the moment it comes in, with the link to it.

  3. 03

    Nothing leaks.

    Answers run as the person asking, with exactly their access.

  4. 04

    Set up once.

    One admin connects it; everyone else just mentions @anedai.

What it does

Inside Slack.

  1. 01

    Connect once

    A workspace admin clicks Connect in Settings → Integrations and approves it in Slack. Nobody else sets anything up.

    Settings → Integrations: the Slack card goes from Connect to Connected, with the workspace's name
  2. 02

    Ask in any thread

    Mention @anedai in a channel, or send it a direct message. It answers in the thread, and replies there carry the conversation on.

    A Slack thread: who's on PAY-142, anedai answers, then a follow-up without the @ gets answered too
  3. 03

    Updates where the team already is

    A workflow's “Post to Slack” step drops a message in the channel you pick, with the signal's or issue's title, customer and link filled in.

    A workflow's Post to Slack step, and the message it posts in #support with the customer, the signal's title and its link

The details

Small things that add up.

  • It answers as you

    Matched to your anedai account by email, so it sees only what you can: private teams stay private.

    A member gets the Growth backlog; someone without an anedai account is told to use the same email in both
  • The thread remembers

    Each thread is its own conversation; follow-ups don't need the @.

    A thread where “who's on it?” gets answered without mentioning anedai again
  • Problems that say how to fix them

    A channel it can't post in, or a workspace that needs reconnecting, says so in the run.

    A failed run: the Slack step says to invite @anedai to the channel first
  • Pick the channel, write the message

    Channels come from your workspace; the message takes the same variables as any workflow step.

    The Post to Slack step with its channel list open: support, payments, product-feedback, releases, and a private channel

FAQ

Questions, answered.

Who sets it up?

A workspace admin, once: Settings → Integrations → Slack → Connect, then approve it in Slack. One Slack workspace connects to one anedai workspace.

What can @anedai see in Slack?

Exactly what the person asking can see in anedai. Their Slack account is matched to their anedai account by email; someone it can't match gets nothing.

Do I need to invite it to a channel?

To mention it there, yes: /invite @anedai. Workflows can post to public channels without an invite; a private channel shows up once @anedai is in it.

Does it use credits?

Yes, like @anedai in the app: each answer is an AI turn on the workspace's credits.

One connected product memory for the people and AI building your product.

Bring your tools, your docs and your team. AnedAI keeps the story between them.