Go-Live Checklist

Use this checklist for each location before launch. The Workspace section applies to every location; the GoHighLevel and Products and bookings sections apply to connected sub-accounts, and Standalone (API-only) replaces them when you run on the API.

Workspace

• Kotally owner account exists and can sign in.
• Billing is active or trialing.
• The sub-account appears in Admin -> Locations.
• Admin users have the right owner, admin, or viewer access.

GoHighLevel

• Marketplace app is installed for the correct location.
• OAuth callback completed without errors.
• GoHighLevel webhooks send to /webhooks/ghl.
• Embedded app or custom menu opens Kotally for staff.

Products and bookings

• Each live offer has one active Kotally product mapping.
• Each mapping has the correct GoHighLevel product id.
• Each mapping points to the calendar that should consume the credit.
• A test purchase grants the expected number of credits.
• A test booking deducts one credit and appears in the contact timeline.

Standalone (API-only)

Use this instead of the GoHighLevel and Products and bookings sections when the location has no GHL connection.

• The API workspace was created from Admin -> Getting Started (“Use the Kotally API instead”).
• At least one API client exists with only the scopes its automation needs.
• The raw token is stored in a secret manager, not in source.
• A test grant creates the expected balance, and a test deduction (and restore) behaves correctly via /api/v2.
• Every mutating call sends a unique request_id so retries are safe.

Support readiness

• Staff know where to find contact balance, ledger, payments, and upcoming bookings.
• API clients are created only for automations that need them.
• Any external automation stores and sends a unique request_id for retries.
• Support has a sample contact to inspect if launch issues appear.