A Kyndra Technologies Company

Kyndra Client Onboarding Checklist

From the day the agreement is signed to the first results in your pipeline — the complete process we use to set up your Kyndra CRM on HighLevel, launch your first automations, and keep the partnership on track.

⚡ What this checklist covers

The first weeks of a new engagement decide whether a client feels looked after — or left waiting. When onboarding is done well, it sets clear expectations, builds trust, and puts the operational foundation in place for a long partnership. When it is rushed or vague, it creates confusion and early friction, and that doubt is hard to undo even after the work itself is solid.

This is Kyndra’s complete client onboarding checklist for HighLevel (GoHighLevel). It walks through every phase from a signed agreement to first-result delivery: creating your HighLevel sub-account, deploying the Kyndra Client Starter Snapshot, connecting email, phone, calendars and lead sources, configuring access, running the kick-off call, launching the first automations, reviewing results at day 30, and the retention system that keeps the relationship active after the setup sprint is over.

Most clients who leave in the first 90 days do not leave because the CRM failed. They leave because the onboarding experience created doubt before results had time to show up. A client who signs, then waits a week for login access, gets a generic welcome note, and does not sit down with us until week two has already started asking whether they made the right decision. Onboarding is the first proof of how we work — and it becomes the frame through which everything after it is judged.

HighLevel’s sub-account architecture and Snapshot system let us deliver a setup that feels tailored, even when much of the work is systematized. This checklist is the process itself: what we do, in what order, what can run automatically, and where a real conversation still matters.

Onboarding timeline: what happens when

Phase Timeframe Who does it Primary outcome
Phase 1 — Pre-onboarding Day 0 (agreement signed) Kyndra (automated + our team) Sub-account created, welcome sequence launched, intake form sent
Phase 2 — Technical setup Days 1–3 Kyndra Integrations connected, Snapshot deployed, CRM configured
Phase 3 — Access & kick-off Days 3–5 Kyndra + you Dashboard access granted, kick-off call completed, expectations set
Phase 4 — First campaign launch Days 5–14 Kyndra First automations live, first leads entering the pipeline
Phase 5 — 30-day check-in Day 30 Kyndra + you First results reviewed, adjustments agreed, month 2 plan confirmed
Phase 6 — Ongoing retention Monthly Kyndra (largely automated) Regular reporting, continued engagement, a clear path forward

💡 The 72-hour rule: The most important onboarding principle we hold is this: you should have a concrete first deliverable — dashboard access, a live automation, or the kick-off call — within 72 hours of signing. When more than three days pass with no visible progress, confidence dips, and that dip is difficult to recover from even when the later work is excellent.

Phase 1: Pre-onboarding checklist (Day 0)

1

Create your HighLevel sub-account

Agency dashboard → Sub-Accounts → Add Sub-Account

⏱ 15 minutes

The moment the agreement is signed and the first payment is collected, we create your sub-account in HighLevel. We do not wait for the kick-off call. Time-to-account is one of the clearest signals that the engagement has actually started.

  • Create the sub-account — we add it under your public business name, spelled the way you use it with customers.
  • Set the business address and timezone — this drives calendar availability, local search data, and any location-based automations. Settings → Business Profile.
  • Upload your logo and brand colors — we add these to the Business Profile so email templates, forms, and pages in the Snapshot pick up your branding automatically.
  • Set the primary phone number and business email — these appear in messages sent on your behalf. We confirm them from the intake form before the account is finalized.
  • Assign your Kyndra contact — the team member responsible for your account is set as the default user so tasks and internal notices route to the right person.
  • Deploy the Kyndra Client Starter Snapshot — this HighLevel Snapshot loads the pipelines, workflows, email templates, pages, and calendar setup that match your plan, so the account is not an empty shell on day one.
2

Send the welcome sequence and intake form

Triggered when the sub-account is created and your contact is tagged

⏱ Automated

