How to Personalize Customer Journeys When a Product Is Started Using the Product Started Trigger in GoHighLevel

Introduction

A customer's journey does not end when they receive access to a course or product. What happens after they actually begin using it can be just as important. Businesses can use this point in the customer journey to provide helpful information, send relevant follow ups, and create a more organized experience.

GoHighLevel includes the Product Started trigger under the Courses category in the Workflow Builder. The trigger starts a workflow when a learner starts a product or course.

This makes it useful for businesses that want their automation to respond to actual product activity rather than simply when a customer signs up or receives access.

For example, once a learner starts a course, a business could begin a follow up sequence, notify a team member, organize the contact, or provide additional guidance related to the product.

What Is the Product Started Trigger?

The Product Started trigger is a workflow trigger in GoHighLevel's Courses category. It fires when a learner starts a product or course.

This is different from simply giving someone access to a product. A customer may receive access but not immediately start the product. The Product Started trigger is designed around the point when the learner actually starts it.

This distinction can help businesses create more relevant automation.

For example, a course creator may want to send a specific message only after a learner begins the course. Instead of sending that message immediately after access is granted, the workflow can wait for the Product Started event.

This gives businesses a better opportunity to respond to customer activity and create a journey based on what the learner is actually doing.

How to Configure the Product Started Trigger

To create this automation, open Automation > Workflows in your GoHighLevel sub account.

Create a new workflow and select Add New Trigger.

Go to the Courses category and select Product Started. HighLevel lists Product Started among its available Courses workflow triggers.

After selecting the trigger, give it a clear name that explains its purpose. For example, Product Started Customer Journey makes it easy to understand what the workflow is designed to handle.

Once the trigger has been added, configure the available trigger settings according to the product or course you want the workflow to monitor.

After the trigger is ready, you can begin adding the actions that should happen when the learner starts the product.

Build a Personalized Customer Journey

After the Product Started trigger fires, the workflow can begin the next stage of the customer journey.

The actions you choose will depend on the type of product and the experience you want to provide.

For example, an online course business could send a follow up message welcoming the learner after they begin the course. The message could remind them where to find their content and explain what they should focus on next.

A business could also notify an internal team member when a learner starts a particular product. This can be useful when the product requires personal support or additional customer service.

Tags can also help organize contacts based on their activity. For example, a business may use a Product Started tag to distinguish learners who have actually started from contacts who only have access.

The important part is that the workflow responds to the Product Started event. This allows the automation to be based on learner activity instead of relying entirely on manual follow up.

Use Product Activity to Improve Follow Up

Customers who have started a product can require different communication from customers who have only signed up or received access.

For example, if a learner has already started a course, future communication can focus on helping them continue instead of repeatedly telling them to get started.

This creates a more relevant customer experience.

GoHighLevel separates several course related events into individual triggers. Its current workflow trigger documentation lists New Signup, Product Access Granted, Product Started, and Product Completed separately.

This allows businesses to build different automations around different points in the learner journey.

Continue the Customer Journey After a Product Starts

Once the Product Started trigger activates the workflow, the next step is to decide what should happen based on the learner's activity.

A simple workflow can begin with a welcome message and then guide the customer toward the next useful step. For example, a course business can send an email explaining where the learner should begin, while another business may notify a team member that the customer has started the product.

The important part is to make the communication relevant to the stage the customer has reached. Since Product Started is specifically tied to the learner starting a product or course, it can be used as a clear point for beginning this part of the customer journey.

Personalize Communication for Different Products

Not every product requires the same customer journey.

A business offering several courses may want different follow up messages depending on which product the learner has started. A beginner course might require basic guidance, while an advanced course may need different resources or instructions.

Keeping the workflow focused on the relevant product can make the communication more useful.

You can also organize your workflows around the different stages of the learning journey. HighLevel lists Product Access Granted, Product Started, and Product Completed as separate course triggers. This allows businesses to build different automations for access, active participation, and completion rather than placing everything into one workflow.

Keep the Automation Simple

A good customer journey does not need to contain dozens of workflow actions.

Start with the most important actions. A simple setup could be:

Product Started → Welcome Message → Follow Up → Internal Notification

From there, additional steps can be added when they provide a clear benefit to the customer.

For example, a delayed follow up can remind the learner to continue with their product. An internal notification can alert a support team when personal assistance may be required.

The goal should be to create a useful experience rather than adding automation simply for the sake of having more steps.

Test the Workflow Before Publishing

Testing is an important part of building any GoHighLevel workflow.

Before publishing the automation, check that the Product Started trigger is configured correctly and that the workflow actions contain the information you expect.

Use a test product and verify that the workflow responds when the product is actually started.

Check every communication that follows the trigger. Make sure the message is appropriate for someone who has started the product and that any links or customer information are working correctly.

Testing also helps you identify unnecessary steps before the workflow reaches real customers.

Conclusion

The Product Started Trigger provides businesses with a useful way to respond when a learner actually begins a product or course.

Instead of treating signup, access, and product activity as the same event, businesses can create separate workflows for different stages of the customer journey. HighLevel's Courses trigger category includes Product Started alongside other product and course related events, giving businesses more control over how they automate customer experiences.

With a well planned workflow, businesses can send relevant communication, organize customer information, notify their team, and guide learners through the next stage of their experience.

The best approach is to keep the workflow focused, make the communication useful, test the automation carefully, and update it whenever the customer journey changes.

Frequently Asked Questions

1. What is the Product Started Trigger in GoHighLevel?

The Product Started Trigger starts a workflow when a learner starts a product or course.

2. Is Product Started different from Product Access Granted?

Yes. HighLevel lists Product Access Granted and Product Started as separate workflow triggers. Access being granted and a learner starting a product are different events.

3. Can Product Started be used for customer follow up?

Yes. Once the trigger starts the workflow, you can add relevant workflow actions to create a follow up process for the learner.

4. Can I create different workflows for different stages?

Yes. Because HighLevel provides separate triggers for events such as access granted, product started, and product completed, businesses can build different automations around each stage.

5. Why should I test the Product Started workflow?

Testing helps confirm that the workflow responds correctly when the product is started and that all following actions work as intended.

Need Expert Help with GoHighLevel?

New to GoHighLevel and ready to get started? Buy your GoHighLevel account here and launch with confidence.

Already know what you need and want our team to handle everything, from complete setup and customization to funnels, workflows, automations, CRM, and pipelines? Click here.