agent hive

AI & RAG

Slack Battlecard Answerbot Grounded in Win-Loss Notes

A Slack bot that answers rep questions about a named competitor by retrieving relevant win-loss notes and approved battlecards, then drafting a grounded, cited response in-thread.

CategoryAI & RAG
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerRep mentions bot in Slack with competitor questionSlack
  • ActionEmbed question and similarity-search win-loss notesPostgreSQLPostgres
  • ActionFetch matching battlecard pagesNotionNotion
  • ActionDraft grounded, cited answer with LLMOpenAI
  • OutputPost cited reply in Slack threadSlack

What it does

Reps in a deal can ask, in Slack, how to handle a competitor objection. The bot retrieves the most relevant win-loss notes and approved battlecard sections, then composes a concise answer that cites exactly which past deals and cards it drew from — so no one is guessing or inventing claims.

When to use it

Use it when your sellers keep pinging product marketing or sales leadership for competitive talk tracks mid-deal, and you want consistent, source-backed answers instead of tribal knowledge. Best when win-loss notes already live in Notion and you have a vector store of them.

How it works

  1. 1A rep mentions the bot in a Slack channel with a competitor name and question.
  2. 2The bot embeds the question and runs a similarity search over indexed win-loss notes in Postgres.
  3. 3It pulls the matching battlecard pages from Notion for that competitor.
  4. 4An LLM drafts a grounded answer, refusing to speculate beyond retrieved sources.
  5. 5The reply posts back in-thread with citations linking each claim to its source note or card.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect SlackChannels, DMs, threads, mentions.
  2. 2
    Connect PostgresAny Postgres URL — query, write, migrate.
  3. 3
    Connect NotionPages, databases, comments.
  4. 4
    Connect OpenAIModels, embeddings, files.
  5. 5
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  6. 6
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  7. 7
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.