When it comes to describing how support software works, the terminology makes sense. Each request gets its own unique ticket with a unique ticket number. This isolates customer requests so that nothing gets overlooked and makes it easy to search for and find specific interactions.
When a customer submits a support ticket, it is logged into a support ticketing system, which assigns a unique identifier or number to the request. This allows both the customer and the support team to track the progress and status of the issue.
Right now, I use Zapier to forward the email that is sent to our support email address. This then creates a new task within the project. However, each time there is a response to that thread where our support team helps the customer, it creates a new task that is a duplicate essentially.
May I ask how you deal with email communication between yourself and the support client? Asana does not allow any old emails to be sent into it, so I assume it has to come from an approved email. So if you need to reply to that task I assume it would not go to the customer email, but to the approved email (e.g. ours!) so how does one deal with communicating on tasks between the support client?
I too would like to use Asana as our support system. At the moment we use Helpscout because anyone can email our support email into Helpscout. But then we have to manually add that as a task in Asana, but then all communication goes trough Helpscout. All because Asana does not allow un-approved email addresses into it. Its not good!
Correspondence with the client is facilitated via the comments field either by @mentioning them using their email address or by adding them as a collaborator. This works very well and the client can reply directly to the email notification they receive, which generates a new comment on the ticket.
Within the My Kaspersky Portal there used to be a section were you where able to see all your previous support tickets and requests. However this feature is now missing and has since been removed after Nov.
Much to the dismay of many Kaspersky subscribers, Kaspersky have removed the incident management feature from the MyKaspersky portal, the issue has been discussed in detail in a topic raised by @JPEKaspersky: My Kaspersky , the support link no longer takes me to the previous configuration where I could even consult my previous requests.
I find the new design of Jamf Nation very confusing. Where has the support section gone. I need to log a support ticket and can't find where it is now done. I can't even find my old tickets. The last thing people with an issue need is not to be able to find out to report a problme. Anyone with help please?
Yeah.......I spent five or ten minutes yesterday trying to figure out where I could submit a ticket. Noticed today that while my old cases are "visible" within the new ServiceNow ticket portal....those cases are all completely blank/empty. So I have zero history insight into past tickets, so that's great.
This has been a very poorly handled transition. The only communication I've been able to find doesn't say anything about there being changes on how ticket submissions would be handled. The email does say
I don't know what Jamf is thinking these days... They're so disconnected from their customers, as evident by their products and half baked, never finished features they add to them. They're too busy buying other companies/products than worrying about the own broken products. Gotta make those share holders/VCs happy, customers are no longer the priority.
Jamf's purpose is to simplify work by helping organizations manage and secure an Apple experience that end users love and organizations trust. Jamf is the only company in the world that provides a complete management and security solution for an Apple-first environment that is enterprise secure, consumer simple and protects personal privacy. Learn about Jamf.
This site contains User Content submitted by Jamf Nation community members. Jamf does not review User Content submitted by members or other third parties before it is posted. All content on Jamf Nation is for informational purposes only. Information and posts may be out of date when you view them. Jamf is not responsible for, nor assumes any liability for any User Content or other third-party content appearing on Jamf Nation.
I took a look at your tickets with Zapier Support, and it seems like they were able to reply to your query today and yesterday. Have you tried searching for emails from zapier.com in your inbox or spam folders?
I have checked your ticket, and it is currently active in our queue. However, our Support Team is currently managing a higher volume of inquiries than usual, which has unfortunately led to longer response times.
If Support asks question by FORWARDING the original Support request, then I know which ticket it concerns and can respond. Occasionally, I will get an email asking if the Issue is still a concern but the email provided no details only the Case ID. I can never seem to get more information.
The only way i have figured out is to open the 2nd post from support (the 1st one is just an auto reply) and idenify the case ID from the subject. It should contain the original information that you have filled.
So the Case ID is in the ticket list. I blanked them out in the image I provided. My problem is that I cannot find out WHERE I can go with that Case ID to refresh my memory on which Case ID related to which issue I submitted.
In other words...with the Case ID in hand, where do I go to look up the submitted ticket details?
So, maybe what you are saying is that I need to SAVE the emails so that if/when I get a follow-up request, I can go back to that original email thread to understand waht issue the Case ID corresponds to. Is that what you mean?
You currently have an open case with us, and you may only have one support case open at a time. If you open a new case, your open case will be CLOSED and you will be placed at the end of the queue. We recommend waiting for your current case to be resolved
Hello everyone, being a newbie on submitting Support Ticket, I was wondering if anyone can help confirm where I can view the list of tickets I have submitted to Support - hopefully with the status as well.
With every Support Ticket you submit, you should receive an email confirming the submission confirming the support ticket number - if you have additional notes to add after the initial submission, please reference that number and respond directly the that first email.
Based on the account associated with your email address, it looks like you are part of an organization that has purchased one of our additional Support packages, providing access to our Support phone line. You can find this information at the bottom of your personal Account Administration window, from your profile Icon in the top right corner of Smartsheet. (See here for more information).
So where can I view a consolidated list of support entries - rather than going thru my Emails individually to find the support ticket, I was hoping to be able to view the list I have submitted via the support portal.
As far as I'm aware, we don't have the ability to show open support tickets from the portal. The list of support entries would be in your email inbox. You may be able to set up rules for your inbox that could automatically filter any of the Support Ticket responses into one place for you, if that would help.
If you have access to support tickets withyour subscription, filing a ticket with Acquia Support or your TechnicalAccount Manager (TAM), depending on your subscription, is as easy as signing into your Acquia account and then visiting the following URL:
Visit the Acquia Status page to ensureAcquia systems are operational. You can click Subscribe to Updates onthe Status page to receive updates whenever Acquia creates or updates anincident.
To create a Support or TAM ticket, you must have an Acquia subscription thatsupports it, and you must not have used all of your provided support or TAMtickets. For more information, see the Support Users Guide.
Event/Notification/Launch: If you want to notify Acquia about animpending event or launch, or communicate time-sensitive subscriptionactivities such as, but not limited to, website traffic warnings,environment testing, scans, or releases.
Make your ticket titles short and to the point, summing up the nature of theissue and include which websites or environments are affected. This approachallows Acquia to quickly identify and respond to trends if multiple customersare experiencing the same issue. As you enter text in the field, related linksmay appear underneath the subject field to assist you with solving commonproblems. Links will open in a new tab.
A good, clear, and complete description helps Acquia respond to your issuespeedily and more accurately. with a first response that is more likely to be auseful solution, rather than only a request for additional information.Keep the following tips in mind when you provide your issue description:
This includes URLs of pages on your website where you see errors listed,Acquia UI URLs, or URLs of third-party services having trouble connecting toyour Acquia website. Acquia can trace these full URLs to exactly what codeis running and creating the behavior you are seeing. These URLs helpdetermine whether you are having issues on Acquia servers, yourCloud Platform servers, or on your own web servers outside ofCloud Platform. This also shows Acquia, at a glance, when you are talkingabout a local instance of a website or a public production website. This isan important part of orienting Acquia in these cases.
b1e95dc632