IT OPS

CEO-Driven Investigation of High-Cost Dormant Seats

For each expensive dormant seat, an agent gathers evidence across usage logs, HR status, and ticket history.

CategoryIT Ops
Enginepaperclip
Difficultyadvanced
Triggerwebhook
Steps5
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWebhook delivers high-cost dormant seatHTTP webhook
  • ActionPull activity timeline from BigQueryGoogle BigQueryBigQuery
  • LogicAgent reasons over evidence for false positives
  • ActionWrite reclaim-or-retain recommendation to NotionNotionNotion
  • OutputFlag review page for IT leadNotionNotion

What it does

When a high-cost seat trips the dormancy threshold, an agent investigates rather than auto-revoking. It pulls last-activity data from BigQuery, checks whether the user is still active in your HR or ticketing context, and weighs whether the seat is genuinely waste or a seasonal-use license. It writes a structured reclaim-or-retain recommendation with its reasoning into a Notion review page.

When to use it

Use it for premium, high-dollar licenses where a wrong revoke is costly and context matters more than a simple idle timer. Best when seat decisions need judgment across multiple signals, not a fixed rule.

How it works

  1. 1A webhook delivers a high-cost dormant seat to the agent.
  2. 2The agent queries BigQuery for the detailed activity timeline.
  3. 3It cross-checks employment and recent ticket signals to rule out false positives.
  4. 4The agent reasons over the evidence and forms a recommendation with confidence.
  5. 5It writes the findings and recommendation to a Notion review page for an IT lead to action.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect BigQueryDatasets, queries, schemas.
  2. 2
    Connect NotionPages, databases, comments.
  3. 3
    Connect HTTP webhookTrigger any URL on agent actions.
  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.