Tracking customer cases and follow-up tasks: a simple system

A simple case system has two parts: a case for every customer issue, with one owner, a status and a running history, and a task with a due date for every promise. Both link to the customer, the statuses stay few, and open items get a weekly review.

Small teams usually track customer issues in an inbox, a chat thread and someone's memory. That works until two people answer the same email, or nobody answers it because each assumed the other would. A case-and-task system does not need special software to start; it needs a few rules everyone follows.

Cases and tasks: what each one is for

	Case	Task
What it tracks	One customer issue, from report to resolution	One action someone has to take
Examples	A billing dispute, a delivery complaint, a support question	Call back on Thursday, send a credit note, check the logs
Owner	One person responsible for the outcome	One person responsible for the action
Ends when	The customer's issue is resolved	The action is done
Linked to	The customer, and any invoice or order involved	A case, a customer, or both

A case can hold several tasks. A complaint about a wrong invoice might need a check by finance, a credit note and a follow-up call, each with its own owner and date. Tasks can also stand alone, such as a reminder to call a prospect next month.

A lifecycle with five statuses

More statuses feel precise but get used inconsistently. Five cover most small-team needs:

1. New: reported, not yet looked at.
2. Open: someone owns it and is working on it.
3. Waiting on customer: the ball is in the customer's court; pause any response targets.
4. Resolved: the fix or answer has been given; the customer can confirm.
5. Closed: confirmed, or no reply after an agreed period.

Write down what moves a case from one status to the next. "Resolved" should mean the customer has the answer, not that someone thinks they sent it.

What every case record needs

• The customer and contact, linked to the customer record, not typed as free text.
• A one-line summary a colleague can understand without opening the thread.
• Type and priority, from short fixed lists, so cases can be counted and sorted.
• One owner. A team can help; one name is accountable.
• Dates: when it was reported, when the next response is due, when it was resolved.
• The history: messages, calls and decisions, in order, with who did what.

That history is what lets someone else pick a case up when the owner is away. It works best when every change is recorded with a name and a time; the guide to why change history on customer records matters explains why.

Priorities and response targets

Response and resolution targets are often set by priority. A small team does not need a formal service-level agreement to benefit from a few internal promises:

Priority	Example	Respond within
Urgent	The customer cannot work or cannot pay	The same business day
Normal	A question or a problem with a workaround	Two business days
Low	A suggestion or a minor issue	One week

Pick targets you can keep. A promise met every time builds more trust than an ambitious one met half the time.

Turn promises into tasks

Most dropped balls are promises, not problems. "I will check and come back to you" is a task. Create it at the moment you say it, with your name and a date, and link it to the case or customer. A task without a due date is a wish.

• Keep task titles as verbs: "Send revised invoice", not "Invoice".
• Assign one owner per task, even when several people help.
• When a task is done, note the outcome in the case history.

The weekly review

Once a week, spend fifteen minutes on three lists: cases past their response target, tasks past their due date, and cases waiting on the customer for longer than a week. Reassign, chase or close each one. This habit does more than any tool feature.

Over time, the case list also tells you something. If the same type of case keeps coming back, fix the cause: clearer invoices, a better onboarding email, a product change. When late or missed deliveries top the list, the guide to planning deliveries and routes covers the habits that prevent them.

Keep it next to the customer record

Cases are most useful when they sit next to everything else about the customer: contacts, invoices, payments and past cases. When a customer calls, the person answering sees the open issue and the unpaid invoice on one screen. The guide to CRM for a small business covers how to structure that record, and why a CRM with invoicing helps explains the value of keeping billing in the same place.

Case notes often contain personal data. In the EU, the GDPR generally applies to what is written in them and how long it is kept, and other regions have their own rules. Write facts, not opinions, and agree how long closed cases are kept.

Frequently asked questions

What is the difference between a case and a ticket?

In practice, very little. "Ticket" is common in support and IT teams; "case" is common in CRM and account management. Both track one customer issue from report to resolution.

Do I need help desk software for a small team?

Not to start. A shared list with the fields above and a weekly review can work for a handful of cases a week. Dedicated tools help when volume grows, when several people share one inbox, or when you need response targets tracked for you.

How do I stop follow-up tasks from slipping?

Create the task at the moment you make the promise, give it one owner and a due date, and review overdue tasks weekly. Most slips happen because the promise was never written down.

Who should own a customer case?

One named person, usually whoever can resolve it or the account owner. Others can contribute, but a single owner keeps the customer from hearing different answers from different people.