How Do I Stop Losing Track of Customer Requests?

If your business keeps losing track of customer requests, give every request one record, one owner, one current status and one next action with a due date. It should not matter whether the customer contacted you through WhatsApp, email, a website form, telephone, social media or in person. Once the request enters the business, it must become a visible piece of work.

You do not necessarily need custom software. A small team with a simple process may solve the problem with a shared spreadsheet or a free visual task board. As the business grows, you may need software that keeps customer history, sends reminders and shows reports. A custom system becomes worth considering when requests must move through your own departments, approvals, quotations, jobs or existing software.

The four things every customer request needs

At minimum, record the customer, contact details, request, source, date received, owner, priority, status, next action, due date, last contact and resolution.

That is the short answer. The rest of this guide will help you find where requests are being lost, choose a practical solution and measure whether it works.

A message is communication. A request is work. Work needs ownership, state and a next action.

Plain-language terms used in this guide

You do not need a technical background to use this guide. These are the main terms you will see:

Are you actually losing customer requests?

The warning signs usually appear in ordinary conversations:

• A customer says, “I emailed you last week.”
• An employee says, “I thought someone else was handling it.”
• A manager asks, “What happened to that quotation?” and nobody can answer without searching several apps.
• A customer has to explain the same problem again.
• Work stops whenever a particular employee is absent.
• Staff can see messages, but nobody can see all open requests.
• The team cannot say how many requests are overdue or unresolved.

Use the symptom to find the process failure:

These are process failures before they are technology failures. Buying software without deciding how work should move can make the confusion more expensive.

Why customer requests disappear: the seven failure points

A request can be lost at any point between contact and closure.

1. Capture failure

The business never reliably receives the request. A website form fails silently, a voicemail is not checked, a direct message goes to an unattended social account or a request is made to an employee’s personal phone.

Fix: list every contact channel, test it and decide who monitors it. Website forms should show a confirmation and create a record or notification that can be checked. Keep a backup process for times when an automatic software connection fails.

2. Record failure

Someone receives the message but leaves the work inside WhatsApp, email or a notebook. The request is visible only while that conversation is visible.

Fix: make “turn the message into a record” part of the process. Do not rely on starred messages or unread status as the only control.

3. Assignment failure

Several people can see the request, but no one is clearly responsible. “The sales team” is not an owner.

Fix: assign one person. That person may involve others, but remains responsible for the next movement or a deliberate handover.

4. Priority failure

The request is recorded but buried beneath newer or louder work.

Fix: define a small number of priority rules. Urgent should mean something operationally specific, such as a safety issue, service outage, deadline within 24 hours or high-value customer blocked from working. Everything cannot be urgent.

5. Action failure

The owner knows about the request but the next step is vague. “Follow up later” is not an action.

Fix: write the next observable action, its owner and due time. For example: “Lerato must send the revised quotation to ABC Ltd by 14:00 Thursday.”

6. Follow-up failure

The business responds once and considers the request handled, even though the customer still needs an answer, decision or result.

Fix: create statuses for Waiting for customer and Waiting internally, each with a review date. An acknowledgement is not a resolution.

7. Closure and learning failure

Nobody confirms the outcome, captures the reason or notices the same problem happening repeatedly.

Fix: record a resolution category and, when appropriate, confirm with the customer. Review recurring categories monthly.

This final step is supported by a broader quality-management principle. ISO 10002:2018, the current international guideline for complaint handling, covers not only receiving and resolving complaints but also analysing them and reviewing the effectiveness of the process. Although not every request is a complaint, the same learning loop is useful.

One customer may look like four requests

Customers do not see your email inbox, WhatsApp account, reception desk and website as separate departments. They see one business.

McKinsey reports that more than half of customers engage through three to five channels while making a purchase or resolving a request. Academic research also finds that customers’ channel choices are influenced by their needs, context and the characteristics they perceive each channel to have (Wolf and Steul-Fischer, 2022).

Consider this journey:

