Subscriptions in HighLevel

Updated: February 6, 2026  | 
Author: Bill Stilwell

This post covers how HighLevel subscription billing works, how to create and sell subscription plans, how free trials and failed payments are handled, and how subscription events connect to CRM automation.

Reading time: about 8 minutes.

What Are Subscriptions in HighLevel?

Subscriptions in HighLevel are recurring billing plans that automatically charge customers on a set schedule without any manual action required after the initial setup.

A customer signs up, enters their payment method once, and billing continues automatically – weekly, monthly, quarterly, or annually – until the subscription is cancelled or paused. The business receives predictable recurring revenue without sending individual invoices each cycle.

HighLevel handles the full subscription lifecycle: checkout, payment collection, failed payment retries, subscriber management, and access control via workflow automation. Everything is managed inside the platform alongside the customer’s CRM record.

Set up subscription products at Payments, then Products. View and manage all subscribers at Payments, then Subscriptions.

Creating a Subscription Product

Subscriptions are created as products in the Payments section. The key distinction from a one-time product is the pricing type: set it to Recurring rather than One-Time.

Once Recurring is selected, configure the billing interval – how often the customer is charged. Common intervals are monthly and annually, but weekly and quarterly are also available.

Set the price for each billing cycle.

Add a product name and description that clearly communicates what the subscriber receives. If the subscription gives access to a service, membership, or course, the description should match what they see on the checkout page.

The product can also have a setup fee – a one-time charge at the first billing in addition to the recurring amount. This is useful for onboarding costs or activation fees that only apply at the start of the subscription.

Selling Subscriptions Through Funnels

Once created, a subscription product is added to an order form or checkout page in a HighLevel funnel.

The customer completes the checkout form, enters their credit card details, and submits. Stripe tokenizes and stores the payment method securely.

The first charge processes immediately (or after the trial ends if a trial is configured). All subsequent charges process automatically on the billing schedule without any customer action.

The checkout experience is the same as any HighLevel product purchase. The subscription nature is reflected in the product description and the recurring billing disclosure shown at checkout.

Subscription products can also be sold through a payment link – a direct URL to the checkout without a full funnel page. Payment links are the quickest way to share a subscription checkout in an email, a social message, or a conversation.

Free Trials

Free trials are configured directly on the subscription product. Enable the trial option and set the trial duration in days – 7, 14, 30, or any number appropriate for the offer.

During the trial, the customer has access but no charge is made. At the end of the trial period, the first recurring charge processes automatically.

If the customer cancels before the trial ends, no charge occurs.

A card capture at trial signup – even for a free trial – significantly improves trial-to-paid conversion compared to a free trial that does not require a payment method upfront. The customer has already taken the payment commitment step.

The conversion friction at trial end is much lower.

For no-card free trials, HighLevel can be configured to require payment details only at the point of trial-to-paid conversion – though this approach typically results in lower conversion rates than card-at-signup trials.

Failed Payment Handling

Failed payments are an inevitable part of subscription billing. Cards expire, funds run low, banks flag unusual charges.

How a business handles failed payments determines how much revenue it actually collects versus how much it loses to silent churn.

HighLevel’s failed payment handling works through Stripe’s dunning logic. When a payment fails, Stripe automatically retries the charge on a configured schedule – typically after 3 days, 5 days, and 7 days.

The subscriber receives email notifications about the failed payment and a link to update their payment method.

If all retries fail, the subscription can be configured to cancel automatically or to flag the subscriber for manual review. In either case, a workflow trigger fires – enabling automated outreach to the subscriber before the situation becomes a cancellation.

A well-configured failed payment workflow contacts the subscriber immediately on the first failure with a direct link to update their card. This single step recovers a significant percentage of failed payments before manual escalation is needed.

Subscriber Management

All subscribers are visible at Payments, then Subscriptions in the sub-account. The view shows each subscriber’s name, plan, status, next billing date, and payment history.

From the subscriber record, a business owner can cancel the subscription immediately or at the end of the current billing period, pause billing, change the plan, view the full payment history, and issue refunds for past charges.

Cancellations made by the subscriber through the customer portal self-service link also appear in this view. The cancellation reason (if collected) and the effective date are recorded.

