Where Do Customer Requests Disappear? Request Tracking in CRM
How to set up customer request tracking in your CRM: the four places requests get lost, what a request record needs, response commitments, and what to measure.
The customer messages the sales rep they know on WhatsApp. The rep is in a meeting and the message scrolls away. Two weeks later the customer says they already asked, and nobody can find what was asked. Because the request never landed in a system, it never existed. Customer request tracking is the operational discipline that makes those losses visible.
Where requests get lost
- In personal channels: WhatsApp, direct calls, a rep's personal inbox.
- Inside meetings: an ask mentioned in conversation and never written down.
- Between teams: a technical question sent to sales, forwarded to support, owned by nobody.
- During handover: a rep goes on leave or resigns, and open requests leave with them.
The common thread: until a request is recorded somewhere, nobody can track it and the loss cannot be measured.
Every channel should land in one place
Asking customers to change channel is unrealistic; they will reach you however they prefer. The answer is not to ban channels but to connect all of them to one record.
The practical rule: whatever channel it arrives through, the request is opened as an activity on the customer record. The rep's first job is not to solve the message but to log it. An unlogged request is unfinished work.
What a request record needs
- Date received and channel
- Request type: technical issue, information, change request, complaint, pricing
- Owner — a person's name, not a team name
- Target resolution date
- Status: open, waiting, resolved
- The linked customer, and the deal record where relevant
Making the owner a person is critical. "Support team" is not ownership; a request everyone is responsible for is a request nobody owns.
Why request type matters
A complaint and an information request cannot run through the same process. A complaint needs a response within hours and management visibility; an information request can wait a few days.
Once type is a closed list, within a few months you hold a valuable table: how many requests arrive about what? The same question asked thirty times is the clearest evidence of a product or documentation gap.
Make a realistic response commitment
Do not build a complex service level matrix. Three tiers work for most teams: critical, normal, low. Set one response time per tier and make it achievable.
Measure two different times separately: first response and resolution. What frustrates customers most is not a slow fix but silence. A fast first response buys you room on resolution time.
Sales needs to see requests
If a rep walks into a renewal conversation not knowing the customer has five open requests from the last three months, that conversation goes badly before it starts.
Rather than keeping requests isolated in a support system, link them to the customer record. That single change lets sales see which accounts need careful handling.
Confirm with the customer before closing
Some requests marked resolved are not; the team finished on their side without telling the customer.
Add a small rule to the closing step: no request closes without notifying the customer. Track your reopen rate — if it is high, resolutions are being closed too early.
Four numbers to track
- Open request count and age: anything open past 30 days is a warning.
- First response time: the number most strongly tied to satisfaction.
- Reopen rate: an indicator of resolution quality.
- Requests per customer: feeds directly into service load and profitability.
Where to start
This week's job: ask your sales and support teams how many customer requests they are working on right now that exist in no system at all. The number makes the case for a tracking process beyond argument.
Closync links requests to the customer record regardless of the channel they arrive through, so sales and operations see the same picture.