The welcome sequence starts as soon as the sub-account exists — or as soon as your contact record is tagged as a new client in our CRM. This is a HighLevel workflow, not a one-off email someone has to remember to send.

  • Welcome email — personal, specific to what you signed up for. It uses your business name, your plan, and the name of the person who will work with you. It is not a generic “thanks for signing up.”
  • Intake form — a form that collects everything we need for technical setup: domain access, ad account details, Google Business Profile email, any existing contact export, and brand assets (logo, colors, fonts). Answers land directly on your contact record.
  • Kick-off booking link — the calendar link is in the welcome email so you can book in one click. We never leave scheduling to a back-and-forth later.
  • Login details — we send your login URL at app.gokyndra.com (our white-label HighLevel domain), your username, and the separate “Activate your account” message so you can set a password.
  • A clear timeline — the email states when the kick-off will happen and when the first automation is expected to go live. Specific dates reduce the “is anything happening?” feeling.

ℹ️ How this runs in HighLevel: we tag the new client contact “Onboarding Started,” and that tag triggers the workflow. It sends the welcome email, waits 24 hours, reminds you if the intake form is still open, waits another 24 hours, and then creates a call task for your account manager. Every new client gets the same follow-through without anyone having to remember the steps.

Phase 2: Technical setup checklist (Days 1–3)

3

Configure your email sending domain

Sub-account Settings → Email Services → Email Domain

⏱ 30 minutes + DNS propagation

Every automated email from your Kyndra CRM should come from your domain, not a generic sender. Skipping this step is how campaigns end up in spam before they have a chance to work.

  • Add your sending domain — Settings → Email Services → Add Domain. We enter the domain you actually use with customers (for example, yourbusiness.com).
  • Add the SPF record — HighLevel provides the SPF value; we add it at your domain registrar (GoDaddy, Namecheap, Cloudflare, or similar). DNS access is one of the items on the intake form.
  • Add the DKIM record — the DKIM TXT record authenticates outbound mail as genuinely from your domain.
  • Add a DMARC record — we start with a monitoring policy (p=none) and tighten it after the first weeks of clean delivery. Inbox providers increasingly expect this.
  • Verify the domain in HighLevel — once DNS has propagated (often 15 minutes, sometimes a few hours), we verify in Email Domain settings. All three records should show as valid.
  • Send a test email — we send a test from your sub-account to a personal inbox and a Gmail address, and confirm delivery, the from-name, and that it did not land in spam.

⚠️ We do not turn on email campaigns until the domain is verified. Sending volume from an unverified domain can damage your sender reputation, and recovering from that takes weeks. This step is finished before any automated email workflows are activated.

4

Set up phone and SMS

Sub-account Settings → Phone Numbers → Add Number

⏱ 20 minutes

If your plan includes texting and calling, a number has to be provisioned in HighLevel before any SMS workflow can send. We start this immediately, because US compliance approval is not instant.

  • Provision a local number — Settings → Phone Numbers → Add Number. We choose a number in your local area code. Local numbers typically see better answer and reply rates than toll-free numbers for local service businesses.
  • Start A2P 10DLC registration — business SMS in the US requires A2P 10DLC registration. We submit the brand and campaign in Settings → Phone Numbers → Compliance. Approval can take one to five business days, and SMS workflows cannot send until it is complete, so this is not something we leave for later in the week.
  • Set call forwarding — inbound calls to the HighLevel number can forward to your existing business phone, so the number works as a real line, not only as an outbound text sender.
  • Turn on missed-call text-back — this is one of the highest-return automations in the platform. If a call is missed, a text goes out to the caller within seconds. We confirm it is active as soon as the number is in place. Growth and Advisory plans include the AI receptionist and missed-call text-back as part of the setup.
  • Test send and receive — we send a test text from the Conversations inbox, confirm it arrives, reply from the test phone, and confirm the reply appears in HighLevel.
5

Connect Google Business Profile and reputation tools

Sub-account Settings → Integrations → Google My Business

⏱ 15 minutes

For local businesses, connecting Google Business Profile in HighLevel unlocks review monitoring, review-request automations, and Google Messaging — all of which affect how new customers find and trust you.

  • Connect Google Business Profile — Settings → Integrations → Google. We authenticate with your Google account and select the correct location.
  • Turn on review monitoring — new Google reviews flow into Reputation Management. We set an internal alert so your account manager sees a new review when it is posted.
  • Configure the review-request automation — typically triggered a few days after a job is marked complete or a deal is won, then a text goes out with your direct Google review link.
  • Connect your Facebook Page — Settings → Integrations → Facebook, so Messenger conversations appear in the same HighLevel inbox as texts and email.
  • Connect Google Messaging — if it is enabled on your profile, inbound Google Business messages land in Conversations alongside everything else.
