Customer Service Tracker for Small Businesses: Free

Every small business has the same morning ritual around the shared info@ inbox. Someone opens it, scans the unread count, and asks the room: "Did anyone reply to the lady with the warranty thing?" Silence. Then two people start typing at once, and the customer gets two replies — one warm and apologetic, one brisk and procedural — from the same company.

The shared inbox fails in both directions at once. On slow days it produces duplicate answers in clashing tones. On busy days it produces the opposite: a message everyone saw, everyone assumed someone else had, and nobody touched, discovered a week later when the customer calls back, less friendly than before. Warranty claims sit next to order-status checks sit next to "are you open Monday?" — all equally unread, none belonging to anyone.

The owner has the worst seat in the house: caring how customers are treated, with no way to see it short of reading every thread — surveillance, not management. The business doesn't need a bigger inbox or a per-agent help desk. It needs a list where every question has exactly one owner and a visible status. That's a Google Sheet with a front door.

Step 1: Lay Out the Service Sheet

One tab, one row per customer question:

Two more tabs finish the setup. A directory tab mapping question types to people — Teo takes warranty and repairs, Anita takes orders and shipping, the counter takes general questions. And an FAQ tab holding the answers you give daily: store hours, return policy, how to check an order.

The Received/Resolved pair is quietly the most valuable part — the gap between them is your actual service quality, measured instead of guessed.

Step 2: Open a Free Account

Go to lovespreadsheets.com and sign up — no charge to build or operate the tracker. The paid tier adds individual team logins behind the internal view and a branded address like help.yourshop.com.

Step 3: Say What You Want in Plain English

Select the Website template and describe the customer's side first:

"Customers reach one contact page with a short form: name, email, what kind of question — warranty, order, or general — and the details. Each submission lands as a row with an auto-generated ticket ID, and the customer instantly receives a confirmation email with that number. If their question resembles something in my FAQ tab, tuck the likely answer into the confirmation as 'this may cover it — a real person will reply shortly regardless.' Then notify whoever my directory tab says handles that type."

Then the team's side:

"Give the team an internal view of all tickets — filter by status, type, and assignee, edit in place. Nothing should ever be unassigned."

Three asks tailored to a shared-inbox refugee:

• One intake form to rule the channels — the website contact link, the email signature, even the phone script all point here, so questions stop scattering
• Single-owner assignment — every ticket carries exactly one name from the moment it arrives; duplicate replies and orphaned messages both die with this rule
• A Monday summary for the owner — an automatic weekly email counting resolved versus still-open tickets, oldest ones listed, so oversight takes ninety seconds

Use AI Optimize if your description gets wordy, answer any clarifying questions, and expect the finished build in around 15–20 minutes.

Step 4: The Inbox Retires Gracefully

You'll have a portal URL for your website's contact page and an internal view where the whole queue lives. When Rosa's warranty part is delayed, anyone can see Teo owns it, what he last said, and how long it's been — without forwarding a thread or interrupting his lunch. New submissions appear as rows the second they're filed, ID already attached, confirmation already sent.

The info@ address can keep existing as a side door. It just stops being the system.

Why Small Businesses Keep the Sheet

One name per ticket changes the culture. Ambiguity, not negligence, is what drops customers. When ownership is a column, "I thought you had it" stops being a sentence anyone says.

The owner gets truth without hovering. A weekly resolved-versus-open count with the stalest tickets listed tells you more than a month of spot-reading threads — and the team feels trusted, not watched.

Seat-based pricing makes no sense at this size. Help-desk platforms run $40–55 per agent monthly — a tax on sharing the work. A sheet-backed tracker costs the same at three helpers as at eight: nothing.

Common Questions from Small Businesses

Our customers like emailing us directly. Will a form annoy them? Keep the address — reply with the form link and log walk-in or phone questions yourselves using the channel column. The point is one record, not one door.

Three of us write very differently. Does this fix the tone problem? Partly by routing — each type of question consistently gets the same person. Ask for AI reply drafts too, and everyone starts from the same professional baseline.

Can we track how fast we respond? Yes — that's the received/resolved pair. Ask for SLA timers if you want tickets to flag themselves after, say, one business day without a reply.

Build Yours

List the eight columns, jot who owns which type of question, and describe your counter-to-inbox reality at lovespreadsheets.com. By this time tomorrow, "did anyone reply to that?" has an answer nobody has to ask out loud.