IT OPS

Dormant-Seat Self-Service Keep-or-Release Poll

Weekly, it DMs each user flagged as dormant a keep-or-release prompt; non-responders after a grace window are auto-released and the result is logged to the license register.

CategoryIT Ops
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule fires
  • ActionRead dormant seats and prompt dates from AirtableAirtableAirtable
  • LogicBranch: newly flagged vs past-grace non-responder
  • ActionSend Keep/Release DM to user in SlackSlack
  • OutputRelease seats and update license registerAirtableAirtable

What it does

Pushes the reclaim decision to the seat holder instead of a manager. Dormant users get a direct Slack message asking if they still need the tool; anyone who actively keeps it stays, while silence past the grace window means the seat is released automatically.

When to use it

Best for self-serve tools where the user is the right judge of need and you want to scale reclamation without manager bottlenecks, while still giving people a fair chance to opt in.

How it works

  1. 1A weekly schedule starts the run.
  2. 2The flow reads dormant seats from Airtable, including the assigned user and the date they were first prompted.
  3. 3A logic step branches users into newly flagged (send prompt) and past-grace non-responders (release).
  4. 4Newly flagged users receive a Keep / Release Slack DM, and the prompt date is recorded.
  5. 5Past-grace non-responders have their seats released and the outcome is written back to the license register in Airtable.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect AirtableBases, tables, views, automations.
  2. 2
    Connect SlackChannels, DMs, threads, mentions.
  3. 3
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  4. 4
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  5. 5
    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.