In reality, this may be one customer, one request and four contact attempts. Treating the attempts as separate work can cause duplicate responses, inconsistent promises and misleading reports.

Your shared system therefore needs a way to connect contact attempts to the same customer and request. For a spreadsheet, use a request ID and search before adding another row. For customer relationship management software (a CRM) or a helpdesk, attach later conversations to the existing record where appropriate.

Why email and WhatsApp are not enough

Email and WhatsApp are excellent communication tools. Their weakness is that a conversation often contains hidden work:

“Please send the revised quotation on Thursday after confirming the dimensions with our site manager.”

Inside that message are at least two actions:

1. Confirm the dimensions with the site manager.
2. Send the revised quotation on Thursday.

The message alone does not reliably tell the team who owns those actions, whether the first one is complete, what is due today or what happens if the owner is absent.

The solution is not to stop using the customer’s preferred channel. Keep communicating there, but create a shared work record behind it.

Which solution should I use?

Choose the smallest system that can reliably enforce your process. Tool availability, pricing and free-plan limits change, so confirm current terms and make sure the product meets your privacy, security and record-retention needs before storing customer information.

Use a Kanban board when ownership is unclear

A Kanban board is a visual task board. Each request is a card, and staff move the card through columns that show its current stage. Trello’s published free plan currently includes unlimited cards, assignees and due dates, with limits on collaborators, boards and automation. That can be enough for a small team to test the process before buying or building anything.

Create these lists:

New
Assigned
In progress
Waiting for customer
Waiting internally
Resolved

Each card should contain:

• request ID and customer name;
• a concise description;
• one owner;
• due date;
• priority;
• next action;
• link to the complete customer record or conversation; and
• notes on promises and handovers.

Do not put sensitive customer information into a board merely because it is convenient. Restrict access, use the minimum information needed and check the tool’s settings and terms.

Use a CRM when customer history and sales follow-up are the problem

A CRM, short for customer relationship management software, is a shared place for customer details, conversations, sales opportunities and follow-ups. It is useful when the same customer may have several conversations or quotations and your team needs one history. HubSpot advertises a free CRM, which may be enough to test a basic customer and follow-up process. Before committing, check how many users it allows, what it can automate, which reports it offers, what other software it connects to and whether you can export your data.

A CRM is not automatically the right system for operational jobs, technical support or complex approvals. Define the work first, then check whether the product fits it.

Use a helpdesk when requests are support cases

A helpdesk, also called a ticketing system, turns incoming emails or forms into numbered cases called tickets. It keeps the replies together and shows which tickets are waiting, who owns them and how long they take. This is useful for faults, complaints and repeatable support requests.

It may be a poor fit if a request must become a quotation, site visit, stock reservation, installation and invoice across several departments. In that case, an integration—a connection that passes information between software products—or a broader operations system may be needed.

Use custom software when the workaround becomes the process

General products are designed to support many businesses. That is their strength—and sometimes their limitation.

Custom software becomes reasonable when your team has to:

• copy the same request between several systems;
• follow industry- or company-specific approval rules;
• connect enquiries to quotations, jobs, stock, scheduling or billing;
• apply different permissions across departments or branches;
• route work using your own territories, skills, service levels or customer rules;
• give customers a portal or app with live status;
• retain a reliable audit trail; or
• report on information that generic tools do not capture.

Sometimes you do not need to replace everything. Connecting existing tools can remove the gap. Read how to integrate different business systems or compare buying existing software with building custom software before deciding.

Build a simple customer-request tracker today

For a small operation, start with a shared spreadsheet using these columns:

Then agree on five operating rules:

1. Every request is logged, regardless of channel.
2. No request stays unassigned beyond an agreed intake period.
3. Every open request has a next action and due date.
4. The team reviews overdue and unassigned requests at a set time.
5. A request is closed only after the outcome is recorded.

If a spreadsheet remains dependable, keep it. If staff cannot tell which row is current, who changed it or what must happen next, read the guide to knowing when your business has outgrown Excel.

What should happen after a customer sends a request?

