When the customer becomes the case manager
A customer sends a WhatsApp message about a faulty appliance. Your team asks for purchase details, reviews the request and agrees on a replacement. A few days later, the customer calls to ask what happens next. The person answering cannot see the earlier decision. The customer explains the problem again.
Take a fictional appliance retailer with a service desk in Nairobi and a separate fulfilment team. The customer has sent purchase evidence by email, discussed the fault on WhatsApp and followed up by phone. Each person may have handled their own conversation, yet the replacement remains unfinished. This example illustrates a business workflow, rather than a GoDesk customer case study.
The customer is now carrying the history between departments, resending information and reminding the business what it promised. That is extra work for the customer and your team. A better process keeps the history, responsibility and next action available to the people handling the request.
Let the customer change channels while your team keeps the context
Customers use the channel that suits the moment. WhatsApp is convenient for an initial enquiry. Email may carry purchase information. A phone call can help when a customer needs an explanation or an urgent update. An omnichannel contact centre brings those conversations into a connected operation.
GoDesk brings business calls and supported messaging channels together with customer records, tickets and tasks. When a customer calls after an earlier message, the agent needs to see the relevant history and outstanding work. Matching customer records and linking interactions correctly are part of the setup.
For a warranty process, agree how the team records purchase evidence and approvals against the case. If documents live in another system, define how staff find and review them. The next agent should be able to establish what has already been received, what was agreed and what remains outstanding.
Give the issue a ticket and a clear route to resolution
A conversation can end while the customer still needs help. A ticket provides a record for the issue, with an owner, a status and a route through the work. GoDesk supports configurable ticket workflows, assignment, response and resolution targets, and escalation rules.
For our fictional retailer, an example set of stages is: request received, evidence reviewed, replacement approved, fulfilment arranged and issue resolved. At each stage, the team needs an agreed responsibility and a reason to move the ticket forward. Approval creates the next piece of work; resolution confirms the customer’s issue has been addressed.
The steps below are an example process to configure around your business. Warranty decisions and the criteria for approving a replacement remain with the people responsible for your policy.
Capture the request
Link the conversation to the customer and assign a service ticket.
Review the evidence
Record what was received, what was checked and the decision.
Approve the action
Record the agreed action and assign the next task to an owner.
Arrange fulfilment
Connect the order reference and progress from the responsible business system.
Confirm resolution
Check the agreed outcome, close the ticket and request feedback.
Make the handover specific
An escalation should tell the next person what to do. Record the decision, the outstanding action, who owns it and when an update is due. A handover such as “arrange the approved replacement and record the order reference” is useful to the fulfilment team and to the next agent who answers the customer.
GoDesk tasks, ticket ownership, service targets and supervisor visibility can help teams organise this work. Configure escalation responsibilities around the people who can move the case forward. Supervisors should be able to identify overdue requests, outstanding tasks and cases awaiting another team.
When another agent takes over, they should continue from the existing record. The customer can ask for an update without having to prove that an earlier conversation happened.
Connect the service case to the replacement order
An approved replacement still needs to be arranged. Where orders, stock or delivery records live in an ERP or another fulfilment system, connect the service workflow to that system. GoDesk can connect customer communication and follow-up work to other CRMs and ERPs through an agreed integration.
Define which system creates the replacement order, how its reference is associated with the ticket and how progress returns to the service team. The agent needs a reliable answer when the customer asks whether the replacement is being prepared, is on its way or still needs attention.
GoDesk handles the customer communication and service work around those records. The connected business system continues to handle the order, stock and delivery functions assigned to it. Integration scope, available APIs, status mapping and exception handling are agreed during implementation.
Keep the customer informed as the work progresses
Agree useful update points: receipt of the request, confirmation that information has been reviewed, the approved next action and a meaningful fulfilment update. Customers should know what happens next and when the business will contact them again.
Configured GoDesk workflows can create follow-up tasks and send messages through supported channels when the agreed event occurs. An update that depends on an order or delivery status needs that information from the connected system. Give incoming replies an owner so a customer’s response becomes part of the ongoing work.
Messages should reflect the actual case status. Confirm an order has been created before telling the customer their replacement is being arranged. If progress is delayed, the responsible team needs a task and a clear way to review the exception.
Confirm resolution and learn from the experience
Agree what counts as resolution for this process. It may include confirmation that the customer received the replacement and that the original issue has been addressed. Record the resolution reason and close the ticket when the agreed conditions have been met.
A configured survey can request feedback after resolution. Reporting helps managers review response and resolution times, outstanding work and service performance. Customer feedback can reveal whether the experience felt clear and helpful, even when the team followed its internal process.
The useful result is a request followed through to resolution, with a customer who knows what happened and a team that can explain the work behind it.
Bring one real customer journey to your GoDesk demonstration
Start with a situation your team handles today. Ask to see a WhatsApp message become an assigned ticket, an email add context and a later phone call reach an agent who can review the history. Follow the ticket through a handover, the next task and a customer update.
If you already use a CRM or ERP, include the point where the service case needs information or an action from that system. Ask what happens when an order reference is missing, a status update arrives late or a customer replies after the ticket has been closed.
Your customers have already spent time explaining their needs. Give your next agent the context and tools to continue the work.
← All articles & guides