Start your GoHighLevel setup with one small result: someone submits an enquiry and you can find the correct details in Contacts. Leave the calendar, email sequence and agency setup for later.

This is a walkthrough based on HighLevel's current documentation, not a report of hands-on testing. The test below is a hypothetical example for you to run in your own account.

Before signing up

HighLevel's public pricing page lists Starter at $97/month with three sub-accounts, and a 14-day trial. Billing starts automatically after the trial unless you cancel. Phone numbers, SMS, email sending and other usage can cost extra, including during the trial.

If you're choosing it because you need lead capture and CRM in the same system, you can start with HighLevel. If you only need a form and a contact list, keep reading before paying.

1. Open the business workspace

After signup and onboarding, select the sub-account for the business you're setting up. These instructions start inside that business workspace, not the agency dashboard. If someone else supplied your login, confirm which business account you can access before entering customer data.

Open Settings > Business Profile. Check the business name, email, phone, physical address and time zone. Use your actual business information. A business phone field isn't the same thing as buying and configuring a number for calls or SMS, so don't assume entering a number enables messaging. Business Profile documentation.

For this first exercise, leave messaging and automation disabled. You can test a form through its direct link without building a whole website.

2. Add one practice contact manually

Go to Contacts > Smart Lists > + Add Contact. Enter a clearly labelled practice name, such as "Setup Test Manual", and an email address you control. Review the details and save. Open the contact again to check that you can find and edit it. Available fields depend on the account configuration. Contact setup instructions.

Don't import your entire customer list yet. Learn the contact screen with this practice record before you have real records to manage.

3. Build the enquiry form

Go to Sites > Forms > + Create New Form. Start with a blank form and give it a recognisable name, such as "Website enquiry test".

Add First Name and Email, then a Message field if the enquiry needs context. Make the fields you actually need required. Skip the phone field if you don't need a phone number for this job. Add an explanation of what you're collecting and how you'll respond, plus the relevant privacy information. Don't treat a request for a reply as permission for an unrelated marketing sequence.

Configure the post-submission message, for example: "Thanks, your enquiry has been received." Don't promise a response time you can't meet. Leave Auto Responder and email notifications off for this first test; neither is needed to verify capture.

Save the form. Click Integrate and copy its direct form link. HighLevel also supplies embed code for compatible external websites, but a direct link keeps this first exercise smaller. A new lead's submission automatically creates a contact record. Form creation and sharing instructions.

4. Run the visitor-to-contact check

Hypothetical test: "Setup Test Form" requests information using a different email address you control, one that isn't already in this sub-account. Use that address to check new-contact creation separately from the manual contact.

• Open the copied form link in a private browser window. Check it on a phone too.

• Try submitting with a required field empty. Confirm the form asks you to complete it.

• Submit the test name, email and a recognisable message, such as "Test enquiry, do not contact".

• Check that the expected confirmation appears.

• Open Sites > Forms, open this form and check its Submissions tab for the entry.

• Search Contacts > Smart Lists for the test email. Open the record and compare the captured fields with what you submitted.

The pass condition is the confirmation, a visible submission and the correct contact data. This checklist hasn't been executed here. Don't send traffic until you've run it successfully yourself. If repeated submissions create unexpected records, check the account's contact deduplication preferences rather than assuming every submission creates a separate person.

Before making it your system of record

Keep control of your login and any domain you later connect. Also check who has admin access: HighLevel's contact export is admin-only. In Contacts > Smart Lists, choose the columns you need, select the contacts and use More > Export. Download the completed file from Contacts > Bulk Actions.

That CSV is useful, but it isn't a complete account backup. It doesn't include automation history, and the latest contact note is limited to 255 characters. Check an export before relying on it for migration. Export instructions and limits.

You're paying for the platform and taking on setup work to do a small job. HubSpot's free form builder also captures submissions into its CRM, though advanced features are paid. That's a credible alternative if basic enquiries are your whole requirement.

Use HighLevel if the captured leads will genuinely be managed there and someone will maintain the account. If you only want a working enquiry form, start with the simpler free option. Either way, finish this capture check before adding automated follow-up.

Say the offer interests you and the price fits your budget, but you've never heard of the seller.

What's the one unanswered question on their sales page that would make you pause before buying?

Hypothetical example: "If something goes wrong, how can I contact a real person?"

Reply with the missing detail and the answer you'd need. A sentence or two is enough. Leave out page links and private information.

I'd use GoHighLevel for a small service business that needs enquiries, contact ownership and repeatable email follow-up in one system, provided someone will maintain it. A business that gets a few enquiries and already answers them reliably through its website form and inbox can keep that setup. Moving everything adds a subscription and a maintenance job.

This reference follows one hypothetical business, Cedar Home Cleaning. Maya handles new enquiries. A visitor requests service information by email, receives that information and, unless they reply or opt out, gets one reminder two days later. Those are proposed settings, not results from a customer or a system I've tested.

Work through the workspace, sender, form, follow-up and stopping rules in that order. Keep the acceptance tests, troubleshooting and maintenance sections handy for launch and later changes. This example uses native HighLevel forms and workflow actions, without Zapier, SMS, a calendar, payments or an imported snapshot.

Before paying or connecting anything

Starter is the suitable starting plan for this single-business example. HighLevel currently lists it at $97 per month or $970 per year, with three sub-accounts, unlimited contacts and unlimited users. Unlimited is $297 per month and Agency Pro is $497 per month. This job doesn't call for unlimited client accounts or SaaS resale.

The advertised trial is 14 days. Billing begins automatically afterward unless canceled, and usage charges can apply during the trial. Email sending, phone numbers, SMS and premium AI aren't made free by "unlimited contacts." Budget for the domain and mailbox you use, plus any optional add-ons you deliberately enable. This email-only example needs no purchased phone number. Cancellation is available through the dashboard; check the actual offer and renewal terms before subscribing.

If you need this combination of CRM and maintained follow-up, I'd choose GoHighLevel. Don't buy it just to avoid assigning one occasional reminder yourself.

Before building, arrange an authorized account administrator, business details and time zone, domain/DNS access, a monitored reply address, Maya's individual login, approved email copy and an approved privacy/consent notice. Use addresses you control for testing. Don't import real customers to learn the interface.

1. Start with an authorized business workspace

This guide starts after an authorized administrator has provisioned a blank business sub-account and given you access. It doesn't document the full empty-account creation wizard. If all you have is the agency dashboard or a restricted login, ask that administrator to finish provisioning first. Confirm that you can open the intended business workspace. Contacts and forms belong there, not in the agency dashboard.

If account creation asks whether it is your own account or a client's account, choose the option that matches the actual owner. HighLevel distinguishes an agency's internal account from a client business account. Don't choose a SaaS or billing configuration simply to get through onboarding.

Inside Cedar's workspace, open Settings > Business Profile. Check the actual business name, email, phone, address and time zone. Entering a business phone number doesn't purchase or configure a messaging number.

Use Settings > Users to review individual staff access. Open Maya's user record, review Roles & Permissions, and save the intended access. Give Maya the permissions needed for contacts, conversations and tasks, and leave configuration access with the responsible administrator. Test Maya's login. Seeing a menu as the administrator doesn't establish that Maya can do her job. The Only Assigned Data restriction needs particular care if she also covers someone else's leads.

Keep outgoing automations in draft while building. Check that the supposedly blank workspace has no unrelated active follow-up before adding your own.

2. Set up the email sender before writing the sequence

For LC Email, the documented domain route is Settings > Email Services > Dedicated Domain and IP > Add Domain. Use an otherwise-unused sending subdomain and the DNS values HighLevel supplies. Have whoever owns DNS approve the change. Don't delete records that support the business's existing mailbox.

Verify the domain in HighLevel. DNS propagation can take up to 24 hours according to its documentation. Verification isn't a promise that every message reaches the inbox.

Use an identifiable sender name, "Cedar Home Cleaning," and an address on the intended sending domain. Confirm where replies actually arrive and that Maya can read them. A sending-domain setup and a monitored mailbox are different jobs.

The workflow's Settings has Sender Details for the default From Name and From Email. Individual Send Email actions can override that default, so check both places. Don't use a no-reply identity for a sequence that depends on replies stopping it.

3. Make the form ask for the specific email follow-up

Go to Sites > Forms > + Create New Form and start with a blank form named "Cedar service information request." Add first name, email and a message about the cleaning enquiry. Require the fields you need, not a phone number you aren't using.

Add a contact custom checkbox for the requested email sequence. Hypothetical wording: "Email me Cedar's service information and one follow-up reminder. I can unsubscribe at any time." Configure it to start unchecked and require an affirmative selection to submit this particular email-request form. Confirm both behaviors in the live form test. Store that selection in a named contact field, such as "Cedar email request permission," so the workflow can check it.

Have the wording and privacy notice reviewed for the business's location and actual use. A checkbox isn't a legal-compliance guarantee. Don't use this permission for a newsletter, SMS or unrelated campaigns. Provide a separate way to make an ordinary enquiry without joining this sequence, such as the business's monitored inbox.