6

Configure calendars and booking

Calendars → Calendar Settings

⏱ 30 minutes

Your booking calendar should be live before the kick-off call — ideally before your first login — so the first time you open the dashboard, you are looking at a working, professional scheduling system, not a blank settings page.

  • Set your actual availability — we use the hours you give us on the intake form, not a default 9–5.
  • Confirm the timezone — Settings → Business Profile → Timezone must match where you work. This is the most common setup mistake in HighLevel, and it is also the easiest to prevent.
  • Connect Google Calendar (two-way sync) — so existing commitments block time and new Kyndra bookings appear on your personal or business calendar.
  • Brand the booking page — your logo, a short description, and a photo where it helps. A finished booking page is easier to share and feels like part of your business, not a generic form.
  • Activate reminder workflows — confirmation, 24-hour reminder, and one-hour reminder by SMS and email. We place a test booking and confirm the full sequence fires.
  • Share the booking link — it is included in the kick-off confirmation so you can start sending it to customers right away.
7

Configure your pipeline and CRM

CRM → Pipelines → Configure Stages

⏱ 20 minutes

The Snapshot installs a starting pipeline. Before any real contacts move through it, we review the stages and language so they match how you actually sell — not a generic template.

  • Review and rename stages — a cleaning company’s flow (New Lead → Estimate Requested → Estimate Sent → Booked → Completed → Review Requested) is not the same as a consultant’s (Discovery Booked → Call Completed → Proposal Sent → Won / Lost). We rename until the pipeline sounds like your business.
  • Set typical deal values — an average opportunity value at creation gives the pipeline a useful revenue view for reporting.
  • Add custom fields you actually need — property address, vehicle type, pet details, location, or anything HighLevel’s default contact fields do not cover. Those fields are then added to forms and workflows.
  • Import existing contacts — if you are coming from another CRM or a spreadsheet, we import a CSV, map the fields, and tag records (Existing Customer, Past Lead) so new and existing contacts stay distinct.
  • Test the pipeline automations — we create a test contact and move it through the stages to confirm texts, emails, and tasks fire at the right moments.

Phase 3: Client access and kick-off call (Days 3–5)

8

Set up your dashboard access

Sub-account → Settings → Team → Add User

⏱ 10 minutes

Before you log in, we configure permissions so you see what is useful — and so a setting that should stay stable cannot be changed by accident.

  • Create your user — Settings → Team → Add User, with your name and business email. For most clients we assign the User role, not Admin, unless you have a clear reason to need admin access.
  • Set permissions — HighLevel allows this to be fairly specific. Typically we enable Contacts, Calendar, Conversations, and Reporting, and we restrict the workflow builder, Settings, and sub-account configuration. Those are the areas where a stray edit can break automations.
  • Send login through our white-label domain — you sign in at app.gokyndra.com, not the public HighLevel app URL. The account should feel like your Kyndra CRM, not a third-party tool you were handed.
  • Record a short walkthrough — a five-to-seven-minute screen recording of your dashboard (your pipeline, your inbox, your calendar) is more useful than a generic help doc. We use your business name and the features that actually apply to your plan.
  • Point you to help and support — the access email includes how to reach us at [email protected]. Support hours are Monday–Friday, 9 AM–3 PM CST. At minimum we cover how to view and reply to conversations, how to check the pipeline, and where reports live.
9

Kick-off call agenda

30–45 minutes · You + your Kyndra account manager

⏱ 30–45 min call

The kick-off is the most important human moment in onboarding. It is not a product tour of HighLevel — that is what the walkthrough recording is for. The call is there to agree on goals, set expectations, and confirm the technical setup is actually right for your business. A well-run kick-off turns a nervous new client into a confident one.

  • [0–5 min] Welcome and context — we thank you, name why this partnership exists, and preview what the call will cover. We do not start with technical questions.
  • [5–15 min] Goal alignment — we ask what success looks like at 90 days, and which single metric will tell you this is working. Those answers are written into your HighLevel contact record and become the benchmarks we report against.
  • [15–25 min] Technical confirmation — we walk through the live CRM: pipeline, calendar, Conversations inbox, and the first automation. We ask if anything does not look right for your business. This is the moment to catch a Snapshot mismatch before it causes problems.
  • [25–35 min] How we will communicate — preferred report format (dashboard vs. a written summary), preferred channel (email, text, or a shared thread), response-time expectations, and how to escalate if something is wrong.
  • [35–45 min] The next 14 days — we tell you exactly what goes live, on which dates, what you will start seeing in the pipeline, and when the first report arrives. Specifics here prevent the “nothing is happening” worry that leads to early frustration.

