Ask Flow, collect from the locker.
Someone reports a broken laptop in Teams, Flow raises it, and a locker code could come straight back.
Tools you may already run, plus the one that hands the device over.
From the first signal to a device in hand.
An employee tells Flow in Microsoft Teams or Slack that their laptop screen is smashed.
Flow raises the request, confirms the entitlement and asks Smart Collect® to reserve a pre-built laptop nearby.
A locker code comes back in the same chat. The employee swaps devices and the swap is recorded.
The full sequence
- An employee tells Flow in Teams that their laptop screen is broken.
- Flow asks a short set of questions and raises the request.
- Flow checks entitlement against policy.
- Flow asks Smart Collect® to reserve a pre-built laptop near the employee.
- A locker code comes back in the same chat, with the location.
- The employee swaps devices, and the swap is recorded against them and the asset.
What you need in place
- Flow by ServiceNow set up in Microsoft Teams or Slack
- Smart Collect® running on a ServiceNow instance
- Smart Lockers or Smart Vending on site, with stock
- Agreed entitlement rules for replacements
How the pieces connect
- Flow by ServiceNow
- Understands the request in chat and calls Smart Collect® to reserve the item.
- Microsoft Teams or Slack
- Where the employee asks for help, and where the code comes back.
- Smart Collect®
- Reserves the device, issues the code and records the handover in ServiceNow.
The physical steps stay the same, whichever system makes the decision.
This recipe starts with AI. The physical steps stay the same whichever AI you choose.
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. Flow by ServiceNow set up in Microsoft Teams or Slack · Smart Collect® running on a ServiceNow instance · Smart Lockers or Smart Vending on site, with stock · Agreed entitlement rules for replacements
- How the pieces connect. The role of Flow by ServiceNow, Microsoft Teams and Slack 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. Replace automatically for agreed fault types within entitlement.
- Handover rules and exceptions. Reservations, codes, expiry, returns, and what happens when stock runs out or nobody collects
- What to measure. Time from first message to device in hand · Share of requests completed without a person · Cost per completed request
- 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 we need the full ServiceNow platform?
Flow does not need it. Smart Collect® runs on ServiceNow, so we agree the right set-up for your estate in the first call.
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.
Which AI does this need?
Whichever fits your estate. Otto suits companies on the ServiceNow platform, Flow suits teams not on it yet, and the physical steps are the same either way.