Kotally turns every purchase into trackable credits and keeps the ledger accurate across bookings, renewals, freezes, and refunds — inside GoHighLevel, or from your own stack via the API.
Two ways to run Kotally
Same credit ledger and membership rules underneath. Pick how you feed it — or use both.
No code
Install from the GoHighLevel Marketplace. Kotally listens to your GHL and Stripe webhooks, so purchases, renewals, and bookings sync into the ledger automatically.
Developers
Run memberships from your own app, site, or automation. Create scoped API keys and call /api/v2 to grant, check eligibility, deduct, and restore credits — no GoHighLevel required.
How it works
Kotally connects payments, packages, bookings, and staff operations — whether you run on GoHighLevel or call the API directly — without rebuilding your CRM.
Follow one member's credits through each stage — hover, tap, or wait.
Step 1 of 5 · Payment
She checks out in GoHighLevel — or through Stripe. Kotally ingests the confirmation through one provider-neutral pipeline.
Step 2 of 5 · Packages & memberships
You define what each product is worth once. This pack is configured as ten class credits, ready to grant.
Step 3 of 5 · Kotally ledger
Kotally's ledger becomes the source of truth — every credit carries a reason, timestamp, and source.
Step 4 of 5 · Bookings
Each reservation checks eligibility before it is confirmed, then deducts a credit once the visit happens.
Step 5 of 5 · Staff + CRM
Her up-to-date credit state shows right inside GoHighLevel — or through the API — no spreadsheets, no guesswork.
Flow: a payment creates packages and memberships, which feed the Kotally ledger, which governs bookings and stays visible to staff and your CRM.
Why Kotally
Freezes, renewals, no-shows, and refunds are where membership systems break. Kotally makes them boring — predictable workflows, not staff guesswork.
Every credit movement carries a reason, a timestamp, a source, and a member. Double-entry and idempotent — simple to audit, easy to sync, impossible to quietly lose.
Freezes, cancellations, renewals, no-shows, refunds, and upgrades become workflows that run themselves.
Every reservation checks eligibility before it's confirmed, then updates the ledger after the visit happens.
Define what a package includes once. Kotally restores, deducts, expires, and rolls credits forward by your rules.
One engine, two surfaces: a no-code GoHighLevel install, and a scoped machine API for everything else.
Pricing
One plan with transparent per-location pricing. Use it through GoHighLevel or the API — same price. No per-seat fees, no surprises.
Launch memberships for one location, then add more as you grow.
Example monthly pricing
Billed monthly. Only active locations beyond the first are charged at the additional location rate.
FAQ
Answers to the things people usually ask before signing up.
Kotally connects to your GoHighLevel account via the official GHL marketplace OAuth flow. Once connected, Kotally listens to GHL webhooks for appointments, contact updates, and opportunity events so your credit ledger stays in sync without manual data entry. No custom code or API keys to manage.
Yes. Kotally ships a machine API at /api/v2 that runs the same credit ledger without any GoHighLevel connection. During getting-started, choose "Use the Kotally API instead", then create a scoped API key under Admin → API Clients. From there your own app, site, or automation can call grant, check-eligibility, deduct, and restore with a Bearer token. Pricing is the same — billed per active location whether you connect GHL or use the API.
No. You keep your existing Stripe setup. Kotally connects as a read listener to your Stripe account and watches for payment events (charges, refunds, subscription renewals). When a qualifying event arrives, Kotally automatically grants or adjusts the relevant member's credits according to your package rules.
A credit is a unit of access you define — it could represent a class visit, a session hour, or any service slot. Kotally maintains a double-entry ledger per member: every grant, deduction, expiry, rollover, or refund is recorded with a timestamp, reason, and source. You can inspect the full history for any member at any time.
Yes. Kotally provides a CSV import tool so you can seed opening balances for existing members before you go live. After import, Kotally takes over ongoing credit management. If you need a custom migration path for large data sets, reach out — we handle it with you during onboarding.
You own your data — always. Kotally stores your membership ledger on your behalf but it is never sold or used for any purpose other than operating the service. On cancellation you can export a full CSV of your ledger and member records at any time. We retain your data for 90 days post-cancellation before deletion.
Neither — Kotally adds a membership credit layer, it doesn't replace your CRM. If you run GoHighLevel, Kotally complements it: GHL handles your CRM, pipeline, and booking while Kotally runs eligibility checks before a booking is confirmed, deducts after a visit, and keeps the audit trail that makes refunds and renewals predictable. If you don't run GoHighLevel, the same engine is available standalone through the Kotally API.
Get started today
Start with credits and packages. Add memberships, renewals, freezes, booking rules, and reporting when you need them.
