PLAYBOOKS

Reuse proven fixes without rewriting every step.

Save VPN, printer, EDR, and recovery instructions once, load them into live sessions, and adapt them for the endpoint or environment in front of you. Pharaoh helps teams move faster on repeat work while preserving the local judgment each incident still needs.

Reusable fixes Saved instructions keep frequent troubleshooting steps ready to load.
Adapt per incident Teams can start from a proven draft and adjust only what the endpoint requires.
Usage visible Sent messages record the Playbook reference and whether it was changed.

Scope a Pilot View Playbook examples

WHERE IT HELPS

Built for repeatable work that still needs technician judgment.

Playbooks reduce variance in high-volume endpoint and support requests while preserving local review, approval gates, and the final technician instruction.

In plain English Playbooks are reusable troubleshooting instructions. They help technicians start from approved steps, but they do not grant Pharaoh permission to make changes by themselves.

Use this when

Your team or service desk keeps rewriting the same VPN, printer, disk cleanup, or EDR health checks.
A new admin or technician needs approved standard work during an incident instead of relying on memory.
You need the session record to show which shared instruction was loaded, what changed, and what was sent.

Governance model

Reusable instructions speed up drafting, but the outgoing request remains visible, editable, and subject to the normal approval model before it leaves.

Standard work, not approval: Playbooks help draft the request; approval rules still control what Pharaoh may do.
Local edits stay local: Changing a loaded draft affects the outgoing message, not the shared Playbook.
Shared change is visible: The editor shows autosave, metadata, owner, and usage count before shared instructions change for everyone.

HOW IT WORKS

Save once, reuse consistently, adapt per incident.

Playbooks live as a governed library. Loading one into a composer is local to that message; your team's reusable standard work only changes when someone edits the shared Playbook.

01
Save

Capture a repeatable incident instruction as a Playbook with Markdown content and tags so the team or service desk can find it quickly.
Markdown · tagged
02
Load

Open Load Playbook from any supported composer, search and preview, then load it into the active draft — Pharaoh confirms before replacing existing text.
Composer · confirm-on-replace
03
Adapt

Edit the loaded instructions for the specific endpoint and incident — local edits stay with the message, not the Playbook.
Local edits · global preserved

LIBRARY

A searchable home for repeatable incident instructions

The Playbooks list is the discovery surface during an incident or ticket: search by title or content, filter by tag, sort by Last updated, and create or open a Playbook from one place. Use clear titles and tags that match the system, symptom, or workflow your team reaches for.

Search by title or content and filter by tag
Sort by Last updated, Title A-Z, or Title Z-A
Create with New Playbook or open an existing one for editing
Pagination keeps larger libraries usable without losing filters

Playbooks list showing search, tag filtering, sort controls, and reusable incident instructions

EDITOR

Edit Markdown, tags, and metadata in one focused page

The detail editor is where Playbooks evolve. Watch autosave status as you change Title, Markdown content, or tags. Created by, Last edited by, and usage count tell you how widely instructions are used before you make a shared change.

Edit Title, Markdown content, and tags with visible autosave state
Duplicate a Playbook for a close variant; delete only with confirmation
Created by, Last edited by, and usage count surface impact before edits
Deletes do not strip Playbook metadata from messages already sent

Playbook detail editor showing Markdown content, tags, autosave state, usage count, duplicate, and delete actions

COMPOSER LOAD

Load proven instructions without leaving the workspace

Load Playbook is available from the Endpoint Session composer, the Remote KVM web composer, and the Agent Core thread composer. Search, sort, preview, and load — and edit the global Playbook itself in the picker if you spot a correction worth keeping.

Search, sort, and preview inside the picker before loading
Edits in the picker autosave back to the global Playbook
Available in Endpoint Session, Remote KVM web, and Agent Core composers
Sent-message metadata records the Playbook reference and whether it changed after loading

Load Playbook picker showing searchable Playbooks, preview, global editor, and the Load Playbook action

GUARDED REPLACE

Never lose a draft to an accidental Playbook load

When the composer already has draft text, loading a Playbook prompts for confirmation before replacing it. Local composer edits remain with that request — only edits in the detail editor or the picker change the reusable Playbook for everyone else.

Confirm-before-replace protects in-flight composer drafts
Local composer edits stay with the outgoing message, not the Playbook
Global edits via detail page or picker affect all future use
Usage count increments only on accepted send, not on previews or loads

Playbook replacement warning shown when loading a Playbook over an existing composer draft

Reusable

A Playbook is a starting instruction — not approval and not an automation grant.

Discoverable

Tags, search, and sort keep the right Playbook reachable mid-incident or mid-ticket, not buried under stale ones.

Traceable

Sent messages record the Playbook reference and whether it was edited after loading.

EVALUATE PHARAOH

Scope a governed remediation pilot.

Review the product, active controls, security review questions, integration priorities, and deployment fit across your internal environment or managed client fleet.