Made for Administrators
Use Ready-to-Send Messages for Intake, Boundaries, and Follow-Up
Also useful for: people in Government
Create a reusable message pack for handling incomplete requests, wrong-channel work, unsupported urgency, ownership, dependencies, delays, escalation, and closure. Get three tone options for each situation.
Create a free account to save your progress and use this Playbook.
Use this when
Use this when you regularly coordinate requests across email, chat, forms, or ticketing systems and need firm but adaptable language for common intake and follow-up moments.
You'll need
- Approved Intake Channel
- Required Request Details
- Priority and Urgency Rules
- Ownership and Escalation Rules
- Closure Standard
- Primary Message Channel
- Default Tone
- Style Constraints
You'll get
- 24 distinct message templates across eight situations and three tones
- A trigger, fact check, channel recommendation, and record note for every situation
- Your templates don't invent commitments, and each one makes ownership, action, and timing visible
- You can select, customize, and send the right message in a few minutes.
By the end of this playbook
You will have:
- 24 distinct message templates across eight situations and three tones
- A trigger, fact check, channel recommendation, and record note for every situation
- Your templates don't invent commitments, and each one makes ownership, action, and timing visible
- You can select, customize, and send the right message in a few minutes.
Sample
This is sample data, not your prompt. Pro unlocks this higher-stakes Playbook. On Free Playbooks you can still copy the assembled prompt into any AI.
Sample input
Your approved intake channel is the Service Requests form. You need the outcome, reason, requested date, deadline source, affected service, and approving lead. Your urgent category covers service outages, safety issues, and fixed compliance deadlines. Your normal turnaround is three business days. You escalate blocked requests to the Operations Manager after two missed dependency dates. Your default channel is email, and your default tone is neutral.
Sample assembled prompt
Situation: You need to decline unsupported... Direct version: Subject: Priority review needed... Your earliest confirmed completion window is... If your impact has changed, submit... Neutral version: Subject: Timing for [REQUEST]... Your requested [DATE] deadline can't be... Your current completion window is [DATE]. You can request a priority review... Your request will remain in the... Collaborative version: Subject: Confirming the right... Based on your current details, the... If your impact meets an urgent... Your record note: Your requester received...