Skip to main content
The Human Bit

GuidesBy professionCustomer service agents, front desk and reception teams

AI for customer service and front desk teams who still answer as a person

For Customer service agents, front desk and reception teams.

Start here

What this helps you do
Use AI to get through a queue of near identical enquiries and to turn a long call into a usable note, while the tone, the exception and the decision to hand a person to a person stay yours.
What you leave with
A repeatable workflow and a starter prompt you can adapt to your own work.
What to check before trusting it
You hear the thing underneath the complaint. A third email about a delivery is rarely about the delivery.
Ask Bit to set up this workflow

Best fit today: Claude, Gemini or ChatGPT.Our read of the reviewed tool guides, not tested by us. Reviewed 19 September 2026. Open a tool guide for what each one does with this kind of work.

When to use this

Forty messages in the queue, and thirty of them are the same three questions. Then there is the one that is not: somebody upset, with a case that fits no template, who can tell straight away when they are being processed rather than answered.

  • Drafts the reply to a routine enquiry in your team's own wording, so you are editing rather than typing from nothing
  • Turns a fifteen minute call into a short note covering what was asked, what you promised and what happens next
  • Reads a long and angry message and pulls out the actual requests buried inside it
  • Offers two or three ways to say no, so you can choose the one that suits this particular person

Workflow

  1. Gather your ten most common enquiries and the best real reply your team has already sent for each. That set is what makes the drafts sound like you, far more than any clever instruction.

  2. Build a reusable helper instead of starting cold every shift. A Gem is a customised version of Gemini made for a repeated task, so your enquiry wording lives in the helper rather than in your head.

  3. Keep the standing context in one workspace. Claude Projects holds its own uploaded files alongside the chat, which is where your refund wording and escalation rules belong.

  4. Ask for the right size. Tell it the reply has to fit in six lines and must not open with a paragraph of apology.

  5. Read it back as the customer would. If you would not believe it, do not send it.

  6. After a call, dictate the note while it is still fresh, then ask for the structure: what they asked, what you agreed, what is outstanding, who owes the next move.

Prompts to try

Use it, adapt it, and make it your own.

You are helping a front desk team. Here is a customer message: [paste it]. First list what they are actually asking for, including anything implied rather than stated. Then draft a reply of no more than six lines, in this tone: [describe it, or paste one real reply we are proud of]. Do not promise a date, a refund or an outcome that is not in my notes, and mark anything you are unsure about as [CHECK].

Human lens

  • You hear the thing underneath the complaint. A third email about a delivery is rarely about the delivery.
  • You decide when to stop replying in writing and pick up the phone
  • You are the one who can make an exception, and a draft has no authority to make one
  • You own every promise in the text, so you cut the ones you cannot personally keep

What to avoid

  • A draft will cheerfully commit you to a callback time, a delivery date or a refund that nobody has approved. Every promise in the text has to be one you can keep.
  • If model output goes in front of a customer, check the ground rules first. Anthropic's usage policy requires anyone presenting model output directly to consumers to disclose that AI helped produce it, at a minimum at the start of each session.
  • Working through a queue in a batch is exactly when the unusual case gets swept along with the routine ones. Pull the exceptions out before you start the batch, not after.
  • The sixth polite variation on the same answer is what makes somebody ask for a manager. If a case needs a person, hand it over early rather than after three more drafted replies.
  • A summarised call is your memory of it, not a recording. Anything contested goes back to the customer in writing for confirmation.

Reviewed 19 September 2026

The Human Bit Weekly

The useful changes, not every launch.

One short issue every Monday. What changed, what it means for your work, and the part that stays yours.

The Human Bit records when and how consent was given. Subscription is confirmed only after the email provider accepts the request.