On Thursday 20th May, we celebrated Global Accessibility Awareness Day. Not only did we champion the importance of creating a more accessible world for all but we also celebrated some fantastic recent achievements that are helping us achieve this mission. Here, I’d like to share our experiences of trying to make the TOPdesk product more accessible over the past year – and will also be offering some tips to help product developers and service managers on their own journey towards creating a more accessible future.
3 June 2021
We’re excited to announce that we’ve recently developed a new Zapier integration, meaning it’s now easier than ever before to integrate TOPdesk into your existing ecosystem.
8 March 2021
The TOPdesk Asset Management module makes organization-wide asset management easier and more intuitive than ever before. But despite adding a range of new features, there has still been one major hurdle holding customers back from migrating: reporting.
15 February 2021
Here at TOPdesk, we want to be at the heart of your organization: linking different departments, projects, goals, and services together in one centralized system. But in order to do this, we need to make it as easy as possible for our users to access TOPdesk wherever they are. That’s why we’re thrilled to announce that we’ve recently made some exciting changes to TOPdesk Mobile.
6 January 2021
Effective communication makes the world go round. Whether you’re using TOPdesk to communicate with your colleagues or your customers, one thing’s for sure: you have to communicate clearly.
15 December 2020
Many of our customers have been in touch throughout 2020, eager to find out if we can help them keep their office as safe as possible from COVID-19 outbreaks and compliant with local rules and regulations. As such, we’re excited to announce that we’ve recently launched our new Workplace Reservations Feature within TOPdesk, which also includes Workspace Booker.
27 October 2020
6 October 2020
If your organization uses TOPdesk but has incidents or changes without prefixes, it will eventually run into problems. These can range all the way from being unable to include external numbers in email subject lines to accidentally importing information into the wrong incident or change. But changing the prefix can lead to its own problems, too—like no longer being able to refer to old incidents within the request/action fields. So how did we tackle this problem here at TOPdesk? And why did we wait so long to do it?