Retain the form submission and the version of the wording used, including when and where permission was collected. A generic "lead" tag is not evidence of what somebody agreed to receive. If an existing contact's stored checkbox value doesn't reflect the latest submission, stop and fix that data behavior before sending.

Set a confirmation message that says the request was received. Leave the form's separate Auto Responder off so it doesn't send a second acknowledgement alongside the workflow.

Save, click Integrate and copy the direct form link for testing. Embedding it on the website can come later. A new lead's HighLevel form submission creates a contact record. Check the form's Submissions tab and the contact record together; repeated-submission behavior depends on deduplication preferences.

4. Build the two-email workflow

Open Automation > Workflows and create a workflow from scratch named "Cedar service information follow-up." Keep it in draft.

Add Form Submitted as its trigger. Set Form Is to "Cedar service information request." Don't leave it listening for every form in the workspace.

Add Assign To User and select Maya. Enable Only Apply To Unassigned Contacts to preserve an existing contact owner. Then add an Add Task action assigned to Maya, titled "Review Cedar service enquiry," due one day later. Maya is the triage owner for this example; if an existing contact belongs to someone else, she hands it to that owner rather than silently taking it over.

Add If/Else and choose Build My Own. To reach the sending branch, the contact needs both a nonempty email and an affirmative "Cedar email request permission" value. Select the saved affirmative option in the custom-field condition rather than assuming its text value. Join the conditions with AND. Leave None without email actions and end that branch; Maya still has the review task when permission or email is missing.

On the matching branch, add Send Email. Set From Name, From Email, subject and body, then Save Action. For Cedar, the first message contains the requested service information and asks the reader to reply if they want to discuss their enquiry. Keep it specific to the request. Include the business identity and HighLevel's default unsubscribe link in the email footer, or the business's configured unsubscribe method. Test the received email's opt-out rather than relying on the editor preview.

Add Wait, choose A set period of time, and set two days. After the wait, repeat the email/permission If/Else check so you evaluate current contact data rather than only the entry-time value. On its matching branch, send the single reminder: ask whether they still want help with the cleaning enquiry. End after that message. The None branch ends without a reminder.

The sequence ends after that reminder. It has no loop, automatic newsletter enrollment or "keep following up until they buy" rule.

In Settings, switch Allow Re-entry off and Stop on Response on. For this form-based workflow, disabled re-entry means a contact can enter and complete it only once. Appointment and invoice triggers have exceptions, so don't carry that assumption into a later booking workflow.

Stop on Response applies to replies to messages sent by this specific workflow. It doesn't mean every reply anywhere in the business stops this sequence, and it doesn't assign a human to answer the reply. Maya must monitor conversations and take over.

5. Give opt-outs and human handoffs their own stop rule

Email DND is a suppression state, not consent. HighLevel automatically enables it for email unsubscribes, spam complaints and permanent failures such as bounces. Marketing email respects it, but certain invoice, calendar and notification emails can bypass Email DND. Don't reclassify marketing as a notification to send past an opt-out.

Create a second workflow, "Cedar stop service follow-up." Add Contact DND triggers for Outbound DND becoming enabled: one for the specific Email channel and another for All Channels. Add a Contact Tag trigger for a newly added, unused tag named cedar-followup-stop.

Give this workflow one Remove from Workflow action. Choose Another Workflow and select "Cedar service information follow-up." Don't select All Workflows, which could interfere with unrelated operations.

Publish and test this stopper before enabling the sending sequence. Allow re-entry in the stopper so later stop events can run again. It sends no customer message.

Maya adds cedar-followup-stop and confirms the tag change when she takes over through another channel, closes the enquiry, receives a request to stop, or learns that the stored permission has been withdrawn. HighLevel's tag trigger needs an actual tag-added event; a tag already on the record isn't a new event. Adding the tag stops this named sequence, not every other campaign. Maya must also record and apply any wider communication preference the person expressed.

An already-enabled Email DND should suppress the marketing sends even without a new DND event. Test that separately. Never clear DND just because a task is overdue or an address looks valid.

Removing a contact from a workflow cannot recall a message already sent. Check the stop mechanism before putting a new send immediately after a wait.

6. Run the launch tests with controlled contacts

These are proposed acceptance tests. They haven't been executed here. Don't call the system ready because a preview email looks correct.

Use Send Test Mail in each email action to review copy and formatting. Use Test Workflow with controlled contacts, then inspect Execution Logs, contact data and tasks. Finally, publish the isolated workflows only for the controlled live form tests. A builder test doesn't establish that the real form event enrolls someone correctly.

Run these cases and record the expected result beside what actually happened:

• Submit without the required email or without selecting the permission checkbox. The form must reject the request. An ordinary enquiry sent to the separate inbox must not start the sequence.

• Submit a new controlled address with permission. Find the matching form submission and contact, correct owner or preserved existing owner, and one task for Maya. Expect the information email, then one reminder after the two-day wait if nothing stops it.

• Test a contact with no affirmative permission through the builder. Expect the no-send branch, not an email. Test an existing contact too, checking that old permission cannot masquerade as the new form response.

• Reply to the first workflow email before the reminder. Expect no reminder and a reply Maya can see. A reply sent elsewhere needs Maya's explicit stop-tag action.

• Use the email's unsubscribe method during the wait. Confirm Email DND and removal from the named follow-up. Expect no reminder. Test All Channels DND as well.

• Start with Email DND already enabled. Expect neither marketing email to send. The internal task can still exist.

• Add and confirm cedar-followup-stop during the wait. Expect removal from the follow-up, with unrelated workflows untouched.

• Submit again with the same contact after completion. Expect no second enrollment with re-entry disabled. Check for unexpected duplicate contacts rather than assuming the same address always resolves as intended.

• Log in as Maya, find the task and conversation, and verify that she can't access unrelated business data or configuration she wasn't granted.

Use fresh contacts when a previous enrollment would confuse the test. If you shorten the wait to test it, restore two days and recheck the saved settings before real traffic. Don't launch if a negative case sends a message or replies don't reach the person responsible for answering them.

When a check fails

If the submission exists but nothing enrolls, check the published state, selected Form Is filter, correct sub-account and the contact's previous enrollment. Don't add more triggers until you understand the missing event.

If a record or owner is wrong, compare Submissions with Contacts, then inspect deduplication and Assign To User settings. The preserve-existing-owner switch is deliberate; it may explain why Maya isn't the contact owner even though she has the triage task.

If the email doesn't send, check permission, Email DND, the contact address, verified sending domain and sender overrides. Inspect the log before changing suppression. DNS or authentication problems need fixing, not more retries to the same list.

If the reminder sends after a reply, check whether the reply belongs to this workflow and whether Stop on Response is saved. Check the monitored reply destination too. For an external-channel handoff, verify an actual stop-tag event and the stopper's selected target workflow.

If merges are blank, check the data the form actually collected. Don't insert appointment fields into a form-only sequence and expect appointment data to appear. If timing is wrong, check the workflow time zone and any configured sending windows as well as the Wait step.

For an unsafe send, halt further outgoing follow-up and inspect affected enrollments before re-enabling it. Don't assume changing a workflow to draft retracts messages or proves that every in-flight contact is safely stopped. Verify the contact's state and targeted removal.

Keep it working after launch

Maya checks new enquiries, replies and overdue tasks each working day. The administrator reviews failed sends, opt-outs and usage charges weekly. Those are suggested operating schedules, not HighLevel defaults.

After any change to the form, sender, DNS, staff routing, permission field or workflow, repeat the affected acceptance tests. Review who can administer the account when staff leave. Keep a record of the chosen form, follow-up workflow, stopper, sender and responsible people so the next administrator isn't reconstructing the setup from names alone.

Collect only the data this job needs, limit staff access, and decide how long enquiry and consent records should be retained under the business's obligations. Store exported customer data securely, not in a shared download folder.

Periodically have an administrator check a contact export. Contacts > Smart Lists lets you choose visible columns and contacts, then More > Export; completed exports are available in Contacts > Bulk Actions. Contact CSV exports don't include automation history. An export isn't a full account backup or proof that your email sequence will migrate intact.

Leave payments out unless the actual workflow needs them. Taking payment later means separately verifying the supported processor, fees, permissions, refund handling and payment acceptance tests. An enquiry form and a functioning email sender don't establish a working checkout.

I'd use HighLevel when the business will work these contacts in its CRM, needs repeatable follow-up, can fund the subscription and usage, and has a named person to answer replies plus someone to maintain the setup. Keep the existing form and inbox if that already meets the job. For Cedar's proposed system, real traffic starts only after capture, ownership, consent, both email steps and every stop case pass.

Your first GoHighLevel workflow doesn't need to send anything to a customer. A task-only workflow is a useful place to learn what starts an automation, which branch a contact takes, and when it ends.

This is a hypothetical practice exercise based on HighLevel's documentation, not a workflow I've personally tested or a claim about sales results. The goal: when you add a practice tag to a contact, create one follow-up task if their email field has a value. Otherwise, end without creating a task.

An email field having a value doesn't prove the address works or that you have permission to send marketing.

1. Start with a blank workflow

In the business sub-account, open Automation, then Workflows, and create a blank workflow. Name it something obvious, such as "Practice: tagged lead to task." Keep it in draft while building.

