Collecting & tracking customer feedback is very important to make more informed product decisions. At a glance, you need to understand in which position the requests are standing, how the SLA is working, and if required you need to investigate a request in full. Customer request handling is one of the essential business processes in any organization.
A customer request management process typically goes through the following stages -
In GoodFlow, based on your industry and requirement, you can customize the customer request primary introduction form. Your customer support executives can log the requests manually or if you are capturing the request from your website and passing the value to GoodFlow via API, the fields can be -
Whenever a new request arrives, based on the request details the task of customer support is to segment the request by understanding the request type and assigning proper value like billing issue, feature request, functional issue, etc. Also setting the priority of the issue, so that the internal team can take action depending on the priority basis.
If the issue is some type of issue or feature request, which has to be addressed, the developer team changes the status to 'solving'. In this stage for future audit and understanding, the root cause analysis of the issue and the solution need to be written down.
Before releasing to the customer or on the production, the quality analyst tests if the problem is sorted or not. If it is some other type of issue like billing, or related to the account, this testing phase can be bypassed and the case can be closed.
Once the request is properly dealt with, the customer request status can be moved to closed. Many organizations also keep another status as resolved. Once the request is solved an automated email notifies the customer and once they confirmed, the stage of the workflow changes to closed.
If a customer request is currently not addressable, the customer support team puts it on hold. Some businesses don't move these requests as it becomes obsolete if untouched for a while, some keeps an option open so that on-hold requests can be moved to the acknowledged stage again.
A customer request moves into the escalation stage if there is any dependency on 3rd party which requires further investigation and approval and discussion with the senior management.
To reduce the repetitive work, you can set multiple triggers as required. In any business process, automation plays an important role in enhancing productivity and streamlining the work.
Once the task under 'solving' stage is done, let the client know via email automatically that the request is solved and will be available soon. Rather than crafting these emails each time manually, automation saves a lot of time and human effort.
After any event like task completion, field value changes if you want to send data to any other software, we got you covered. You can use triggers in GoodFlow and put the webhook details so that we can send the data to the API of your choice.
With GoodFlow, you can design your own methods, tweak the flows, and implement best practices the way you like easily. Let's start with the template and start managing your customer requests right away.
All our templates are customizable