Apps

How to build a customer requests desk from your inbox

The short answer

Give every customer email that needs an answer a record with a status, a priority and an answer-by date. Then work from a board of those records instead of the inbox.

4 min read

Which setup fits your volume?

How many people answer customer email?

Gmail labels and stars

Free and nothing new to learn. You get no answer-by dates and no view of what is late, so check the label daily.

Do you want replies drafted for you?

A shared inbox

Google Groups Collaborative Inbox, Front or Hiver let you assign each email to one person and filter what is unresolved.

App

A requests desk app

It turns each email into a record, sorts it by kind and priority, and drafts a reply that waits for your yes.

See the ready-made version: Track customer requests from email

A help desk such as Zendesk or Freshdesk

Tickets, service-level targets, macros and reports across email, chat and phone. Heavy for a small team.

What each request record holds

FieldValuesWhy
Subject, customer, emailFrom the emailWho and what
StatusNew, Waiting on us, Waiting on them, SolvedWho owes the next reply
PriorityLow, Normal, UrgentWhat to answer first
KindQuestion, Problem, Request, ComplaintWhat to fix in product or policy
Answer byA dateTomorrow if urgent, else two days
DetailsLong textThe ask, plus what was done

How to build a customer requests desk, step by step

  1. Step 1: Pick one address for requests

    support@ or help@. Requests sent to personal inboxes get lost when someone is away.

  2. Step 2: Decide what becomes a request

    A question, a problem, a change, a complaint. Not newsletters, invoices or sales pitches.

  3. Step 3: Create a record per request

    By hand from a label, or automatically from new email. Keep the thread link on the record.

  4. 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 it

    Captain 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.

  5. 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.

  6. 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.

Read next

Or let Captain build it

One sentence to Captain. Free to start.

Build it with Captain
How to build a customer requests desk from your inboxBuild it