An acknowledgement should confirm receipt and set a realistic expectation. It should not pretend that a person has reviewed the request or promise a response time the business cannot meet.

Automation means letting software complete an agreed step after a known event. Automate only steps you can clearly define and monitor. For example, after a website enquiry arrives, software can create a record, send a confirmation and alert the team. If that automatic step fails, a named person should be able to see and fix it. For a fuller approach, see how to automate business admin without automating the wrong work.

How to prioritise without ignoring quieter customers

“First in, first out” is simple but may be unsafe when requests vary greatly. “Whoever complains loudest” is worse.

Define priority using agreed factors such as:

• safety or legal risk;
• number of customers affected;
• whether the customer is blocked from using a paid service;
• contractual response commitments;
• time-sensitive deadlines; and
• business impact.

Keep the model simple enough for staff to apply consistently. Record why an item was escalated. Separate priority from customer value so ordinary customers are not quietly abandoned.

How to measure whether the process is improving

Start with a small scorecard:

Do not improve one metric blindly. An instant automated acknowledgement may reduce a response-time number without resolving anything. Review speed, quality and customer outcome together.

What could missed requests be costing you?

Use a scenario, not an exaggerated promise:

Monthly enquiries × estimated missed-request rate
× average sale value × normal close rate
= potential opportunity associated with missed enquiries

Example:

This does not prove that the business is losing R230,400 a year. The missed rate and conversion assumption must be tested against real data, and not every captured enquiry would convert. The calculation shows whether the problem may justify further investigation.

Also measure the cost of rework: staff time spent searching messages, asking colleagues, apologising, duplicating responses and rebuilding customer history.

Customer requests are business intelligence

Tracking requests does more than prevent forgetting. Categories can reveal why customers need help.

Suppose six months of records show:

The 421 delivery enquiries may indicate that proactive tracking updates are missing. The 337 invoice questions may reveal unclear invoices. Repeated password requests may justify a secure self-service reset.

Do not only ask, “How can we answer these faster?” Ask, “Why did the customer need to contact us at all?”

Can artificial intelligence (AI) manage customer requests?

Artificial intelligence, usually shortened to AI, can read language and find patterns. It can assist with:

• suggesting a category or priority;
• summarising a long conversation;
• detecting possible duplicates;
• drafting a response;
• extracting suggested fields from a message; and
• finding similar resolved requests.

AI should not replace the underlying controls. The request still needs a record, owner, status, next action and history. Human review is important when an incorrect classification or reply could affect safety, money, legal commitments or a customer relationship.

Treat uncertain AI output as a suggestion, measure its errors and give staff access to the original message. Automation without an exception queue can hide failures faster than a manual process.

Protect the customer information you collect

A request tracker may contain names, contact details, addresses, complaints and commercially sensitive information. Collect only what you need, restrict access by role, remove former staff promptly, use strong authentication and define how long records should be kept.

For South African businesses, the Protection of Personal Information Act 4 of 2013 includes processing-limitation, purpose and security-safeguard requirements. This article is operational guidance, not legal advice; obtain appropriate advice for your organisation and information types.

Avoid copying customer data into several free products merely to test them. A useful tool must also fit your privacy, export, backup, access-control and deletion requirements.

A 30-minute audit you can run today

Minutes 0–10: map every entrance

Write down every place a customer can contact the business:

• website forms;
• email addresses;
• WhatsApp numbers;
• telephone and voicemail;
• Facebook, Instagram and LinkedIn;
• mobile app or customer portal;
• walk-ins and paper forms; and
• employees’ personal devices.

For each channel ask: Who monitors it? What happens outside working hours? How is failure detected? Where does the request go next?

Minutes 10–20: follow three real requests

Choose one completed, one delayed and one currently open request. Trace each from first contact to its latest outcome.

Ask:

• Where was it recorded?
• Who owned it at each stage?
• What promise was made?
• Was a next action and due date visible?
• What happened during absence or handover?
• Could the customer or manager see progress?
• How was resolution confirmed?

