# Customer Request Prioritisation Table Prompt

> A reusable chat prompt that turns a pasted list of open customer requests into a prioritisation table using stated urgency and effort only.

## Install

Copy the content below into your project:

# Customer Request Prioritisation Table Prompt

A reusable chat prompt that turns a pasted list of open customer requests into a prioritisation table using stated urgency and effort only.

## 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](<https://help.openai.com/en/articles/6825453-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](https://help.openai.com/en/articles/6825453-chatgpt-release-notes)

Original TokRepo prompt · [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/). Reference documents retain their own rights.

---

<!-- ZH -->

# 客户请求优先级排序表提示词

一套可在普通 AI 对话中复用的提示词，把粘贴的未结客户请求清单整理成优先级排序表，仅依据请求中明确写出的紧急程度和工作量。

## 开始使用

先把未结客户请求清单粘贴到普通 AI 对话中（任何能接收纯文本的助手），再粘贴完整提示词。如果没有附上清单，助手应向你要清单并停止。

作为输入粘贴的内容：每条请求以文本给出，最好包含请求 ID 或简短标签、客户要求的内容、提出人、收到日期、客户使用的紧急措辞、已记录的工作量估计和提到的截止日期。可选补充你每天的工作时长和可用人数。

如何检查输出：

- 没有写明紧急程度或截止日期的请求会标为“unranked — needs input”，而不是给出猜测的排名。
- 每个假设值都出现在 assumption flag 列并写明原因。
- 客户的原话紧急程度必须引用客户原话，否则写“not stated”。
- 缺失输入清单要为每个缺口写明具体该问的问题。
- 你清单里的请求不会被丢掉。

## 简介

这套提示词仅依据明确写出的事实生成纯文本优先级排序表。它不会检索、浏览、联系任何人，也不安排、发送或更新任何内容，只是供你复核的规划草稿。

这是 TokRepo 原创提示词；完整原文及中文译文随附在下方。

## 前提与权限

- 一个能接收粘贴文本的普通 AI 对话。
- 你的请求清单，或愿意被追问清单。
- 无需终端、API 密钥或账户设置。该提示词除生成文本外不授予任何操作权限。

## 限制

- 缺失的紧急程度、工作量或截止日期，助手不会替你补全。
- 输出质量取决于你粘贴的内容；空的或不可读的清单应被报告并停止。
- 已复核来源；未做运行时测试。作者未在此处运行该提示词，也未声称任何测试结果。

## 常见问题

**如果我只粘贴了部分清单怎么办？**
助手应当只依据现有内容处理，缺失输入清单会标出缺口。补齐后重试即可。

**它能决定先做什么吗？**
它只按写明的紧急程度和写明的截止日期排序。其他情况一律保持“unranked — needs input”。

## 来源与致谢

TokRepo 原创提示词，CC BY 4.0。参考：[ChatGPT release notes](<https://help.openai.com/en/articles/6825453-chatgpt-release-notes>)。外部参考材料保留其自身权利。已复核来源；未做运行时测试。

## 完整可复制提示词

你正在帮助我对一份未结客户请求清单进行优先级排序。我会粘贴请求清单。只依据我提供的内容处理；不要检索、浏览或联系任何人。

我将提供的输入
- 一份文本形式的未结客户请求清单。每一行可能包含：请求 ID 或简短标签、客户要求的内容、提出人、收到日期、客户使用的任何紧急措辞、已记录的任何工作量估计，以及提到的任何截止日期。
- 可选：我每天的工作时长，以及可用于此项工作的人数。

如果我没有提供请求清单，向我要清单并停止。如果清单为空或不可读，说明情况并停止。

任务
构建一份优先级排序表。只使用写明的紧急程度和写明的工作量。任一项缺失时，不要猜测——标为假设并清楚标注。

输出格式
1. 摘要：收到的请求数量，写明紧急程度的数量，写明工作量的数量，两项都缺失的数量。
2. 优先级排序表，包含这些列：
   | Rank | Request ID/Label | What was asked | Stated urgency | Stated effort | Deadline stated? | Assumption flag | Notes |
   - Rank 只依据写明的紧急程度和写明的截止日期。两者都不存在时，排为“unranked — needs input”。
   - Stated urgency 在可用时必须引用客户原话，否则写“not stated”。
   - Stated effort 必须来自所提供的清单，否则写“not stated”。
   - Assumption flag 写“none”，或准确说明哪个值是被假设的以及原因。
3. 缺失输入清单：紧急程度、工作量或截止日期缺失的请求，并写明我应向客户或请求人提出具体问题。
4. 行动前复核检查：我应对表格进行的三到六项检查，例如对照截止日期核验排名、确认 assumption flag 与备注一致，以及检查没有请求被遗漏。

规则
- 不要臆造紧急程度、工作量、截止日期、客户姓名或请求 ID。
- 引用紧急程度时不要改动客户的原话。
- 如果我提供了可选的工作时长，你可以增加一列给出粗略的工作顺序建议，但要清楚标为建议，并与 Rank 分开。
- 不要安排、发送或更新任何内容。这是供我复核的规划草稿。
- 保持表格可排序，并在纯文本中可读。

示例（虚构，仅示意形式——不是真实客户数据）
输入：“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.”
示意输出行：
| 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 |

与示例相关的检查
- 如果 REQ-014 因写明了紧急程度而排在 REQ-015 之前，则通过。
- 如果没有给 REQ-015 猜测的排名或工作量，则通过。
- 如果 REQ-014 的 assumption flag 列为“none”，且 REQ-015 列出了缺失的值，则通过。
- 如果输出为 REQ-015 声称了一个未提供的截止日期，则失败。

开始
如果请求清单尚未包含，请让我粘贴它。

## 参考资料与复用

- [ChatGPT release notes](https://help.openai.com/en/articles/6825453-chatgpt-release-notes)

TokRepo 原创提示词 · [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/)。参考资料保留各自原有权利。

---
Source: https://tokrepo.com/en/workflows/customer-request-prioritisation-table-prompt-d6adc701
Author: Prompt Lab