Arcanum Engine integration
How Hollow Reserve and Arcanum Engine work together — experience commerce plus playbook automation on the same Shopify store.
Hollow Reserve orchestrates client journeys — booking, intake, deposits, and follow-up. Arcanum Engine installs commerce playbooks that act on store signals — winback, review requests, inventory alerts, and more. Together they cover experience delivery and operational automation without duplicating dashboards.
Product roles
| Hollow Reserve | Arcanum Engine |
|---|---|
| Experience Blueprints and booking widget | Playbook installs and attributed automation results |
| Calendar, staff, and client ledger | Operating score and commerce systems |
| Deposits and experience analytics (Professional+) | Slack execution alerts and industry packs |
| Memberships and rebook automation (Studio) | Storefront tracking and GUARD opportunities from Sentinel |
Same-store experience
When both apps are installed, Command Center shows an ecosystem card linking to Engine opportunities and systems. Reserve does not require Engine for core booking — install Engine when you want playbook automation beyond journey stages built into your blueprints.
Running one product
- Reserve only — full booking, ledger, and blueprint orchestration
- Engine only — operating score and playbooks without Reserve's experience surfaces
- Both — recommended for appointment-led brands that also want attributed winback, review, and inventory automation
Lifecycle dedupe when both apps are installed
Reserve owns appointment lifecycle touchpoints — no-show recovery, post-visit review stages, and Studio rebook automation. When Hollow Reserve is installed, Arcanum Engine defers overlapping lifecycle playbooks (Appointment No-Show Recovery, Review Accelerator, Rebook Nudge) so your team is not double-alerted for the same client event.
| Topic | Hollow Reserve | Arcanum Engine |
|---|---|---|
| No-show | Journey stages + team notifications | No-Show Recovery defers when Reserve is installed |
| Post-visit review | Blueprint review stage + Klaviyo | Review Accelerator defers when Reserve is installed |
| Rebook after journey | Studio rebook automation + Klaviyo Journey Completed | Rebook Nudge defers when Reserve is installed |
| Abandoned checkout | Not applicable | Winback Engine and related commerce playbooks still run |
On Engine Systems, lifecycle playbooks show a Reserve handles client lifecycle badge when Reserve is co-installed. Install Engine for store-wide commerce automation — winback, inventory, VIP routing, weekly digest — not duplicate appointment alerts.
Klaviyo client lifecycle
Hollow Reserve sends booking journey events to Klaviyo on Professional+. Arcanum Engine sends separate commerce metrics (abandoned checkout, VIP, review request) on Growth. Use Reserve docs for appointment flows; use Engine docs for store-wide playbooks.
Was this page helpful?