GoHighLevel Pricing Table Element: Setup, Configuration and Testing Guide

What the GoHighLevel pricing table element does

The pricing table element presents several packages side by side so a visitor can compare them on one page. A typical column contains a plan title, price, billing period, list of included features and a call-to-action button. One plan can usually be given additional visual emphasis to indicate a recommended option.

The element is most effective when every column represents a clearly defined offer. For example, a table might compare service levels, subscription tiers or access packages. The table should make the differences between those options easier to understand, then direct each visitor to the correct next step such as an order form, booking page or subsequent funnel step.

How to add a pricing table in GoHighLevel

The exact labels in the editor may change as GoHighLevel updates its interface, but the normal setup sequence follows the same logic:

1. Open the relevant funnel or website page. Go to the funnel step or website page where the plan comparison should appear.
2. Open the page editor. Select the option to edit the page and locate the layout section where the table belongs.
3. Find the Pricing Table element. Use the elements panel to locate the pricing table component.
4. Place it in the page layout. Drag the element into the appropriate section and column. Leave enough room around it for supporting copy or a short explanation if the offer needs context.
5. Save the page. Save the initial layout before making detailed content and styling changes.

Before editing the columns, confirm that the table has a clear job on the page. It may be helping a visitor select a subscription, choose a service package or decide whether to proceed to a consultation. That decision determines what the buttons should do and what information belongs in each column.

Configure plan content before changing the design

Start with the content and offer logic. Design work is faster when the plan structure is already settled.

Define the number of plans

Choose the number of columns that matches the real offer structure. Do not create extra plans simply to fill available space. If two packages are genuinely different, two columns may be clearer than three. If several tiers exist, use only the tiers that are relevant to the decision on that page.

Name each plan clearly

Plan titles should help visitors understand the level or intended use of the offer. Names such as Starter, Professional and Enterprise can work, but they should be supported by copy that explains the practical difference. Internal names, vague labels and unexplained abbreviations create unnecessary comparison work.

Enter price and billing information accurately

Set the displayed price and make the billing period visible wherever it affects the decision. A monthly amount, annual amount, one-time fee and usage-based price communicate different commitments. If taxes, setup fees or limits apply, make sure the surrounding page copy explains them rather than relying on a small visual detail in the table.

Write comparable feature lists

Each column should use a consistent structure. If one plan lists outcomes while another lists technical features, comparison becomes difficult. Keep the items short and specific. Describe meaningful inclusions, limits or service levels rather than repeating broad promises such as quality, flexibility or support.

Set the button label and destination

The button should reflect the next action. A visitor selecting a plan might need to complete checkout, request a call, book a meeting or continue to a detailed page. Use a label that makes the action clear and link each plan to the correct destination.

Use the design settings to support comparison

Once the content is accurate, use the styling controls to make the table easy to scan. Common settings include typography, colors, borders, corner radius, spacing and alignment. The available controls depend on the GoHighLevel editor and the element version in use.

Keep the visual structure consistent across columns. Align plan titles, prices, feature lists and buttons so the eye can compare equivalent information quickly. Avoid giving every column a different color or layout because excessive variation makes the table feel more complex than the offer itself.

A highlighted plan can guide attention toward the option you want visitors to consider first. The emphasis should support a genuine recommendation, such as the package that fits the most common use case. It should not obscure the other options or make them difficult to evaluate.

Edit each plan as a complete workflow step

Work through the columns one at a time. For each plan, check the title, price, billing period, feature list, button label and destination together. This reduces the risk of updating visible copy while leaving an old link or mismatched plan configuration behind.

1. Select the plan column. Open the local settings for the individual pricing column.
2. Replace placeholder content. Update the title, price, billing information and included features.
3. Configure the call to action. Use an action-specific label and connect it to the intended page, form, checkout or booking flow.
4. Apply only necessary visual differences. Highlight the recommended plan if there is a clear reason to do so.
5. Compare the columns as a group. Check that the structure, terminology and visual hierarchy remain consistent.

For example, imagine a consultancy with three packages: an initial diagnostic, a guided implementation and ongoing operational support. The pricing table should not only show three prices. It should explain what decision each package supports, where the visitor goes next, and what information the business needs after that selection. The right design depends on that process.

Test the pricing table before publishing

Previewing the table is not enough. Test the complete path a visitor will take from comparison to the next business action.

Pay particular attention to mobile behavior. Side-by-side columns may stack vertically, which changes the order in which visitors see the plans. Make sure the recommended plan still makes sense in that order and that the table does not require excessive horizontal scrolling.

Common pricing table problems and how to diagnose them

The plans differ only by price

If visitors cannot explain why one plan costs more than another, the problem is usually offer design rather than page styling. Ask: what additional outcome, capacity, access or level of support does the higher tier provide?

The recommended plan is not genuinely recommended

A highlighted plan should reflect a business decision, not an arbitrary visual preference. Ask which option best fits the audience and explain that value through the feature list or nearby page copy.

Every button uses the same destination

Using one generic destination can be valid when every plan follows the same selection process, but it can also remove useful context. Ask whether the next step needs to know which plan was selected and whether that information is being carried forward.

The table contains too much copy

A pricing table is a comparison interface, not the entire sales page. Move detailed explanations to supporting sections or linked pages when the columns become difficult to scan. Keep the table focused on the differences that affect the decision.

The table is accurate but the workflow is unclear

Pricing content often connects to a CRM, checkout, calendar or follow-up process. If ownership is unclear after a submission, the page may generate activity without creating a reliable handoff. Review the destination, data capture and next action together. For broader CRM workflow design, see CRM consulting.

Connect the table to a wider operating process

The pricing table is one part of a larger system. A visitor may move from the table to a form, then to a CRM record, an internal notification, a calendar booking or a payment process. Map those transitions before adding automation.

For example, define what should happen when a visitor selects each plan: which form or page receives them, what plan value is recorded, who owns the next action, and what reporting should show the result. Only after that logic is clear should you automate notifications or downstream updates. If the wider process involves multiple systems, an automation service such as Zapier workflow automation may be relevant, but the workflow should be designed before it is connected.

When a pricing table is part of a broader funnel or CRM journey, the page should support a meaningful business state. A selected plan, completed form or booked consultation should be distinguishable from a simple page visit.

When to review the pricing table again

Review the table whenever the offer, pricing, checkout process or sales handoff changes. A page can remain visually correct while becoming operationally inaccurate. Schedule a content and link review when plans are retired, new services are introduced, billing changes or the next-step workflow is redesigned.

If the table is part of a larger systems improvement project, the useful question is not only whether the element can be configured. Ask whether it helps visitors make the intended decision and whether the business can reliably act on that decision afterward. More page elements and more automation do not automatically create a better customer journey.

ConsultEvoCommerce and Operations Intelligence PlatformAn example of connecting commercial activity, operational workflows, reporting and business data into a clearer operating system.→