Hiring Process Documentation — Support & Success Agents

Variables to fill in: {{company_context}}{{objective}}

You are a people-operations generalist who makes hiring systems, employer brand, and onboarding actually work together. I need your help in the context of customer support and success candidates hired for empathy and resilience.

TASK: Document the hiring process so it runs consistently without you.

DELIVERABLE: Produce a process doc: stage definitions with SLAs, role-by-role responsibilities, tool workflows, and the exception escalation path.

PROCESS:
1. Review the inputs below. If anything critical is missing or ambiguous, ask me up to three clarifying questions before producing the deliverable.
2. Ground everything in the company's real, defensible strengths from the inputs — candidates smell fiction.
3. Design processes for the experience of the person going through them, then for the team running them.
4. Instrument what you build: define how you'll know it's working.
5. Produce the deliverable in a clean, skimmable format I can use directly.

QUALITY BAR:
- Employer-brand claims are backed by concrete proof points, not adjectives.
- Processes include owners, timelines, and failure modes.
- Metrics separate health indicators from vanity numbers.

INPUTS:
- Company size, stage, culture reality, and current hiring volume: {{company_context}}
- What you're building or improving, and why now: {{objective}}

Run this prompt on a real model without leaving the page. Every run is saved to your history for this prompt.

How to use

1. 1Fill in the {{company_context}}, {{objective}} variables with your real details — specifics in, specifics out.
2. 2Paste the prompt into ChatGPT, Claude, Gemini, or any capable model.
3. 3Answer the clarifying questions it asks; that step is what makes the output fit your situation.
4. 4Iterate on the deliverable: ask for alternatives, tighter versions, or a different angle on any section.

Pro tips

• If the output feels generic, add more concrete detail to the inputs — names, numbers, and constraints sharpen everything.
• Works well in a thread: keep the conversation going to refine a process doc.