💡 We record the kick-off, with your permission. The recording goes out right after the call so you have a reference, and we create an internal HighLevel task to capture any commitments made on the call so they are not lost in the notes.

Ready to start with Kyndra?

This is the onboarding system we run for every new client — HighLevel sub-account, Snapshot, automations, white-label dashboard, and a kick-off that is actually a plan, not a product demo. If you are considering a partnership, we would rather walk you through it in conversation.

Talk with Kyndra →

Phase 4: First campaign launch (Days 5–14)

10

Activate and test Snapshot workflows

Automation → Workflows → Review each workflow’s status

⏱ 45 minutes

HighLevel Snapshots often deploy workflows in a draft or inactive state. Each one has to be reviewed, adjusted for your business, and turned on deliberately. This is the step that gets rushed most often — and the one that causes the most visible failures when it is.

  • Audit every workflow in the sub-account — we open each one and check the trigger, filters, and actions. Phone numbers, email addresses, calendar links, and personalization tokens must be yours, not leftover placeholders from the Snapshot.
  • Test with a live contact — we use a real mobile number and email, trigger each workflow, and confirm texts arrive, emails land in the inbox (not spam), and pipeline actions actually run.
  • Activate in order of impact — first: missed-call text-back, new-lead follow-up, and appointment reminders. Review requests and re-engagement sequences can follow in week two.
  • Turn on failure alerts — HighLevel can notify us when a workflow action fails. A quiet failure is how leads sit untouched for days.
  • Document what is live — we keep a simple list of active automations to share at the 30-day check-in: what has been running, since when, and how much it has already sent.
11

Connect lead sources and watch the first leads arrive

Ad accounts, website forms, and other sources into HighLevel

⏱ 1–2 hours

A pipeline only matters once leads are flowing into it. Connecting every source in the first two weeks is how you see real activity in the dashboard from the start, not after a long quiet stretch.

  • Connect Facebook Lead Ads — Settings → Integrations → Facebook. We link the ad account, map form fields to HighLevel contact fields, and confirm new submissions create contacts and start the follow-up workflow.
  • Connect Google Ads where relevant — for conversion tracking and lead-form import, when you are already running search campaigns.
  • Put HighLevel forms on your website — we replace or supplement existing contact forms so submissions go into the CRM, instead of arriving as untracked emails.
  • Tag each lead source — Facebook Ad, Google Ad, Website Form, Referral, Direct Call, and so on, applied automatically from the entry point so reporting can show which channels are actually producing conversations.
  • Import a historical list if you have one — past prospects can go into a re-engagement workflow, tagged so they stay distinct from new leads in reports.
  • Verify the first live lead end to end — when the first real inquiry arrives, we manually confirm the contact was created, the opportunity appeared, the follow-up text and email sent, and the internal notice reached the right person.

Phase 5: 30-day check-in checklist

12

30-day performance review

Scheduled call + a written report

⏱ 30 min call + 1 hour prep

The 30-day check-in is the first formal look at results, and the most important retention conversation in the first 90 days. A clear, data-backed review makes you feel informed. Silence for a month makes you feel forgotten.

  • Pull the numbers before we meet — total leads, leads by source, appointments booked, pipeline distribution, SMS and email delivery, and any revenue tied to closed work. We take this from HighLevel reporting and the pipeline dashboard, not from memory.
  • Compare against the kick-off goals — the report is framed around the outcomes you named on the call, not a pile of activity metrics. If success meant a certain number of qualified appointments, that is the number we lead with.
  • Explain anything that is behind — if results are short of the target, we say so plainly and bring a specific adjustment plan. Clients can live with a slow start when it is explained honestly. They cannot live with a surprise on the next invoice.
  • Confirm the month 2 plan — which additional automations go live, any campaign changes, any new pages or forms. You should leave with a forward plan, not only a look backward.
  • Ask how the experience has felt — we close with a direct satisfaction question about onboarding so far. A lukewarm answer is a signal, and we treat it as one: we ask for specifics and act on them.
  • Send the written report within 24 hours — a PDF or shared doc, the same day or the next, so you have a record you can revisit or share.

