PRODUCT DRAFT · INTERNAL

Shuby v2 — from FAQ chatbot to operational advisor

Today Shuby answers questions about S-HUB. The next version answers questions about your fleet — and turns each answer into a recommendation an ops user can act on in two clicks.

ASSUMPTIONS Chat-first — Shuby never interrupts. It asks a clarifying question before advising. It links into S-HUB with prefilled filters; it does not execute actions.
SCOPE OF ADVICE Three families only: redistribution against turn rate, lost-in-transit / no-signal triage, and demand prep for upcoming cases.
DESIGN RULE Every recommendation carries its evidence: the assets counted, the window, the KPI. No number appears without its source.

Screens below are drawn on the live S-HUB dark shell from your screenshot. The map is real Natural Earth geometry — it turns from the globe and settles on the located assets; swap in the live Mapbox surface when wiring up. Data shown is illustrative.

1Shuby v2 — interaction models & the recommendation object
1aSide panel — the opening state, five ways in
SMADE
Locate Monitor Analyze Set up Shuby
Makalu-V › Makalu-V2
QJ
42 assets located Serial number Product line Last autoclaving Loan Parked MedEd Trial Hot Cold Search (facility) Select
42 assets located · nothing needs you right now
Shuby Your companion can make mistakes. Please read carefully.
ACT ×
Good morning, Quentin. I have read Makalu-V2 up to 4 minutes ago. Start anywhere — or ask me something else.
SUGGESTED FOR THIS FLEET Investigate the lost-in-transit assets Look for a product line in a specific state Tell me which kits are in my DC today Chase stagnant and dormant kits List kits autoclaved in the last 7 days
Each one opens with a clarifying question before I advise.
{{ pickedLabel }}
{{ clarify }}
Availability at Knoxville — never miss a case Fewer idle kits across the whole fleet Both — show me the trade-off
I'll read the last 60 days of Activity Journal for 42 assets in 6 facilities. Show the stagnant-kit answer instead →
{{ prioLabel }}
Then the fastest fix is a transfer, not a purchase. Here is what I would do.
REDISTRIBUTION · high confidence
Move 3 FRACTURE kits from Nashville to Knoxville before Aug 12. Nashville has 4 kits parked 41+ days. Knoxville ran 6 loan requests against 3 kits in July and lost 9 non-operational days waiting on returns.
0.4 → 1.6 Nashville turn rate, no purchase needed
Open the 4 parked Nashville kits in Locate →
Show the source data Not now
42 assets · Activity Journal, May 28 – Jul 27
What if Nashville picks up in August?
What if Nashville picks up in August?
You would still be covered. Nashville has 3 cases booked for August against the 8 kits it keeps — one above its own busiest month. If it passes that, I would move two kits back, not three. Who approves the transfer?
Who approves the transfer?
Your DC lead at Nashville releases parked kits, and the Knoxville rep confirms receipt. I cannot send that request — I can draft the serials and the dates for you. Draft it and remind me on Aug 12.
Draft it and remind me on Aug 12.
Done. The draft holds the 3 serials, both facilities and the Aug 12 date. I will flag it if nothing is logged by then. Open the draft →
 Start over
Ask about your fleet
↑
1bSide panel, upgraded — Shuby asks first
SMADE
Locate Monitor Analyze Set up Shuby
Makalu-V › Makalu-V2
QJ
42 assets located Serial number Product line Last autoclaving Loan Parked MedEd Trial Hot Cold Search (facility) Select
How is your fleet today?
Shuby Your companion can make mistakes. Please read carefully.
ACT ×
SWITCH TO Floating mode Bubble over the map, collapsible Side panel Docked beside Locate Full screen Shuby as its own workspace
Knoxville keeps running short on fracture kits. What should I do?
I can look at this two ways. Before I recommend anything — what matters more this month?
Availability at Knoxville — never miss a case Fewer idle kits across the whole fleet Both — show me the trade-off
I'll read the last 60 days of Activity Journal for 42 assets in 6 facilities.
Ask about your fleet
↑
1cSide panel — the recommendation object, evidence attached
SMADE
Locate Monitor Analyze Set up Shuby
Makalu-V › Makalu-V2
QJ
14 assets located Product line · FRACTURE Parked Facility · 6 selected Filters applied from Shuby · redistribution Close Shuby
Shuby Your companion can make mistakes. Please read carefully.
ACT ×
Availability at Knoxville
Then the fastest fix is a transfer, not a purchase. Here is what I'd do.
REDISTRIBUTION · high confidence
Move 3 FRACTURE kits from Nashville to Knoxville before Aug 12. Nashville has 4 kits parked 41+ days. Knoxville ran 6 loan requests against 3 kits in July and lost 9 non-operational days waiting on returns.
0.4 → 1.6 Nashville turn rate, no purchase needed
Open the 4 parked Nashville kits in Locate →
Show the source data Not now
42 assets · Activity Journal, May 28 – Jul 27 · refreshed 4 min ago
What if Nashville picks up in August?
Ask about your fleet
↑
1dInline — demand prep answered inside the asset list
SMADE
Locate Monitor Analyze Set up Shuby
Makalu-V › Makalu-V2
QJ
18 assets located Product line · FRACTURE Parked Last autoclaving Filters applied from Shuby · week 32 coverageClose Shuby
DEMAND PREP answering: “Am I covered for week 32?”
You are two kits short for week 32 — and both gaps close themselves if Mak-LC11 and Mak-LC14 come back on time.
CASES BOOKED 9
KITS AVAILABLE 7
RETURNING BY AUG 3 2
AT RISK 1 late return
Mak-LC14 is 4 days past its expected return and its last autoclaving was Jun 04 — it will need reprocessing before the Aug 5 case. I'd chase that one today and leave the rest alone.
Show the 2 late returns → How did you count cases? Dismiss
Based on 18 FRACTURE assets · loan history Jun 1 – Jul 27 · autoclaving events from Activity Journal
ASSET FACILITY STATUS EXPECTED BACK AUTOCLAVED
Mak-LC14 G038 · Knoxville, TN Loan · 4 d late Jul 24, 2026 Jun 04, 2026
Mak-LC11 G040 · Nashville, TN Loan · on time Aug 03, 2026 Jul 11, 2026
Mak-LC02 G040 · Knoxville, TN Parked · 12 d — Feb 22, 2026
1eDedicated workspace — Shuby as a page, evidence side by side
SMADE
Locate Monitor Analyze Set up Shuby
Makalu-V › Makalu-V2
QJ
THIS WEEK
Fracture kits at Knoxville Redistribution · today
Mak-LC07 silent since Jul 14 Signal triage · Jul 24
Cover for 9 cases in week 32 Demand prep · Jul 22
START FROM
Which facility is over-stocked? What is stuck in transit? Am I covered for next month?
History Switch to
SWITCH TO Floating mode Side panel Full screen
REDISTRIBUTION

