wowprompt

Support response time targets by ticket priority and channel

Sets first response and resolution time targets for each ticket priority and channel, checks them against your team size and ticket volume, and writes the customer-facing promise to match. Use it when setting up a support desk, adding a new channel such as WhatsApp or chat, or when targets are missed every week.

A priority definition table, a target table by priority and channel, a staffing check with the numbers shown, and the wording for the public support promise
The output this prompt produced, unedited.

The prompt

Fill in these first

  • Business and what customers contact you about: [e.g. software subscription, billing and login issues]
  • Channels: [e.g. email, live chat, WhatsApp, phone]
  • Support hours and days: [e.g. 9 am to 7 pm, Monday to Saturday, IST]
  • Agents per shift: [number]
  • Average tickets per day by channel: [numbers]
  • Average handling time per ticket: [minutes, or unknown]
  • Current targets and how often they are met: [paste, or none]
  • Customer tiers, if any: [e.g. free, paid, enterprise]

Task

Define ticket priorities, set realistic time targets for each priority and channel, and show whether the team can meet them.

Output format

  1. Priority definitions: | Priority | Meaning | Two example tickets | Who can raise or lower it |
  2. Targets: | Priority | Channel | First response | Next update | Resolution | Counted in business or calendar hours |
  3. Staffing check: tickets per agent per shift against capacity, with the arithmetic shown in one line per channel.
  4. What happens when a target is about to be missed: the alert, who takes over, what the customer is told.
  5. Public promise: two or three sentences for the help centre and the auto-reply, matching the targets exactly.

Rules

  • Keep four priorities at most; more levels are rarely applied consistently.
  • Live channels such as chat and phone get minutes; email and forms get hours.
  • Never publish a target the staffing check shows the team cannot meet; show the gap and the options instead.
  • Say whether the clock pauses while waiting for the customer.
  • Use only the numbers given; write [estimate] wherever you had to assume one.

Example

Priority 1, chat: first response 2 minutes, update every 30 minutes, resolution 4 business hours.

support slafirst response timeresolution timeticket prioritysupport targetsservice level agreement

How to run this

Copy the prompt and paste it into Gemini, then set the aspect ratio to 3:4. No reference photo is needed for this one.

The prompt is written in Markdown with each part under its own heading, which is what the copy action hands over. Change one section at a time, keeping the rest intact, so you can tell which change did the work.

Related prompts

All productivity