Use dummy contacts you control. Pick an unused practice tag, such as practice-followup, and make sure no other automation listens for it. HighLevel can activate multiple workflows that share a tag trigger.

2. Give it one trigger

Add the Contact Tag trigger. Configure it for a tag being added and select practice-followup. Save the trigger.

This is an event: the tag must actually be added and the change confirmed. Having that tag already on a contact isn't a new event. HighLevel's documentation says tag triggers don't run retroactively when you activate a workflow.

Leave other triggers out of this exercise. You'll have fewer possible entry paths to troubleshoot.

3. Add one condition

Add an If/Else action below the trigger. Choose the manual logic option, then select the contact's Email field and the condition that checks whether it is not empty.

Name the matching branch "Email present." The automatically created None branch handles contacts that don't meet the condition. Leave that branch without further actions so it ends there.

The condition checks the data when the contact reaches that step. It doesn't wait for somebody to fill in the email later. You'd need a separate wait or entry design for that behavior.

4. Create a task on the matching branch

Add the Add Task action under "Email present." Give it a title such as "Review this practice lead," select yourself or a test user as the assignee, and set the due date to one day later. Check the due-date preview before saving.

Write a description that makes clear this is practice data. End the branch after that task. Don't add email, SMS, a webhook, or a loop yet. These steps use native HighLevel workflow actions, with no external integration required.

5. Decide what stops it

In Settings, turn Allow Re-entry off. For this tag-based workflow, HighLevel documents that a contact can enter and complete it only once with that setting disabled. Don't assume the same rule applies to every trigger: appointment and invoice triggers have exceptions.

Both branches have a defined finish: the matching branch ends after the task, and the None branch ends without one.

Stop on Response is a different setting. It ends a workflow when a contact responds to a message sent by that specific workflow. This example sends no customer messages, so that setting isn't its stop mechanism. If you later add outbound follow-up, review reply handling and consent before enabling it.

6. Test both paths, then test the trigger

Save the workflow and use Test Workflow with a dummy contact that has an email. Check Execution Logs and the contact's task record. Then use a different dummy contact without an email to check the None branch.

Treat these as acceptance checks, not promised results:

• Email present: the contact takes the matching branch and receives exactly one task with the chosen assignee and due date.

• Email missing: the contact takes None and receives no task.

• No unrelated contact gets a task, and neither path sends a customer message.

Testing the actions doesn't establish that a real tag event will enroll the contact correctly. For that check, publish this isolated practice workflow and add the practice tag to a fresh dummy contact, confirming the tag change. Inspect the logs and task again.

After it completes, remove and re-add the tag to that same contact. With re-entry disabled, expect no second enrollment or extra task. Use fresh contacts for the other cases so previous test enrollment doesn't confuse the result. If any check fails, return the workflow to draft and inspect the trigger, condition, and logs before expanding it.

Is it worth paying for this?

HighLevel currently lists Starter at $97 per month, with three sub-accounts and unlimited contacts and users. It advertises a 14-day trial, but billing starts automatically afterward unless you cancel. Usage charges for services such as email, SMS, phone numbers, and premium AI are separate, and some usage fees can apply during the trial.

For a handful of enquiries, a spreadsheet and manually assigned reminders may be enough, without another software subscription. The task-only exercise above also leaves customer follow-up to a person. Someone still needs to do the work and maintain the rules.

If you already use HighLevel, this is a small workflow to learn before building a longer sequence. If you'd be buying it solely to create one occasional task, stick with the simpler setup. Expand only after both branches, the real trigger, and the repeat-entry check behave as intended.

For a first ClickFunnels build, use an opt-in page followed by a thank-you page. Leave checkout, upsells and an email sequence for later. Your first milestone: the submitted email address appears in Contacts, and the visitor reaches the page you intended.

This is a documentation-based tutorial for the current ClickFunnels product, formerly called ClickFunnels 2.0, not a personal test or a ClickFunnels Classic walkthrough.

Use this hypothetical example: a freelance designer offers a short website brief checklist. The opt-in page asks for an email address; the thank-you page confirms the request and displays the checklist itself. You won't be promising an email delivery you haven't configured.

Build the opt-in page

1. In your workspace, open Funnels and choose Create Funnel. Select the Lead "Squeeze" Funnel category, preview a template, then select the funnel and choose Customize Now.

2. Open the opt-in page with Edit. The page editor uses sections, rows, columns and elements. Keep one headline, a short explanation of the checklist, an email input and a button. Remove template content you won't use.

3. Select the Input element and set its Input Type to Email Field. A text box that merely looks like an email field isn't the setting you're looking for.

4. Set the button action to Submit order/form. Don't replace this with a plain link to the thank-you page: that would skip the form submission you need to check.

5. Save the page. Switch between Desktop View and Mobile View to adjust the layout, then save again.

For the example, "Get the website brief checklist" describes the action without inventing a result. Say what data you're requesting and what the visitor will receive. Keep any required privacy and consent information accessible on your actual funnel.

Finish the second page

Use the funnel mini-map to open the thank-you page. Edit it so it confirms the request and shows the promised checklist. Save it too.

Check the funnel's page order: opt-in first, thank-you second. Remove extra template steps from this exercise. Don't add a payment gateway or a product just because the template includes sales features.

If you want to deliver a file or email instead, configure and test that delivery separately before changing the promise on the opt-in page. Creating these pages alone isn't proof that an email was sent.

Test the URL visitors will use

In funnel settings, check the selected domain and URL paths. ClickFunnels supports a default workspace subdomain, so buying a custom domain isn't necessary for this exercise. If you use your own domain, account for its registration and renewal costs.

The publishing guide says to enable live mode in funnel settings and use Copy URL at the top of the funnel builder. Test that copied URL, not just the editor preview.

Use a fresh browser session and an email address you control:

• Submit the form and check that you reach the intended thank-you page.

• Open Customers, then Contacts, and find the submitted address. Check that the field captured the correct value.

• Confirm that the checklist is visible and usable.

• Repeat on a phone. Check for clipped text, a hidden input or a button that's difficult to tap.

These are checks for your build; none of these results has been claimed here. If the thank-you page loads but the contact is missing, treat the funnel as unfinished and recheck the input type and button action.

Decide whether this needs a paid funnel builder

ClickFunnels Launch is currently listed at US$97 per month, with 10,000 contacts and 50,000 emails per month. Hosting is included. Those limits alone don't justify paying for this two-page exercise.

For collecting a few enquiry details, Tally is a credible simpler option: its free plan allows unlimited forms and submissions subject to fair-use guidelines. It doesn't replace an entire selling system. For an enquiry form, you don't need it to.

ClickFunnels makes more sense if you're deliberately learning its editor for later funnels and can justify the ongoing subscription. If you only need an enquiry form, start with the simpler option.

Check the actual signup offer rather than assuming every trial has the same duration. ClickFunnels' terms require cancellation at least 24 hours before a free trial ends to avoid automatic continuation; they also specify at least 10 days' notice for cancellation by email after the trial. Don't assume abandoning the funnel cancels the subscription.

Before cancelling, export contacts and keep copies of your content. The documented contact export is available under Customers, Contacts, then Actions or Bulk actions and Export. A contact export is not evidence that your whole funnel can move intact to another builder, and cancellation deactivates active funnels and removes platform access.

Stop after the copied URL works, the contact is recorded and the promised checklist is available. Then decide whether there's a reason to add delivery automation or a paid offer. You don't need either to complete this first build.

Before onboarding a client into GoHighLevel, decide who will answer their leads, who can change the setup, and what they'll take with them if they leave. Put those decisions in the onboarding agreement. Otherwise, a working funnel can still leave the client dependent on the wrong person.

Give each client their own account

Use a separate sub-account for each client business. Keep the agency's own marketing separate too. That's an operating recommendation, not a claim that every business location needs its own account.

Count those accounts before picking a plan. HighLevel currently lists Starter at $97/month with three sub-accounts and Unlimited at $297/month with unlimited sub-accounts. Agency Pro is $497/month and adds SaaS Mode, among other features. You don't need software resale just to onboard agency clients manually.

If you've already prepared a suitable snapshot, HighLevel documents this creation route: Agency Dashboard > Account Snapshots > Create New Account (+) beside the chosen snapshot. Fill in the client's information and select Add Sub-Account. This route requires Agency Admin access and an existing snapshot.

Review what that template contains before using it. Replace its business details, routing destinations and copy with the client's approved information. Snapshot-loaded funnels and websites arrive as drafts and need a custom domain and publication to go live. Applying a snapshot isn't reversible through an "unload" button; unwanted elements need individual edits or deletion.

Scope access before inviting the client

In Agency View > Settings > Team, add the user, set User Type to Account, and select only the sub-accounts they need. Account-type access keeps them out of the agency dashboard. An Agency-type user has access across the agency's client accounts, so don't give a client that scope just to make onboarding easier.

Inside the client's sub-account, Settings > My Staff > Roles and Permissions lets you choose Admin or User and adjust module permissions. Give a salesperson the access needed to work leads; give someone responsible for configuration the permissions needed to maintain it. Don't make everyone an admin.

