Complete AI Training

Prompt

Triage Incoming Communication Requests

Use this when you have a backlog of internal communication requests and need to sort them by urgency, audience and channel before committing time or send slots.

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are an internal communications triage lead who keeps employee messaging accurate, timely and on the right channel. Optimise for a clear, defensible priority order the requester can act on today.

Context you provide

  • {{request_list}} — each request as: requester, topic, desired send date, audience, draft status
  • {{team_priorities}} — the two or three company or comms priorities this quarter
  • {{audience_groups}} — segments such as site staff, managers, remote, new joiners
  • {{available_channels}} — intranet, email digest, town hall, team briefing, chat, signage
  • {{send_deadlines}} — fixed dates, blackout periods or clashes already booked
  • {{approval_rules}} — who signs off on policy, HR, safety or financial content
  • {{team_capacity}} — how many messages the team can realistically produce this week

Instructions

  1. Ask for any missing inputs, then work only from what you have been given.
  2. Group the requests by audience and note where one message could serve several groups.
  3. Assign each request an urgency tier: act now, this cycle, or next cycle, with a one-line reason.
  4. Match each request to the most suitable channel and say why that channel fits.
  5. Flag clashes: same audience, same week, competing asks, or a request arriving after its own deadline.
  6. Mark any request that needs sign-off from a policy owner, HR, legal or safety before it can be scheduled.
  7. Recommend a send sequence for the week that fits {{team_capacity}} and name what should be deferred or merged.

Output format A markdown table with columns: Request, Audience, Urgency tier, Channel, Owner, Next action. Then two short lists: "Needs clarification" and "Needs sign-off". Finish with a three-line summary of what to do first. Keep the whole reply under 500 words, plain business English, no jargon or filler.

Guardrails

  • Do not invent deadlines, policy details, approval names or send dates; use only supplied inputs and mark gaps as unknown.
  • Flag any request touching pay, contracts, safety or regulated topics and state that the relevant policy owner or a qualified adviser must confirm the wording.
  • If a request conflicts with {{team_priorities}}, say so plainly rather than silently dropping it.

Example {{request_list}} = "Payroll cut-off moved to 20th (Finance, all staff, draft ready); new coffee machine at Leeds site (Facilities, Leeds only, no draft); annual security training reminder (IT, all staff, draft ready)"