Console's Proactive Playbooks: IT That Moves Before You Do

Today, we're hard launching Proactive Playbooks: automation that doesn't wait for humans to kick it off.

[INSERT LAUNCH VIDEO - YOUTUBE LINK]

Playbooks that act without a human

Proactive Playbooks extend Console's existing playbook system to trigger on external events, not just inbound requests. Your team configures them the same way they configure any Console playbook: natural language instructions, connected integrations and actions, approval gates where needed. The difference is what kicks them off:

• A webhook fires when a new hire is created in Workday. Console provisions their apps, adds them to the right groups, asks them what size sweatshirt they wear, and delivers onboarding materials before they've sent a single Slack message.

• A scheduled event triggers a Playbook to run every Monday morning at 9:00 and reminds managers to complete access reviews. Even better, a scheduled event triggers a Playbook to run every Monday for an agent to complete user access reviews and deliver a completed report to you, the user.

• Console detects a user’s machine has been running slow for 3 days, conducts an investigation, proposes a fix to the user in Slack or Teams and their device is back to full speed without anyone from IT getting involved.

A compliance alert comes in from your device management tool and Console opens a remediation ticket, notifies the user, and logs the incident. Additionally, Console agents will reason and take additional steps, like gathering more information from humans, to accomplish the task.

We could go on but you get the idea. The work gets done. Your team directed a team of agents to do it. They just didn't have to be there when it happened.

A Unified Authoring Experience

Proactive Playbooks are a natural extension of what your team already does.

It’s the same execution model, but a different upstream trigger. Proactive Playbooks run without a human requester and often without a conversation thread. Agents take in inputs from the triggering event, resolve the right entities, and execute. When they need to reach out to a user, like walking an employee through a compliance remediation, they hand off to a standard Console conversation, then close out the job.

Every execution is logged. Your team can see what triggered the playbook, what inputs it received, what actions it took, and where it succeeded or failed. Full visibility, with 100% parity with requests, into what happened, without anyone having to watch it happen.

Why This Matters

Engineers made a shift when they stopped writing code and started delegating to agents. The leverage wasn't just writing code faster, it was that a team of agents could cook while the engineer was doing something else entirely. They went from manning the line to running the kitchen.

Proactive Playbooks give IT and operations teams the same kind of leverage. 

IT teams have spent years being reactive by necessity. The tooling forced it. Proactive Playbooks are built on the premise that the best operations don't wait for problems to arrive, they act and avoid problems all together.

Getting Started

Proactive Playbooks are available now. If you're already using Console, you can start configuring webhook and schedule triggers in your playbook settings.

Your team builds the playbook once. Console runs it every time the conditions are met. Things happen. Problems don’t. 

IT’s time to build.

Interested in seeing Proactive Playbooks in action? Get in touch →