Phase 6: Ongoing retention system

13

Build the client retention automation

Automation → Workflows → Client engagement sequence

⏱ 60 minutes to build

Good onboarding should lead to a relationship that does not go quiet between calls. Part of that is human; part of it is a HighLevel workflow that keeps useful touchpoints happening from month two onward.

  • Monthly performance summary — an automated email with the month’s activity: leads captured, appointments booked, calls handled, reviews generated. This does not replace the monthly conversation. It means you see the numbers before the call, not for the first time on it.
  • Inactivity alert for our team — an internal workflow flags a sub-account with no meaningful activity (no conversations opened, no pipeline updates) for 21 days, and assigns a check-in task. Silence in the platform is often an early warning, not a sign that everything is fine.
  • A 90-day milestone note — at the quarter mark, a message that names a real result, not a generic “happy anniversary.” Specific progress is what people remember and repeat.
  • A timely renewal conversation — if there is a defined term, we start that discussion about 30 days before it ends, rather than scrambling after it lapses. (Many Kyndra plans are month-to-month and can be cancelled any time — even then, we would rather talk early than go quiet.)
  • A referral ask, when results support it — around day 60, if things are going well, a short, specific request: who else in your world could use what we have built, and how to introduce them.

💡 This lives in the Snapshot: the retention automation is part of the Kyndra Client Starter, so it deploys with every new HighLevel sub-account. We tag the client “Active Client” on the day they go live, and that tag runs the sequence. If an engagement pauses or ends, we remove the tag and the sequence stops.

Seven onboarding mistakes that create early churn

These are the patterns we built this checklist to avoid — in our own work, and in any HighLevel onboarding that starts strong on paper and then loses the client in the first quarter.

  • Waiting more than a day to create the sub-account. Every hour between a signed agreement and a visible account is an hour for second thoughts. The HighLevel sub-account should exist the same day. If manual creation is the bottleneck, we trigger it from the contract or pipeline stage so it cannot slip to “tomorrow.”
  • Sending a generic welcome email. A note that could have gone to any business in any industry tells the client they are a ticket, not a partnership. We use the business name, the plan they chose, and the name of the person who will actually work with them.
  • Skipping email domain authentication. Agencies that leave SPF, DKIM, and DMARC for later send campaigns from unverified domains. Deliverability fails, results look weak, and the platform gets blamed for a 30-minute day-one task that never happened.
  • Handing over the entire HighLevel dashboard on day one. The platform has a lot of features. An unguided first login feels overwhelming, not empowering. We start people in the four areas they will actually use — Conversations, Calendar, Pipeline, and Reporting — and open more as they get comfortable.
  • Holding a kick-off with no agenda in advance. Sending the agenda a day ahead lets you arrive with goals and questions. Calls without one drift into troubleshooting and waste the best early chance to get strategically aligned.
  • Forgetting what was promised on the kick-off call. Every commitment — “that campaign will be live by Friday,” “we will turn on the review automation this week” — is logged as a dated HighLevel task assigned to a named person. Dropped promises are the fastest way to lose trust in a new relationship.
  • Going quiet between calls. If the only time you hear from us is the monthly meeting, the other 29 days feel empty. A short “here is what we finished this week” note every week or so in the first 60 days makes a visible difference. We use tasks and reminders in HighLevel so those updates actually go out.

What goes in the Kyndra Client Starter Snapshot

The scalable way to run this checklist is to put every repeatable piece into a HighLevel Snapshot so it deploys with each new client sub-account. This is what a complete Kyndra onboarding Snapshot contains, and what still has to be customized after it lands.

