Build an Inquiry Tracker You Will Actually Use

Open your inquiry list. Can you tell, within a few seconds, who needs a reply today? If not, the list is storing information without helping you run the work. Start with a spreadsheet if that is what you already use. The important part is the structure, not the software.

Give every row a next action Use these fields: inquiry ID, received date, contact, request, status, owner, next action, next-action date, and source link. If you have not defined how inquiries arrive, start with the workflow map. Keep the original request behind the source link. A summary should help you scan, not replace the evidence. Collect only information you need; consult the FTC’s business data-protection guide when setting access and retention practices.

Use statuses that tell you who is waiting New: nobody has reviewed the request. Waiting on us: your team owes the next action. Waiting on customer: you need a reply or detail. Closed: no action remains; record the reason. Avoid “In progress” unless everyone knows what it means. “Waiting on us; Daniel; ask for cabinet measurements; Tuesday” is much easier to act on. The handoff guide covers transferring that responsibility.

Try these fictional rows R-104: cabinet repair; waiting on us; Daniel; request measurements; Tuesday. R-105: service outside our area; closed; Alex; no next action; reason recorded. R-106: customer sent photos; waiting on us; Daniel; review photos; Wednesday. Notice R-106 should not remain “Waiting on customer” after the photos arrive. A tracker needs a routine for updating states, not just adding rows.

Build two useful views Daily work: open items you own, ordered by next-action date. Exceptions: missing owners, overdue actions, and incomplete contact details. Use Google Sheets filter views if you work in Sheets. Keep your follow-up reminders tied to the current status so they stop when the situation changes.

Connect the form last Enter five fictional records manually. Ask someone else to identify the next action. Fix any ambiguity before automating imports. Preserve a submission ID and test repeated events. Zapier’s duplicate-data guide can help investigate unexpected duplicates. Do not mistake that check for merging customer identities.

Your finish line Run the pre-launch checks, then use the tracker for a small pilot. Count missed actions and review effort. Use the weekly update format to review unresolved work. Remove fields nobody uses. A reliable nine-column sheet is more valuable than an elaborate database everyone avoids.