Zero-touch Mac refresh.
A Mac flagged for refresh is replaced by one already enrolled and waiting.
Tools you may already run, plus the one that hands the device over.
From the first signal to a device in hand.
A Mac reaches its refresh date.
A new Mac is enrolled in Jamf or Iru and assigned in ServiceNow before collection.
The user swaps in a locker, and the old Mac goes back for wipe.
The full sequence
- A Mac reaches its refresh date in ServiceNow.
- A new Mac is assigned to the user and enrolled in Jamf or Iru.
- Smart Collect® reserves a cell, and the user is invited to collect.
- The user moves their data, usually by sync or Migration Assistant.
- They return the old Mac to the same cell.
- The old Mac is wiped and routed for reuse or disposal.
What you need in place
- Jamf or Iru managing your Macs, with Automated Device Enrolment
- ServiceNow with Macs recorded as hardware assets
- Smart Lockers holding new Macs
How the pieces connect
- Jamf or Iru
- Enrols the new Mac and applies your configuration, linked to ServiceNow through its integration.
- ServiceNow
- Tracks refresh dates and runs the refresh request.
- Smart Collect®
- Reserves the new Mac and records the swap.
The physical steps stay the same, whichever system makes the decision.
Run this recipe from a standard ServiceNow workflow today, and let AI take the decision later. Nothing on the physical side changes.
One record of what was decided, and what physically happened.
A reference design for your technical team.
The Blueprint shows how this recipe would work in your ServiceNow instance and what a build would involve. It is a design, not a step-by-step installation guide.
- What you need in place. Jamf or Iru managing your Macs, with Automated Device Enrolment · ServiceNow with Macs recorded as hardware assets · Smart Lockers holding new Macs
- How the pieces connect. The role of Jamf, Iru and ServiceNow and Smart Collect®, and what stays in your instance
- Step by step. All 6 steps, from the first signal to the returned device
- Approval and policy. Refresh by age and model, in line with your policy.
- Handover rules and exceptions. Reservations, codes, expiry, returns, and what happens when stock runs out or nobody collects
- What to measure. Refreshes completed without an appointment · Days from refresh date to new Mac in use · Old Macs recovered
- What a build involves. The questions to settle first, the roles involved, and how we would scope a six to eight week pilot
Request the Blueprint
A four-page reference design for your technical team. Tell us who you are and the Blueprint downloads straight away.
Before you ask
Do users need an appointment?
No. They collect when it suits them, within the reservation window, and return the old Mac in the same cell.
Is this an off-the-shelf integration?
No. It is a recipe concept that shows what becomes possible when these tools are combined with Smart Collect®. We build it with you, and where needed with the vendor, when it fits your estate.
Where does the data live?
In your own ServiceNow instance. Smart Collect® does not keep a separate database of your users or devices.
Do we need AI for this?
No. A standard ServiceNow workflow can run every step today. Otto or Flow can take over the decision later without changing anything on the physical side.