CHATBOTS

Outlook HR Bot: Escalate Sensitive Cases to a Teams Queue

Triages incoming HR emails, auto-answers routine questions, and routes sensitive or unanswerable cases to an HR triage channel in Teams with a logged ticket in Postgres.

CategoryChatbots
Enginesim
Difficultyintermediate
Triggerevent
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew email in HR mailboxOutlook
  • LogicClassify sensitivity + topic
  • LogicBranch: sensitive/out-of-scope vs. routine
  • ActionLog triage ticket to PostgresPostgreSQLPostgres
  • ActionPost escalation card to Teams triage channelMicrosoft Teams
  • OutputSend 'human reviewing' ack via OutlookOutlook

What it does

This flow is the escalation half of an HR helpdesk. It reads each email to the HR mailbox, handles the safe routine ones, and reliably escalates anything sensitive — harassment, accommodations, terminations, anything not covered by docs — to a human, with a tracked ticket.

When to use it

Use this when the risk of a bot mishandling a delicate HR matter is real. It guarantees sensitive topics never get an automated answer and always reach a person, while still deflecting routine volume.

How it works

  1. 1A new email arrives in the Outlook HR mailbox and triggers the flow.
  2. 2A classifier scores sensitivity and topic, tagging anything legal, medical, disciplinary, or out-of-scope as an escalation.
  3. 3Sensitive cases skip auto-answering entirely and branch to escalation.
  4. 4The flow writes a triage ticket (requester, subject, category, priority) to a Postgres helpdesk table.
  5. 5It posts a summary card to the HR triage channel in Teams so a coordinator can pick it up.
  6. 6The requester gets an Outlook acknowledgment that a human is reviewing their case.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect OutlookMail, calendar, contacts.
  2. 2
    Connect Microsoft TeamsChannels, chats, files.
  3. 3
    Connect PostgresAny Postgres URL — query, write, migrate.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    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.