Customer Request Prioritisation Table Prompt

Start here

Paste an open customer request list into an ordinary AI chat (any assistant that accepts plain text), then paste the full prompt. If you have not included the list, the assistant should ask for it and stop.

What to paste as input: each request as text, ideally with a request ID or short label, what the customer asked for, who asked, date received, any urgency words the customer used, any recorded effort estimate, and any deadline. Optionally add your working hours per day and how many people are available.

How to check the output:

• Requests with no stated urgency or deadline are marked "unranked — needs input", not given a guessed rank.
• Every assumed value appears in the assumption flag column with the reason.
• Customer urgency is quoted from the customer's own words, or written as "not stated".
• The missing-input list names the exact question to ask for each gap.
• No request from your list is dropped.

Introduction

The prompt builds a plain-text prioritisation table from stated facts only. It does not research, browse, contact anyone, schedule, send, or update anything. It is a planning draft for you to review.

This is the TokRepo original prompt; the complete original text and its Chinese translation are appended separately.

Prerequisites and permissions

• An ordinary AI chat that accepts pasted text.
• Your request list, or the willingness to be asked for it.
• No terminal, API key, or account setup is needed. The prompt does not grant any action permission beyond producing text.

Limitations

• Missing urgency, effort, or deadline is never filled in by the assistant.
• Output quality depends on what you paste in; unreadable or empty lists should be reported and stopped.
• Source reviewed; runtime not tested. The author did not run this prompt here, and no test results are claimed.

FAQ

What if I paste only part of the list? The assistant should work only from what it has, and the missing-input list will flag gaps. Add the rest and repeat.

Can it decide what to do first? It ranks only by stated urgency and stated deadline. Anything else stays "unranked — needs input".

Attribution

Original TokRepo prompt, CC BY 4.0. Reference: ChatGPT release notes. External reference material retains its own rights. Source reviewed; runtime not tested.

Complete reusable prompt

You are helping me prioritise a list of open customer requests. I will paste the request list. Work only from what I provide; do not research, browse, or contact anyone.

INPUT I WILL PROVIDE

• A list of open customer requests in text form. Each item may include: request ID or short label, what the customer asked for, who asked, date received, any urgency words used by the customer, any effort estimate already recorded, and any deadline mentioned.
• Optionally: my working hours per day and number of people available for this work.

If I have not provided the request list, ask me for it and stop. If the list is empty or unreadable, say so and stop.

TASK Build a prioritisation table. Use only stated urgency and stated effort. Where either is missing, do not guess — mark it as an assumption and label it clearly.

OUTPUT FORMAT

1. Summary: number of requests received, number with stated urgency, number with stated effort, number missing both.
2. Prioritisation table with these columns: | Rank | Request ID/Label | What was asked | Stated urgency | Stated effort | Deadline stated? | Assumption flag | Notes |
   • Rank is based only on stated urgency and stated deadline. If neither is present, rank it as "unranked — needs input".
   • Stated urgency must be copied from the customer's words where available, otherwise "not stated".
   • Stated effort must come from the provided list, otherwise "not stated".
   • Assumption flag says "none" or names exactly which value is assumed and why.
3. Missing-input list: requests where urgency, effort, or deadline is absent, with the specific question I should ask the customer or requester.
4. Review checks before I act: three to six checks I should perform on the table, such as verifying ranks against deadlines, confirming assumption flags match notes, and checking that no request was dropped.

RULES

• Do not invent urgency, effort, deadlines, customer names, or request IDs.
• Do not change the customer's wording when quoting urgency.
• If my optional working hours are provided, you may add a column for a rough order-of-work suggestion, but mark it clearly as a suggestion and keep it separate from Rank.
• Do not schedule, send, or update anything. This is a planning draft for me to review.
• Keep the table sortable and readable in plain text.

WORKED EXAMPLE (fictional, for shape only — not real customer data) Input: "REQ-014: customer wants invoice format changed, said 'this is blocking our month-end', 2 hours estimated. REQ-015: asked for a new report, no urgency given, no effort given." Illustrative output rows: | 1 | REQ-014 | Change invoice format | customer said 'blocking our month-end' | 2 hours (stated) | none | none | deadline not stated; rank based on stated urgency | | unranked — needs input | REQ-015 | New report | not stated | not stated | no | assumption: none; missing urgency and effort | ask requester for required-by date and rough effort |

CHECKS TIED TO THE EXAMPLE

• Pass if REQ-014 is ranked above REQ-015 because urgency was stated.
• Pass if REQ-015 is not given a guessed rank or effort.
• Pass if the assumption flag column is "none" for REQ-014 and names the missing values for REQ-015.
• Fail if the output claims a deadline for REQ-015 that was not provided.

START Ask me to paste the request list if it is not already included.

References and reuse

• ChatGPT release notes

Original TokRepo prompt · CC BY 4.0. Reference documents retain their own rights.