CHATBOTS

Slack HR Escalation Router

Catches HR questions the concierge bot can't resolve, classifies them by topic and sensitivity, opens a tracked ticket in the HR Postgres.

CategoryChatbots
Enginepaperclip
Difficultyadvanced
Triggerevent
Steps6
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerUnresolved HR question flagged in SlackSlack
  • ActionClassify topic and sensitivityOpenAI
  • ActionCreate tracked ticket in HR PostgresPostgreSQLPostgres
  • LogicBranch on case sensitivity
  • OutputEmail sensitive cases to HR leadGmailGmail
  • OutputReply in Slack with ticket referenceSlack

What it does

When a Slack HR question falls outside what the bot can safely answer (payroll discrepancies, leave-of-absence, sensitive personal matters), this flow turns it into a tracked HR ticket and routes it to the right person, then confirms the ticket number back to the employee.

When to use it

Use this as the escalation backstop behind your Slack HR concierge. It ensures nothing gets dropped: every unhandled question becomes a logged, owned ticket instead of a message that scrolls away.

How it works

  1. 1An escalation event (a message flagged as unresolved, or one posted to the escalation channel) triggers the flow.
  2. 2OpenAI classifies the question's topic and whether it is sensitive or confidential.
  3. 3The flow inserts a ticket row into the HR Postgres tracker with topic, requester, and priority.
  4. 4A logic branch checks sensitivity: routine cases stay in the Slack HR channel thread.
  5. 5Sensitive cases are routed directly to the HR lead by email via Gmail, and the employee gets a Slack reply with their ticket reference.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect SlackChannels, DMs, threads, mentions.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect PostgresAny Postgres URL — query, write, migrate.
  4. 4
    Connect GmailRead, draft, send, label.
  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.