Hi, Jamf Nation!
Good news…you will soon see an enhancement to your support experience with Jamf! In an effort to always improve, we’re launching a new Jamf support portal through Jamf Account. You’ll access it with your Jamf ID. And nope, there won’t be any changes to the support email, phone number or the teams who support you.
But to reiterate, you will need a Jamf ID to access this new portal. The Jamf ID will also allow you to access more functionality within Jamf Nation (think profiles), as well as Training Courses, with a single set of login credentials.
And as a reminder, if you’re experiencing issues with Jamf Account please email firstname.lastname@example.org.
Yes - more information about this exciting new portal is coming soon! Check back here (and watch your email) for the details!
- Your Jamf Support Team
🙂 Yes I understand that, in fact I just did that 2 min ago. I had to log into Jamf Account in order to create a ticket, it is also where I have to go in order to chat to support? I guess I am just not understanding what has changed. Or is it that only some customers had to do this and now everyone does?
Could y'all consider taking the Apple approach when it comes to announcing new features?
- Develop the new product or feature set
- Test the bejesus out of it
- Test it some more
- Don't announce it until it's actually ready
By pre-announcing this, you've already taken the wind out of its sails and confused most of us.
Can anyone from Jamf explain to me, why this new approach is better?
I was really happy to have everything in one place. Now I have the account page for the products and I need to login to another page to open a support ticket. Also this other page seems to be using service now, which I don't like, because it often makes a case very confusing with all the status messages in between.
JAMF! THIS IS A STEP BACK !
I posted this in the other (newer) post but copying here for visibility...
I have encountered three usability issues already:
Problem: User cannot log into the support portal directly.
Steps to Reproduce:
When you go to https://support.jamf.com while signed out, it shows 3 links on that page.
When you click either Knowledge or Get Help, there are two redirect steps:
Neither seem to be intended for customer use because they don't work. Or... someone forgot a step in the integration.
Workaround: log into account.jamf.com first, then go to support.jamf.com.
Critique: this is unnecessary work and defeats the purpose of having a dedicated support link.
Problem: After logging out of the Support portal, there is no link back to the home page.
Steps to Reproduce:
After logging into the support portal using the aforementioned steps, a user clicks "Log Out."
The resulting page says "Logout Successful: You have successfully logged out."
Now the user has no obvious way to log back in.
Notes: This is a default behavior in ServiceNow. The log out page needs to be customized.
Workaround: close the page and open a new one.
Critique: Was this even tested? Did UI / UX get a chance to review before release?
Problem: Jamf Account page does not consistently pass session token to Support page.
Steps to Reproduce:
Sign into account.jamf.com
Click "Get Help" > forwards to support.jamf.com in a new tab, and the page signs into ServiceNow.
Log out of the support page. Close the tab.
In the Account.jamf.com page, click Get Help.
Jamf.ServiceNow.com loads, but does not sign in.
Workaround: User must click "Log In" again.
Additionally, the https://jamf.service-now.com/stats.do page is showing. Some admins like that to be turned off for security reasons. It's not a PII leak because those pages do not show any personal or customer info. They only reveal information about your instance. It's enabled by default on ServiceNow instances.
...plus, the response time from the "support team" is waaaayy longer than before ServiceNow. I've created a case yesterday's morning and I've got a reply from the support, just to confirm what I've said in the notes. I've replied back with more detailed info and...NO replies since then! And the case is set at Medium, as priority!!!
The login issue @bradtchapman talked about is by far the one I run in to every time I go to open or update a case. The Service Now/Okta login doesn't take my info (email or username) at all. Sometimes it takes my credentials if I come from account.jamf.com/support first, other times it wants me to login.
Somehow I came across this page: https://jamf.service-now.com/idp_disco.do. It gave my two options:
Selecting Okta brought me to the login prompt that doesn't work. When I click the salesforce link, it sends me to https://jamf.service-now.com/login_with_sso.do?glide_sso_id=be6b272d1b050110dfb1da0dbc4bcb91 which then redirects to https://id.jamf.com/idp/login and I am able to login successfully.
I am posting here unfortunately because I cannot get a timely response from Jamf support. I would say after (during?) this revamp to support, this is easily the worst it has ever been in my 11 years of working with Jamf. If I'm lucky, I might get a chat agent after 40 minutes of waiting, and sometimes nobody picks up. Then, I create the ticket manually...and get a half baked answer linking me to the admin guide...thanks a lot... really disappointing.