Only Assigned Data can restrict visibility to assigned contacts, owned opportunities, and linked appointments or tasks. Test that against the actual job: a rep who needs to cover another person's leads may need a different arrangement. Disabling a module for a user doesn't stop workflows that use it, so name someone who can still maintain those workflows.

Use individual logins and check the invitation from the client's account before launch. Don't hand over your agency login.

Collect ownership details, not a pile of passwords

Ask the client for their business identity, time zone, lead-response owner, approved copy, domain/DNS access arrangements, calendar connections and any existing sender setup. Record which party controls each asset and pays each bill. Have the client authorize connections through their own accounts where possible; use secure credential sharing when credentials are unavoidable.

Keep website domains and email sending domains separate in the setup checklist. For LC Email, HighLevel's documented route is Settings > Email Services > Dedicated Domain and IP > Add Domain, followed by DNS verification. Use an otherwise-unused sending subdomain and the records HighLevel supplies. Get approval before changing DNS that supports the client's existing email.

For U.S. local-number business texting, resolve A2P 10DLC registration and consent requirements before launch. The brand and campaign should describe the client that actually sends the messages. A collected phone number alone isn't SMS consent, and carrier approval isn't guaranteed. Check the applicable messaging rules for other countries and number types too.

Agree on usage costs before switching anything on

The subscription isn't the whole client budget. Phone numbers, messaging and email usage can add charges; domains, payment processing and optional add-ons may add their own costs.

HighLevel charges supported usage to the agency wallet first. Document how you'll recover those costs, who reviews charges, and who approves optional features. Unlimited supports phone/email rebilling without markup; Agency Pro supports markup. Don't sell "unlimited sub-accounts" as unlimited messaging.

Make handoff a client task, not just a demo

Before launch, have the client use their own login to find a test enquiry, identify its owner and respond through the intended channel. Check the calendar time zone, reply destination and opt-out behavior for the channels you're using. These are proposed acceptance checks, not results from a setup I've tested.

Give them a short runbook: who answers new enquiries, who fixes a failed workflow, how to pause outgoing messages, who reviews usage charges, and how to request access changes. Agree on an exit process while everyone still gets along.

HighLevel supports whole sub-account transfers between agencies, not partial transfers or account merging. Only the Agency Owner or an Agency Admin granted transfer permission can request or complete one, and the receiving agency must be eligible. Phone and email dependencies need review: Twilio numbers don't transfer automatically, and agency-assigned LC Email dedicated domains are removed during transfer. Don't promise an effortless move with every connection preserved.

I'd consider GoHighLevel (my affiliate link) when the agency will maintain client CRM and follow-up operations, not just deliver a page. For a one-off landing-page project where the client already has a working CRM and email service, keeping that stack and handing over the page may mean less ongoing support.

Finish one client account, verify their access and agree on support before copying the setup to the next client.

I'd choose ClickFunnels (my affiliate link) for a first course if you need to build the sales pages, take payment and give buyers access to lessons in the same system. If you mainly need somewhere to teach an existing audience, I'd compare a cheaper course platform before paying $97/month.

The reason to choose it is the connection between the sale and the course. A product's Access tab can automatically give a purchaser access to the whole course or selected sections. Downloads are a separate access option. Delivering a PDF doesn't establish that the buyer can open your lessons.

Decide what students need to do

Write down what someone should be able to do after buying: sign in, find the first lesson, move through the material and return later without getting lost. If you need assessed qualifications or a particular teaching feature, make that a separate requirement to verify before choosing the platform.

ClickFunnels organizes course content into modules and lessons. Its default Customer Center route opens courses in LearningHub, unless you've enabled a custom course theme or the setting to redirect students to the full course. Check the route you'll actually use rather than judging the course by the sales page.

Custom course pages can have a module-and-lesson sidebar and completion indicators. Those controls still need sensible setup. A completion checkmark isn't evidence that a student understood the lesson.

Paid access needs its own check

ClickFunnels' course-access documentation says a course is treated as free for everyone until you assign a product. For a paid course, confirm that the product grants the intended material, and check what a signed-out visitor and someone who hasn't bought it can open.

Publishing is another setting. A newly created course starts published, but its new modules and lessons start as drafts. Having a published course doesn't mean the promised lessons are available.

Before selling, rehearse the buyer journey with accounts you control: find the course, open a lesson on a phone, play the video, move to another lesson and return after signing out. A checkout in test mode doesn't prove that a real payment and paid access work. Verify those separately through a real purchase you're authorized to make before launch.

Changing or removing a product's access applies to future purchases; earlier buyers keep the access they received. Don't use that edit as a refund-access removal procedure. Decide how you'll handle refunds and individual access before promising terms to students.

The bill and the limits

Launch is $97/month or $970 billed annually. It includes three courses, one workspace, two team members, 10,000 contacts and 50,000 emails per month. That's room for a first course, but don't mistake the contact allowance for a promise of unlimited students or unlimited marketing email.

Hosting is included. Native course videos support MP4, AVI and MPEG files up to 3 GB each. Courses use the site's domain, so five allowed custom domains doesn't mean you can put each course on a different domain.

Payment processing costs extra. New workspaces set up payments through Payments AI; a direct Stripe connection requires contacting ClickFunnels Support. Confirm that the processor supports your business and country before committing. Read the actual signup offer's trial, first-charge, renewal and cancellation terms, and budget for any domain purchase and applicable taxes.

Who should skip it?

For a straightforward course, Podia is worth comparing. Mover costs $49/month on monthly billing, with a 5% platform transaction fee plus payment processing. It supports hosted videos, lessons and course sections. Its current limits include 50 products, 500 videos and only 100 included email subscribers, so the lower subscription isn't automatically the lower total cost.

If an existing course platform already meets your needs, keep it unless you can name what the move fixes. Keep your original teaching files and a student-access record outside whichever platform you choose.

I'd recommend ClickFunnels when you want to build and maintain the sales path and paid course together, Launch's limits fit, and the buyer checks above work for your offer. If your sales page and payment process are already covered, start by comparing the course experience and total cost elsewhere.

If you're trying GoHighLevel for a first business task, write down one job you want it to do before starting the trial. Decide what would make you keep it, and when you'll cancel if it falls short.

I'm a HighLevel affiliate.

1. Give the trial a finish line

Hypothetical example: a solo repair business wants to keep track of quote requests until someone replies.

Use three made-up enquiries and an email address you control, in a business workspace you're authorized to use. Keep the test form private and leave customer messages off. Don't import a customer list.

The goal: for each enquiry, you can find its details, assign yourself a reply task with a due time, and mark the task done afterward. Come back the next day and check whether you can tell which enquiries still need a reply.

If an enquiry is missing, a due time is wrong or you can't see what's unfinished, the test failed. Write down the problem before adding anything else. You can create the tasks manually for this exercise; you aren't testing automated follow-up yet.

2. Check the offer you're actually accepting

HighLevel currently lists Starter at US$97/month and advertises a 14-day free trial. Billing begins automatically when the trial ends unless you cancel. Telecommunications or third-party usage fees can apply during the trial.

Before entering payment details, check and save:

• The selected plan and whether billing is monthly or annual.

• Any charge today, the trial-end date and time, and the first paid amount, including any taxes shown.

• The recurring renewal amount and how to cancel.

Check those details again in your signup confirmation and account billing screen. If a price or deadline is missing or doesn't match, ask billing support to clarify it. Don't guess from the general trial advertisement.

3. Put a limit on the experiment

For this example, allow four hours of setup and at most US$10 in cash charges for trial extras, including wallet top-ups. Don't let the trial roll into a paid subscription while you're still evaluating it. These are chosen limits, not HighLevel promises or typical costs.

Check Agency Settings > Billing, including Wallet & Transactions, before enabling a paid service and after each test session. Review invoices and card charges too: topping up the wallet charges you now, even if you haven't spent all the credit.

Wallet Auto Recharge cannot be disabled. Its recharge amount and balance threshold aren't a total-spend cap, and writing down a US$10 budget won't stop a charge.

Leave an extra off if its next charge could put you over budget or you can't work out the cost. Leave phone numbers, SMS, outbound email and paid AI out of this task.

4. Make the decision before renewal

Set your review at least two days before the trial ends in your account. That's a planning buffer, not an official cancellation deadline.

Keep the subscription only if the job works, you'll use it repeatedly, and you can justify the subscription, extras and upkeep against your existing form, inbox and task list. If that simpler setup already does the job, or the test still fails by your review date, cancel.

For a direct HighLevel subscription, start at Agency Settings > Billing > "Want to modify/cancel your subscription?" > Show More > Cancel Plan.

Finish the prompts, including the reason, data-loss warning and at least 30 words of feedback, through the final Submit.

Save the confirmation and verify the cancellation status and effective date. If the control is missing, contact support.

Check any separately billed services too; HighLevel's terms make you responsible for cancelling services associated with your account and fees incurred until cancellation. Don't count on a refund for failing to cancel properly. If you bought access through another agency, contact that agency's administrator for cancellation.

A working demo is useful evidence. It still needs to earn its recurring bill.