Filtering the subscriber view by status makes it easy to identify which subscribers have failed payments, which have recently cancelled, and which are approaching their renewal date – all actionable segments for targeted follow-up.

Subscription Workflow Triggers

Subscription events are some of the most important triggers in the HighLevel automation system. Each event represents a significant moment in the customer relationship that warrants an automated response.

New Subscription – fires when a customer completes checkout. Use it to send a welcome email, grant access to a membership or course, apply a subscriber tag, and notify the team of a new signup.

Subscription Payment Received – fires on each successful billing cycle. Use it to send a payment receipt and a brief value reminder – a short note reinforcing why the subscription is worth the ongoing cost.

Subscription Payment Failed – fires on each failed payment attempt. Use it to send an immediate notification to the subscriber with a payment update link.

Timing matters here – the first notification should go out within minutes of the failure.

Subscription Cancelled – fires when a subscription is cancelled. Use it to confirm the cancellation, set expectations for access end date, and start a win-back sequence after a cooling-off period.

Multiple Subscription Tiers

Most subscription businesses benefit from offering more than one tier. A basic plan and a premium plan serve different segments of the audience – price-sensitive customers and those who want more features or access.

In HighLevel, each tier is a separate product with its own recurring price and billing interval. A basic monthly plan and a premium monthly plan are two separate products.

A monthly plan and an annual plan for the same service are also two separate products.

Each tier can have its own checkout page, its own funnel, and its own workflow triggers. When a subscriber upgrades from basic to premium, the cancellation of the basic subscription triggers one workflow and the creation of the premium subscription triggers another – handling the upgrade transition automatically.

What Can You Do With It?

• Create predictable recurring revenue: Each active subscriber contributes to monthly recurring revenue (MRR) without any manual billing action. The subscription charges on schedule whether or not anyone on the team is actively managing it.
• Offer free trials that convert automatically: Card-at-signup free trials convert to paid subscriptions at the end of the trial period without any outreach required – the billing starts automatically when the trial ends.
• Recover failed payments automatically: Stripe’s retry logic combined with an immediate failed payment workflow notification recovers a significant portion of declined charges before they become cancellations.
• Automate the full subscriber lifecycle: Welcome sequences, receipt emails, failed payment alerts, and win-back campaigns all fire automatically based on subscription events – the relationship is managed systematically without manual tracking.
• Sell multiple plans from one platform: Basic, premium, monthly, annual – all managed in the same Payments section alongside invoices, one-time products, and proposals. No separate subscription billing tool required.
• Connect subscribers to your CRM and community: A new subscription creates a contact, applies tags, and can grant access to a HighLevel Course or Community automatically – the subscription purchase is the entry point into the full client experience.

Key Definitions

Use Cases by Industry

Marketing Agencies

An agency offers three service packages as monthly subscriptions – Starter at $997, Growth at $1,997, and Agency at $3,497. Each is a separate HighLevel subscription product with its own checkout page and welcome workflow.

New subscribers trigger a workflow that sends a welcome email, schedules an onboarding call, grants access to the client portal, and notifies the assigned account manager. Billing renews automatically on the 1st of each month.

The agency’s MRR is visible at a glance in the Subscriptions view.

Result: Recurring agency revenue is fully automated. No monthly invoice creation, no payment chasing, no manual access management – the subscription infrastructure handles all of it.

Online Education and Coaching

A business coach sells a monthly group coaching membership at $297/month with a 7-day free trial. New subscribers enter the trial on the checkout date.

At day 7, billing begins automatically – no manual conversion step required.

Failed payment notifications go out within 15 minutes of a decline. The subscriber receives a direct link to update their card.

Subscribers who cancel receive a confirmation email and a 30-day win-back sequence starting 14 days after cancellation.

Result: Trial-to-paid conversion happens automatically. Failed payment recovery is immediate and systematic. Cancellations trigger re-engagement – all without any manual monitoring of the billing queue.

SaaS and Software Products

A software product built on HighLevel offers a monthly plan and an annual plan – the annual plan at a 20% discount versus 12 months of monthly billing. Both are HighLevel subscription products.

