Go-Live Checklist

Use this checklist for each location before launch. The Workspace section applies to every location. Use GoHighLevel or API-only depending on how the location is connected.

Workspace

• Kotally owner account exists and can sign in.
• Billing is active or trialing (or a free trial is still valid).
• The location appears in Admin → Locations.
• Admin users have the right owner, admin, or viewer access.

GoHighLevel

• Marketplace app is installed for the correct location (or connected from setup / Locations → Add location).
• OAuth callback completed without errors.
• GoHighLevel webhooks send to /webhooks/ghl.
• Embedded app or custom menu opens Kotally for staff.
• Each live offer has one active product mapping with the correct GHL product id.
• Booking calendars are mapped where credits should deduct.
• A test purchase grants credits; a test booking deducts one credit.

API-only

Use this instead of the GoHighLevel section when the location has no GHL connection.

• API location created from setup (Use the API) or Admin → Locations → Add location.
• At least one API client exists with the scopes its automation needs (manage to create members, grant / check / deduct / restore / summary as required).
• The raw token is stored in a secret manager, not in source.
• A test POST /api/v2/contacts (or grant) creates a member; a test grant and deduction behave correctly.
• Every mutating call sends a unique request_id so retries are safe.

Support readiness

• Staff know where to find member balance, ledger, payments, and upcoming bookings.
• API clients are created only for automations that need them.
• Support has a sample member to inspect if launch issues appear.