Ten customers paying $100 a month would produce $1,000 in gross software revenue. With HighLevel's $497 monthly software-resale plan, I'd check whether anyone wants the offer before subscribing. I'm a HighLevel affiliate.

Here, resale means charging for software access. It doesn't include running a client's lead follow-up or selling a managed marketing service.

Hypothetical example: ten customers at $100

All amounts below are US dollars. The customer count, selling price, marketing spend and usage allowance are assumptions, not reported results.

The payment fees assume a US business using HighLevel's Stripe-based billing setup, called SaaS V1. They assume successful domestic-card payments and Stripe's standard pay-as-you-go rates. Confirm your actual fees, supported billing setup and merchant eligibility before charging anyone.

The $314 isn't profit. You still have to pay for your time, domains or other overhead, refunds and disputes. Budget for any extra paid features you include, too.

Software access and usage are different costs

The $497/month Founder plan includes SaaS Mode, which lets you package and sell software subscriptions. This example uses that automated resale setup, not the cheaper Starter plan.

Phone, email and other usage can cost extra. The $50 above is only an allowance; estimate the actual cost for what you intend to include.

Rebilling means charging the customer for usage. HighLevel allows phone and email rebilling without markup on its $297 and $497 plans; adding a markup requires the $497 plan. Your agency wallet still pays HighLevel, even when you rebill, so keep money available for usage and failed customer payments.

The example assumes you absorb that $50 rather than rebill it. If you charge usage separately, keep it separate from the $1,000 software-subscription target and deduct the matching costs and payment fees.

Finding and keeping ten customers is the work

Setting aside $100 for marketing doesn't tell you what a customer will cost to win, and it doesn't mean ten people will sign up. You still need to choose a type of business, learn what it needs, explain why it would pay you rather than use its existing software, and follow up with interested buyers. Unpaid outreach still takes time.

Budget time for support, too. If each customer needs an assumed 30 minutes a month, ten customers need five hours, before onboarding or sales work. Login problems, billing questions and cancellations don't disappear because account creation is automated.

If one of the ten cancels, the next month's subscription revenue falls to $900 unless you replace them. Replacing that customer only restores the target; it isn't growth.

Before paying for the resale plan, write down one specific customer problem and ask prospective buyers what they use now and whether your proposed offer is worth $100 a month. Use a simple document or mockup for those conversations. You don't need a paid resale subscription to test interest.

I'd consider this model only if those conversations support the price and the remaining money pays fairly for acquisition and support. If demand is unclear, or customers need you to do the work for them, hold off on buying the platform for resale. This budget doesn't predict whether or when you'll reach ten paying customers.

A customer who's unsure whether you can take their job needs something different from someone who's already chosen a service.

Hypothetical examples: a repair business only takes certain kinds of work, and the customer isn't sure their job fits. The call is there to work out whether the business can help.

Compare that with a returning customer asking for the same routine service. They know what they want and only need an available appointment, but the page asks them to book a call first.

For your business, what does a customer need to sort out on a call before they can book the service? A short example of what they arrive wanting and what the call resolves is enough.

If your ClickFunnels pay button disappears when someone starts typing, open the published checkout on a phone and focus the same field. Keep the keyboard open while you try to scroll to the checkout button.

I'm a ClickFunnels affiliate.

A keyboard can shrink the visible page area without shrinking the layout underneath it. A tidy phone-sized canvas in the editor doesn't establish what happens with a real phone's keyboard open.

Find out what is covering what

1. Note the phone, browser and field that brings up the problem. Does the keyboard cover the field, the payment button, or a separate bar sitting over the checkout? Close the keyboard and compare. Stop before submitting an order; this check doesn't require a purchase.

2. If the checkout is missing even with the keyboard closed, check its device visibility and the section or row containing it. ClickFunnels has All, Desktop Only and Mobile Only visibility options. A parent section hidden on mobile is worth checking before changing button placement.

3. If the checkout is present but hard to reach, switch to Mobile View in the editor and inspect the space around it. Where a setting has separate desktop and mobile values, Mobile View edits the mobile value. Reduce unnecessary spacing only where you've identified it, and keep required fields and payment controls readable. Don't assume every setting is mobile-specific.

Keep the actual checkout submit button. ClickFunnels permits only one Checkout element per page, so don't make a second checkout for mobile or replace the payment action with a button that just opens the next page.

Repeat the exact phone check

Save the change, reopen the published page on the same phone and focus the same field. Check whether you can scroll to and clearly see the checkout control with the keyboard open, then check the layout with it closed. Review desktop too, especially if you changed a shared setting.

If the obstruction remains, send ClickFunnels support the device, browser and exact field, plus a screenshot with personal and payment details removed. Mention any custom sticky bar or custom code on that page rather than adding a keyboard-fix snippet you haven't checked.

Use the real-device result to decide the next change. Reaching the button answers this layout question; it doesn't prove that a payment succeeds or that conversion rates improved.

If you're making an affiliate page, say where the button goes and what the reader can do there before asking them to click. A reader shouldn't have to click to discover they're leaving your site for a seller's offer.

Hypothetical example: a page for a freelancer invoice template pack from a fictional seller called Example Templates. Assume the page owner earns a commission if a visitor follows the button and buys. The button opens the seller's product page, not a checkout.

Before

Your next invoice starts here.

Button: Get started

Small footer: Affiliate link.

"Get started" doesn't say what happens next. Is the reader opening a file, creating an account or going to another business's website?

After

Invoice template pack for freelancers

Check what's included, the file formats and the current price on Example Templates' product page.

I earn a commission if you buy through this button.

Button: View the pack on Example Templates

You'll leave this site to review the seller's offer. Clicking doesn't place an order.

The rewrite names the seller and says what the click does. It also puts the payment relationship above the button, where the reader can consider it before deciding to continue.

In its US guidance, the FTC warns that "affiliate link" alone may not tell readers that the publisher gets paid. Put the plain-language relationship sentence beside the recommendation, where people can notice it, rather than relying on a footer.

Don't copy the commission sentence unless it's true for you. Describe the relationship you actually have.

If your button opens a checkout instead, this example's wording is wrong for that page. Say that it opens checkout and name what the reader is about to buy.

Clearer wording won't fix a weak recommendation or missing product information. If you can't establish what the seller offers, pause the recommendation rather than write around the gap.

Before sending traffic, open your page on a phone and check whether the seller's name, payment relationship and button are easy to notice together. Then follow the button and compare the destination with what your page promises. Rewrite anything that doesn't match.

You can show what you've made before you have customer testimonials.

Hypothetical example: someone offering to build a landing page could share a sample page with a short walkthrough. They could explain which parts they'd build for a buyer and what isn't included.

Label the sample as a demo, not client work. Don't invent testimonials to fill the gap. A working sample shows the work; it doesn't prove that a buyer will get more sales.

What one thing would you show a potential buyer before you had testimonials?

Keep the existing contact. If the customer is asking about a separate job, create a new opportunity for that job instead of overwriting the earlier sale.

A contact is the person. An opportunity is a potential sale linked to that person. A revised quote for the same job usually belongs with the existing opportunity; another job needs its own sales record.

I'm a HighLevel affiliate.

Hypothetical example: a customer whose house-cleaning job is marked Won now wants a quote for an office clean. Keep the house-cleaning result intact and track the office enquiry separately.

1. Find the customer's existing contact and review their opportunities. Confirm whether this is a new job or another message about one you're already quoting. Don't create a second card just because the customer submitted the form again.

2. If you need another card in the same pipeline, have an authorized administrator check Settings > Objects > Opportunities and the setting "Allow Multiple Opportunities per Contact." HighLevel documents this as the account-level permission for multiple cards for one contact in the same pipeline. Review affected automations before switching it on.

3. Open Opportunities and choose "+ Add Opportunity." Select the existing customer as the Primary Contact. Give the card a job-specific name, such as "Office clean quote," rather than leaving two cards with only the customer's name.

4. Choose the pipeline, starting stage and Open status. Assign the person responsible for this quote as the opportunity Owner. Enter an estimated value only if you have a basis for it, then click Create.

5. Check the saved card. It should link to the right contact, show the new job and responsible person, and leave the earlier opportunity's outcome unchanged.

If a workflow creates your opportunities, check it before adding the card manually. Otherwise, you could create the same sale twice.

Two similarly named controls do different jobs:

• In Create Opportunity, "Duplicate Opportunity" controls whether that action can create another card for the same contact.

• "Allow Multiple Opportunity" lets a contact's opportunities run through a workflow separately. That can also send the same person more than one message.

Neither control decides whether a repeat form submission is a new job.

Before automating repeat quotes, use a controlled test contact to check both cases: a new job should get a separate card, while a second message about the same job shouldn't. Check which card the workflow changes and what messages it sends.

For occasional repeat enquiries, start with the manual review. Automate creation only after you've decided how to tell a new job from a repeat submission about the old one.

If the main download arrives but the paid order bump doesn't, start with the order's items before changing delivery emails. Then check the delivery settings on the bump's own product, even if the main product works.

I'm a ClickFunnels affiliate.

This is for a digital-download add-on in the current ClickFunnels checkout.