Monthly subscribers receive a workflow email at month 10 offering the annual plan upgrade with the savings amount clearly stated. Annual subscribers receive a renewal reminder 30 days before their anniversary with a loyalty discount for renewing.

Result: Plan upgrade and renewal campaigns run automatically based on subscription age – reducing churn at the moments when it is most likely to occur.

Fitness Studios and Wellness

A fitness studio offers unlimited class access as a monthly membership at $149/month and a premium package with personal training sessions at $349/month. Members sign up online through a funnel.

New membership purchases grant access to the booking calendar automatically via a workflow tag.

Failed payments trigger an immediate email and a 48-hour hold on class bookings – giving the subscriber time to resolve the payment before access is suspended. Suspensions and reinstatements are handled by workflow tags applied on payment events.

Result: Membership access management is connected to billing status automatically. Paying members have access. Members with failed payments enter a grace period workflow. The front desk is not involved in routine billing operations.

Membership Communities

A paid online community charges $49/month for access. The HighLevel Community feature handles the member experience.

The HighLevel Subscription handles the billing. A new subscription grants community access via workflow.

A cancellation removes community access at the end of the billing period.

Members who cancel are shown a cancellation confirmation and offered a pause option – pause billing for one month rather than cancelling outright. The pause workflow suspends billing for 30 days and sends a reactivation reminder before the pause ends.

Result: Community access and billing are synchronized automatically. The member experience is uninterrupted for paying members and cleanly managed for those who cancel or pause.

Who Is This For?

How to Set Up and Sell a Subscription

Step 1: Create the subscription product

Go to Payments, then Products. Click Create Product.

Give the product a clear name, set the pricing type to Recurring, and configure the billing interval and price.

Step 2: Configure trial and setup fee if needed

Enable the free trial option and set the trial duration in days if a trial is part of the offer.

Add a setup fee if the first billing cycle should include a one-time onboarding charge in addition to the recurring amount.

Step 3: Add to a funnel order form or payment link

Add the subscription product to a funnel order form, a standalone checkout page, or a payment link.

Configure the post-purchase redirect to a confirmation or onboarding page. Include a clear billing disclosure on the checkout page so the customer knows what they are signing up for.

Step 4: Configure failed payment handling

In the subscription and Stripe settings, configure the retry schedule for failed payments and the action when retries are exhausted.

Decide whether to auto-cancel after exhausted retries or flag for manual review – and build the corresponding workflow for each outcome.

Step 5: Build subscription event workflows

In Workflow Builder, create workflows for each key subscription event:

New Subscription – welcome email and access grant. Payment Received – receipt email.

Payment Failed – immediate notification with card update link. Subscription Cancelled – confirmation and win-back sequence after cooling period.

Step 6: Test with a Stripe test card

Use a Stripe test card to complete a test subscription checkout. Confirm the subscription appears in Payments, then Subscriptions, the contact is in the CRM, and all workflows fire correctly.

Also test a failed payment scenario using a Stripe test decline card to confirm the failed payment workflow triggers as expected.

Step 7: Launch and monitor

Go live with the subscription checkout. Check Payments, then Subscriptions regularly in the first few weeks – confirm new subscribers appear, billing dates are set correctly, and no failed payments are sitting unaddressed.

Step 8: Add tiers if needed

Once the first plan is running cleanly, create additional subscription products for higher or lower pricing tiers.

Build separate checkout flows for each tier and update upgrade/downgrade workflow logic as the tier structure grows.

Step 9: Review churn regularly

Filter the Subscriptions view by Cancelled status monthly. Look at the volume of cancellations and any reasons captured.

Use the data to identify the most common point of churn – and whether the cancellation follow-up workflow is successfully winning back any of those subscribers.

How Does It Connect to HighLevel?

• Courses and Memberships: A subscription purchase is the most common entry point into a HighLevel Course or Community. A New Subscription workflow trigger grants course access, adds the subscriber to the relevant community group, and sends onboarding content – making the subscription the key to the Courses and Memberships experience.
• Workflow Builder: Subscription events trigger the full Workflow Builder automation system. Welcome sequences, payment receipts, failed payment recovery, and cancellation win-back campaigns all operate through the same workflow infrastructure as every other HighLevel automation.
• Invoicing: Invoicing handles one-time and recurring invoice billing. Subscriptions handle automatic recurring card billing. The two work together for businesses that combine project invoicing with ongoing subscription billing in the same client relationship.
• Client Portal: Subscribers with Client Portal access can view their subscription status, billing history, and update their payment method from the portal – reducing inbound billing support queries.
• Tag-Based Automation: Subscription events apply tags that drive Tag-Based Automation – active subscriber tags grant access, cancelled subscriber tags remove it, failed payment tags trigger dunning sequences. The tag state mirrors the subscription state automatically.

