Which setup fits your volume?
What each request record holds
| Field | Values | Why |
|---|---|---|
| Subject, customer, email | From the email | Who and what |
| Status | New, Waiting on us, Waiting on them, Solved | Who owes the next reply |
| Priority | Low, Normal, Urgent | What to answer first |
| Kind | Question, Problem, Request, Complaint | What to fix in product or policy |
| Answer by | A date | Tomorrow if urgent, else two days |
| Details | Long text | The ask, plus what was done |
How to build a customer requests desk, step by step
Step 1: Pick one address for requests
support@ or help@. Requests sent to personal inboxes get lost when someone is away.
Step 2: Decide what becomes a request
A question, a problem, a change, a complaint. Not newsletters, invoices or sales pitches.
Step 3: Create a record per request
By hand from a label, or automatically from new email. Keep the thread link on the record.
Step 4: Sort each one as it arrives
Set kind, priority and answer-by date. Rules first, then judgement for the unclear ones.
Tip. Write the rule for Urgent in one sentence: something is broken, money is at stake, or the customer is upset. Otherwise everything drifts to urgent.
Do this step in 50agents
Keep track of customer requests and draft the replies
Build itCaptain builds the desk with an AI agent that sorts each new request, drafts a reply from what your business knows, and waits for your yes. See the ready-made version.
Step 5: Work from the board
Waiting on us, oldest first, urgent at the top. The inbox becomes where replies go out, not where work is tracked.
Step 6: Close the loop
Waiting on them for three days with no reply: send a short check-in, then mark it Solved.
What can go wrong
Two people answer the same email
Nobody could see who had it. Assign each request to one person, or have one person own the desk.
A thread splits
The customer replies with a new subject and it becomes a new request. Match on the customer's email and merge.
Forwarded requests lose the customer
A colleague forwards an email and the record shows the colleague as the customer. Read the original sender from the forwarded text.
Drafts that promise too much
An AI-drafted reply offers a refund you would not give. Keep your policies in its memory, and review every draft before it goes.
Questions people ask
Shared inbox or help desk?
A shared inbox for a small team with modest volume; a help desk once you have many support staff, several channels or service-level targets to report on.
How do I stop two people replying to the same email?
Assign each conversation to one person. Google Groups' Collaborative Inbox lets members take a conversation; a desk app shows each request's owner and status.
How do I track open customer requests?
Give each one a record with a status and an answer-by date, and work from a view of everything Waiting on us, oldest first.
Which emails should become requests?
A question, a problem, a change or a complaint from a customer. Not newsletters, invoices or sales pitches. Write the rule down so everyone sorts the same way.
How quickly should we answer?
Set an answer-by date on every request: tomorrow if urgent, otherwise two days. Work from Waiting on us, oldest first, urgent at the top.
What happens when a customer never replies?
Mark it Waiting on them. After three days with no reply, send a short check-in, then mark it Solved. A desk full of stale requests hides the live ones.