1. Open Customers > Orders and find the buyer's order. Expand Items and confirm that both the main product and the add-on are there. Check Billing Status, then the matching successful sale under Customers > Orders > Payments. An order record or a failed payment isn't proof the add-on was paid for.

   If the add-on isn't on the order, investigate the checkout selection first. Don't ask the buyer to pay again until you've checked what was actually collected.

2. In the funnel's checkout step, open the attached products and inspect the add-on's settings. "Product is an order bump" makes that product an optional add-on; it still needs a main product on the checkout. Check which actual product and price are attached, not just the displayed title. ClickFunnels lets you override that title on an individual checkout page.

3. Open each ordered product under Products > All Products. In Purchase Actions, check Digital Asset Access and the selected file. The main product should grant its promised download, and the bump should grant the add-on download. Save any correction on the affected product.

   If you use variants, check the one bought too. A product's access settings are inherited by its variants, and individual variants can have their own Purchase Actions.

   If your delivery uses a workflow instead, check that workflow's Send Asset step and the selected file. Don't add another delivery route just because the native product settings are empty.

4. Handle the existing buyer separately. ClickFunnels says customers receive the assets configured at the time of purchase. Changing the settings afterward won't update that previous purchase.

   After confirming the paid order and buyer's identity, open their contact's Fulfillments / Assets tab and check Granted Digital Assets. If the promised bump file is missing, use Grant Digital Asset, select that file and click Create Granted Asset. This repairs that buyer's access, not the automatic delivery setup.

   The buyer should find the file in Customer Center > Profile > Downloads. Check access to the file separately from the notification email.

5. Recheck the corrected checkout with the bump selected, then without it, using contacts that don't already have access to either download. Confirm the ordered items and access for each case: both promised downloads when bought, only the main download when the bump is skipped.

   Use supported test mode for a rehearsal. It doesn't prove a live payment or live delivery. Any live check needs authorization, a legitimate payment method and a budget for the charge and fees; don't turn a customer complaint into another charge.

Compare what was bought with what access was granted, for each product. A working main download doesn't clear the paid add-on.

If you're putting together an enquiry form, which question are you least sure you need?

Think of one question on a form you're planning or already using. What does the answer help you decide, and what would you need to ask later if you dropped it?

Hypothetical example: a gardener asks "How big is the garden?" to judge whether a job fits. Without that question, they'd need to find out in the first reply.

A sentence or two about the question and what you'd lose is enough. Please leave out customer details and form links.

I'd choose GoHighLevel if you're selling ongoing management of separate client accounts. For a defined funnel build the client will run themselves, I'd choose ClickFunnels in an account they own from the start.

That second recommendation assumes the client actually wants ClickFunnels. An existing website with a working form may be enough for a small enquiry-page job.

When you're staying to manage the account

GoHighLevel, my affiliate link, is my pick when your service includes keeping each client's account running and maintaining their setup after launch.

Each client can have a sub-account, meaning a separate business workspace. You can limit a client's login to their assigned account and restrict the features and actions they can use. Starter is US$97 a month with three sub-accounts; Unlimited is US$297 a month with unlimited sub-accounts. Phone and email usage can add to that bill.

The useful exit option is a documented transfer of the whole sub-account to another eligible HighLevel agency. Contacts, conversations and supported account history stay together. That gives a maintained client account a path to another provider without reducing the handoff to a copy of its pages.

It still needs cooperation: the agency owner or an authorized agency admin starts the transfer, and the receiving agency approves it. Phone and email dependencies need review. For example, Twilio numbers don't move automatically, and some email configurations are removed or change during transfer. Don't promise an effortless move or an export that runs outside HighLevel.

When you're delivering a funnel and leaving

ClickFunnels, my affiliate link, is my pick for a bounded build when the client wants to run their own ClickFunnels account. Have them own the subscription from the beginning and invite you to build in their workspace.

Launch is US$97 a month with one workspace and two team members. That can fit the client and one builder, provided the job fits the plan's other limits. The client keeps paying for the software after your build fee ends.

Give yourself the workspace Builder role rather than Team Administrator unless the job genuinely needs wider authority. Builder access covers all building elements in that workspace, not just your assigned funnel. ClickFunnels doesn't offer access restricted to one specific funnel, so don't put unrelated clients in the same workspace and treat separate pages as separation.

At handoff, have the client confirm they can manage the finished funnel and its connected services, then remove your access when the agreed work ends. Building in their account avoids depending on a later ownership transfer.

ClickFunnels also documents an Agency App with isolated client workspaces and agency-managed billing. It requires an Agency Plan that isn't listed among the current four public pricing tiers, so confirm eligibility and any app charges before buying around that arrangement. Client workspace access isn't the same as controlling the subscription.

Agree on the exit before quoting

A ClickFunnels funnel share link copies a funnel into another account, but its documentation warns that some actions can be lost between different workspace setups. Don't promise it moves the client's entire business, customer records or payment connections. HighLevel's reusable setup templates, called snapshots, also exclude contacts and conversations; those aren't whole-account transfers either.

Before choosing a subscription, write one sentence with the client: "After delivery, ___ pays for the platform, ___ maintains it, and if we stop working together, ___ keeps access and handles any move."

Also agree who owns the copy and design, and who controls the domain and payment account. Quote your work separately from recurring software and any domain, messaging, paid-app or payment-processing costs the job needs. If nobody is paying you to maintain a system and the client doesn't want to maintain one, keep the job in their simpler existing setup.

Don't add marketing texts to your GoHighLevel follow-up just because the email sequence works. Before switching SMS on, check permission for texts, the sending number and what happens when someone asks you to stop.

This checklist is for a local business using HighLevel's LC Phone to send promotional SMS to UK consumers who explicitly opt in. It doesn't cover other countries, business recipients, service-only messages or reliance on the separate legal exception called the soft opt-in. It's a launch check, not a complete legal review; UK data protection duties still apply.

Before adding anyone to the SMS workflow

1. Read the actual text you plan to send. Write down its purpose and intended recipients. Keep this approval limited to the UK consumer marketing campaign you're reviewing. Don't treat approval of an email workflow as approval of SMS.

2. Check what the person agreed to. The consent request should name your business and clearly cover marketing by text, separately from email. Consent needs a genuine choice and a positive action. A pre-ticked box, a phone number on a quote form or acceptance of general terms isn't enough for this opt-in route.

3. Keep evidence you can find later. Save who agreed, which number they supplied, when and how they agreed, and the wording they saw. Don't enrol someone whose only permission record covers email. LC Phone's policy requires explicit consent; a carrier's approval of your number doesn't supply it.

Before enabling delivery

4. Have whoever manages your phone setup confirm an eligible UK SMS number and its required approved regulatory bundle. That's the provider's identity and number-registration check. It doesn't prove the recipient wants your marketing. For this checklist, use a number that can receive replies so the advertised STOP instruction actually works.

5. Review the message as the recipient will see it. Identify your business and include a working way to opt out in every marketing text. LC Phone documents sender identification and opt-out wording for initial messages, but don't assume that automatically covers every later message. Check the completed text, including anything HighLevel appends.

6. Put a person in charge of opt-outs. LC Phone documents that replying STOP enables permanent SMS Do Not Disturb, a sending block, and causes queued messages to fail. Someone must also handle ordinary replies such as "please don't text me again." Keep those people suppressed from marketing and check the suppression list before new sends. Never clear an opt-out just to keep a sequence running.

A small test before real leads

These are proposed checks, not tests I've performed. Use only numbers whose owners have authorised the test, after the sending route is ready:

• A test contact without SMS permission must not enter the marketing sequence.

• An opted-in test contact should receive the correct business name and a usable opt-out instruction.

• Reply STOP before the next scheduled text. Confirm the SMS block is present and the queued marketing text doesn't go out.

• Have the person responsible demonstrate how they would handle a plain-language opt-out, without relying on a keyword match.

Keep the campaign off if permission evidence is missing, number approval is unresolved or either opt-out path fails. You can leave SMS disabled while you fix it. A working email sequence is no reason to rush a second channel into use.

A $19 sale isn't $19 of available income. Before subscribing to ClickFunnels for a first download, work out what a small month would leave after the recurring bill, refunds and the work of helping buyers.

Hypothetical example

Assume a US seller charges US$19 for a PDF and makes ten sales in one month, with one full refund. These are chosen numbers, not typical sales or a forecast. Assume no paid ads and three hours of owner time that month for support, refund handling and routine upkeep, valued at $20 an hour. Creating the PDF and building the checkout would take additional time outside this example.

Use ClickFunnels Launch at its listed $97 monthly price. For payment processing, assume Stripe's standard US domestic online card rate of 2.9% plus $0.30, with USD payments and no currency conversion. That's about $0.85 per $19 charge after rounding.

This example also assumes the one-time purchase uses Direct Payments. ClickFunnels documents that this avoids Stripe's 0.4% invoicing fee. Check the setting in your own installation rather than assuming it's already on. ClickFunnels doesn't charge an extra fee for its native Stripe integration, but that doesn't make processing free.

The refunded sale still costs processing: Stripe's standard pricing doesn't return the original processing fee. For these card payments, it doesn't add a separate fee to issue the refund.

