How do you build a reply classification sheet for outbound?
Create one Google Sheet with a row per reply and fixed columns for date, account, contact, campaign, step, reply text, category, and next action. Use a short dropdown of reply categories, then add a summary tab that counts categories by campaign. In an hour, you get a clear picture of what your outbound is actually producing.
This tutorial is for one specific situation: a founder or small sales team running outbound, getting a steady trickle of replies, and losing track of what those replies say. Positive replies get handled. Everything else, the "not now," "wrong person," and "how did you get my email," disappears into the inbox, along with the lessons inside it.
A reply classification sheet fixes that. It is deliberately simple, so you will actually keep it updated, and it becomes the best feedback loop your outbound has.
Why classify outbound replies at all?
Reply rates alone hide the story. A campaign with a high reply rate might be producing mostly unsubscribes and "wrong person" answers, while a quieter one produces real meetings. Classifying every reply shows which messages, segments, and steps create interest, and which create annoyance or confusion.
It also turns replies into decisions. A pile of "not the right person" replies means your targeting is off. A wave of "we already use a tool for this" means your positioning against the incumbent needs work. Those patterns are invisible until replies are counted by category.
Finally, it gives you a shared language. When everyone uses the same categories, a weekly review takes minutes instead of turning into a debate about what "interested" means.
Step 1: Which columns should the sheet have?
Use these columns: reply date, account, contact name, contact title, campaign, sequence step, reply text, category, sentiment, next action, owner, and done. Keep reply text as a pasted excerpt, not the full thread. Each column should answer a question you will ask later in a review.
Campaign and sequence step are the columns people skip, and they are the most useful. Without them, you cannot tell which message produced which kind of reply. If your outbound tool can export these fields, copy them in. If not, add them by hand when you log the reply.
Freeze the header row and keep one tab for raw replies. Do not add colors, merged cells, or notes in random places. A plain, consistent table is what makes the summary tab work.
Step 2: Which reply categories should you use?
Use a short, fixed list of six to eight categories: interested, referral to someone else, not now, not a fit, using a competitor, unsubscribe or stop, out of office, and other. Each reply gets exactly one category. If two seem to apply, pick the one that decides the next action.
Write a one-line definition for each category on a separate tab. "Not now" means the buyer is a fit but the timing is wrong. "Not a fit" means they will not need this. "Referral" means they pointed you to someone else. Definitions stop drift when more than one person logs replies.
Out of office replies deserve their own category because they need a specific action, usually a pause and a later restart. I covered that handling in routing out of office replies back into a sequence.
Step 3: How do you add dropdowns so categories stay consistent?
Put your category list on the definitions tab, then apply data validation to the category column so it only accepts values from that list. Do the same for sentiment and next action. Dropdowns prevent typos like "intrested" or "not-now," which would quietly break your counts later.
In Google Sheets, data validation lets you create a dropdown from a range of cells. Point it at your category list, and set it to reject entries that are not on the list. If you need a new category later, add it to the list, and every dropdown updates.
Keep the lists short. A dropdown with twenty options gets used inconsistently. Six to eight categories, three sentiment levels, and five next actions is enough for most outbound programs.
Step 4: How do you set next actions for each category?
Map every category to a default next action, and write the mapping on the definitions tab. Interested becomes book a meeting. Referral becomes contact the referred person. Not now becomes set a follow up date. Unsubscribe becomes remove from all sequences immediately. A default action means no reply sits without a plan.
The unsubscribe action is not optional. Honor stop requests promptly, remove the contact from every active sequence, and keep a record. Ignoring them damages your sender reputation and your brand, and depending on where you sell, it may break the rules that apply to you.
Add an owner and a done checkbox to every row. The weekly review then has a simple question: are there rows without a done mark? Those are the replies about to be forgotten.
Step 5: How do you build the summary tab?
Create a summary tab with campaigns as rows and categories as columns, then count replies for each pair with COUNTIFS. Add a total column and a percentage view. This one grid shows, at a glance, which campaigns produce interest and which produce friction.
A pivot table works too if you prefer it. The point is a single view that answers three questions: which campaign has the highest share of interested replies, which has the most not a fit replies, and which has any unsubscribe spike.
Add a second small grid by sequence step. If most interested replies come from step three, your first two emails may be too weak or too generic. If most unsubscribes come from step one, the opener is the problem.
Step 6: Should you use AI to classify replies?
You can, once your categories and definitions are stable. A small model can read each reply and suggest a category, with a person confirming it. Start manually for a few weeks first, so you have clean examples and definitions that a model can follow reliably.
When you add AI, keep the person in the loop. Have the model fill a "suggested category" column and a short reason, and let the owner accept or change it. Track how often the suggestion is changed. If corrections are rare on a category, you can trust the model more there.
Never let a model handle unsubscribe requests without a person checking. A missed stop request is the one error that can cause real harm, so the safest design routes anything that looks like an opt out straight to a human.
Step 7: How do you review the sheet each week?
Spend twenty minutes once a week. Check that every reply has a category and a completed action. Look at the summary grid for changes from last week. Pick one campaign to improve, based on the categories, and write down the change you will test. Then close the sheet.
The review is where the sheet pays off. A rise in "using a competitor" might mean you need a sharper comparison line. A rise in "not a fit" might mean your list filters are too loose. Each pattern points to one change you can make this week.
Before you change a live sequence, run it through a quick quality check. The steps I use are in writing an outbound sequence QA checklist. When the categories show a campaign is simply not working, the decision framework in deciding when to stop an outbound campaign helps you call it.
What should you do next?
Open a new Google Sheet today. Add the columns from Step 1, the category list and definitions from Step 2, and dropdowns from Step 3. Log every outbound reply from the past two weeks. Build the summary grid, then hold your first twenty minute review at the end of this week.
My view is that outbound gets better through listening, not volume. The replies you ignore are full of free feedback on your list, your message, and your timing. A plain sheet that captures them is one of the cheapest GTM upgrades you can make.
If you want help building reply classification into your outbound stack, or connecting it to your CRM and enrichment tools, reach out through pravinkumar.co. Let's chat about turning your replies into a feedback loop.
Get found, cited and the back office automated
Let's make your site the source AI engines quote and wire up the systems behind it.
Read more blogs
Let's get your website found and cited by AI
Tell me what you're working on, whether AI search is skipping your product, your back office is buried in manual work, or you need a build that does both.