Common Questions

What are Subscriptions in HighLevel?

Recurring billing plans that automatically charge customers on a configured schedule – weekly, monthly, quarterly, or annually. Created as products with Recurring pricing in Payments, then Products.

Subscribers are managed in Payments, then Subscriptions.

Where do I set up Subscriptions in HighLevel?

Go to Payments, then Products. Create a product and set the pricing type to Recurring.

Configure the billing interval, price, and any free trial period. Add the product to a funnel order form or payment link for checkout.

How does HighLevel handle failed subscription payments?

Stripe retries the charge automatically on a configured schedule. The subscriber receives email notifications about the failure and a link to update their payment method.

If all retries fail, the subscription cancels automatically or flags for manual review based on configuration.

Can I offer a free trial with a HighLevel subscription?

Yes. Enable the trial option when creating the subscription product and set the trial duration in days.

No charge is made during the trial. Billing begins automatically at the trial end date.

Can subscribers cancel their own HighLevel subscription?

Yes. Through the customer portal link in subscription emails or the HighLevel Client Portal. Cancellations can also be processed manually from the Subscriptions view in Payments.

Can I sell subscriptions through a HighLevel funnel?

Yes. Add the subscription product to a funnel order form or checkout page. The customer completes checkout, their payment method is stored, and recurring billing begins on the configured schedule.

Can a subscription purchase trigger a workflow in HighLevel?

Yes. New Subscription, Payment Received, Payment Failed, and Subscription Cancelled are all workflow triggers.

Use them to automate welcome emails, receipts, failed payment alerts, and cancellation follow-up.

Can I offer multiple subscription tiers in HighLevel?

Yes. Each tier is a separate subscription product. Create as many tiers as needed – each with its own price, billing interval, and checkout flow.

What payment processors support HighLevel Subscriptions?

Stripe is the primary processor for recurring subscription billing in HighLevel. NMI and Authorize.net have different recurring capabilities – check your specific processor’s current HighLevel integration for subscription support details.

How do I view all active subscribers in HighLevel?

Go to Payments, then Subscriptions. The view lists all active, past, and cancelled subscribers with their plan, billing date, payment status, and associated contact.

Filter by status to identify specific segments.

To Wrap It Up

Subscriptions are the most efficient revenue model for service businesses and content creators – and HighLevel makes the billing infrastructure as straightforward as it can be without a dedicated subscription platform.

The setup is simple: create the product, configure the billing interval, add it to a checkout, build the event workflows. After that, billing runs on its own.

New subscribers pay automatically. Existing subscribers renew automatically.

Failed payments trigger recovery workflows automatically. Cancellations trigger confirmation and win-back sequences automatically.

The piece most businesses underinvest in is the failed payment workflow. Stripe handles the mechanical retries, but the workflow notification – sent immediately when the first payment fails – is what actually recovers the majority of at-risk subscriptions.

A subscriber who sees a failed payment notification with a direct card update link within 15 minutes of the failure pays far more often than one who receives a generic dunning email two days later.

Here is how to get started:

1. Go to Payments, then Products and click Create Product
2. Set the pricing type to Recurring
3. Configure the billing interval and price
4. Add a free trial if appropriate for the offer
5. Add the product to a funnel order form or payment link
6. Build workflows for New Subscription, Payment Failed, and Subscription Cancelled events before going live
7. Test with a Stripe test card – including a test decline scenario
8. Launch and monitor Payments, then Subscriptions weekly in the first month
9. Add additional tiers or annual plan options once the first plan is running cleanly

The failed payment workflow is the most valuable 20 minutes of setup in the entire subscription configuration. Build it before you launch.

The first failed payment from a real subscriber is not when you want to be figuring out the automation.