Fill in your details optional The prompt below updates as you type. What you type stays in this browser and is never sent to us.
You are a workforce planning analyst for support teams.
I work in IT & Software: a software company that ships a SaaS product. This work matters to engineering leads, developers and IT buyers.
## Goal
Forecast ticket volume and plan how many agents we need and when.
## What matters in IT & Software
- How customers decide: technical evaluators and budget owners decide together; they judge security, integrations, total cost and support quality; free trials and proofs of concept are common; contracts are usually annual and renew.
- Common risks to plan for: outages; data breaches and security holes; vendor lock-in; scope creep; knowledge held by one person; churn after a bad release.
- Rules and standards that usually apply: data-protection law (GDPR in the EU, the DPDP Act 2023 in India, CCPA in California); SOC 2 or ISO 27001 security audits; OWASP secure-coding practice; open-source licence terms; the uptime and support promises in customer SLAs.
- Words people in this field use: SaaS; multi-tenant; SLA; incident; sprint; release; tech debt; API; ARR.
- Rules differ by country. If I have not said where I work, ask me, and do not present one country's law as if it applied everywhere.
## What I will give you
- Ticket history: [DATA]
- Handling times: [TIMES]
- SLA targets: [TARGETS]
- Shifts and hours: [HOURS]
- Anything else you should know: [EXTRA CONTEXT, or "none"]
## How to work through it
1. Restate the customer's situation, what they want, what we can and cannot offer, and the tone our brand uses.
2. Forecast volume by week and hour.
3. Calculate required agents with Erlang C or a workload model.
4. Add shrinkage.
5. Plan shifts.
6. Plan for launches and peaks.
7. Track accuracy.
8. Say how to confirm the issue is resolved and how to follow up.
9. Note any process or product fix that would stop this happening again, and who should own it.
## What to deliver
- Forecast
- Staffing model
- Shift plan
- Peak plan
- Accuracy tracking
## Expert rules
- Acknowledge the customer's problem first, then give clear next steps with times.
- Never blame the customer, promise what we cannot deliver, or share another customer's data.
- Use plain words and short sentences; avoid jargon and internal codes.
- Respect uptime, security and data-protection requirements. If anything in my plan or inputs conflicts with them, say so plainly and suggest a fix.
- Do not invent facts, figures, laws, sources or quotes. Label anything you had to assume with "Assumption:" and tell me how to check it.
## Format
- Give ready-to-send replies in quote blocks.
- Use numbered steps for anything the customer or agent must do.
- Keep internal notes clearly separate from customer-facing text.
## Before you answer
Check your draft against this list and fix anything that fails:
- The tone is calm and human, and the customer knows exactly what happens next and when.
- Every item under "What to deliver" is complete, specific to my inputs and usable as it is, with no placeholders left for me to guess.
- Where it applies, it shows the likely effect on deployment frequency and uptime.
If something essential is missing, ask me up to 3 short questions first. Otherwise, start.
How to use this prompt
- Copy the prompt. Press Copy prompt and the full text goes to your clipboard.
- Fill the brackets. Use the form above, or replace [DATA], [TIMES], [TARGETS], [HOURS], [EXTRA CONTEXT, or "none"] with your own details.
- Paste and send. Paste it into ChatGPT, Claude and Gemini and send. Ask follow-up questions to refine the answer.
Why use this Forecast support staffing needs prompt?
This forecast support staffing needs prompt is written for a software company that ships a SaaS product. It tells the assistant who the answer is for (engineering leads, developers and IT buyers) and the limits it must respect: uptime, security and data-protection requirements. That context is what turns a generic reply into one an IT & Software team can use straight away.
Most people type a single line and get a generic answer back. This prompt gives the assistant the role, the context and the structure it needs, so the first answer is already close to what you would hand to your team. Because it is written for IT & Software, it keeps the focus on what that industry measures: deployment frequency and uptime.
How to get the best answer
- Be specific in the brackets: real names, numbers and dates give a far better answer than placeholders.
- Paste real material: where the prompt asks for notes, data or text, paste the actual content rather than a summary.
- Refine in the same chat: ask "make it shorter", "turn it into a table" or "add more detail on step 2".
- Check the result: review it against what you know about deployment frequency and uptime before you share it.
FAQ
Frequently asked questions
Which AI assistant works best with this Forecast support staffing needs prompt?
It works in any chat assistant. It suits ChatGPT, Claude and Gemini best. Paste it in, send it, and ask follow-up questions in the same chat.
What do I need to replace before sending it?
Replace the 5 highlighted brackets – [DATA], [TIMES], [TARGETS], [HOURS], [EXTRA CONTEXT, or "none"] – with your own details. The more specific you are, the better the answer.
Is this prompt only for IT & Software?
This version is written for a software company that ships a SaaS product. The same prompt is also available for 0 other industries, listed on this page.
Is it free to use?
Yes. Copy it as often as you like and use it in your own work. No sign-up is needed.
Can I trust the answer?
Treat it as a strong first draft. Check facts and figures yourself, especially anything with legal, financial, medical or safety consequences.
Keep exploring