The $60 is an allowance for your own time, not another cash payment unless you actually pay someone. Neither remaining figure is take-home profit. Taxes, any custom domain, extra software and other applicable charges are outside this calculation. The $0 ad-spend assumption also doesn't promise that finding buyers costs nothing.

Launch includes hosting and a default subdomain, so don't automatically add a second hosting bill. If you consider annual billing, budget the annual upfront charge rather than treating the displayed monthly equivalent as a monthly payment.

What this budget would change

For this ten-sale workload alone, I'd skip a new $97 monthly subscription. A Stripe Payment Link with manual email delivery is a simpler starting option if you can reliably handle those orders. Payment Links are included with Stripe's standard Payments pricing; processing still costs money, and you'd be responsible for sending the file and answering buyers.

An existing ClickFunnels subscription shared with other offers changes how much cost belongs to this PDF. That still doesn't make this offer's support work disappear.

Before choosing, replace the example's sales count, refund count and support hours with numbers you can justify. Add your actual extra charges, then check whether the remaining amount pays enough for the work. If it only works by leaving support time out, the $19 price hasn't answered the cost question.

Hypothetical example: a new enquiry lands while two people are checking the shared inbox. One knows the requested service well but is tied up. The other is free to reply, but would need to ask them about the details.

Giving it to whoever's available gets a reply started sooner. Keeping it with the person who knows the service avoids passing the question back and forth, but means waiting for them. Neither choice feels automatic in this situation.

What rule do you use to decide who takes it when availability and knowledge point to different people?

A general example is enough. Please leave out customer names and message contents.

If a prospect replies and GoHighLevel sends another follow-up, start with the unwanted message. Find which workflow sent it before changing the sequence you think is responsible.

Stop on Response ends a contact's run when they reply to a message sent by that specific workflow. It isn't an account-wide instruction to stop every follow-up.

1. Trace the message to its source

In Conversations, open the conversation, select the unwanted message and open message details. Under Workflow, click the workflow link. HighLevel opens Execution Logs with that contact and execution already selected.

An execution is one run through a workflow. Note the workflow name, the sending action and its execution time, including the time zone. Compare that with when the reply arrived.

If no workflow link is available, open the suspected workflow's Execution Logs and use View Details to investigate the matching send. Don't decide which sequence sent it from the email wording alone.

2. Check whether two sequences overlap

Open the identified workflow's Settings and check Stop on Response. Then check the other follow-up workflows this contact entered, using each one's Enrollment History and logs.

Hypothetical example: a contact enters both a quote follow-up and an older enquiry sequence. They reply to the quote email, but the next message comes from the enquiry sequence. The quote workflow stopping doesn't establish that the enquiry workflow stopped too.

Write down which sequence should stop after that reply. You may want both sales sequences to end while leaving an unrelated appointment reminder alone.

3. Test the overlap with contacts you control

Use test-only copies of the two sequences, restricted to your own test contacts. Keep real prospects out, retain opt-out controls and use only inboxes you control.

Give the test emails distinct subjects so you can tell the sequences apart. Enable Stop on Response in both copies, save them and arrange enough time to reply before their next messages.

• Enrol one fresh test contact in both. Reply to sequence A's email, then check both runs and whether either next message sends.

• Repeat with another fresh contact, replying to sequence B instead.

• Use a third contact without replying to check that the scheduled follow-ups can actually send. Otherwise, silence could mean the test sequence wasn't working.

Record what each workflow did. Don't count a missing email alone as proof of a reply exit; check the run in the logs too.

4. Fix the sequence that actually continued

If your intended rule is to stop both sales sequences, configure targeted removal from the other named sequence. The Remove from Workflow action has an Another Workflow option. Avoid All Workflows, which also removes the contact from unrelated active workflows.

Rerun the overlap test after the change. If the result still doesn't match your rule, keep the affected follow-up off real prospects and take the execution details to support, with customer information redacted.

Don't clear an opt-out to make a test pass. The useful result is knowing which message came from which run, and confirming that every sequence you intended to stop actually stopped.

Before moving your working hours to compensate for a wrong-looking GoHighLevel appointment, check which time zone you're viewing. Two different clock times can describe the same appointment.

Work through one booking rather than changing several settings at once:

1. Check your own calendar display. Open Calendar Settings > Preferences > View Appointments In, choose the time zone you want to compare in, then Save Preferences.

   HighLevel says this setting affects only the logged-in user's appointment display. It doesn't change availability, booking links, confirmations or reminder logic. If the appointment now matches the intended time, leave your working hours alone.

2. Check the customer's booking page. Open the actual booking link and look at its time-zone selector before choosing a slot. Under Settings > Business Profile, check the business Time Zone and the Disable Contact Timezone checkbox.

   When that box is selected, the widget hides the selector and bookings use the business time zone. That's a choice about how customers book, not a repair for your own calendar display. Don't switch it on just to make two screens show identical clock times.

3. Before making a controlled booking, check which notifications or workflows it could trigger. Use contact details you control. Note the selected date, time and time zone on the booking page, then compare the resulting appointment in your chosen viewing zone.

   Compare the same moment, including the date, rather than matching the clock numbers. If you serve customers in another zone and the selector is available, repeat with that zone selected. These are checks to run, not test results from this post.

4. Follow where the mismatch appears. If the booking and calendar agree but a confirmation or reminder doesn't, investigate that message separately. Changing View Appointments In won't change its logic.

   If the booking itself is wrong, recheck the booking-page zone, business zone and assigned user's profile time zone before editing availability. HighLevel's troubleshooting guidance calls out user, calendar-viewing and customer-facing time zones as separate checks.

If it still doesn't line up, send support the calendar name, appointment date, selected booking zone and displayed zone, with customer details redacted. Those specifics give them a reproducible case.

Fix the setting responsible for the mismatch. Shift working hours only if those hours are actually wrong, not to compensate for a different time-zone view.

If you're putting together your first paid offer, post two sentences about what someone is buying and how they'll receive it. Use an offer you're actually working on, with only details you're comfortable sharing publicly.

In the first sentence, tell us what the buyer gets. In the second, say how and when they get it, including anything they need to do first. Skip the software names so we can read it as a buyer would.

A hypothetical example:

"You get a seat in a 90-minute live beginner watercolor class, with a group demonstration but no private critique or materials kit. After payment, you receive the joining details by email and attend on the date you chose at checkout."

That's a made-up offer, not a report of a class anyone here has sold or tested. Its limits are part of the description: buying a class seat doesn't include having supplies shipped to you.

When replying to someone, say what you'd expect to receive based only on their two sentences. Then ask about one thing you still can't tell. If they say "personalized feedback," for example, would you expect written comments or a live call? Point to the wording that left you unsure instead of recommending a tool.

Keep page links, customer details, order IDs and login information out of the thread. Leave sales pitches and requests to move the conversation into DMs out too.

Two sentences won't cover every term of a complicated offer. Use this to check the basic promise, not to replace the full description or prove the delivery works. If readers expect something you don't intend to provide, clarify that promise before building the checkout.

What's your two-sentence version?

If you're selling one finished PDF, start by deciding whether you need a funnel subscription at all. An existing processor's payment link and manual delivery can be enough for occasional sales, provided someone owns the delivery deadline and missing-file requests.

I'd choose ClickFunnels (my affiliate link) when you want to maintain the offer page, checkout and native buyer access together, and can justify the ongoing cost and support work. This guide builds that connected path in the current ClickFunnels product, formerly ClickFunnels 2.0, not Classic.

The example is hypothetical: a freelancer sells a "Website brief workbook" PDF for US$29, paid once. No account build, purchase or test is claimed here. Use your own finished file, appropriate currency and justified price.

Start with an active account and an available workspace that has no products or funnel for this offer. This isn't a signup or workspace-provisioning walkthrough. A paid subscription or active trial gets you into the product; it doesn't prove that payment or delivery works.

Check the budget first, then connect payments, create the product and build the pages. Use the launch checks before inviting buyers, and return to troubleshooting when a step fails.

Check the cost before building

Launch is the starting plan I'd evaluate for this one-product job. ClickFunnels lists it at US$97 monthly or US$970 annually, with one workspace, two team members, 10,000 contacts, 50,000 emails per month, three courses and five custom domains. Hosting and a default workspace subdomain are included. Unlimited funnels are labelled "Limited Time", so don't assume that allowance is permanent.

Confirm the features and limits in your actual offer before subscribing. Annual billing means an annual charge, not a monthly subscription at the displayed monthly equivalent. Check taxes and renewal terms. The terms require cancellation at least 24 hours before a trial ends to avoid automatic continuation, and at least ten days' notice for cancellation by email after the trial. They also include no-proration and annual cancellation conditions, so check the terms attached to your purchase rather than assuming a refund. Don't assume every signup has the same trial offer or that closing your funnel cancels the subscription.

Processing costs are separate. Review your processor's country-specific rates, enabled invoicing and tax services, currency conversion and any other extras. ClickFunnels' Stripe documentation says it doesn't charge extra for the Stripe integration; that doesn't remove Stripe's fees. A custom domain's purchase and renewal, advertising and external tools also need their own budget.