Snapshot component What it includes Customization after deploy
Onboarding workflow Welcome email sequence, intake form reminder, kick-off call reminder Replace placeholder business name and account manager details
Lead follow-up workflow Immediate SMS and email on new contact creation, then a five-touch sequence over seven days Review the copy for your industry tone — trades, professional services, and care businesses do not sound the same
Appointment reminders Confirmation SMS and email, 24-hour reminder, one-hour reminder, no-show rebooking sequence Confirm appointment length and that the calendar link points to your calendar
Pipeline A default multi-stage pipeline with stage-change automations Rename stages to match how you actually talk about your sales process
Booking calendar A pre-configured calendar with standard hours as a starting point Update availability, timezone, and the Google Calendar connection
Review request workflow Post-service review request by SMS and email, with a Google review link placeholder Replace the placeholder with your actual Google Business Profile review link
Monthly report email A branded template summarizing the month’s metrics Confirm branding; metrics pull from HighLevel reporting
Client retention workflow Inactivity alert, 90-day milestone note, renewal or check-in prompt Runs from tags — little to change once the client is marked active
Missed-call text-back Pre-built automation that activates once a phone number is provisioned Universal — usually no customization required
Funnel and site pages Thank-you page, contact form page, appointment booking page Update logo, colors, copy, and the calendar link

Let’s get your HighLevel onboarding right from day one

Every item on this checklist runs inside your Kyndra CRM on HighLevel — sub-accounts, Snapshots, workflows, a white-label dashboard at app.gokyndra.com, and the follow-through that keeps the partnership from going quiet. If you are ready to start, or you want to pressure-test how your current onboarding compares, we will walk through it with you.

Get in touch with Kyndra →

Questions in the meantime? Email [email protected]
Support hours Monday–Friday, 9 AM–3 PM CST · (512) 815-2298

Frequently asked questions

How long does Kyndra client onboarding take?

Full technical setup — HighLevel sub-account creation, email domain configuration, phone provisioning, Google Business Profile connection, workflow activation, and calendar setup — typically takes three to five business days once we have what we need from you. The kick-off call is usually on day 3–5. The first live automation (missed-call text-back or the lead follow-up sequence) should be active within 48 hours of the sub-account being created. When onboarding runs longer than five days, the bottleneck is almost always the intake form: DNS access, Google credentials, or brand assets arriving late. That is why the welcome sequence includes automatic reminders, and why we are direct that technical setup cannot really begin until the form is complete.

Will I have admin access to my HighLevel sub-account?

For most clients, no — and that is intentional. Admin users can edit or delete workflows, change phone numbers, and alter settings that break the automations we have just built. We give you a User role with access to Contacts, Calendar, Conversations, and Reporting. We reserve admin access for clients who specifically need it and understand the responsibility. If something in the platform needs to change, the request goes through your Kyndra account manager rather than through a wide-open admin login.

What is in the Kyndra Client Starter Snapshot?

A production-ready HighLevel onboarding Snapshot should include, at minimum: a lead follow-up workflow (immediate SMS and email, then a multi-day sequence), an appointment calendar with reminders, a post-appointment follow-up and review request, a CRM pipeline with stages that can be renamed for your business, missed-call text-back, a monthly reporting email template, and a basic lead-capture page. Ours also includes the client welcome sequence, a re-engagement path for quieter leads, and a referral request once results support it. Where it helps, we adjust the Snapshot for the type of business — a practice, a trade, and a professional-services firm do not need identical language or stages.

What happens if I have not finished the intake form?

A three-step follow-up runs automatically when your contact is tagged “Onboarding Started” and the form is still outstanding. After 24 hours: an email reminder with the form link. After 48 hours: a short text that names what we still need. After 72 hours: a task for your account manager to call you directly. We do not start technical setup on placeholder information — that creates rework and errors. The welcome email is explicit that setup waits on a completed intake form, so this is never a surprise.

How does Kyndra keep onboarding on track when several clients start at once?

The process is a HighLevel workflow sequence, not a set of personal reminders. “Onboarding Started” triggers the client-facing steps, and we track every engagement on an internal Client Onboarding pipeline in our own Kyndra account — separate from your sub-account — so we can see which stage each client is in, which technical items are still open, and where something is slipping. That is how the same standard holds when more than one onboarding is in motion at the same time.

This page describes Kyndra’s standard client onboarding process on HighLevel, including the Kyndra Client Starter Snapshot and the first 30 days after you sign. It is a process guide, not a contract. For questions about your own setup, email [email protected] or visit Contact form. Support is available Monday–Friday, 9 AM–3 PM CST.