Who among you enjoys waiting in line? Who likes to read nested message threads in ticket systems? Who enjoys sorting out issues in emails with many participants in the distribution list? Who willingly sets ticket emails for follow-up? Okay, I admit, these are rhetorical questions.
All of these are just means to an end, to integrate ourselves into the manufacturer support processes. And I’m sure you’ve experienced it too, when you eventually feel like you need to take the reins and moderate the support processes of your manufacturer so that the problem at hand is truly resolved, and not just, for example, the resulting issue when creating and submitting the requested log data.
Perhaps you have also already asked yourself: Has the person on the other side understood what I want to achieve and where the problem lies that needs to be solved?
Today, we can’t completely free ourselves from such conflicts in IT. But progress is immediately noticeable in your everyday life.
When working with solutions provided as a collaboration between multiple manufacturers, it is important that you are not sent back and forth between A and B due to finger-pointing among the manufacturers.
Organizations that use #Qumulo and #Yuzuy, access Qumulo and Yuzuy simultaneously through their company-specific Slack channel (unless otherwise desired). This way, Qumulo Customer Success and Yuzuy work directly together, and customers are not in the situation of having to hold everything together. Cases are jointly analyzed and resolved with high dynamics.
Qumulo and Yuzuy understand that customer benefit is essential. Not our per-ticket overhead costs.
If you already use Qumulo, you know what I’m talking about. You have the same experience when using Qumulo and Yuzuy in conjunction.
Thank you for reading!