CHATBOTS

Agentic Benefits Concierge Across Confluence and Past Tickets

An agent in Teams resolves multi-step benefits questions by reasoning over the HR Confluence space and prior resolved questions in Postgres.

CategoryChatbots
Enginepaperclip
Difficultyadvanced
Triggerchat
Steps6
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerEmployee asks a multi-part benefits question in TeamsMicrosoft Teams
  • ActionAgent searches HR Confluence policy pagesConfluenceConfluence
  • ActionAgent queries prior resolved questions in PostgresPostgreSQLPostgres
  • LogicDecide: enough evidence vs. ask a clarifying question
  • ActionSynthesize cited answer via OpenAIOpenAI
  • OutputPost answer in Teams and log resolution to PostgresMicrosoft Teams

What it does

Handles harder, open-ended benefits questions that need more than one lookup. The agent decides whether to search Confluence policy pages, check how a similar question was resolved before (from a Postgres history table), or both, then synthesizes a single grounded answer in Teams.

When to use it

When employees ask layered questions ("I'm relocating mid-year and adding a dependent, what changes?") that a single retrieval can't cover. Use it when you want agent-driven reasoning that mirrors how an experienced HR rep chains sources.

How it works

  1. 1An employee asks a multi-part question in Teams.
  2. 2The agent plans which sources to consult based on the question.
  3. 3It searches the HR Confluence space for the relevant policy pages.
  4. 4It queries Postgres for previously resolved questions on the same topic to reuse vetted answers.
  5. 5The agent evaluates whether it has enough grounded evidence; if not, it asks a clarifying question in Teams.
  6. 6Once confident, it synthesizes a cited answer and posts it, then logs the resolution back to Postgres for reuse.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect Microsoft TeamsChannels, chats, files.
  2. 2
    Connect ConfluenceSpaces, pages, blueprints.
  3. 3
    Connect PostgresAny Postgres URL — query, write, migrate.
  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.