Before you post the job, count the work the seat would do: what comes in, when, how fast, and what a person must approve.
A new seat at the front desk is usually a response to a feeling: the phone rings too much, quotes go out late, emails sit over the weekend. The feeling is real. But a job post written from a feeling describes a person, not the work.
This guide turns the feeling into numbers you can check. Seven questions, each answered from the last 4 weeks of your own inquiries. For each one: why it matters, how to count it, and how our Inbound module handles that part when agents do the work, with the control that keeps you in charge.
Whatever you decide, hire or not, you will write a better job description with the worksheet at the end filled in.
01
What comes in, and on which channel
Why it matters
A seat is sized by the work, and the work arrives in different forms. A site chat wants a quick answer; a form can carry a full quote request; email threads run for days; a missed call is often a customer who will try someone else. The mix decides the skills you need as much as the volume does.
How to count it (last 4 weeks)
Pull 4 weeks from each place inquiries land: website forms (your site or CRM), chat transcripts if you have chat, the shared inbox, and your phone system’s call log, including missed calls. Count each channel per week. Leave out spam and vendors.
How the Inbound module handles it
Agents answer site chat, forms, email and missed calls (a text-back to the caller), qualify each inquiry, and book or route it. One queue for every channel, so nothing depends on which inbox someone checked.
02
When it comes in
Why it matters
One seat covers the hours someone is at the desk. Inquiries also arrive at lunch, after five, before seven and on weekends, and those wait until someone is back. For a buyer comparing suppliers, waiting is often the answer.
How to count it (last 4 weeks)
Take the same 4 weeks and mark every inquiry that arrived outside your staffed hours. Count missed calls after hours separately. Note the share that came in on weekends.
How the Inbound module handles it
The department answers day and night. Anything that needs a person is queued with the conversation so far, and the weekly briefing lists the after-hours inquiries it captured.
03
How fast each needs an answer
Why it matters
Not every inquiry is urgent, and treating them all the same is how urgent ones get lost. A quote request may need an answer today; a question about a delivery window can wait an hour. Call it the answer clock: the time from arrival to a first useful reply.
How to count it (last 4 weeks)
For each inquiry, note the time between arrival and the first reply. Then sort them into “needed it fast” and “could wait”. The gap between the two groups tells you more than the average does.
How the Inbound module handles it
Every inquiry gets a first answer on its own clock, and the weekly briefing shows the answer clock against a target of 15 business minutes, so you can see when it slips.
04
What your own pages can answer
Why it matters
Many questions are already answered on your site: hours, service areas, product lines, minimum orders, how to open an account. Each one still takes a person a few minutes. Knowing how many are “already on our site” changes the job.
How to count it (last 4 weeks)
Tag every inquiry: answered from a page we already have, answered from something we know but never wrote down, or needed a decision. Keep a list of the questions in the middle group: those are pages you are missing.
How the Inbound module handles it
Answers come from your own pages and the rules you approve. When the answer is not in them, the agent does not guess: it hands the conversation to a person, and the missing answer becomes a page or a template you approve.
05
What needs a person
Why it matters
Some inquiries need judgement or authority: a pricing exception, a credit request, a complaint, a disputed delivery. These are the reason to have a good person, and they are rarely the bulk of the volume.
How to count it (last 4 weeks)
From the “needed a decision” group, write down who made each decision. If it was you or a manager, that work stays with you whether or not you hire.
How the Inbound module handles it
These go to a named person on call, with the conversation and the customer’s details. A person on our side also reads the conversations, so nothing sensitive is handled by an agent alone.
06
Who approves what goes out
Why it matters
Your replies, your quotes and your follow-ups are your company speaking. Whoever sits in the seat needs rules: what can be promised, which templates to use, when to escalate. Writing those rules down is most of a good job description.
How to count it (last 4 weeks)
List the replies you send again and again, the templates you already have, and who signs off on a quote today. Note any reply you would never want sent without a look.
How the Inbound module handles it
You approve the rules and the templates before anything goes live. Quote follow-ups go out only from templates you approved, and a change to a rule goes through you.
07
Where it is logged
Why it matters
If inquiries live in one person’s inbox, they leave with that person: on vacation, on a sick day, or for good. A log in your CRM is what lets anyone pick up a customer where the last conversation ended.
How to count it (last 4 weeks)
Pick 10 inquiries from last month at random. For each, can you find it in your CRM with the reply that was sent? Count how many you found.
How the Inbound module handles it
Every inquiry and its conversation is logged in your CRM. You keep your CRM, your number and your data; the department works inside them.
What the answers usually point to
If most of the work is decisions only a person can make, hire the person, and give them the rules you just wrote down.
If most of it is routine, arrives after hours or is already answered on your pages, look at the Inbound module first: agents for the inquiry work, a named person on call, your approval on what goes out. The agents alone come with the Sales department, $350 a month; with the person on call, Head of Digital: $6,000 a month for all six departments, 3-month minimum, live in 30 days.
Fill one row per question from the last 4 weeks. Print this page, or save it as a PDF from your browser.
Question
Your count (last 4 weeks)
Who handles it today
Notes
Inquiries per week, by channel (chat, forms, email, calls, missed calls)
Inquiries outside staffed hours (and on weekends)
Time to first reply: needed it fast vs could wait
Answered from a page we already have / from what we know / needed a decision
Decisions only a person can make, and who made them
Replies and templates sent again and again; who approves quotes
Out of 10 inquiries, how many are in the CRM with the reply
Email me the worksheet
Leave your email and we send you the link to this worksheet, which prints on its own or saves as a PDF. If it can’t go out right away, a person on our team sends it within two business days. Nothing else is sent unless you tick the second box.
May we see which company you are visiting from? Our providers Snitcher and Apollo.io look up the company (never you) from your visit’s IP address, which we do not keep; both may set cookies to recognise a returning company. We use it to prepare a private page for that company and follow up with the right businesses, and we remember in your browser which of our links brought you here (sent only with a form you submit). We never identify you personally. Privacy