Nashville is holding 4 fracture kits that Knoxville needs before Aug 12.

Nashville turns its fracture kits 0.4 times a month — the lowest of your 6 facilities. Knoxville turns them 1.9 and still ran out twice in July.
RECOMMENDED, IN ORDER
1 Release 3 of the 4 kits parked 41+ days at Nashville — keep the fourth as local cover.
2 Ship them to Knoxville so they land before the Aug 12 case block.
3 Log the transfer in Set-up so the turn rate is attributed correctly.
Open the 4 parked kits in Locate → Show the source data
Shuby does not move assets. It prepares the list and the dates; your DC lead releases them.
WHAT I READ
Nashville turn rate 0.4 / month
Kits parked 41+ days 4 of 11
Knoxville demand 6 requests, 3 kits
Non-operational days 9 in July
Sources Activity Journal
Monthly Performance
Every figure links to the S-HUB view it came from. Nothing here is generated without a record behind it.
SIGNAL TRIAGE

Mak-LC07 has been silent for 13 days. Treat it as lost in transit, not lost.

Its last fix was inside a carrier hub, and two other assets on that lane went quiet for 9–15 days before reporting again. I'd chase the carrier before declaring it lost.
RECOMMENDED, IN ORDER
1 Ask the carrier for a status on the Jul 14 pickup — reference the last fix at Memphis hub, 04:12 UTC.
2 Keep the kit in loan status until Aug 4 so it stays out of your non-operational count.
3 If it is still silent on Aug 4, escalate for a replacement tracker.
Open Mak-LC07 in Locate → See the 2 comparable lanes
Shuby cannot open a carrier claim. It drafts the reference details; you send them.
WHAT I READ
Last known fix Memphis hub
Jul 14, 04:12 UTC
Battery at last fix 62 %
Alert raised No-signal · Jul 21
Comparable lanes 2 assets, 9 & 15 d
Sources Activity Journal
Monitor alerts
Every figure links to the S-HUB view it came from. Nothing here is generated without a record behind it.
DEMAND PREP

You are two kits short for week 32 — both gaps close if Mak-LC11 and Mak-LC14 come back on time.

Nine cases are booked against seven available kits. Two are due back before Aug 3, and one of those is already late.
RECOMMENDED, IN ORDER
1 Chase Mak-LC14 today — 4 days past its expected return at Knoxville.
2 Book reprocessing for it before the Aug 5 case; last autoclaving was Jun 04.
3 Leave the rest alone — no transfer is needed if both returns land.
Show the 2 late returns → How did you count cases?
Shuby reads booked cases from the loan history. It does not change any booking.
WHAT I READ
Cases booked, week 32 9
Kits available 7
Returning by Aug 3 2
At risk 1 late return
Sources Loan history
Activity Journal
Every figure links to the S-HUB view it came from. Nothing here is generated without a record behind it.
Ask a follow-up, or start a new question
↑
1fDepth per plan — what WATCH, WATCH+ and ACT each get
WATCH Answers only
Shuby explains what it sees. It does not advise.
“Mak-LC14 is at G038, Knoxville, last seen 2 h ago. It has been on loan for 26 days.”
Location and status questions · S-HUB how-to · troubleshooting
WATCH+ Answers + diagnosis
Shuby diagnoses one asset at a time.
“Mak-LC14 is 4 days late and last autoclaved Jun 04 — it will need reprocessing before its next case.”
Single-asset reasoning · alert explanations · no cross-facility advice
ACT Full advisor
Shuby recommends across the fleet, with evidence.
“Move 3 FRACTURE kits from Nashville to Knoxville before Aug 12 — Nashville's turn rate is 0.4, Knoxville lost 9 days waiting on returns.”
Redistribution · signal triage · demand prep · prefilled deep links
On WATCH and WATCH+, Shuby names the recommendation it would make and stops there — the reasoning stays locked. That is the upsell moment: honest, specific, never nagging. Talk to your account manager

Try next: “wire 1a to the redistribution answer” · “build the 1e workspace as a clickable prototype” · “tighten the reco card in 1c — too many numbers” · “add the redistribution follow-up conversation, 3 turns deep”