Deployment runbook

Summit Coffee

Grow · $49/mo · ob_demo_deploy

activating

Verification credentials

Sub-account verification API Requires FORGE_SUBACCOUNT_API_TOKEN

Snapshot verification API Requires FORGE_SNAPSHOT_API_TOKEN

Without these secrets, verification steps stay pending — never faked. Add them via the secrets tool to enable read-only checks.

Human step — sub-account + snapshot

The one manual gate. Forge staff creates the sub-account and loads the snapshot.

Sub-account location id

1. Create client sub-account

human

Create a new CRM location/sub-account for Summit Coffee. Legal name: Summit Coffee LLC (DBA: Summit). Owner contact: Jordan Avery, +15551234567, jordan@summitcoffee.com. Address: 123 Main St, Boulder, CO 80301, US. Industry: coffee · EIN: 12-3456789. Record the returned location id — Forge uses it for read-only verification.

Verify: Sub-account location id exists and is returned by the admin.

Done

2. Load the Forge Perks snapshot

human

Load the frozen Forge Perks Pro snapshot into the new sub-account. The snapshot contains the finished Perks app, loyalty engine, workflows, SMS templates, and CRM config templates. Do not rebuild or reconfigure the engine — the snapshot is the product ceiling.

Verify: Snapshot load API returns success; the AI Studio project is present.

Done

Forge verification — auto-continue

Read-only checks. On pass, Forge applies entitlement + config and transitions to Activating.

3. Verify sub-account exists

forge

Read-only API check that the location id from step 1 exists and is active. Auto-retries with backoff.

Verify: GET location/{id} returns 200 and status active.

Done

4. Verify snapshot loaded

forge

Read-only check that the AI Studio project + loyalty workflows are present in the sub-account.

Verify: Project + workflow endpoints return the expected Perks resources.

Done

5. Apply entitlement

forge

Set the business's tier to GROW (49/mo) on the deployed instance, matching the purchased plan. Maps to the frozen entitlement matrix.

Verify: Entitlement flag reads back grow; referral=true, tiers=false.

Done

6. Write client config into the instance

forge

Push businessConfig into the deployed engine (configure, do not rebuild): name="Summit Coffee", rewardsLabel="Summit Coffee Rewards", logoUrl="". Use Forge neutral chrome (brand colors ignored). Earning rules: 1 active. Rewards: 2 active. Tiers: 0.

Verify: businessConfig reads back the client's values (name, logo, rules, rewards).

Done

7. Generate activation handoff

forge

Produce deep links + instructions the client needs for Pass 4: phone purchase, Persona identity verification, A2P brand + campaign registration, and domain (rewards.summitcoffee.com). Store on the onboarding record.

Verify: Activation handoff payload present on the onboarding record.

Done

8. Transition to Activating (owner notified by workflow)

forge

Transition the Opportunity to the "Activating" lifecycle stage. The Forge application does NOT send SMS — the native "Pipeline Stage Changed → Activating" workflow delivers the transactional "ready for activation" message to the owner. Delivery is the workflow's job; the authoritative record is the CRM message/workflow history, not an application log.

Verify: Opportunity stage moved to "Activating". Owner notification is handled by the HighLevel workflow, not the application.

Done

Entitlement applied

Grow — feature access on the deployed instance.

ReferralVIP tiersRetention campaignsSegmentsWin-back automationForge IntelligenceAsk ForgeAdvanced insightsCustom domain

Downgrades change feature access only — collected config is never deleted.

Go-live verification

Enrollment, points, redemption, SMS, workflow, domain. All must pass to mark LIVE.

Sub-account

Created

Snapshot

Loaded

Entitlement

Applied

Domain

pending

Activation handoff

Forge verified and configured the instance. Hand the client into their sub-account to complete phone, identity, A2P, and domain.

Open activation