Task management
What is task management in customer contact and why doesn't a ticket cover it?
A task is the work left over after you've answered the customer. That work usually sits in someone's head, and there it's invisible.
In short
Task management in customer contact is recording and following up the work that still has to happen after a conversation, with an owner and a date. Where a ticket is a question from a customer, a task is an action of yours. The two don't run in parallel: a ticket can be resolved while the promise inside it is only carried out two weeks later.
Why a ticket doesn't cover this
A ticket closes when the customer has an answer. But the answer was often a commitment: we'll call the supplier, we'll send a credit note, we'll come back once the delivery arrives. Keep the ticket open until that's done and you pollute your response time with waiting that isn't the customer's. Close it and the commitment is recorded nowhere.
That's why task management exists alongside ticketing rather than inside it. One list is about questions waiting on an answer, the other about actions waiting on a date.
What makes a task followable?
Most tasks that get stuck don't lack urgency but one of three things. There's no person attached, there's no date, or there's no definition of done. A task called "call supplier" with nothing else attached will slip a day every week.
- A name, not a department
- A task for "the warehouse" is a task for nobody. Put a person on it, even if someone else eventually does it.
- A date that means something
- Not today plus three days because the field needed filling, but the day the customer expects something or the delivery arrives.
- The link to the conversation
- Whoever picks up the task in a week must be able to read back what exactly was promised. A task without context gets researched again.
- A close-out visible to the customer
- The task is only done when the customer knows. Otherwise you ticked it off internally and they call anyway.
Why a separate task list rarely works
Many teams put their follow-up in a separate task system. It works for the first weeks and then sags, for the same reason as a manually filled CRM: creating costs time at the busiest moment, and reading happens at a different moment by someone else.
What makes the difference is where the task is created. If you can create it from the conversation itself, with the context automatically attached, it's a five-second action. If you have to open another tab and retype the situation, it won't happen when it's busy.
Recurring tasks and the things nobody asks for
Not every task comes from a conversation. Part of the work in customer contact is periodic: checking open returns, reviewing last week's unanswered conversations, updating knowledge base articles that have gone stale. That work has no customer to remind you, and without a recurring task it slips until someone suffers for it.
Task or ticket?
| Task | Ticket | |
|---|---|---|
| Originates from | A commitment or internal work | A message from a customer |
| Clock | A date it must be done by | A timer on the customer's waiting time |
| Visible to the customer | No, unless you message them | Yes, it's their conversation |
| Done when | The action has been carried out | The question has been answered |
If you tell a customer "I'll come back to you", close the ticket and create a task. If you say "I'll look into it now", keep the ticket open. The line runs along whether the customer is still waiting right now.
Where it goes wrong
Tasks without an owner in a shared list
A list owned by the team is owned by nobody. Always name a person, even if you reassign later. Redistributing is easier than working out afterwards who should have done it.
Setting everything to today
A list where everything is due today isn't a plan but a pile. Once the list is structurally overdue nobody looks at it any more, and the system dies more quietly than if you'd never used it.
Not messaging the customer on completion
Ticking off internally without telling the customer it's arranged produces a second conversation about exactly the same thing. Tie completing the task to a message.
Using tasks as a second ticket list
If every awkward conversation moves to the task list, your response time number hides in there. A question the customer is still waiting on should stay a ticket.
From commitment to completed task
Record the commitment during the conversation
Not afterwards from memory. What you promise, you create right then, with the text you sent the customer attached.
Put on the date the customer heard
If you said "Friday at the latest", Friday is the date. A task with a different date than the promise is late before it starts.
Name a person, even when unsure
If you don't know who'll do it, put it on yourself and hand it over. A task without a name waits for the first person who feels guilty.
Review the list at a fixed moment
A task list without a fixed reading moment is an archive. Ten minutes at the start of the day is enough.
Message the customer when you tick it off
The task is done when the customer knows, not when you know.
What to do this week
Search last month's resolved conversations for phrases like "we'll come back to you" and "I'll let you know". For ten of those, check whether another message went to that customer afterwards. Every time the answer is no, you made a commitment that was recorded nowhere, and that's exactly the gap task management closes.
What this looks like in a system
In Cuego you create a task from the conversation, with the customer, the order and the message automatically attached. The task gets an owner and a date, and appears in that person's list and the shared overview. When you complete it you can message the customer in the same action. Recurring work such as reviewing open returns is set as a repeating task or through a workflow that creates it on time.
TasksRelated terms
Workflow
A workflow is a sequence of steps that runs by itself once something happens. The skill is choosing which steps deserve it.
Read onBacklog
A backlog is the pile of open questions. The number says little; the age of the oldest says everything.
Read onAppointments and video calls
Some questions take three days in text and nothing in a fifteen-minute call. The skill is recognising which.
Read on