Minutes 20–30: choose one repair

Do not redesign the whole business. Fix the highest-risk gap first—for example, create a shared intake sheet, build a Trello board, assign one person to monitor website enquiries or add an overdue review each morning.

Run the change for two to four weeks and compare missed, unassigned, overdue and repeat-contact requests.

Common mistakes to avoid

• Creating another WhatsApp group: it adds another stream, not necessarily ownership or a queue.
• Forwarding everything to another inbox: moving a message does not create a next action.
• Treating “seen” as “handled”: reading is not resolution.
• Making everyone responsible: shared visibility is useful; shared responsibility without an owner is not.
• Closing after the first reply: an acknowledgement may leave the actual request unresolved.
• Buying a CRM before defining the workflow: configuration cannot compensate for missing decisions.
• Automating without monitoring: failed forms, integrations and reminders need a visible exception process.
• Tracking too much: unnecessary fields slow capture and create privacy risk.

Software does not fix an undefined process. It digitises it.

Customer-request management maturity model

You do not need Level 5 if Level 2 reliably solves the problem. The best system is the simplest one your team consistently uses and your business can properly govern.

What if existing software does not fit our business?

Start with the simplest option that reliably captures and moves the work. If a spreadsheet, Kanban board, shared inbox, CRM or helpdesk fits your process and budget, use it.

Custom software is most useful when the real difficulty comes from how your business operates: requests cross departments, follow custom approval rules, connect to quotations or jobs, need different role permissions, or arrive through systems that do not share a reliable history.

Exceed IT designs custom business software and integrations around these workflows. The objective is not to replace a tool that already works. It is to close the gaps between people, processes and systems when those gaps cause requests, work or customers to disappear.

If you need a purpose-built CRM, see what a custom CRM for a small business should include. If you already understand the process, use the guide to turning a business process into custom software.

Not sure whether you need new software at all? Start with the problem and talk to Exceed IT. No technical brief is required.

Frequently asked questions

What is the easiest way to track customer requests?

Use one shared spreadsheet or Kanban board. Give every request an ID, owner, status, next action and due date. Review unassigned and overdue items daily. Move to a CRM or helpdesk only when customer history, volume, automation, permissions or reporting justify it.

How do I track customer requests from WhatsApp and email together?

Keep using the channels for communication, but create one shared request record behind them. Manually log low volumes. At higher volumes, use supported integrations or a system that can connect the channels and match later messages to the same customer and request.

Is Trello suitable for customer requests?

Trello can suit a small team that mainly needs visibility, ownership, statuses and due dates. It is less suitable when you need a complete customer history, complex permissions, service-level reporting or links to quotations, orders and jobs. Do not store sensitive data without checking access and privacy requirements.

Should I use a spreadsheet, CRM or custom system?

Use a spreadsheet for low-volume, simple work; a CRM for shared customer and sales history; a helpdesk for support queues; and a custom or integrated system when your workflow, rules and connected operations do not fit general products. Compare total cost, controls, adoption and maintenance—not only licence price.

How often should we review open requests?

Match the review to the urgency and volume. Many small teams benefit from a short daily review of new, unassigned and overdue requests, plus a weekly review of stalled work and a monthly review of recurring categories and performance measures.

Can automation guarantee that no request is missed?

No. Automation can capture, acknowledge, assign and remind, but forms, integrations and rules can fail. Use monitoring, an exception queue and a named person responsible for investigating failed or unmatched requests.

Sources and further reading

• ISO 10002:2018 — Guidelines for complaints handling in organizations
• McKinsey — Redefine the omnichannel approach: Focus on what truly matters
• Wolf and Steul-Fischer — Factors of customers’ channel choice in an omnichannel environment
• South African Government — Protection of Personal Information Act 4 of 2013
• Trello pricing and current free-plan details
• HubSpot free CRM

*Product features and plan limits were checked on 14 September 2026 and may change. Examples and financial calculations in this article are illustrative, not guaranteed outcomes. This article provides general operational information and is not legal advice.*