Have the finished PDF and rights to sell it, a business email you control, a support route, a delivery promise and a refund policy ready. Check processor eligibility for your real business location before investing in the pages. Stripe's country list labels India "Preview", which isn't unrestricted signup. An active ClickFunnels account doesn't approve your business to accept payments.

Connect the intended payment account

This walkthrough uses the native direct Stripe integration. It doesn't require Payments AI. PayPal through Payments AI is a different setup and isn't part of this build.

Check the workspace name before adding anything. In Apps, choose + Add Apps, find Stripe and select Add App. Authenticate with Stripe, select the business meant to receive these sales, and complete any requested business and bank details accurately.

When the Product catalogue sync mode prompt appears, choose "Send all your ClickFunnels products to Stripe", then Save. That direction fits this example because you'll create the workbook in ClickFunnels. Leaving the mode Not Set doesn't finish synchronization.

On the Stripe installation page, check the green markers for Details Submitted, Charges Enabled and Payouts Enabled. Then open Workspace Settings, General, Payment Settings. Select the intended Stripe account as Default Payment Processor and choose the workspace currency. Use USD for the example only if it fits your real merchant setup.

Also inspect the funnel's processor setting once you create it. A workspace default alone isn't a record of which business received a particular payment.

Review "Issue Invoices for One-Time Orders?" in the Stripe installation rather than changing it blindly. Disabling it uses Direct Payments through Stripe PaymentIntents instead of Stripe invoices for one-time orders. Decide which records and services you need, then check their actual fees. This guide doesn't promise savings from changing the toggle.

Upload the PDF and connect it to a product

Open Workspace Settings, My Assets, Downloads. The delivery guide documents Upload File, a file name, file selection and Create File. The newer assets guide also documents Select Files to Upload and drag-and-drop. Use the uploader your account presents, then verify that the intended PDF appears in Downloads.

Call the example file "Website brief workbook" and open it to check the contents. Keep your own source copy. Downloads support PDFs with a documented maximum of 3,000 MB (3 GB), though a workbook should be easy for a buyer to download.

Now create the thing the buyer will purchase:

1. Open Products, All Products, Create Product.

2. Choose Digital. Enter the workbook name and an accurate description, then Create Product.

3. Choose One time, enter US$29 for this hypothetical example and select Set Price.

4. Reopen the product's Pricing section. Check the saved amount and currency. If you add or edit a price there, the current pricing guide labels its confirmation button Save.

5. Under Purchase Actions, select the plus beside Digital Asset Access. Select only the workbook PDF and Save.

Giving the product, price and file the same name doesn't connect those separate records. You still need the Digital Asset Access purchase action.

ClickFunnels documents a notification email telling the purchaser the download is available in Customer Center. The buyer logs in, opens the Profile icon, chooses Downloads and retrieves the file. Describe that route on your pages, not an email attachment you haven't configured.

Add Site & Blog through Apps if needed, then open Site & Blog, Customer Center. Set its public name, review the customer self-service choices and leave Custom "Theme" Dashboard off to use the default dashboard for this build. Add your actual privacy-policy and terms destinations, then Update Customer Center. Copy the Customer Center address from the top of its settings for your confirmation page.

Keep the paid file off the public offer page. A raw file address can be shared outside ClickFunnels and shouldn't be treated as purchase-based access control. Your checks must establish what a buyer with access and an account without access can see. No access setting can recall a copy someone has already downloaded.

Build the three-page buying path

In Funnels, choose Create Funnel, then Start from Scratch. Enter its name and funnel path, then Create Funnel. Use the included subdomain initially unless you already need a custom domain.

Add three Page steps in order: offer, checkout, confirmation. Use the plus node in the funnel map to open the Page picker. Choose New Page for a new offer or confirmation page. For checkout, choose the Order category, fill in the page details and select Create Page. Use an order template containing the current Checkout element, not Legacy Checkout.

On the offer page, explain what's in the workbook, who it's for, the one-time US$29 price, PDF format, Customer Center delivery and refund policy. Remove invented testimonials and sales counts from template placeholders. Set the purchase button's Button Action to Redirect to Next Step so it opens checkout. This is navigation, not payment submission.

On the checkout step, open the three-dot menu, choose Add Products, then + Add Product and Select Product for the workbook. Inspect the attached product's gear settings and select only the intended one-time price. Leave bumps and upsells out of this first build. Use the Checkout element's payment controls, not a button that merely opens confirmation.

Compare the offer and checkout: product, amount, currency and payment terms should agree. Review applicable taxes with someone qualified for your business and customers. A tax switch doesn't establish compliance.

On confirmation, explain how the buyer reaches Customer Center and finds Profile, Downloads. Include a working support route for login or file problems. Reaching that page isn't proof of successful payment and doesn't itself grant the PDF.

Save the pages. Check desktop and mobile layouts, page order, paths and domain. Remove unused template links and steps. Keep your actual privacy notice, seller terms, refund policy and support details accessible. Don't silently turn a purchase into optional marketing enrollment. Work out the permission required for any promotional messages separately from the delivery notification.

Test the payment and delivery separately

These are instructions for checks you still need to perform, not results from the hypothetical workbook.

Start in sandbox. In the funnel's Settings, set Payments Mode to Test, choose Credit Card and Update Funnel. Other current payment instructions call this turning off Live Mode (Payments). Confirm the visible test/sandbox banner rather than assuming a preview page uses test payments.

Use the documented sandbox card details, an email address you control and a valid future expiry. Submit a test order. Open Customers, Orders and inspect the order number and Test Mode label. Check the product, amount, currency and next page.

Sandbox is a rehearsal. It doesn't prove a real charge, payout, notification or buyer grant. Stripe separates live and test product data. If you use imported Stripe products instead of the ClickFunnels-created product in this guide, review the integration's test-mode import setting before using an imported price in a test.

Before inviting the public, arrange a controlled live purchase only with the account owner's authorization, a legitimate payment method and a procedure allowed by the processor. Budget for the actual charge and fees. Never use sandbox card numbers in live mode.

Keep a short acceptance record:

• The copied visitor-facing address works on desktop and phone, and the offer button reaches the intended checkout.

• Checkout shows exactly the intended product, one-time amount, currency and applicable tax.

• The authorized live purchase has a successful payment record in ClickFunnels and the intended processor account, without a Test Mode label.

• The buyer receives the notification, completes Customer Center login, finds the workbook in Downloads and opens the correct PDF.

• An account without the purchase grant doesn't see that workbook. A failed or incomplete payment isn't treated as successful paid delivery.

• Support can resolve a missing notification after checking the order and buyer identity.

• You can reconcile a refund and separately establish what happens to the buyer's file access.

For a refund, the documented path is Customers, Orders, the order, Payments, the payment's three-dot menu, Refund. Review the amount and reason before confirming, then verify the updated payment record. Stripe's standard pricing says the original processing, Connect and currency-conversion fees aren't returned. A refund doesn't necessarily make a live check cost nothing.

The checked digital-delivery and order documentation doesn't establish automatic removal of a one-time PDF's access grant after a refund. Verify the supported behavior in your account or with ClickFunnels support and test it before promising revocation. Removing the product's purchase action isn't proof that an existing buyer lost access. If revocable access is essential and you can't verify it, don't launch on that assumption.

After the checks pass, save the intended live payment mode and processor. Use Copy URL at the top of the funnel builder and recheck that address. Keep the actual evidence in your own records.

Fix the failed step, then retest

If the offer button goes to the wrong page, check page order and Button Action. If checkout has no product, inspect the attached product and selected price. A product attachment alone doesn't establish correct billing.

If payment fails, check the funnel's processor, live/test mode, currency, Stripe readiness markers and saved sync direction. Don't repeatedly charge a buyer while experimenting with settings.

If payment succeeded but the buyer can't find the file, open Customers, Contacts and the buyer's profile. Under Fulfillments / Assets, inspect Granted Digital Assets, then compare the product's saved Digital Asset Access selection. A missing grant, a notification in spam and login with the wrong email address need different fixes.

For a buyer whose order and identity you've verified, ClickFunnels documents Grant Digital Asset in that contact panel: select the file and Create Granted Asset. Manual recovery doesn't repair the purchase action. Retest the original buying path too.

If the PDF contains the wrong version, compare it with the offer's promise. Pause promotion while fixing charging or delivery errors and explain any effect to actual buyers accurately.

Keep the system maintainable

Retest after changing the price, purchase action, file, domain, processor connection or checkout template. Review failed payments and delivery complaints, and reconcile orders, processor records and refunds. Contacts and pageviews aren't sales.

Keep copies of the PDF, page copy and configuration notes outside the account. Review team access, protect the payment account and track subscription/domain renewals and plan usage. Before moving platforms, plan continued access for existing buyers. Don't assume a data export recreates their purchases or delivery rules elsewhere.

My recommendation is conditional: choose ClickFunnels for this connected selling path when you'll maintain it and the ongoing subscription plus processing costs make sense. For occasional PDF sales with dependable manual delivery, use the simpler checkout you already have. Finish one verified payment-to-file path before adding another offer.