Wouldn't it be nice if the laptop were ordered and the company phone arranged automatically whenever a new employee is hired? The good news: it works, and quite simply, if you use a device-as-a-service provider such as Everphone.
You automate device provisioning in ITSM by letting an event such as "joiner" create a ticket that orders a fixed device package for the role via API from the DaaS provider. The DaaS provider takes care of procurement and enrolment and, depending on the package, of additional services such as a phone number or eSIM and registration in the MDM. Device data such as the serial number, the IMEI, the phone number and the status then flow back into the ticket.
This article describes the process we recommend as a blueprint and also covers possible mistakes, which you can avoid quite easily. How the API itself works is explained in the article on the API for ordering laptops. How HR and IT experience the process is described in the article on automated device provisioning in onboarding.
What is an ITSM blueprint for workplace automation?
Well-known IT service management (ITSM) tools include …
- ServiceNow,
- Atlassian (Jira Service Management),
- TOPdesk,
- USU,
- BMC,
- Matrix42,
- Freshworks,
- Ivanti,
- DCON or
- OTRS/EasyVista.
An ITSM blueprint is the fixed template your ticketing system uses to handle device processes: which event triggers it, who approves, what is ordered and where the feedback goes. You build it once and use it for every joiner, role change and leaver.
A usable blueprint has six building blocks.
| Building block | The question it answers | Example |
|---|---|---|
| Trigger | Which event starts the process? | Contract signed, role change, leaver |
| Catalogue | Which device package or device choice does which role get? | Sales: 14-inch laptop, smartphone, headset |
| Approval | Who has to agree, and when does that step fall away? | Standard package automatic, exception approved by team lead |
| Order | How does the order reach the supplier? | REST call with role, start date, delivery address |
| Feedback | What comes back into the ticket? | REST message with status, serial number, delivery date |
| Exceptions | What happens when something goes wrong? | Error message to the IT team, retry after review |
The catalogue is the most important building block. It decides whether the automation covers the standard cases or triggers a follow-up question on every ticket.
How do I automate device provisioning in an ITSM system?
Planning and implementation are easier if you start with a pilot and expand afterwards. Start the pilot with a single process and a single pilot role. Then you work through the other roles until all the eventualities for a new order are covered.
The remaining process steps are then basically identical. Before going live, you test everything, of course. This is how you proceed step by step:
- Decide which event starts the process. Choose the moment the contract is signed, not the first working day. Otherwise the laptop arrives too late, no matter how fast the interface is.
- Define a device package (or a selection from a predefined portfolio) for the pilot role and enter it in the service catalogue.
- Build the call to the supplier's API and test it with a test ticket.
- Write the feedback back into the ticket: status, serial number, delivery date.
The pattern is similar for service cases such as defect reports. Role changes and leavers also follow a similar structure, although the sequence of steps differs and further steps may be added.
At Everphone, we have already implemented these device-as-a-service processes hundreds of times for customers and have proven blueprints ready to go. They are easy to implement and, where necessary, can be customised for the customer's organisation.
Why do ITSM projects fail at device integration?
They rarely fail because of the technology. Connecting a REST interface is routine for an ITSM team. The problems are decisions that were not made beforehand. These are the six mistakes we see most often.
1. Doing everything at once
It is best to start with a pilot: a user group, a site, a region, a country or a cost centre. Even in ServiceNow practice, trying to map everything at the first attempt and pushing integration planning to the end is considered a typical mistake (Ksolves). A pilot, by contrast, delivers results after a short time that the team can use as orientation.
2. No clean device catalogue
Without a fixed package per role, every ticket decides anew what is ordered. Define a few packages instead and treat deviations as a separate approval path.
At Everphone, choose-your-own-device is available on top: employees choose within a set framework, optionally with a co-payment. You can map this in the catalogue as a selection field instead of creating a special package for every wish. As mentioned: we have done all of this a hundred times and have the blueprints ready. Just talk to us.
3. Poor master data in the asset inventory
Duplicates and outdated entries are among the most common data problems in the CMDB, especially when data comes together from several sources (Nihilent). If the serial number comes back from the supplier automatically, the entry is created in one place. That prevents the duplicates that appear when someone adds the same device by hand.
4. No return channel
If you only order but nothing is reported back, your ITSM has no idea which device is with whom. In the end, someone maintains a list after all. Plan the return path of the information from the start: status, serial number, assignment.
5. No error handling
A call runs into a timeout. The ITSM repeats it, and suddenly two laptops are ordered. Or the call fails and nobody finds out.
Two rules help. First: every order gets a unique reference, and the recipient recognises repeats with the same reference. The pattern is known as idempotency, and there are guides on how to implement it in ServiceNow flows (ServiceNow Community). Second: not every error is retried. A network error yes, a missing delivery address no (DZone).
6. Unclear responsibility
If the process runs across HR, ITSM, procurement and the supplier, nobody feels responsible when something breaks. Name one person who owns the blueprint and a mailbox where error messages land. That costs half an hour of planning and saves you weeks of searching.
How does the ITSM integration of Everphone work?
Everphone offers a REST API that connects to common ITSM solutions, such as ServiceNow, Jira, Freshservice, Ivanti, Matrix42 and TOPdesk. The API costs nothing extra, and in the vast majority of cases the integration is straightforward.
The portal and the API work on the same data. What you order in the Everphone portal, you see via the API, and what arrives via the API, you see in the portal. Your team can therefore handle special cases by hand in the portal without disturbing the automated process.
You can find the details of the connection on the integrations page. If you use ServiceNow, the process is shown in the article Integrating Everphone with ServiceNow. If your joiner process runs through the HR system instead of an ITSM, the article on ordering devices via the HR system fits better.
Who benefits from automation in ITSM
It pays off as soon as your team regularly moves devices for joiners, role changes and leavers and the order still runs by email or form today. That is true regardless of company size.
If you only have a few cases a year, order in the portal and skip the blueprint. If you do not have an ITSM yet, the HR system is the better trigger.
Frequently asked questions
Which DaaS providers can be integrated into existing IT systems?
For every provider, check whether it has a documented REST API, whether it covers ordering and feedback, and whether it costs extra. At Everphone, the REST API is free and can be used with common ITSM systems such as ServiceNow, Jira, Freshservice, Ivanti, Matrix42 and TOPdesk. Further criteria are in the article on choosing a DaaS provider.
How long does it take to integrate device as a service into an ITSM?
A general duration cannot be stated reliably. It depends on how clear your device catalogue and approval paths already are. If you start with one role as a pilot, you will have something running sooner than someone who tackles all roles at the same time.
Do I need a clean CMDB before I start?
You do not need a perfect CMDB. But you should clarify which system is the leading source for devices. If serial number and status come automatically from the supplier, the entry is created in one place, and duplicates become rarer.
What happens if an API call fails?
That depends on your blueprint. Define which errors the ITSM retries, for example network errors, and which go to a person, for example a missing delivery address. Also give every order a unique reference so that a retry does not trigger a second order.
What is the difference between an ITSM blueprint and a workflow?
A workflow is a single process, such as "joiner". The blueprint describes the building blocks behind all processes: trigger, catalogue, approval, order, feedback and exceptions. That lets you add new processes without starting from scratch each time.
