<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:media="http://search.yahoo.com/mrss/"><channel><title><![CDATA[Lumikha Learning]]></title><description><![CDATA[Lumikha Learning]]></description><link>https://lmki.lumikha.co/</link><image><url>https://lmki.lumikha.co/favicon.png</url><title>Lumikha Learning</title><link>https://lmki.lumikha.co/</link></image><generator>Ghost 5.82</generator><lastBuildDate>Thu, 04 Jun 2026 17:04:54 GMT</lastBuildDate><atom:link href="https://lmki.lumikha.co/rss/" rel="self" type="application/rss+xml"/><ttl>60</ttl><item><title><![CDATA[Schedule Social Posts in Postly]]></title><description><![CDATA[This module covers the end-to-end process of scheduling a social post in Postly — our scheduling tool of choice — for LinkedIn and Facebook. ]]></description><link>https://lmki.lumikha.co/schedule-social-posts-in-postly/</link><guid isPermaLink="false">6a0a6fb4667e580837556134</guid><category><![CDATA[Social]]></category><category><![CDATA[Content]]></category><dc:creator><![CDATA[Administrator]]></dc:creator><pubDate>Mon, 18 May 2026 01:53:11 GMT</pubDate><media:content url="https://images.unsplash.com/photo-1573152143286-0c422b4d2175?crop=entropy&amp;cs=tinysrgb&amp;fit=max&amp;fm=jpg&amp;ixid=M3wxMTc3M3wwfDF8c2VhcmNofDR8fHNvY2lhbCUyMG1lZGlhfGVufDB8fHx8MTc3OTAyOTQ4Nnww&amp;ixlib=rb-4.1.0&amp;q=80&amp;w=2000" medium="image"/><content:encoded><![CDATA[<img src="https://images.unsplash.com/photo-1573152143286-0c422b4d2175?crop=entropy&amp;cs=tinysrgb&amp;fit=max&amp;fm=jpg&amp;ixid=M3wxMTc3M3wwfDF8c2VhcmNofDR8fHNvY2lhbCUyMG1lZGlhfGVufDB8fHx8MTc3OTAyOTQ4Nnww&amp;ixlib=rb-4.1.0&amp;q=80&amp;w=2000" alt="Schedule Social Posts in Postly"><p><strong>Track:</strong> Content Operations<br><strong>Estimated time:</strong> 12 minutes<br><strong>Difficulty:</strong> Beginner</p>
<!--kg-card-begin: html-->
<iframe width="560" height="315" src="https://www.youtube.com/embed/7ays41MfbE8?si=jlsY14XTy4wztn0q" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>
<!--kg-card-end: html-->
<p></p><h2 id="what-this-covers">What this covers</h2><p>This module covers the end-to-end process of scheduling a social post in Postly &#x2014; our scheduling tool of choice &#x2014; for LinkedIn and Facebook. </p><p>You&apos;ll load the caption, attach the media, select the right account, schedule for the right time, and then duplicate the post twice to create a package of three staggered posts from the same asset. This is the standard posting regime for every piece of content we publish.</p><h2 id="step-by-step-reference">Step-by-step reference</h2><p><strong>Step 1 &#x2014; Prepare before you open Postly</strong></p><p>Before creating the post, have these three things ready:</p><ol><li>The captions document (spreadsheet or markdown) with all three caption variants</li><li>The video or image file exported and saved locally</li><li>Confirmation of which accounts you&apos;re posting to (Harry&apos;s personal LinkedIn, Lambent company LinkedIn, Facebook)</li></ol><blockquote>Captions are pre-written by Claude and exported &#x2014; your job is to paste, light-edit, and schedule. Do not write captions from scratch in Postly.</blockquote><p><strong>Step 2 &#x2014; Create a new post</strong></p><p>In Postly, click <strong>Create post</strong>. A new post composer opens.</p><p><strong>Step 3 &#x2014; Select the target account</strong></p><p>Before doing anything else, select the social media account you&apos;re posting to. Do this first &#x2014; Postly&apos;s restrictions (character count, media format) vary by platform, and selecting the account helps you catch issues early.</p><blockquote><strong>Do not post to multiple platforms simultaneously from one post.</strong> Each platform has different content restrictions and formatting rules. Create separate posts for LinkedIn and Facebook even if the caption is similar.</blockquote><p><strong>Step 4 &#x2014; Paste and edit the caption</strong></p><p>Copy the first caption variant from the captions document and paste it into the composer. Then:</p><ul><li>Add a <strong>hard return (blank line) between each sentence or paragraph</strong> &#x2014; Postly does not always respect line breaks on paste, and a wall of text kills engagement</li><li>Your <strong>first line is your hook</strong> &#x2014; make sure it reads well on its own, because that&apos;s all people see before clicking &quot;more&quot;</li><li>Light-edit as needed: remove anything that doesn&apos;t land, tighten phrasing. The caption should feel human, not generated</li></ul><p><strong>Step 5 &#x2014; Upload the media</strong></p><p>Drag and drop the video or image file into the media area, or use the upload button. Wait for the spinner to complete before proceeding &#x2014; large video files take a moment. Once loaded, select the file and click <strong>Add selected media</strong>. A thumbnail appears in the composer confirming it&apos;s attached.</p><blockquote><strong>Image sizing:</strong> For this workflow we&apos;re using square format video (1:1). Make sure the asset matches the platform&apos;s spec before uploading. Mismatched aspect ratios will crop or letterbox unpredictably.</blockquote><p><strong>Step 6 &#x2014; Schedule the post</strong></p><p>Set the date and time. Timing guidelines:</p>
<!--kg-card-begin: html-->
<table class="min-w-full border-collapse text-sm leading-[1.7] whitespace-normal"><thead class="text-left"><tr><th scope="col" class="text-text-100 border-b-0.5 border-border-300/60 py-2 pr-4 align-top font-bold">Audience</th><th scope="col" class="text-text-100 border-b-0.5 border-border-300/60 py-2 pr-4 align-top font-bold">Target window</th></tr></thead><tbody><tr><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top"><strong>Lambent</strong> (US market)</td><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top">Early morning or end of day US Eastern &#x2014; 8&#x2013;9 AM or 5&#x2013;6 PM ET. Avoid mid-business-hours.</td></tr><tr><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top"><strong>Lumikha</strong> (SEA/ANZ market)</td><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top">Morning Manila time targets Singapore, HK, Australia.</td></tr></tbody></table>
<!--kg-card-end: html-->
<p>Use the <strong>week view</strong> in the Postly calendar to see what&apos;s already scheduled before picking a slot. Switch to week view using the toggle &#x2014; it&apos;s easier to spot gaps and avoid clustering.</p><p><strong>Step 7 &#x2014; Duplicate for the second post (2&#x2013;3 weeks out)</strong></p><p>Once the first post is scheduled, <strong>duplicate it</strong> using Postly&apos;s duplicate function. This carries over the media. Then:</p><ul><li>Replace the caption with the <strong>second variant</strong> from the captions document</li><li>Paste and reformat (add hard returns again &#x2014; the paste issue repeats)</li><li>Move the date out 2&#x2013;3 weeks from the first post</li><li><strong>Vary the day of the week and time</strong> &#x2014; don&apos;t repeat the same slot. If the first was a Tuesday morning, make this a Thursday afternoon.</li><li>Update and save</li></ul><p><strong>Step 8 &#x2014; Duplicate for the third post (2&#x2013;3 months out)</strong></p><p>Duplicate again. Then:</p><ul><li>Replace the caption with the <strong>third variant</strong></li><li>Move the date out 2&#x2013;3 months from the first post</li><li>Again, vary day and time. Friday is a good LinkedIn day; afternoon US time works well for the third touch</li><li>Update and save</li></ul><p><strong>Step 9 &#x2014; Repeat for each account</strong></p><p>You now have a package of three posts scheduled for one account. Repeat Steps 2&#x2013;8 for each additional account in scope. For a standard Lambent content drop, this means:</p><ul><li>Harry&apos;s personal LinkedIn (3 posts)</li><li>Lambent company LinkedIn (3 posts)</li><li>Facebook (3 posts)</li></ul><p>That&apos;s 9 scheduled posts total from one asset.</p><hr><h2 id="rules-edge-cases">Rules + edge cases</h2><p><strong>LinkedIn frequency limit:</strong> LinkedIn deprioritises accounts that post too frequently. As the calendar fills up, be conscious of gaps &#x2014; avoid scheduling two posts from the same account within 24 hours. Personal profile and company page are treated separately, so Harry&apos;s LinkedIn and Lambent&apos;s LinkedIn don&apos;t compete with each other.</p><p><strong>Three accounts, three caption variants:</strong> Each account gets a different caption variant &#x2014; not the same caption posted three times. The variant is what makes reposts feel fresh rather than duplicate.</p><p><strong>If the caption paste comes in as a text block</strong> &#x2014; always reformat with hard returns before scheduling. A wall of copy without breaks reads poorly on mobile and buries the hook. This is not optional.</p><p><strong>If Postly drops the media when you duplicate</strong> &#x2014; this can happen occasionally. Before scheduling each duplicate, confirm the thumbnail is visible. If it&apos;s missing, re-upload.</p><p><strong>Instagram and Google Business</strong> are not covered in this workflow. Both require individual posts and have their own process &#x2014; these will be documented separately.</p><p><strong>If you&apos;re unsure which caption variant to assign to which account</strong> &#x2014; default to: Variant A for Harry&apos;s personal LinkedIn (most conversational), Variant B for Lambent company page (most professional), Variant C for Facebook (can be slightly more casual). When in doubt, ask before scheduling.</p><p><strong>Escalation signal:</strong> If a post goes out at the wrong time or to the wrong account, notify Harry immediately. Do not delete or modify a published post without sign-off.</p><hr><h2 id="self-assessment-checklist">Self-assessment checklist</h2><p>Before moving to the next module, confirm you can do all of the following without referring back to this page:</p><ul><li>I know why we use Postly and what its automation benefit is</li><li>I can create a post, select the correct account, paste and reformat a caption, and attach media</li><li>I understand the hard return rule and why the hook matters</li><li>I can schedule a post for the correct time window for US vs. SEA audiences</li><li>I can duplicate a post and swap in a new caption variant for the rescheduled versions</li><li>I know the standard package structure: 3 variants &#xD7; 3 accounts = 9 posts per asset</li><li>I know the LinkedIn frequency rule and how to avoid over-clustering</li></ul>]]></content:encoded></item><item><title><![CDATA[Basic Data Validation for a B2B File]]></title><description><![CDATA[This module covers how to spot-check a sample of records using web search and LinkedIn to estimate what percentage of a list is still usable,]]></description><link>https://lmki.lumikha.co/basic-data-validation-for-a-b2b-file/</link><guid isPermaLink="false">6a0a6764667e58083755611a</guid><category><![CDATA[Data]]></category><category><![CDATA[Basics]]></category><dc:creator><![CDATA[Administrator]]></dc:creator><pubDate>Mon, 18 May 2026 01:19:43 GMT</pubDate><media:content url="https://images.unsplash.com/photo-1542744173-05336fcc7ad4?crop=entropy&amp;cs=tinysrgb&amp;fit=max&amp;fm=jpg&amp;ixid=M3wxMTc3M3wwfDF8c2VhcmNofDE0fHxkYXRhfGVufDB8fHx8MTc3ODk3NTQ0NXww&amp;ixlib=rb-4.1.0&amp;q=80&amp;w=2000" medium="image"/><content:encoded><![CDATA[<img src="https://images.unsplash.com/photo-1542744173-05336fcc7ad4?crop=entropy&amp;cs=tinysrgb&amp;fit=max&amp;fm=jpg&amp;ixid=M3wxMTc3M3wwfDF8c2VhcmNofDE0fHxkYXRhfGVufDB8fHx8MTc3ODk3NTQ0NXww&amp;ixlib=rb-4.1.0&amp;q=80&amp;w=2000" alt="Basic Data Validation for a B2B File"><p><strong>Track:</strong> Outreach Operations<br><strong>Estimated time:</strong> 9 minutes<br><strong>Difficulty:</strong> Beginner</p>
<!--kg-card-begin: html-->
<iframe width="560" height="315" src="https://www.youtube.com/embed/X7kmwydDTkA?si=t-uVpHBCDWiQAlVA" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>
<!--kg-card-end: html-->
<p></p><h2 id="what-this-covers">What this covers</h2><p>Before we invest time enriching or submitting a legacy contact list for validation, we need to know whether the data is still worth anything. </p><p>This module covers how to spot-check a sample of records using web search and LinkedIn to estimate what percentage of a list is still usable &#x2014; and what signals tell you a record is dead.</p><h2 id="step-by-step-reference">Step-by-step reference</h2><p><strong>Step 1 &#x2014; Pull a sample of records</strong></p><p>Open the legacy list. Do not try to check every record &#x2014; that&apos;s not the goal here. Select a representative sample of 5&#x2013;10 records spread across industries or segments if possible. You&apos;re building an estimate, not a full audit.</p><p><strong>Step 2 &#x2014; Run a quick web search on each contact</strong></p><p>For each record, take the person&apos;s name and current (listed) company and drop them into Google search together. Scan the first page of results for:</p><ul><li>Their current role and company</li><li>Any news about a job change, promotion, or departure</li><li>LinkedIn profile appearing in results (check it directly)</li></ul><blockquote><strong>Cautionary note on AI summaries (Google/Bing overviews):</strong> These give you a useful first clue but are not definitive. Use them to form a hypothesis, then verify against the actual LinkedIn profile or company page. Never update a record based on an AI summary alone.</blockquote><p><strong>Step 3 &#x2014; Check LinkedIn directly</strong></p><p>Open the contact&apos;s LinkedIn profile. Look at:</p>
<!--kg-card-begin: html-->
<table class="min-w-full border-collapse text-sm leading-[1.7] whitespace-normal"><thead class="text-left"><tr><th scope="col" class="text-text-100 border-b-0.5 border-border-300/60 py-2 pr-4 align-top font-bold">Signal</th><th scope="col" class="text-text-100 border-b-0.5 border-border-300/60 py-2 pr-4 align-top font-bold">What it tells you</th></tr></thead><tbody><tr><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top">Current role + company</td><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top">Is the listed data still accurate?</td></tr><tr><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top">Location</td><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top">Have they moved region or country?</td></tr><tr><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top">&quot;X VP&quot; / &quot;Former&quot; labels</td><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top">Likely retired or between roles</td></tr><tr><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top">Recent activity</td><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top">Active profile = more reliable data</td></tr></tbody></table>
<!--kg-card-end: html-->
<p>For senior contacts (Director and above), LinkedIn profiles are usually more complete and easier to verify.</p><p><strong>Step 4 &#x2014; Classify each record</strong></p><p>As you work through the sample, assign each contact one of three statuses:</p><ul><li><strong>Good</strong> &#x2014; Still at the listed company, role roughly the same, contact details likely still valid</li><li><strong>Moved but trackable</strong> &#x2014; Changed company or role, but still active and potentially a viable lead depending on ICP fit</li><li><strong>Dead</strong> &#x2014; Retired, relocated out of region, or profile data no longer matches the use case</li></ul><p>Flag &quot;moved but trackable&quot; records in the sheet (bold, highlight, or a status column &#x2014; use whatever convention is already in place). Do not delete them; they may be enrichable via Lusha.</p><p><strong>Step 5 &#x2014; Make the call on the full list</strong></p><p>After working through your sample, estimate the percentage of records that fall into each category. Use this as your decision framework:</p><ul><li><strong>&gt;50% good or trackable</strong> &#x2192; Worth submitting the full list to a validation service (e.g. NeverBounce, ZeroBounce) to recover accurate emails and phone numbers</li><li><strong>&lt;50% good or trackable</strong> &#x2192; Flag to Harry before proceeding; the list may not be worth the enrichment cost</li></ul><p>Note: even a record with an accurate name and company is only partially useful. <strong>Email address and direct phone number are the critical data points for outreach</strong> &#x2014; if those are likely stale (person left the company), the record needs re-enrichment regardless of everything else.</p><h2 id="rules-edge-cases">Rules + edge cases</h2><p><strong>If you can&apos;t find the person at all on LinkedIn or Google</strong> &#x2014; that&apos;s useful signal too. Flag as &quot;unverifiable&quot; in the sheet. Don&apos;t spend more than 2 minutes on a single record.</p><p><strong>If the person has changed company but is still in the same industry and seniority</strong> &#x2014; they may still be a viable lead depending on the campaign. Flag as &quot;moved but trackable&quot; and note the new company. Harry will decide whether to re-enrich via Lusha.</p><p><strong>If the person appears to be retired</strong> &#x2014; mark as dead. Look for signals: &quot;X VP&quot;, &quot;Former&quot;, no recent activity, returned to home country after an expat posting.</p><p><strong>If the list has mixed industries</strong> &#x2014; check at least one or two records from each industry cluster. Data decay rates vary; hospitality and pharma senior roles, for example, turn over frequently.</p><p><strong>Do not spend more than 30&#x2013;45 minutes on a spot-check.</strong> The goal is a directional read on list quality, not a full audit. If the task is taking longer, pause and check in.</p><p><strong>Escalation signal:</strong> If more than 70% of your sample comes back dead or unverifiable, stop and flag to Harry before doing anything else with the list. Do not submit it for validation without sign-off.</p><hr><h2 id="self-assessment-checklist">Self-assessment checklist</h2><p>Before moving to the next module, confirm you can do all of the following without referring back to this page:</p><ul><li>I know how to pull a representative sample from a legacy list for spot-checking</li><li>I can run a web search and read the signals that indicate whether a record is still current</li><li>I understand why AI-generated search summaries are a clue only &#x2014; not a source of truth</li><li>I can check a LinkedIn profile and classify a contact as good, moved but trackable, or dead</li><li>I know which data points (email, phone) make a record actionable for outreach</li><li>I know the threshold for recommending list validation vs. flagging to Harry</li></ul>]]></content:encoded></item><item><title><![CDATA[Basic Blog Posting in Ghost CMS]]></title><description><![CDATA[This module walks through the end-to-end process of publishing a weekly blog post to Ghost — from pasting in the content through to hitting publish. ]]></description><link>https://lmki.lumikha.co/basic-blog-posting-in-ghost/</link><guid isPermaLink="false">6a0a644c667e5808375560fa</guid><category><![CDATA[Content]]></category><category><![CDATA[Basics]]></category><dc:creator><![CDATA[Administrator]]></dc:creator><pubDate>Mon, 18 May 2026 01:07:08 GMT</pubDate><media:content url="https://images.unsplash.com/photo-1524995997946-a1c2e315a42f?crop=entropy&amp;cs=tinysrgb&amp;fit=max&amp;fm=jpg&amp;ixid=M3wxMTc3M3wwfDF8c2VhcmNofDMxfHxibG9nfGVufDB8fHx8MTc3OTA2NjUzOXww&amp;ixlib=rb-4.1.0&amp;q=80&amp;w=2000" medium="image"/><content:encoded><![CDATA[<img src="https://images.unsplash.com/photo-1524995997946-a1c2e315a42f?crop=entropy&amp;cs=tinysrgb&amp;fit=max&amp;fm=jpg&amp;ixid=M3wxMTc3M3wwfDF8c2VhcmNofDMxfHxibG9nfGVufDB8fHx8MTc3OTA2NjUzOXww&amp;ixlib=rb-4.1.0&amp;q=80&amp;w=2000" alt="Basic Blog Posting in Ghost CMS"><p><strong>Track:</strong> Content Operations<br><strong>Estimated time:</strong> 8 minutes<br><strong>Difficulty:</strong> Beginner</p>
<!--kg-card-begin: html-->
<iframe width="560" height="315" src="https://www.youtube.com/embed/4QLX4nyQk_A?si=BvvaKlyaXspeRaHJ" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>
<!--kg-card-end: html-->
<p></p><h1 id="what-this-covers">What this covers</h1><p>This module walks through the end-to-end process of publishing a weekly blog post to Ghost &#x2014; from pasting in the content through to hitting publish. </p><p>This task can be independent or one step in the Newsletter Cascade: the same article will later be distributed as a Beehiiv newsletter and a LinkedIn newsletter, with social posts driving traffic back to this Ghost URL.</p><h2 id="step-by-step-reference">Step-by-step reference</h2><p><strong>Step 1 &#x2014; Log in and create a new post</strong></p><p>Go to your Ghost admin panel and log in. Click the <strong>+</strong> button or &quot;New post&quot; to open a blank editor. You&apos;re now in the Ghost editor canvas.</p><p><strong>Step 2 &#x2014; Paste in the article content</strong></p><p>Copy the full article text from the approved Google Doc. Paste it directly into the Ghost editor body. The headings, paragraphs, and structure should carry over. Do a quick scan to confirm heading levels look right &#x2014; minor formatting tweaks are fine but not required at this stage.</p><p><strong>Step 3 &#x2014; Add the header image</strong></p><p>Click into a blank area at the top of the canvas to create an insertion point. Use the block insert menu (the <code>+</code> icon that appears on a new line) to add an image. Drag your pre-prepared header image file directly from your local folder into the upload area.</p><ul><li>Add a <strong>caption</strong>: pull a short phrase from the body of the article &#x2014; something descriptive that could stand alone.</li><li>Add <strong>alt text</strong>: describe what is literally in the image, then work in a relevant keyword where it reads naturally. Alt text is primarily for accessibility; the keyword is a secondary benefit.</li></ul><p><strong>Step 4 &#x2014; Configure the post settings (sidebar)</strong></p><p>Open the post settings panel (gear icon, top right). Work through these fields:</p>
<!--kg-card-begin: html-->
<table class="min-w-full border-collapse text-sm leading-[1.7] whitespace-normal"><thead class="text-left"><tr><th scope="col" class="text-text-100 border-b-0.5 border-border-300/60 py-2 pr-4 align-top font-bold">Field</th><th scope="col" class="text-text-100 border-b-0.5 border-border-300/60 py-2 pr-4 align-top font-bold">What to do</th></tr></thead><tbody><tr><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top"><strong>Slug</strong></td><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top">Ghost auto-generates one. Review it &#x2014; shorten if too long, remove stop words.</td></tr><tr><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top"><strong>Tags</strong></td><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top">Add 1&#x2013;3 relevant tags (e.g. <code class="bg-text-200/5 border border-0.5 border-border-300 text-danger-000 whitespace-pre-wrap rounded-[0.4rem] px-1 py-px text-[0.9rem]">digital-marketing</code>, <code class="bg-text-200/5 border border-0.5 border-border-300 text-danger-000 whitespace-pre-wrap rounded-[0.4rem] px-1 py-px text-[0.9rem]">marketing-excellence</code>). Tags will be standardised across the site in a future update.</td></tr><tr><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top"><strong>Excerpt</strong></td><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top">Write 1&#x2013;2 sentences summarising the post. This appears on the homepage card below the post title.</td></tr><tr><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top"><strong>Template</strong></td><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top">Select the full background image template (recommended default).</td></tr></tbody></table>
<!--kg-card-end: html-->
<p><strong>Step 5 &#x2014; Add metadata</strong></p><p>Still in the post settings panel, scroll to the <strong>Meta</strong> section:</p><ul><li><strong>Meta title:</strong> Use the article&apos;s H1, or a close variant optimised for search.</li><li><strong>Meta description:</strong> Write 1&#x2013;2 sentences (150&#x2013;160 characters) that describe the article for search results. This is what Google displays in the snippet below the link.</li><li><strong>Canonical URL:</strong> Leave blank. This is original content &#x2014; no canonical reference needed.</li></ul><p>The table of contents (if your Ghost theme supports it) will be auto-generated from your headings. Leave it enabled &#x2014; Google treats it as a positive signal.</p><p><strong>Step 6 &#x2014; Publish</strong></p><p>Click <strong>Publish</strong> (top right). Confirm in the publish dialog.</p><p><strong>Step 7 &#x2014; QC the live post</strong></p><p>Open the published URL in a browser and scroll through the full post:</p><ul><li>Does the header image display correctly? (Note: text-over-face overlap in the hero area is a known theme behaviour &#x2014; acceptable.)</li><li>Do all headings and paragraph breaks look right?</li><li>Is the excerpt showing on the homepage blog listing?</li><li>Does the meta title/description look right if you paste the URL into a social preview tool?</li></ul><p>If anything looks wrong, return to the Ghost editor and correct before moving on.</p><hr><h2 id="rules-edge-cases">Rules + edge cases</h2><p><strong>If the slug auto-generates something long or weird</strong> &#x2014; edit it manually before publishing. Keep it under 5&#x2013;6 words, hyphens only, no special characters.</p><p><strong>If you don&apos;t have a header image ready</strong> &#x2014; do not publish without one. Hold the post as a draft and flag in Discord. Publishing without a header image breaks the visual layout on the homepage.</p><p><strong>If Ghost pastes the content with broken formatting</strong> &#x2014; the most common issue is heading levels coming in wrong (e.g. H2s appearing as H3s). Fix manually using the Ghost text toolbar. Do not re-paste from a different source without checking first.</p><p><strong>If the excerpt field is left blank</strong> &#x2014; Ghost will auto-pull the first sentence of the article. This is usually fine but often pulls in a subheadline or an awkward fragment. Always write a custom excerpt.</p><p><strong>If you&apos;re unsure about tags</strong> &#x2014; use <code>digital-marketing</code> as a safe default until the tag taxonomy is updated. Don&apos;t create new tags without checking with Harry first.</p><p><strong>Escalation signal:</strong> If the post publishes but does not appear on the homepage after 2 minutes, or if the URL returns a 404, do not troubleshoot alone &#x2014; ping Harry directly.</p><h2 id="self-assessment-checklist">Self-assessment checklist</h2><p>Before moving to the next module, confirm you can do all of the following without referring back to this page:</p><ul><li>I can create a new post in Ghost and paste in formatted article content</li><li>I can add a header image with a caption and correct alt text</li><li>I can configure the slug, tags, excerpt, and template in the post settings</li><li>I can write a meta title and meta description, and I know where to enter them</li><li>I know when to leave the canonical URL blank</li><li>I can QC a published post and identify the most common visual issues</li></ul>]]></content:encoded></item><item><title><![CDATA[How We Use Trello]]></title><description><![CDATA[Think of Trello as a whiteboard with sticky notes on it — except the whiteboard is on your computer and anyone on the team can see it.]]></description><link>https://lmki.lumikha.co/how-we-use-trello/</link><guid isPermaLink="false">6a02e20b667e5808375560e9</guid><category><![CDATA[Basics]]></category><category><![CDATA[Tools]]></category><dc:creator><![CDATA[Administrator]]></dc:creator><pubDate>Tue, 12 May 2026 08:58:37 GMT</pubDate><content:encoded><![CDATA[<h3 id="your-guide-to-getting-work-done-without-losing-track-of-it">Your guide to getting work done without losing track of it.</h3><hr>
<!--kg-card-begin: html-->
<iframe width="560" height="315" src="https://www.youtube.com/embed/IpwcWX6BFrQ?si=NeK8Ek8_oEcA82cM" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>
<!--kg-card-end: html-->
<h2 id="what-is-trello-really">What Is Trello, Really?</h2><p>Think of Trello as a whiteboard with sticky notes on it &#x2014; except the whiteboard is on your computer and anyone on the team can see it.</p><p>Each sticky note is a <strong>card</strong>. Each section of the whiteboard is a <strong>list</strong>. The whole whiteboard is a <strong>board</strong>.</p><p>That&apos;s it. Everything else is just details.</p><hr><h2 id="why-trello-and-not-something-more-powerful">Why Trello and Not Something More Powerful?</h2><p>Short answer: more powerful tools create more problems.</p><p>We tried other tools. The issue wasn&apos;t the features &#x2014; it was that managing the tool started taking more time than managing the actual work. Trello is simple enough that it stays out of your way. It&apos;s a tool that works for you, not the other way around.</p><hr><h2 id="the-five-lists-you-need-to-know">The Five Lists You Need to Know</h2><p>Every board is organized into these lists. Think of them as lanes on a road &#x2014; every task lives in exactly one lane at a time.</p>
<!--kg-card-begin: html-->
<table class="min-w-full border-collapse text-sm leading-[1.7] whitespace-normal"><thead class="text-left"><tr><th scope="col" class="text-text-100 border-b-0.5 border-border-300/60 py-2 pr-4 align-top font-bold">List</th><th scope="col" class="text-text-100 border-b-0.5 border-border-300/60 py-2 pr-4 align-top font-bold">What it means</th></tr></thead><tbody><tr><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top"><strong>Resources</strong></td><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top">Reference materials you&apos;ll come back to repeatedly &#x2014; playbooks, trackers, links.</td></tr><tr><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top"><strong>Pending</strong></td><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top">Tasks waiting for you to pick up and start. Check this at least twice a day.</td></tr><tr><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top"><strong>Working</strong></td><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top">Tasks you&apos;ve actively started.</td></tr><tr><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top"><strong>In Review</strong></td><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top">Tasks you&apos;ve finished and submitted for approval.</td></tr><tr><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top"><strong>On Hold</strong></td><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top">Tasks blocked by something outside your control &#x2014; missing info, a dependency, a decision that hasn&apos;t been made yet.</td></tr></tbody></table>
<!--kg-card-end: html-->
<p>When a task moves from one list to another, everyone on the board can see it. No need to send an update message every time &#x2014; the board tells the story.</p><hr><h2 id="whats-inside-a-card">What&apos;s Inside a Card</h2><p>A card is more than just a task name. Here&apos;s what each part does:</p><p><strong>Members</strong> &#x2014; who is working on this task. You can add yourself to watch a card even if it&apos;s not assigned to you.</p><p><strong>Labels</strong> &#x2014; tags that categorize the task by client and type of work (e.g., Administration, Planning, Content, Outreach). These matter for reporting and automation later, so apply them when you can.</p><p><strong>Due Date</strong> &#x2014; the deadline. If a task gets blocked and goes On Hold, remove the due date so it doesn&apos;t sit there turning red.</p><p><strong>Checklist</strong> &#x2014; for tasks with multiple steps. Add one when the steps are clear and repeatable. It helps the next person understand exactly what &quot;done&quot; looks like.</p><p><strong>Description</strong> &#x2014; context and instructions for whoever picks up the task.</p><p><strong>Attachments</strong> &#x2014; drag and drop files, screenshots, or anything relevant right into the card. Don&apos;t make people go hunting for what they need.</p><p><strong>Comments</strong> &#x2014; how you communicate about a specific task. Tag someone with @theirname to notify them directly.</p><blockquote><strong>Remember to save your work inside a card.</strong> If you don&apos;t save, your changes won&apos;t be visible to the rest of the team. You&apos;ll see a warning that says &quot;unsaved changes&quot; &#x2014; that&apos;s your reminder.</blockquote><hr><h2 id="how-tasks-move-around">How Tasks Move Around</h2><p>Anyone on the board can assign a task to anyone else. This isn&apos;t a top-down system &#x2014; tasks flow in all directions. If you need something from a colleague, create a card and assign it to them.</p><p>If you&apos;re worried a task will get lost, copy the card link and paste it in Discord with a quick note. Belt and suspenders.</p><hr><h2 id="setting-the-table">&quot;Setting the Table&quot;</h2><p>Before you assign a task to someone, set it up properly. This means:</p><ul><li>Link to the relevant Google Doc, spreadsheet, or website inside the card</li><li>Attach any files they&apos;ll need &#x2014; logos, briefs, screenshots</li><li>Add a checklist if the steps are clear</li></ul><p>The goal is for whoever picks up that card to have everything they need without asking. Don&apos;t make people go hunting.</p><hr><h2 id="when-youre-done">When You&apos;re Done</h2><p>When you think a task is complete, mark it as <strong>Complete</strong> inside the card. This signals to the reviewer that it&apos;s ready to be looked at. The reviewer (usually your manager) will then archive the card, which removes it from the board.</p><p>Archiving isn&apos;t deleting &#x2014; you can always recover archived cards if you need to find something again.</p><hr><h2 id="quick-reference">Quick Reference</h2><ul><li><strong>Check Pending at least twice a day.</strong> That&apos;s where your work lives until you grab it.</li><li><strong>Update your card&apos;s list</strong> as you move through the work. Pending &#x2192; Working &#x2192; In Review.</li><li><strong>Comment on the card</strong> instead of sending a separate message about it &#x2014; keeps everything in one place.</li><li><strong>If a task is blocked</strong>, move it to On Hold and remove the due date.</li><li><strong>If something&apos;s urgent</strong>, drop the card link in Discord with a note.</li></ul><hr><h2 id="the-one-thing-to-remember">The One Thing to Remember</h2><p>Trello only works if everyone keeps their cards current. A board full of stale cards is just noise. A board that reflects real work in real time is the closest thing to everyone being in the same room.</p><p>Do your part and it works for everyone.</p>]]></content:encoded></item><item><title><![CDATA[Heartland - Haitian Workshop - Outreach Workflow]]></title><description><![CDATA[<!--kg-card-begin: html-->
<iframe width="560" height="315" src="https://www.youtube.com/embed/CcFR0_eKZes?si=ptyuXSGE5Qr3ZLCg" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>
<!--kg-card-end: html-->
<p></p><h2 id="how-each-day-is-structured">How Each Day Is Structured</h2><p>Every day there&apos;s a package of roughly 20&#x2013;30 records to work. That package is organized by sub-industry &#x2014; for example, bakery contacts one day, beverage contacts the next.</p><p>Here&apos;s how that day flows:</p><ol><li><strong>Emails drop first.</strong> Before or at</li></ol>]]></description><link>https://lmki.lumikha.co/heartland-haitian-workshop-outreach-workflow/</link><guid isPermaLink="false">69fc4c58667e5808375560d6</guid><dc:creator><![CDATA[Administrator]]></dc:creator><pubDate>Thu, 07 May 2026 08:30:12 GMT</pubDate><content:encoded><![CDATA[
<!--kg-card-begin: html-->
<iframe width="560" height="315" src="https://www.youtube.com/embed/CcFR0_eKZes?si=ptyuXSGE5Qr3ZLCg" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>
<!--kg-card-end: html-->
<p></p><h2 id="how-each-day-is-structured">How Each Day Is Structured</h2><p>Every day there&apos;s a package of roughly 20&#x2013;30 records to work. That package is organized by sub-industry &#x2014; for example, bakery contacts one day, beverage contacts the next.</p><p>Here&apos;s how that day flows:</p><ol><li><strong>Emails drop first.</strong> Before or at the start of your shift, emails go out to that day&apos;s package via Woodpecker. You won&apos;t manage these directly &#x2014; they&apos;re handled on the operations side and passed to you. These are short, direct emails that pitch the workshop. No beating around the bush.</li><li><strong>You make the calls.</strong> Work through the day&apos;s records. For each one: call, follow the script, log the outcome, then find and work the LinkedIn profile before moving to the next record.</li><li><strong>You check follow-ups.</strong> Before or alongside the day&apos;s new package, go back through everything from the previous days &#x2014; voicemails you left, LinkedIn requests you sent, emails that were opened but not answered. That&apos;s the iteration layer.</li></ol><p>Each of these three channels &#x2014; email, phone, LinkedIn &#x2014; has its own disposition codes in the spreadsheet. More on that below.</p><hr><h2 id="the-three-channels-and-what-you-do-in-each">The Three Channels and What You Do in Each</h2><h3 id="email-woodpecker">Email (Woodpecker)</h3><p>You won&apos;t be sending emails directly. Woodpecker handles that. What you will do is check outcomes &#x2014; who opened, who responded, who opted out &#x2014; and factor that into your calling and LinkedIn work.</p><ul><li>If someone <strong>opted out</strong> of email: you&apos;ll still likely call once, but if they explicitly say &quot;do not contact me&quot; on the phone, stop all outreach and note it.</li><li>If someone <strong>opened but didn&apos;t respond</strong>: that&apos;s a warm signal. They saw it. Call them.</li><li>If someone <strong>didn&apos;t open</strong>: still call. The email not landing doesn&apos;t mean the call won&apos;t.</li></ul><h3 id="phone-quo">Phone Quo)</h3><p>This is your primary tool. For each record:</p><ul><li><strong>Call.</strong> Use the script. Stay in the posture of solving their problem, not pitching a product.</li><li><strong>Voicemail?</strong> Leave a short, clear message. Log it. Cool that record for a couple of days before calling again &#x2014; don&apos;t hammer the same person back-to-back.</li><li><strong>Live answer?</strong> Work the conversation. Push toward enrollment. The CTA is the form, not &quot;let me know.&quot;</li><li><strong>Right party contact but not ready?</strong> Log it, note what they said, and plan your next touch accordingly.</li></ul><p>After every call, log the disposition in the spreadsheet before moving on.</p><h3 id="linkedin">LinkedIn</h3><p>LinkedIn is not a pitch channel &#x2014; at least not upfront. The connection request goes out with <strong>no pitch attached</strong>. Just connect. Once they accept, then you can follow up with the workshop angle.</p><p>Do LinkedIn as you work each record &#x2014; not in a batch at the start of your shift. Come to the record, do the call, then find the profile and send the request. That way it&apos;s tied to the same record and you&apos;re not context-switching all over the place.</p><p>Check your LinkedIn account daily. If someone accepted your request, follow up with a message. If requests are still pending, note them and wait.</p><hr><h2 id="the-spreadsheet-activity-vs-performance">The Spreadsheet: Activity vs. Performance</h2><p>The spreadsheet tracks two different things, and it&apos;s important to understand the difference.</p><p><strong>Activity</strong> = what you did (call made, voicemail left, LinkedIn request sent, email opened)</p><p><strong>Performance</strong> = outcomes that move toward enrollment (form clicked, enrolled, expressed strong interest)</p><p>Doing things is not the same as performing. You can make 30 calls and leave 30 voicemails and that&apos;s solid activity &#x2014; but it&apos;s not a closed deal. Both matter and both get tracked, but don&apos;t confuse the two.</p><p>Each channel has its own disposition codes in the spreadsheet. When you finish a call, you pick the disposition that best describes what happened. Same for LinkedIn. This data is what tells us which segments are responding, which sub-industries are converting, and where to press harder.</p><p>If a disposition is missing &#x2014; something happened that doesn&apos;t fit any of the options &#x2014; flag it. The spreadsheet is a work in progress and will be refined as the campaign runs.</p><hr><h2 id="how-to-work-the-records-the-right-mindset">How to Work the Records: The Right Mindset</h2><p><strong>Inhabit the data</strong>. Wear it like a shirt.</p><p>That means:</p><ul><li><strong>Look at the LinkedIn profile</strong> before or while you&apos;re working the record. You&apos;re not building a dossier &#x2014; you&apos;re just getting enough context to have a real conversation if they pick up.</li><li><strong>Know what happened last time.</strong> Did you leave a voicemail two days ago? Check. Did they open the email? Check. Did they accept your LinkedIn request? Check. Come to the call informed.</li><li><strong>Don&apos;t over-assume.</strong> The only qualification that matters is whether they have Haitian Creole-speaking employees. You can&apos;t know that for certain until you talk to them. Don&apos;t write someone off based on their title or company size. Stay open.</li></ul><hr><h2 id="the-follow-up-loop-this-is-where-results-come-from">The Follow-Up Loop (This Is Where Results Come From)</h2><p>The first pass through the list is about planting seeds. Most people won&apos;t say yes on the first contact. That&apos;s expected &#x2014; not a failure.</p><p>What you&apos;re building is recognition. The contact who opens the email, then gets a voicemail, then sees a LinkedIn request, then gets a second email, then gets another call &#x2014; that contact is moving through a process. By the time they pick up and hear &quot;this is Alelie calling from Heartland,&quot; there&apos;s a decent chance they already know why you&apos;re calling.</p><p>That&apos;s the flywheel. It doesn&apos;t spin on its own &#x2014; you have to keep going back through the list.</p><p><strong>Daily follow-up checklist:</strong></p><ul><li>Anyone who got a voicemail 2+ days ago &#x2192; call again</li><li>LinkedIn requests accepted &#x2192; send follow-up message with pitch</li><li>Email opens with no response &#x2192; call that day if possible</li><li>Anyone who said &quot;maybe later&quot; &#x2192; check if enough time has passed to re-engage</li><li>Opt-outs &#x2192; confirm noted and removed from active outreach</li></ul><hr><h2 id="quick-summary-of-the-daily-flow">Quick Summary of the Daily Flow</h2>
<!--kg-card-begin: html-->
<table class="min-w-full border-collapse text-sm leading-[1.7] whitespace-normal"><thead class="text-left"><tr><th scope="col" class="text-text-100 border-b-0.5 border-border-300/60 py-2 pr-4 align-top font-bold">Step</th><th scope="col" class="text-text-100 border-b-0.5 border-border-300/60 py-2 pr-4 align-top font-bold">What happens</th><th scope="col" class="text-text-100 border-b-0.5 border-border-300/60 py-2 pr-4 align-top font-bold">Your role</th></tr></thead><tbody><tr><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top">Emails drop</td><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top">Woodpecker sends sub-industry emails</td><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top">Review outcomes, note opens/responses</td></tr><tr><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top">Work the package</td><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top">Call the day&apos;s records</td><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top">Call &#x2192; log &#x2192; LinkedIn &#x2192; next record</td></tr><tr><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top">Follow up</td><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top">Check all prior records</td><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top">Callbacks, LinkedIn check-ins, re-engagements</td></tr><tr><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top">Log everything</td><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top">Dispositions in spreadsheet</td><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top">Every touch gets logged, every time</td></tr></tbody></table>
<!--kg-card-end: html-->
<hr><h2 id="the-one-thing-to-remember">The One Thing to Remember</h2><p>Follow-up is the name of the game. Sales don&apos;t happen on the first pitch. You&apos;re going to call someone, leave a voicemail, send a LinkedIn request, have them open the email, call again, and eventually get them on the phone &#x2014; and that&apos;s when the conversation that actually matters happens.</p><p>Keep working the list. Keep tending the garden. That&apos;s the job.</p>]]></content:encoded></item><item><title><![CDATA[Heartland - Haitian Workshop - Outreach Overview]]></title><description><![CDATA[<!--kg-card-begin: html-->
<iframe width="560" height="315" src="https://www.youtube.com/embed/-hJLVV5XWaE?si=lZ12vsnP7M-h-zHu" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>
<!--kg-card-end: html-->
<p></p><h2 id="the-one-thing-to-get-right-before-you-dial">The One Thing to Get Right Before You Dial</h2><p>Every call you make is not a sales call. It&apos;s a help call.</p><p>The people you&apos;re contacting don&apos;t know you, don&apos;t know Heartland, and aren&apos;t sitting around waiting to hear about</p>]]></description><link>https://lmki.lumikha.co/heartland-haitian-workshop-outreach-overview/</link><guid isPermaLink="false">69fc4b0d667e5808375560cb</guid><dc:creator><![CDATA[Administrator]]></dc:creator><pubDate>Thu, 07 May 2026 08:21:15 GMT</pubDate><content:encoded><![CDATA[
<!--kg-card-begin: html-->
<iframe width="560" height="315" src="https://www.youtube.com/embed/-hJLVV5XWaE?si=lZ12vsnP7M-h-zHu" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>
<!--kg-card-end: html-->
<p></p><h2 id="the-one-thing-to-get-right-before-you-dial">The One Thing to Get Right Before You Dial</h2><p>Every call you make is not a sales call. It&apos;s a help call.</p><p>The people you&apos;re contacting don&apos;t know you, don&apos;t know Heartland, and aren&apos;t sitting around waiting to hear about a Haitian Creole workshop. They have their own problems on their plate. Your job is to show up as someone who can solve one of those problems &#x2014; not someone trying to sell them something.</p><p>That&apos;s the posture. Help first. Everything else follows from that.</p><hr><h2 id="what-problem-are-you-actually-solving">What Problem Are You Actually Solving?</h2><p>When you call an HR professional at a food manufacturer, a bakery, or a healthcare facility, here&apos;s what&apos;s likely true about their workplace:</p><ul><li>They have Haitian Creole-speaking employees who may not fully understand English instructions.</li><li>Critical information &#x2014; safety briefings, policy explanations, onboarding paperwork &#x2014; is being delivered anyway, and nobody knows for certain it&apos;s landing.</li><li>When a new hire nods and signs the form, that&apos;s not confirmation they understood. It&apos;s just what you do on your third day when you want to keep the job.</li></ul><p>That&apos;s the problem. And it has real consequences:</p><p><strong>Operations.</strong> If an employee doesn&apos;t understand their instructions, the work suffers. That reflects on the person who gave the instructions &#x2014; meaning the HR or supervisor contact you&apos;re talking to.</p><p><strong>Safety.</strong> In manufacturing and food production, there&apos;s equipment that can hurt people. A misunderstood safety briefing isn&apos;t just an HR problem &#x2014; it&apos;s a liability.</p><p><strong>Their professional standing.</strong> When you help the HR person communicate more effectively with their workforce, you make them better at their job. That matters to them personally.</p><p>Keep these three angles in mind. You don&apos;t need to lead with all of them on every call &#x2014; but knowing them helps you respond when a contact pushes back or asks why this matters.</p><hr><h2 id="why-the-program-is-the-right-solution">Why the Program Is the Right Solution</h2><p>This isn&apos;t a language class. It&apos;s not about making HR professionals fluent in Haitian Creole. It&apos;s about moving them from &quot;I have no idea how to start this conversation&quot; to &quot;I can get through onboarding, confirm a safety instruction was understood, and know the information actually landed.&quot;</p><p>Three sessions. Live on Zoom. July 8, 15, and 22. $899 per participant. Capped at 7 &#x2014; max 2 per company. Enrollment closes July 1.</p><p>The cap is real and it&apos;s a feature, not a limitation. Small cohort = practical, scenario-based sessions with real-time feedback. That&apos;s how it works.</p><p>The Spanish program earlier this year proved the model. It filled on word of mouth. That&apos;s your social proof when you need it.</p><hr><h2 id="segmentation-know-who-youre-calling">Segmentation: Know Who You&apos;re Calling</h2><p>The contact list has been organized by industry and sub-industry. This matters because your call should feel relevant to <em>their</em> world, not generic.</p><p>If you&apos;re calling someone at a bakery or food processing facility, the example that lands is: <em>&quot;If your employee doesn&apos;t understand the production instructions and the product suffers, that reflects on the person who delivered those instructions &#x2014; which is you.&quot;</em></p><p>If you&apos;re calling healthcare, the frame shifts to patient safety and compliance.</p><p>The calling script itself won&apos;t change dramatically by segment, but being aware of their industry lets you speak more specifically if they engage. Don&apos;t fake it &#x2014; just use what you know.</p><hr><h2 id="iteration-youre-not-running-through-the-list-once">Iteration: You&apos;re Not Running Through the List Once</h2><p>This is one of the most important things to understand about how this campaign works.</p><p>Research shows that someone typically needs to encounter a brand <strong>seven times</strong> before they make a real connection with it. That means one email and one call is not enough. You&apos;re building toward recognition &#x2014; and that takes multiple touches across multiple channels.</p><p>Here&apos;s how the touches stack up for each contact:</p><ul><li><strong>Emails</strong> go out by industry/sub-industry on a rolling basis. These warm the contact before or between your calls.</li><li><strong>Your calls</strong> are the follow-up layer. Most of the time you&apos;ll get voicemail. That&apos;s fine &#x2014; leave a short, clear message and move on.</li><li><strong>LinkedIn</strong> outreach is an additional layer. As you work each record, find the contact&apos;s LinkedIn profile and send a connection request or message. Don&apos;t batch this at the start of your shift &#x2014; do it as you come to each record.</li></ul><p>You&apos;re going to work through this list more than once. The goal isn&apos;t to close everyone on the first pass. It&apos;s to get the touches in so that when you call and someone picks up, they already know who Heartland is.</p><p>That&apos;s when you hear: <em>&quot;Oh yeah, you&apos;re the Haitian workshop guys.&quot;</em> That&apos;s the goal. That&apos;s what a working campaign feels like.</p><hr><h2 id="the-daily-workflow">The Daily Workflow</h2><ol><li><strong>Emails go out first</strong> &#x2014; organized by sub-industry. That&apos;s the day&apos;s working package.</li><li><strong>Work the records</strong> &#x2014; call the contacts associated with that day&apos;s emails.<ul><li>Got voicemail? Leave a short message, log it, move on.</li><li>Got a live answer? Use the posture: you&apos;re calling to help, not to sell.</li><li>Got a real conversation? Push toward the enrollment form. The CTA is not &quot;let me know if you&apos;re interested.&quot; It&apos;s: <em>&quot;You can secure your spot right now at the link &#x2014; enrollment closes July 1 and it&apos;s capped at 7.&quot;</em></li></ul></li><li><strong>Work LinkedIn</strong> &#x2014; as you finish each record, find the profile and send your outreach. Don&apos;t stack this separately.</li><li><strong>If you have extra time</strong> &#x2014; go back and work older records for a second or third touch.</li></ol><hr><h2 id="the-cta-say-it-clearly">The CTA: Say It Clearly</h2><p>The goal of every conversation is to get the contact to the enrollment form: <a href="https://forms.gle/5kp8xz5EG5pF3X7h9?ref=lmki.lumikha.co"><strong>https://forms.gle/5kp8xz5EG5pF3X7h9</strong></a></p><p>More info at: <strong>heartlandlanguage.com/haitian-creole-hr</strong></p><p>Do not ask them to &quot;think about it.&quot; Do not offer to &quot;send more info and follow up.&quot; Move them toward the form. If they have questions, answer them. If they&apos;re not ready, note it and plan a follow-up touch.</p><p>Urgency is real: 7 spots, July 1 deadline, first come first served. You&apos;re not manufacturing pressure &#x2014; you&apos;re reporting facts.</p><hr><h2 id="quick-reference">Quick Reference</h2>
<!--kg-card-begin: html-->
<table class="min-w-full border-collapse text-sm leading-[1.7] whitespace-normal"><thead class="text-left"><tr><th scope="col" class="text-text-100 border-b-0.5 border-border-300/60 py-2 pr-4 align-top font-bold">What</th><th scope="col" class="text-text-100 border-b-0.5 border-border-300/60 py-2 pr-4 align-top font-bold">Detail</th></tr></thead><tbody><tr><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top">Program</td><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top">Intensive Haitian Creole for Human Resources</td></tr><tr><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top">Dates</td><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top">July 8, 15, 22</td></tr><tr><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top">Time</td><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top">11:00 AM &#x2013; 12:00 PM CST</td></tr><tr><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top">Format</td><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top">Live on Zoom</td></tr><tr><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top">Price</td><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top">$899/participant</td></tr><tr><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top">Cap</td><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top">7 participants (max 2/company)</td></tr><tr><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top">Deadline</td><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top">July 1 (or when full)</td></tr><tr><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top">Enrollment</td><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top">forms.gle/5kp8xz5EG5pF3X7h9</td></tr><tr><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top">Info page</td><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top">heartlandlanguage.com/haitian-creole-hr</td></tr></tbody></table>
<!--kg-card-end: html-->
<hr><h2 id="the-mindset-to-carry-into-every-call">The Mindset to Carry Into Every Call</h2><p>You&apos;re not interrupting someone&apos;s day to pitch them a product. You&apos;re calling because their organization has a communication problem that creates real risk &#x2014; for their employees, their operations, and their own professional credibility &#x2014; and you have a practical, time-limited way to help them fix it.</p><p>Start there. Stay there. The enrollment follows.</p>]]></content:encoded></item><item><title><![CDATA[LAMB - HubSpot - Schedule Meetings]]></title><description><![CDATA[You have a lead on the line who is interested. Because our HubSpot access level doesn't allow direct meeting reassignment, we use a proxy booking method. ]]></description><link>https://lmki.lumikha.co/lamb-hubspot-schedule-meetings/</link><guid isPermaLink="false">69ae87a5667e5808375560ae</guid><category><![CDATA[Back-office]]></category><category><![CDATA[Sales]]></category><dc:creator><![CDATA[Administrator]]></dc:creator><pubDate>Mon, 09 Mar 2026 08:45:37 GMT</pubDate><content:encoded><![CDATA[<p>You have a lead on the line who is interested. Because our HubSpot access level doesn&apos;t allow direct meeting reassignment, we use a proxy booking method. You will act as the lead to book the meeting directly into the closer&#x2019;s calendar.</p>
<!--kg-card-begin: html-->
<iframe width="560" height="315" src="https://www.youtube.com/embed/rGRXofUrHkU?si=8yHJvCAUWn4PcdHu" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>
<!--kg-card-end: html-->
<p></p><h3 id="why-this-workflow-is-unique">Why This Workflow is Unique</h3><p>Most systems allow you to &quot;hand off&quot; a meeting. Here, you will use our public booking page. This ensures:</p><ul><li><strong>Real-time Availability:</strong> You only see times the closer is actually free.</li><li><strong>Automatic Opt-in:</strong> Booking through this page automatically opts the lead into our mailing list.</li><li><strong>Immediate Confirmation:</strong> The lead gets an invite instantly.</li></ul><hr><h3 id="1-the-preparation-the-always-open-tab">1. The Preparation: &quot;The Always-Open Tab&quot;</h3><p>While dialing, you must always have the <strong>Public Meeting Page</strong> open in a separate browser tab. Do not wait until the lead says &quot;yes&quot; to find the link.</p><h3 id="2-the-booking-process-the-workaround">2. The Booking Process (The &quot;Workaround&quot;)</h3><p>When a lead agrees to a 15-minute discovery call:</p><ol><li><strong>Select the Time Zone:</strong> Always find and select <strong>US Eastern Time</strong> first. This ensures you and the lead are looking at the same clock.</li><li><strong>Pick a Slot:</strong> Aim for the &quot;Sustainable Windows&quot;:<ul><li><strong>Morning Window:</strong> (Starting around 3:00 AM your time / 4:00 PM their time).</li><li><strong>Evening Window:</strong> For late-day wrap-ups.</li></ul></li><li><strong>Enter Lead Information:</strong> You are acting <em>as</em> the lead. Enter:<ul><li>Lead&#x2019;s First &amp; Last Name.</li><li>Lead&#x2019;s Email Address.</li><li><strong>Note:</strong> You do <em>not</em> need to add yourself as a guest. The system will handle the rest.</li></ul></li></ol><h3 id="3-rules-of-the-calendar">3. Rules of the Calendar</h3><ul><li><strong>The 24-Hour Block:</strong> You cannot book a meeting for &quot;later today.&quot; The system requires 24 hours&apos; notice so the closer can prepare.</li><li><strong>The &quot;15-Minute&quot; Rule:</strong> Always push for a <strong>15-minute</strong> meeting. It sounds lightweight, easy, and follows our script.</li><li><strong>The Manual Override:</strong> If the lead <em>insists</em> on a time that isn&apos;t on the calendar:<ol><li>Don&apos;t lose the lead!</li><li>Finish the call.</li><li>Immediately create a <strong>HubSpot Task</strong> for the closer: <em>&quot;Manual Booking Request: [Name] at [Time].&quot;</em></li></ol></li></ul><hr><h3 id="4-how-to-apply-the-learning">4. How to Apply the Learning</h3><ul><li><strong>Act as the User:</strong> When filling out the form, use the lead&apos;s email. This triggers the calendar invite to <em>them</em> and the notification to the <em>closer</em>.</li><li><strong>Confirm Privacy:</strong> You must click the &quot;Agree to Data Privacy&quot; box. This is what legally opts them into our future marketing sequences.</li><li><strong>Reset the Tab:</strong> After booking, the page will redirect to a &quot;Services&quot; page. Simply hit &quot;back&quot; or reload the booking link so you&#x2019;re ready for the next call.</li></ul>]]></content:encoded></item><item><title><![CDATA[LAMB - HubSpot - Dialing Dispositions]]></title><description><![CDATA[The Disposition is an important piece of the puzzle—it’s the "What happened?" of every call.]]></description><link>https://lmki.lumikha.co/hubspot-dialing-dispositions/</link><guid isPermaLink="false">69ae770e667e580837556091</guid><category><![CDATA[Back-office]]></category><category><![CDATA[Sales]]></category><dc:creator><![CDATA[Administrator]]></dc:creator><pubDate>Mon, 09 Mar 2026 07:33:58 GMT</pubDate><content:encoded><![CDATA[<p>This module focuses on the &quot;In Progress&quot; stage of the lead lifecycle. You are actively reaching out via phone, LinkedIn, and email. The <strong>Disposition</strong> is an important piece of the puzzle&#x2014;it&#x2019;s the &quot;What happened?&quot; of every call.</p><h3 id="why-dispositions-matter">Why Dispositions Matter</h3><p>We don&#x2019;t track call outcomes just to watch the numbers. We do it to identify:</p><ul><li><strong>Data Quality:</strong> Are we calling the right numbers?</li><li><strong>Performance Bottlenecks:</strong> Is there a technical lag (latency) making people hang up?</li><li><strong>Lead Quality:</strong> Are we talking to the right people?</li><li><strong>Efficiency:</strong> How can we stop wasting time on dead ends and double down on what works?</li></ul>
<!--kg-card-begin: html-->
<iframe width="560" height="315" src="https://www.youtube.com/embed/UlLN8JtWs8E?si=9AvpTiCFQ4GqcwpQ" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>
<!--kg-card-end: html-->
<hr><h3 id="1-the-setup-where-we-are-in-the-lifecycle">1. The Setup: Where We Are in the Lifecycle</h3><p>Before you even dial, you need to know where the contact stands.</p><ul><li><strong>Lifecycle Stage:</strong> Lead (We haven&apos;t qualified them for sales yet).</li><li><strong>Lead Status:</strong> In Progress (We are actively &quot;chasing&quot; them).</li><li><strong>Channels:</strong> Phone, Email, and LinkedIn.</li></ul><h3 id="2-the-what-happened-common-dispositions">2. The &quot;What Happened&quot;: Common Dispositions</h3><p>When the call ends, you must tag it correctly in HubSpot. Here is your cheat sheet for what different outcomes actually mean:</p>
<!--kg-card-begin: html-->
<table data-path-to-node="14" style="margin-bottom: 32px; font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><thead style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><tr style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><td style="border: 1px solid; font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><strong style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important; margin-bottom: 0px !important;">Disposition</strong></td><td style="border: 1px solid; font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><strong style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important; margin-bottom: 0px !important;">What it means</strong></td><td style="border: 1px solid; font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><strong style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important; margin-bottom: 0px !important;">Action/Insight</strong></td></tr></thead><tbody style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><tr style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><td style="border: 1px solid; font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><span data-path-to-node="14,1,0,0" style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><b data-path-to-node="14,1,0,0" data-index-in-node="0" style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;">No Answer</b></span></td><td style="border: 1px solid; font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><span data-path-to-node="14,1,1,0" style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;">The phone rang but nobody picked up.</span></td><td style="border: 1px solid; font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><span data-path-to-node="14,1,2,0" style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;">Indicates a potential <b data-path-to-node="14,1,2,0" data-index-in-node="22" style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;">data problem</b> or wrong calling time.</span></td></tr><tr style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><td style="border: 1px solid; font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><span data-path-to-node="14,2,0,0" style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><b data-path-to-node="14,2,0,0" data-index-in-node="0" style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;">Early Hangup</b></span></td><td style="border: 1px solid; font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><span data-path-to-node="14,2,1,0" style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;">They hung up before you could finish your intro.</span></td><td style="border: 1px solid; font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><span data-path-to-node="14,2,2,0" style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;">Often caused by <b data-path-to-node="14,2,2,0" data-index-in-node="16" style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;">latency</b> (dead air) or they flagged you as a telemarketer.</span></td></tr><tr style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><td style="border: 1px solid; font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><span data-path-to-node="14,3,0,0" style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><b data-path-to-node="14,3,0,0" data-index-in-node="0" style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;">Gatekeeper</b></span></td><td style="border: 1px solid; font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><span data-path-to-node="14,3,1,0" style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;">You hit a receptionist or assistant.</span></td><td style="border: 1px solid; font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><span data-path-to-node="14,3,2,0" style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><b data-path-to-node="14,3,2,0" data-index-in-node="0" style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;">Pro Tip:</b> Be confident. Ask for help: &quot;When is the best time to reach [Name]?&quot;</span></td></tr><tr style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><td style="border: 1px solid; font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><span data-path-to-node="14,4,0,0" style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><b data-path-to-node="14,4,0,0" data-index-in-node="0" style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;">Call Back Requested</b></span></td><td style="border: 1px solid; font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><span data-path-to-node="14,4,1,0" style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;">They are busy but willing to talk later.</span></td><td style="border: 1px solid; font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><span data-path-to-node="14,4,2,0" style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><b data-path-to-node="14,4,2,0" data-index-in-node="0" style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;">Crucial:</b> Immediately create a <b data-path-to-node="14,4,2,0" data-index-in-node="30" style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;">Task</b> in HubSpot to honor this. It builds trust!</span></td></tr><tr style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><td style="border: 1px solid; font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><span data-path-to-node="14,5,0,0" style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><b data-path-to-node="14,5,0,0" data-index-in-node="0" style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;">Not Interested</b></span></td><td style="border: 1px solid; font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><span data-path-to-node="14,5,1,0" style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;">They explicitly said they don&apos;t want the service.</span></td><td style="border: 1px solid; font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><span data-path-to-node="14,5,2,0" style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;">Tag it and move on. We stop pursuing to keep the database clean.</span></td></tr><tr style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><td style="border: 1px solid; font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><span data-path-to-node="14,6,0,0" style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><b data-path-to-node="14,6,0,0" data-index-in-node="0" style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;">Bad Number</b></span></td><td style="border: 1px solid; font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><span data-path-to-node="14,6,1,0" style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;">Fax machine, out of service, or disconnected.</span></td><td style="border: 1px solid; font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><span data-path-to-node="14,6,2,0" style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;">Vital data! This helps us stop wasting time on &quot;ghost&quot; leads.</span></td></tr><tr style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><td style="border: 1px solid; font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><span data-path-to-node="14,7,0,0" style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><b data-path-to-node="14,7,0,0" data-index-in-node="0" style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;">Appointment Set</b></span></td><td style="border: 1px solid; font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><span data-path-to-node="14,7,1,0" style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><b data-path-to-node="14,7,1,0" data-index-in-node="0" style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;">The Win!</b> They agreed to a meeting.</span></td><td style="border: 1px solid; font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><span data-path-to-node="14,7,2,0" style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;">This triggers your bounty and starts the real sales conversation.</span></td></tr></tbody></table>
<!--kg-card-end: html-->
<h3 id="3-how-to-apply-the-learning">3. How to Apply the Learning</h3><ul><li><strong>Respect the &quot;Call Back&quot;:</strong> If a lead says &quot;Not now,&quot; and you call back exactly when you promised, you&#x2019;ve already proven you&#x2019;re a professional. That&#x2019;s how we win customers.</li><li><strong>The &quot;Confidence&quot; Hack:</strong> When dealing with gatekeepers, don&apos;t sound like you&apos;re asking for permission. Speak as if you are expected. &quot;I&apos;m calling to speak with [Name] regarding [Topic].&quot;</li><li><strong>Update the CRM Immediately:</strong> Data decays quickly. Log the disposition the second the call ends so the AI Agents and marketing team have real-time info.</li></ul><hr><h3 id="summary">Summary</h3><ul><li><strong>Dispositions</strong> are the metrics that tell us how our calls are actually going.</li><li>They help us distinguish between <strong>technical issues</strong> (latency), <strong>data issues</strong> (bad numbers), and <strong>sales issues</strong> (not interested).</li><li><strong>HubSpot tasks</strong> are your best friend for managing call-back requests and maintaining professional integrity.</li></ul>]]></content:encoded></item><item><title><![CDATA[LAMB - Lifecycle Stage vs Lead Status in HubSpot]]></title><description><![CDATA[These two HubSpot properties are alike, but they serve different purposes.]]></description><link>https://lmki.lumikha.co/lifecycle-stage-vs-lead-status-in-hubspot-2/</link><guid isPermaLink="false">69ae5f50667e58083755606a</guid><category><![CDATA[Back-office]]></category><category><![CDATA[Sales]]></category><dc:creator><![CDATA[Administrator]]></dc:creator><pubDate>Mon, 09 Mar 2026 06:21:38 GMT</pubDate><content:encoded><![CDATA[<p>These two properties are alike, but they serve different purposes.</p>
<!--kg-card-begin: html-->
<iframe width="560" height="315" src="https://www.youtube.com/embed/_4YM8lx3eyo?si=fBZ5A-24_qaxxOHi" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>
<!--kg-card-end: html-->
<hr><h3 id="lifecycle-stage">Lifecycle Stage</h3>
<!--kg-card-begin: html-->
<table class="min-w-full border-collapse text-sm leading-[1.7] whitespace-normal"><thead class="text-left"><tr><th scope="col" class="text-text-100 border-b-0.5 border-border-300/60 py-2 pr-4 align-top font-bold">Stage</th><th scope="col" class="text-text-100 border-b-0.5 border-border-300/60 py-2 pr-4 align-top font-bold">Description</th></tr></thead><tbody><tr><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top"><strong>Lead</strong></td><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top">Showed interest (filled a form, downloaded something)</td></tr><tr><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top"><strong>Marketing Qualified Lead (MQL)</strong></td><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top">Marketing has vetted them as worth pursuing</td></tr><tr><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top"><strong>Sales Qualified Lead (SQL)</strong></td><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top">Sales has confirmed they&apos;re worth a direct conversation</td></tr><tr><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top"><strong>Opportunity</strong></td><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top">An active deal is open with them</td></tr><tr><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top"><strong>Customer</strong></td><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top">They&apos;ve bought</td></tr><tr><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top"><strong>Former Customer</strong></td><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top">Previously bought but no longer an active customer</td></tr><tr><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top"><strong>Evangelist</strong></td><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top">They refer others</td></tr><tr><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top"><strong>Subscriber</strong></td><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top">Opted into your content/blog</td></tr><tr><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top"><strong>Other</strong></td><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top">Doesn&apos;t fit the funnel</td></tr></tbody></table>
<!--kg-card-end: html-->
<hr><h3 id="lead-status">Lead Status</h3>
<!--kg-card-begin: html-->
<table class="min-w-full border-collapse text-sm leading-[1.7] whitespace-normal"><thead class="text-left"><tr><th scope="col" class="text-text-100 border-b-0.5 border-border-300/60 py-2 pr-4 align-top font-bold">Status</th><th scope="col" class="text-text-100 border-b-0.5 border-border-300/60 py-2 pr-4 align-top font-bold">Description</th></tr></thead><tbody><tr><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top"><strong>New</strong></td><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top">Just came in, not yet worked</td></tr><tr><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top"><strong>Open</strong></td><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top">Being reviewed</td></tr><tr><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top"><strong>In Progress</strong></td><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top">We&apos;re actively engaging</td></tr><tr><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top"><strong>Connected</strong></td><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top">Had a conversation</td></tr><tr><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top"><strong>Open Deal</strong></td><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top">A deal has been created</td></tr><tr><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top"><strong>Unqualified</strong></td><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top">Not a fit</td></tr><tr><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top"><strong>Lost</strong></td><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top">Good fit but didn&apos;t close</td></tr><tr><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top"><strong>Closed</strong></td><td class="border-b-0.5 border-border-300/30 py-2 pr-4 align-top">Active pursuit ended &#x2014; record retained in HubSpot for future nurture or re-engagement</td></tr></tbody></table>
<!--kg-card-end: html-->
<hr><h3 id="the-simple-mental-model">The Simple Mental Model</h3><blockquote><strong>Lifecycle Stage</strong> = <em>Where are they in the relationship?</em> (Marketing + Sales view) <br><strong>Lead Status</strong> = <em>What is the rep doing with them right now?</em> (Sales operational view)</blockquote><p>A contact can be active for weeks while their lead status cycles through <em>In Progress &#x2192; Connected &#x2192; In Progress</em> multiple times.</p><hr><h3 id="common-mistake-to-avoid">Common Mistake to Avoid</h3><p>Don&apos;t use Lead Status as a substitute for Lifecycle Stage. They work <strong>together</strong> &#x2014; Lifecycle Stage tells you the macro position, Lead Status tells you the micro activity. Both should be updated as contacts progress.</p>]]></content:encoded></item><item><title><![CDATA[LAMB - Appointment Campaign - HubSpot Life Cycle]]></title><description><![CDATA[This module defines how we categorize our contacts, ensuring that both our human team members and AI Agents know exactly where a person stands in our journey.]]></description><link>https://lmki.lumikha.co/hubspot-lead-life-cycle/</link><guid isPermaLink="false">69ae0a77667e580837556046</guid><category><![CDATA[Back-office]]></category><category><![CDATA[Sales]]></category><dc:creator><![CDATA[Administrator]]></dc:creator><pubDate>Mon, 09 Mar 2026 00:04:26 GMT</pubDate><content:encoded><![CDATA[<p>Welcome to the <strong>HubSpot Life Cycle</strong> module. In any high-performing marketing team&#x2014;especially those working across borders&#x2014;data integrity is everything. This module defines how we categorize our contacts, ensuring that both our human team members and AI Agents know exactly where a person stands in our journey</p><h3 id="why-this-matters">Why This Matters</h3><p>If we don&apos;t know where a lead is in their life cycle, we risk sending the wrong message at the wrong time.</p><ul><li><strong>For Marketing Teams:</strong> It ensures you aren&apos;t hard selling someone who just wanted a newsletter.</li><li><strong>For AI Agents:</strong> It provides the context needed to generate appropriate email follow-ups or voice scripts.</li><li><strong>For the Business:</strong> It allows us to track conversion rates from &quot;Raw Lead&quot; to &quot;Paying Customer.&quot;</li></ul><hr><figure class="kg-card kg-image-card kg-card-hascaption"><img src="https://lmki.lumikha.co/content/images/2026/03/2026-03-09_08-28-37.jpg" class="kg-image" alt loading="lazy" width="2000" height="1084" srcset="https://lmki.lumikha.co/content/images/size/w600/2026/03/2026-03-09_08-28-37.jpg 600w, https://lmki.lumikha.co/content/images/size/w1000/2026/03/2026-03-09_08-28-37.jpg 1000w, https://lmki.lumikha.co/content/images/size/w1600/2026/03/2026-03-09_08-28-37.jpg 1600w, https://lmki.lumikha.co/content/images/size/w2400/2026/03/2026-03-09_08-28-37.jpg 2400w" sizes="(min-width: 720px) 720px"><figcaption><span style="white-space: pre-wrap;">Contacts Table View - Scroll Right to See Lifecycle Column</span></figcaption></figure><figure class="kg-card kg-image-card kg-card-hascaption"><img src="https://lmki.lumikha.co/content/images/2026/03/2026-03-09_08-29-33.jpg" class="kg-image" alt loading="lazy" width="2000" height="1084" srcset="https://lmki.lumikha.co/content/images/size/w600/2026/03/2026-03-09_08-29-33.jpg 600w, https://lmki.lumikha.co/content/images/size/w1000/2026/03/2026-03-09_08-29-33.jpg 1000w, https://lmki.lumikha.co/content/images/size/w1600/2026/03/2026-03-09_08-29-33.jpg 1600w, https://lmki.lumikha.co/content/images/size/w2400/2026/03/2026-03-09_08-29-33.jpg 2400w" sizes="(min-width: 720px) 720px"><figcaption><span style="white-space: pre-wrap;">The Lifecycle Stage Column - All the Column Data is Edit-able</span></figcaption></figure><figure class="kg-card kg-image-card kg-card-hascaption"><img src="https://lmki.lumikha.co/content/images/2026/03/2026-03-09_08-30-47.jpg" class="kg-image" alt loading="lazy" width="2000" height="1084" srcset="https://lmki.lumikha.co/content/images/size/w600/2026/03/2026-03-09_08-30-47.jpg 600w, https://lmki.lumikha.co/content/images/size/w1000/2026/03/2026-03-09_08-30-47.jpg 1000w, https://lmki.lumikha.co/content/images/size/w1600/2026/03/2026-03-09_08-30-47.jpg 1600w, https://lmki.lumikha.co/content/images/size/w2400/2026/03/2026-03-09_08-30-47.jpg 2400w" sizes="(min-width: 720px) 720px"><figcaption><span style="white-space: pre-wrap;">Change the Lifecycle Stage Here</span></figcaption></figure><hr><h3 id="1-navigating-the-hubspot-interface">1. Navigating the HubSpot Interface</h3><p>Before defining the stages, you need to know where to change them. In HubSpot, you have two primary ways to manage these stages:</p><ul><li><strong>Table View:</strong> Best for dialing or bulk tasks. It allows you to see many records at once.Uses a simple dropdown menu to change stages quickly.</li><li><strong>Record Detail:</strong> Used when you are deep-diving into a specific contact (e.g., while booking a meeting).</li></ul><figure class="kg-card kg-image-card kg-card-hascaption"><img src="https://lmki.lumikha.co/content/images/2026/03/2026-03-09_08-32-28.jpg" class="kg-image" alt loading="lazy" width="2000" height="1084" srcset="https://lmki.lumikha.co/content/images/size/w600/2026/03/2026-03-09_08-32-28.jpg 600w, https://lmki.lumikha.co/content/images/size/w1000/2026/03/2026-03-09_08-32-28.jpg 1000w, https://lmki.lumikha.co/content/images/size/w1600/2026/03/2026-03-09_08-32-28.jpg 1600w, https://lmki.lumikha.co/content/images/size/w2400/2026/03/2026-03-09_08-32-28.jpg 2400w" sizes="(min-width: 720px) 720px"><figcaption><span style="white-space: pre-wrap;">From the Table View, Select the Record to See More Detail and Edit</span></figcaption></figure><figure class="kg-card kg-image-card kg-card-hascaption"><img src="https://lmki.lumikha.co/content/images/2026/03/2026-03-09_08-33-22.jpg" class="kg-image" alt loading="lazy" width="2000" height="1084" srcset="https://lmki.lumikha.co/content/images/size/w600/2026/03/2026-03-09_08-33-22.jpg 600w, https://lmki.lumikha.co/content/images/size/w1000/2026/03/2026-03-09_08-33-22.jpg 1000w, https://lmki.lumikha.co/content/images/size/w1600/2026/03/2026-03-09_08-33-22.jpg 1600w, https://lmki.lumikha.co/content/images/size/w2400/2026/03/2026-03-09_08-33-22.jpg 2400w" sizes="(min-width: 720px) 720px"><figcaption><span style="white-space: pre-wrap;">Access the Lifecycle Dropdown Here</span></figcaption></figure><hr><h3 id="2-the-marketing-sales-track">2. The Marketing &amp; Sales Track</h3><p>This is the journey from a stranger to a customer. We break it down into these specific categories:</p>
<!--kg-card-begin: html-->
<table data-path-to-node="14" style="margin-bottom: 32px; font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><thead style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><tr style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><td style="border: 1px solid; font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><strong style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important; margin-bottom: 0px !important;">Stage</strong></td><td style="border: 1px solid; font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><strong style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important; margin-bottom: 0px !important;">Definition</strong></td><td style="border: 1px solid; font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><strong style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important; margin-bottom: 0px !important;">When to use it</strong></td></tr></thead><tbody style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><tr style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><td style="border: 1px solid; font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><span data-path-to-node="14,1,0,0" style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><b data-path-to-node="14,1,0,0" data-index-in-node="0" style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;">Lead</b></span></td><td style="border: 1px solid; font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><span data-path-to-node="14,1,1,0" style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;">Raw data.</span></td><td style="border: 1px solid; font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><span data-path-to-node="14,1,2,0" style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;">Recently imported lists or cold contacts we haven&apos;t reached yet.</span></td></tr><tr style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><td style="border: 1px solid; font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><span data-path-to-node="14,2,0,0" style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><b data-path-to-node="14,2,0,0" data-index-in-node="0" style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;">MQL (Marketing Qualified Lead)</b></span></td><td style="border: 1px solid; font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><span data-path-to-node="14,2,1,0" style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;">Passive interest.</span></td><td style="border: 1px solid; font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><span data-path-to-node="14,2,2,0" style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;">Someone who filled out a web form or replied to a cold email but <b data-path-to-node="14,2,2,0" data-index-in-node="65" style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;">hasn&apos;t</b> had a conversation yet.</span></td></tr><tr style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><td style="border: 1px solid; font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><span data-path-to-node="14,3,0,0" style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><b data-path-to-node="14,3,0,0" data-index-in-node="0" style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;">SQL (Sales Qualified Lead)</b></span></td><td style="border: 1px solid; font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><span data-path-to-node="14,3,1,0" style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;">Human-verified interest.</span></td><td style="border: 1px solid; font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><span data-path-to-node="14,3,2,0" style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;">Someone you have spoken to, qualified, and who is interested in an appointment or follow-up.</span></td></tr><tr style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><td style="border: 1px solid; font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><span data-path-to-node="14,4,0,0" style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><b data-path-to-node="14,4,0,0" data-index-in-node="0" style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;">Opportunity</b></span></td><td style="border: 1px solid; font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><span data-path-to-node="14,4,1,0" style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;">A &quot;Bona Fide&quot; deal.</span></td><td style="border: 1px solid; font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><span data-path-to-node="14,4,2,0" style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;">When there is a legitimate, active interest in a specific project or service.</span></td></tr><tr style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><td style="border: 1px solid; font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><span data-path-to-node="14,5,0,0" style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><b data-path-to-node="14,5,0,0" data-index-in-node="0" style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;">Customer</b></span></td><td style="border: 1px solid; font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><span data-path-to-node="14,5,1,0" style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;">Paying client.</span></td><td style="border: 1px solid; font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><span data-path-to-node="14,5,2,0" style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;">The deal is closed and the contract is signed.</span></td></tr><tr style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><td style="border: 1px solid; font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><span data-path-to-node="14,6,0,0" style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><b data-path-to-node="14,6,0,0" data-index-in-node="0" style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;">Former Customer</b></span></td><td style="border: 1px solid; font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><span data-path-to-node="14,6,1,0" style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;">Past client.</span></td><td style="border: 1px solid; font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><span data-path-to-node="14,6,2,0" style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;">No longer active, but still considered a future opportunity for new projects.</span></td></tr><tr style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><td style="border: 1px solid; font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><span data-path-to-node="14,7,0,0" style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><b data-path-to-node="14,7,0,0" data-index-in-node="0" style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;">Subscriber</b></span></td><td style="border: 1px solid; font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><span data-path-to-node="14,7,1,0" style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;">Long-term nurture.</span></td><td style="border: 1px solid; font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><span data-path-to-node="14,7,2,0" style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;">Leads that didn&apos;t convert to a deal but stay on our mailing list for future updates.</span></td></tr><tr style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><td style="border: 1px solid; font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><span data-path-to-node="14,8,0,0" style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><b data-path-to-node="14,8,0,0" data-index-in-node="0" style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;">Evangelist</b></span></td><td style="border: 1px solid; font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><span data-path-to-node="14,8,1,0" style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;">The Recommenders.</span></td><td style="border: 1px solid; font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><span data-path-to-node="14,8,2,0" style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;">People in our network, vendors, or industry peers who won&apos;t buy but will refer us.</span></td></tr></tbody></table>
<!--kg-card-end: html-->
<hr><h3 id="3-the-recruiting-track">3. The Recruiting Track</h3><p>We also use HubSpot to manage talent. If you are handling applicants, use these specific stages:</p><ul><li><strong>Applicant:</strong> Someone who applied via our job board.</li><li><strong>On Hold:</strong> Someone we want to save for a later date.</li><li><strong>Interview Candidate:</strong> Someone currently moving through the interview process.</li><li><strong>Offer:</strong> The final stage before they become a team member.</li></ul><hr><h3 id="summary">Summary</h3><ul><li><strong>MQL vs. SQL:</strong> The difference is the <strong>conversation</strong>. MQLs are form-fills; SQLs are people we&#x2019;ve actually qualified via a call or deep engagement.</li><li><strong>Subscribers:</strong> These are &quot;not right now&quot; leads. We keep them in the loop via newsletters so we stay top-of-mind.</li><li><strong>Evangelists:</strong> These are our fans. They are valuable for word-of-mouth, even if they never sign a check.</li></ul>]]></content:encoded></item><item><title><![CDATA[LAMB - Appointment Campaign - Script Overview]]></title><description><![CDATA[<h3 id="why-this-matters">Why This Matters</h3><p>In B2B outbound marketing, the first 7 seconds determine whether you are viewed as an intrusive telemarketer or a valuable business peer. </p><p>For us, the goal isn&apos;t just to read a script&#x2014;it&apos;s to navigate a conversation that bridges our <strong>Florida Location</strong></p>]]></description><link>https://lmki.lumikha.co/lamb-appointment-campaign-script-overview/</link><guid isPermaLink="false">69a7cd11667e580837556026</guid><dc:creator><![CDATA[Administrator]]></dc:creator><pubDate>Wed, 04 Mar 2026 06:30:49 GMT</pubDate><content:encoded><![CDATA[<h3 id="why-this-matters">Why This Matters</h3><p>In B2B outbound marketing, the first 7 seconds determine whether you are viewed as an intrusive telemarketer or a valuable business peer. </p><p>For us, the goal isn&apos;t just to read a script&#x2014;it&apos;s to navigate a conversation that bridges our <strong>Florida Location</strong> with our <strong>high-quality Philippine operations</strong>.</p><p>This module frames the call as a &quot;service delivery&quot; rather than a &quot;sales pitch,&quot; emphasizing a Western-managed, cost-effective solution for busy entrepreneurs.</p>
<!--kg-card-begin: html-->
<iframe width="560" height="315" src="https://www.youtube.com/embed/-mL-jdMNvhI?si=9bcZyoH_VWkwLgi2" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>
<!--kg-card-end: html-->
<p></p><hr><h3 id="1-the-critical-opening-the-7-second-rule">1. The Critical Opening (The 7-Second Rule)</h3><p>The inflection point of every call happens almost immediately.</p><ul><li><strong>The Goal:</strong> Overcome technical latency (the delay on the line) and gain permission to continue.</li><li><strong>Tone:</strong> Sound <strong>confident and relaxed</strong>. You are offering a solution that saves money and generates leads.</li><li><strong>Action:</strong> Get into the script quickly to signal professional intent.</li></ul><h3 id="2-qualification-mirroring">2. Qualification &amp; Mirroring</h3><p>Once you have permission, you must understand the lead&apos;s current situation.</p><ul><li><strong>Mirroring:</strong> Adjust your tone and pace to match the person on the other end. This builds instant rapport.</li><li><strong>The Small Ask:</strong> Ask a simple question like, <em>&quot;Do you currently use any marketing services?&quot;</em><ul><li><strong>If Yes:</strong> They likely have gaps in value or consistency.</li><li><strong>If No:</strong> They are likely too busy or think it&apos;s too expensive. Both are &quot;open doors&quot; for our solution.</li></ul></li></ul><h3 id="3-framing-the-problem-the-solution">3. Framing the Problem &amp; The Solution</h3><p>We lead with the <strong>Corporate Newsletter</strong> because it is low-impact, high-value, and easy to understand.</p><ul><li><strong>The Problem Frame:</strong> &quot;Most firms feel they aren&apos;t getting value for what they pay, or they are too busy to be consistent.&quot;</li><li><strong>The Solution (The &quot;Miami-Manila&quot; Model):</strong> We are a full-service team managed by our Miami office with a back-office engine in the Philippines.</li><li><strong>The Offer:</strong> We handle data consolidation, AI-driven audience research, design, and distribution of three newsletter options per month with detailed reporting.</li></ul><h3 id="4-handling-objections-the-courtesy-close">4. Handling Objections &amp; The Courtesy Close</h3><p>Not every call will result in an appointment.</p><ul><li><strong>The Send an Email Brush-off:</strong> Agree to send the email, but immediately try to tie them down to a specific follow-up time.</li><li><strong>The Persistence Rule:</strong> If a lead is clearly not interested, give them a <strong>Courtesy Close</strong> and disposition the call. We do not badger leads; we look for fit.</li><li><strong>Proof of Work:</strong> Use our work with <em>Heartland</em> as a credibility anchor in follow-up emails to show we are already doing this successfully for others.</li></ul><h3 id="5-the-feedback-loop">5. The Feedback Loop</h3><p>This script is a living document.</p><ul><li><strong>Log Everything:</strong> Use the notes section to record <em>where</em> people get off the call.</li><li><strong>Identify the Drop-off Point:</strong> If they hang up during the &quot;Problem Frame,&quot; we change the language of the &quot;Qualification&quot; step. If they drop during the &quot;Solution,&quot; we swap the tool we are offering.</li></ul><hr><h3 id="summary">Summary</h3><ul><li><strong>Speed and Tone:</strong> Win the first 7 seconds with confidence.</li><li><strong>Lead with Newsletters:</strong> Use them as a foot in the door to higher-tier services.</li><li><strong>The Hybrid Model:</strong> Position the service as Western Managed (Miami) with Offshore Quality (Philippines).</li><li><strong>Data-Driven:</strong> Your feedback in the notes is what allows us optimize the script daily.</li></ul>]]></content:encoded></item><item><title><![CDATA[LAMB - Appointment Campaign: Lead Generation Sheet]]></title><description><![CDATA[This module introduces the primary tool used to manage outreach for Lambent services. Understanding this sheet is critical for maintaining data integrity, tracking campaign health, and ensuring accurate incentive payouts.]]></description><link>https://lmki.lumikha.co/lambent-appointment-campaign/</link><guid isPermaLink="false">69a7aa14667e580837556009</guid><category><![CDATA[Back-office]]></category><dc:creator><![CDATA[Administrator]]></dc:creator><pubDate>Wed, 04 Mar 2026 03:45:22 GMT</pubDate><content:encoded><![CDATA[<h3 id="context"><br>Context</h3><p>This module introduces the primary tool used to manage outreach for Lambent services. Understanding this sheet is critical for maintaining data integrity, tracking campaign health, and ensuring accurate incentive payouts.</p><p><a href="https://docs.google.com/spreadsheets/d/1ECaJvSVlnRNjWYj47St6XmXVqOYIJEpiMa01wOCr8bA/edit?usp=sharing&amp;ref=lmki.lumikha.co" rel="noreferrer">Check Out the Sheet</a></p>
<!--kg-card-begin: html-->
<iframe width="560" height="315" src="https://www.youtube.com/embed/KbIHfuy_M8I?si=_MLLV6cQKDJWAd4Z" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>
<!--kg-card-end: html-->
<hr><h3 id="why-this-matters">Why This Matters</h3><p>Efficiency in telemarketing isn&apos;t just about making calls; it&#x2019;s about <strong>data management</strong>. Using this spreadsheet correctly allows you to:</p><ul><li><strong>Work Smoothly:</strong> Move through and disposition the data to maximize our time. </li><li><strong>Avoid Redundancy:</strong> Don&#x2019;t call the same person twice in one day or waste time on &quot;Bad Numbers.&quot;</li><li><strong>Optimize Strategy:</strong> Real-time feedback helps us update the script if it&#x2019;s not working.</li></ul><hr><h3 id="1-the-lead-data-knowing-your-prospect">1. The Lead Data: Knowing Your Prospect</h3><p>Before you dial, the sheet provides columns to help you build rapport:</p><ul><li><strong>Company &amp; Contact Info:</strong> Basic details (Name, Title, Location). Most leads are in the Florida/East Coast time zone.</li><li><strong>Website &amp; LinkedIn Links:</strong> Use these for a &quot;quick look&quot; to visualize the person and understand their business.</li><li><strong>Email Field:</strong> Use this only for setting appointments or if requested. <strong>Do not use email as a &quot;crutch&quot; to avoid calling.</strong></li></ul><h3 id="2-the-pass-system-persistence-pays">2. The &quot;Pass&quot; System: Persistence Pays</h3><p>The campaign is designed for <strong>four passes</strong> through the list.</p><ul><li><strong>Pass 1:</strong> Often the slowest. You are cleaning the list by identifying &quot;dead&quot; numbers and hangups.</li><li><strong>Passes 2&#x2013;4:</strong> You return to the remaining &quot;live&quot; leads. Cleaning the list early makes later passes more efficient.</li></ul><h3 id="3-dispositions-tracking-the-outcome">3. Dispositions: Tracking the Outcome</h3><p>Every call must have a &quot;Disposition&quot; (Status). This is the most important column for campaign health:</p><ul><li><strong>The &quot;Wins&quot;:</strong> Appointment Set, Appointment Held, Sale Closed.</li><li><strong>The &quot;Follow-ups&quot;:</strong> Gatekeeper (someone dodging you), Callback Request, Early Hangup (try again at a different time).</li><li><strong>The &quot;Removals&quot;:</strong> Not Interested, Bad Number, Out of Business. (We do not call these again).</li></ul><h3 id="4-incentives-how-you-earn">4. Incentives: How You Earn</h3><p>Your earnings are tracked automatically via the <strong>Activity Report</strong> tab based on your dispositions:</p><ul><li><strong>$2.00:</strong> For every legitimate Appointment Set.</li><li><strong>$5.00:</strong> If the appointment is held (the prospect showed up).</li><li><strong>$50.00:</strong> If the lead results in a Sale Closed.</li></ul><h3 id="5-best-practices-notes">5. Best Practices &amp; Notes</h3><ul><li><strong>Intentional Pacing:</strong> Move through data quickly but don&apos;t rush. Quality conversations lead to appointments.</li><li><strong>Notes Column:</strong> Use this for unique details (e.g., &quot;Very interested, ask about their Miami branch&quot;). <strong>Do not</strong> repeat info already in the disposition or date columns.</li><li><strong>HubSpot:</strong> We only move data into the CRM (HubSpot) <strong>after</strong> an appointment is set.</li></ul><hr><h3 id="summary">Summary</h3><ul><li>The spreadsheet is your &quot;Command Center&quot; for the Landbent campaign.</li><li>Clean the data by marking <strong>Bad Numbers</strong> immediately.</li><li>Your <strong>Incentives</strong> ($2, $5, or $50) are triggered by accurate disposition entry.</li><li>Use the <strong>Activity Report</strong> to monitor your performance and campaign health.</li></ul>]]></content:encoded></item><item><title><![CDATA[RADD - Project Update: Efficiency Standards & Location-Specific Verification]]></title><description><![CDATA[If you update the Name/URL/Address columns, you don't need to write a note explaining why. The data update is the explanation.
]]></description><link>https://lmki.lumikha.co/radd-project-update-efficiency-standards-location-specific-verification/</link><guid isPermaLink="false">693e0721e98662083b26187b</guid><category><![CDATA[Back-office]]></category><category><![CDATA[Data]]></category><dc:creator><![CDATA[Administrator]]></dc:creator><pubDate>Sun, 14 Dec 2025 00:43:19 GMT</pubDate><content:encoded><![CDATA[<h2 id="how-to-document-changes-without-wasting-time">How to Document Changes Without Wasting Time</h2>
<!--kg-card-begin: html-->
<iframe width="560" height="315" src="https://www.youtube.com/embed/_9cS_1kYESo?si=UURiKBhmkVS3PqVA" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>
<!--kg-card-end: html-->
<h3 id="the-data-tells-the-story-philosophy">The &quot;Data Tells the Story&quot; Philosophy</h3><p>We have established that facilities change hands (e.g., &quot;Norwood Clinic&quot; becomes &quot;Complete Health&quot;). When this happens, our goal is to update the record accurately.</p><p>However, a common mistake is <strong>over-documentation</strong>.</p><p><strong>The Principle:</strong> You do not need to write a paragraph in the &quot;Notes&quot; column explaining <em>what</em> happened. The fact that you changed the &quot;Name&quot; column and the &quot;URL&quot; column tells us everything we need to know. We want to eliminate redundant work to speed up your workflow.</p><hr><h2 id="the-deep-dive-investigation">The Deep Dive Investigation</h2><p>When a facility is acquired, they often move physical locations or consolidate offices. You cannot simply flag an address as &quot;wrong&quot;&#x2014;you must try to find the new one.</p><p><strong>Case Study: The &quot;Find a Clinic&quot; Technique</strong></p><ul><li><strong>Scenario:</strong> You find that &quot;Norwood Clinic&quot; was bought by &quot;Complete Health.&quot;</li><li><strong>The Mistake:</strong> You find the main &quot;Complete Health&quot; homepage, paste that as the URL, and flag the address because it doesn&apos;t match the old one.</li><li><strong>The Correct Action:</strong><ol><li>Go to the new owner&apos;s website (&quot;Complete Health&quot;).</li><li>Click <strong>&quot;Find a Location&quot;</strong> or <strong>&quot;Our Clinics.&quot;</strong></li><li>Search for the specific city (e.g., Birmingham) or the specific specialty (Radiology/Cardiology).</li><li><strong>Find the specific branch.</strong> You might discover the facility moved to &quot;Brookwood Blvd.&quot;</li><li><strong>Capture the Data:</strong> Copy the address of that specific branch and the phone number.</li></ol></li></ul><p><strong>The Golden Rule:</strong> Always aim for the <strong>Location-Specific URL</strong>.</p><ul><li><em>Bad:</em> <code>www.completehealth.com</code> (Too general).</li><li><em>Good:</em> <code>www.completehealth.com/locations/brookwood-medical-center</code> (Perfect).</li></ul><hr><h2 id="3-note-taking-protocols-do-this-not-that">3. Note-Taking Protocols: &quot;Do This, Not That&quot;</h2><p>Writing narrative notes slows you down. Follow this guide to streamline your entry process.</p>
<!--kg-card-begin: html-->
<table data-path-to-node="18" style="margin-bottom: 32px; font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><thead style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><tr style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><td style="border: 1px solid; font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><strong style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important; margin-bottom: 0px !important;">Scenario</strong></td><td style="border: 1px solid; font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><strong style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important; margin-bottom: 0px !important;">DON&apos;T Do This (Wastes Time)</strong></td><td style="border: 1px solid; font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><strong style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important; margin-bottom: 0px !important;">DO This (Efficient)</strong></td></tr></thead><tbody style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><tr style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><td style="border: 1px solid; font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><span data-path-to-node="18,1,0,0" style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><b style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;">Name Change</b></span></td><td style="border: 1px solid; font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><span data-path-to-node="18,1,1,0" style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;">Note: <i style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;">&quot;Facility changed name from Norwood to Complete Health.&quot;</i></span></td><td style="border: 1px solid; font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><span data-path-to-node="18,1,2,0" style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><b style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;">Just change the Name column</b> to &quot;Complete Health.&quot;</span></td></tr><tr style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><td style="border: 1px solid; font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><span data-path-to-node="18,2,0,0" style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><b style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;">Dead Link</b></span></td><td style="border: 1px solid; font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><span data-path-to-node="18,2,1,0" style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;">Note: <i style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;">&quot;Website 404 Error: Page not found.&quot;</i></span></td><td style="border: 1px solid; font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><span data-path-to-node="18,2,2,0" style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><b style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;">Just update the URL</b> to the new working link.</span></td></tr><tr style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><td style="border: 1px solid; font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><span data-path-to-node="18,3,0,0" style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><b style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;">Acquisition</b></span></td><td style="border: 1px solid; font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><span data-path-to-node="18,3,1,0" style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;">Note: <i style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;">&quot;This place was bought by a larger group 2 years ago.&quot;</i></span></td><td style="border: 1px solid; font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><span data-path-to-node="18,3,2,0" style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><b style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;">Update the Name and URL.</b> No note needed.</span></td></tr><tr style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><td style="border: 1px solid; font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><span data-path-to-node="18,4,0,0" style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><b style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;">Missing Data</b></span></td><td style="border: 1px solid; font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><span data-path-to-node="18,4,1,0" style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;">Flagging the empty address cell and moving on.</span></td><td style="border: 1px solid; font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><span data-path-to-node="18,4,2,0" style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;"><b style="font-family: &quot;Google Sans Text&quot;, sans-serif !important; line-height: 1.15 !important; margin-top: 0px !important;">Find the address</b> on the new website and fill in the blank cell.</span></td></tr></tbody></table>
<!--kg-card-end: html-->
<blockquote><strong>When to use Notes:</strong> Only use the Notes column for <strong>unsolvable mysteries</strong> (e.g., &quot;Address changed, but I cannot find the new address anywhere online&quot;).</blockquote><hr><h2 id="visual-hygiene-highlighting">Visual Hygiene (Highlighting)</h2><ul><li><strong>Stop Over-Highlighting:</strong> Do not highlight every record you change in yellow.</li><li><strong>Why?</strong> We can already see which records you changed by looking at the version history or the &quot;Last Updated&quot; metadata.</li><li><strong>When to Highlight:</strong> Only use yellow highlights for records you are personally stuck on and need to return to <em>within your own session</em>. If you have finished the record, remove the highlight.</li></ul><hr><h2 id="summary">Summary</h2><ul><li><strong>Don&apos;t Narrate:</strong> If you update the Name/URL/Address columns, you don&apos;t need to write a note explaining why. The data update <em>is</em> the explanation.</li><li><strong>Fill in Blanks:</strong> If an address was missing in the original file, don&apos;t just flag it. Find it on the website and add it.</li><li><strong>Be Specific:</strong> Always hunt for the specific location page on a website, not just the homepage.</li><li><strong>Check for Moves:</strong> When a business is bought, they often move. Verify the address on the new &quot;Locations&quot; page.</li></ul>]]></content:encoded></item><item><title><![CDATA[RADD - Overview -  Understanding Facility Ownership & Rebranding]]></title><description><![CDATA[While some clinics are small "mom and pop" operations, many are owned by large corporate networks. These large networks frequently buy smaller clinics and clinics from other networks.]]></description><link>https://lmki.lumikha.co/radd-project-understanding-facility-ownership-rebranding/</link><guid isPermaLink="false">693e041fe98662083b261861</guid><category><![CDATA[Back-office]]></category><category><![CDATA[Data]]></category><dc:creator><![CDATA[Administrator]]></dc:creator><pubDate>Sun, 14 Dec 2025 00:35:07 GMT</pubDate><content:encoded><![CDATA[<h2 id="on-reason-data-mismatches-happen-mergers-acquisitions">On Reason Data Mismatches Happen (Mergers &amp; Acquisitions)</h2>
<!--kg-card-begin: html-->
<iframe width="560" height="315" src="https://www.youtube.com/embed/gKn4sGxe4lA?si=j7wRwUchim4xNWEe" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>
<!--kg-card-end: html-->
<h2 id="whats-behind-many-of-the-data-mismatches">What&apos;s Behind Many of the Data Mismatches</h2><p>When you see a mismatch between a facility name and a website&#x2014;or a website that no longer works&#x2014;it is not always because the business is closed.</p><p>The radiology and outpatient imaging industry is consolidating. While some clinics are small &quot;mom and pop&quot; operations, many are owned by large corporate networks. These large networks frequently buy smaller clinics and clinics from other networks.</p><p><strong>What happens when a clinic is sold?</strong></p><ul><li><strong>Ownership Change:</strong> &quot;Main Street Imaging&quot; is bought by &quot;National Health Corp.&quot;</li><li><strong>Rebranding:</strong> The sign on the door might change, or it might stay the same, but the <em>digital</em> presence changes.</li><li><strong>Website Shifts:</strong> The old website (<code>mainstreetimaging.com</code>) is shut down, and the facility is added as a location page on the new owner&apos;s site (<code>nationalhealth.com/locations/main-street</code>).</li></ul><p><strong>Why this matters to us:</strong> We must ensure our data reflects the <em>current</em> owner. If we delete a record because the old URL is broken, we lose a valid lead. If we keep the old data, we provide inaccurate info.</p><hr><h2 id="the-anchor-strategy-trust-the-address">The Anchor Strategy: Trust the Address</h2><p>Since names and websites change frequently, the <strong>Physical Address</strong> is your most stable data point. A building rarely moves, even if the business inside changes hands.</p><p><strong>The Problem:</strong> You have a record for &quot;Blue Sky Radiology,&quot; but the website is dead.</p><p><strong>The Solution:</strong></p><ol><li><strong>Search the Address:</strong> Copy the specific street address and city into Google.</li><li><strong>Identify the Tenant:</strong> Look at the results. Is there a radiology center at that exact address with a <em>different</em> name?</li><li><strong>Verify the Connection:</strong><ul><li>If you find &quot;Global Imaging Centers&quot; at that address, check their &quot;Locations&quot; page.</li><li>Confirm that this new entity is operating out of the old &quot;Blue Sky&quot; location.</li></ul></li></ol><hr><h2 id="workflow-handling-acquisitions">Workflow: Handling Acquisitions</h2><p>When you identify that a facility has been acquired:</p><ol><li><strong>Don&apos;t Delete:</strong> The facility likely still exists and needs radiology equipment/services.</li><li><strong>Update the Name:</strong> Change the name in our dataset to the new corporate name (e.g., Change &quot;Blue Sky&quot; to &quot;Global Imaging - Main St Branch&quot;).</li><li><strong>Update the URL:</strong> Replace the dead URL with the specific location page on the new owner&apos;s website.</li><li><strong>Verify Details:</strong> Ensure the phone number is updated. Large networks often centralize their booking numbers.</li></ol><blockquote><strong>Key Takeaway:</strong> We are not just checking for typos; we are investigating the <em>status</em> of the facility. Aligning the data means ensuring the Name, URL, and Address all tell the same story about who owns the building <em>today</em>.</blockquote><hr><h2 id="summary">Summary</h2><ul><li><strong>Changes are Common:</strong> Expect to see facilities changing hands frequently.</li><li><strong>Mom &amp; Pop -&gt; Corporate:</strong> Small clinics are often bought by large groups.</li><li><strong>The Address is Key:</strong> If the name/site doesn&apos;t match, search the address to find the new owner.</li><li><strong>Update, Don&apos;t Delete:</strong> If the facility is open under a new name, it is still a valid record. Update it to reflect the new ownership.</li></ul>]]></content:encoded></item><item><title><![CDATA[RADD - Project Updates: Find Info with No Website]]></title><description><![CDATA[Investigate records with missing URLs, cross-reference data points to verify business status, and determine when to update a record versus when to flag it for a phone call.]]></description><link>https://lmki.lumikha.co/radd-project-updates-find-info-with-no-website/</link><guid isPermaLink="false">693dfd88e98662083b261849</guid><category><![CDATA[Back-office]]></category><category><![CDATA[Data]]></category><dc:creator><![CDATA[Administrator]]></dc:creator><pubDate>Sun, 14 Dec 2025 00:00:30 GMT</pubDate><content:encoded><![CDATA[
<!--kg-card-begin: html-->
<iframe width="560" height="315" src="https://www.youtube.com/embed/A5RqqtKq32c?si=rWqUKbdHMTL_3JJx" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>
<!--kg-card-end: html-->
<h2 id="context">Context</h2><p>In our database, a missing URL (website link) is a red flag. It usually means one of two things: the facility has gone out of business, or the data is incomplete.</p><p>However, we cannot simply guess. We are the &quot;detectives&quot; of data. Our goal is to ensure every record in the RAD database is 100% accurate. If we provide our AI agents or marketing teams with bad links or closed businesses, we waste resources and lower our trust score.</p><p><strong>Learning Objective:</strong> By the end of this module, you will be able to investigate records with missing URLs, cross-reference data points to verify business status, and determine when to update a record versus when to flag it for a phone call.</p><hr><h2 id="the-investigative-workflow">The Investigative Workflow</h2><p>When you encounter a record with a missing URL, follow this four-step investigation process.</p><h4 id="step-1-the-search-bar-trick">Step 1: The &quot;Search Bar&quot; Trick</h4><p>Don&apos;t just look for the name. Copy the <strong>Name + Address</strong> and paste it directly into the Google address bar.</p><ul><li><strong>Why?</strong> This casts a wider net than searching for just the name (which might return similar businesses in other states) or just the address (which might show the building but not the tenant).</li><li><strong>What to look for:</strong> Look for a &quot;Knowledge Graph&quot; on the right side of Google, or listings in directories like Yelp, Yellow Pages, or Healthgrades.</li></ul><h4 id="step-2-cross-reference-secondary-sources">Step 2: Cross-Reference Secondary Sources</h4><p>If Google doesn&apos;t show a direct website, check secondary sources like <strong>MapQuest</strong>, <strong>Yelp</strong>, or <strong>Google Maps</strong>.</p><ul><li><strong>The &quot;Permanently Closed&quot; Indicator:</strong> If MapQuest or Google Maps explicitly tags a location as &quot;Permanently Closed,&quot; this is a strong signal.</li><li><strong>Action:</strong> If you see &quot;Permanently Closed,&quot; do not delete the record immediately. We must follow the &quot;Court of Last Resort&quot; rule (see Step 4).</li></ul><h4 id="step-3-analyze-data-discrepancies">Step 3: Analyze Data Discrepancies</h4><p>Sometimes you will find a website that <em>looks</em> like the right business, but the details don&apos;t match.</p><ul><li><strong>Scenario:</strong> You search for &quot;Cabot Imaging Center.&quot; You find a website for a center with that name, but the <strong>Address</strong> and <strong>Phone Number</strong> are different from what is in our database.</li><li><strong>The Trap:</strong> Do not assume they moved and simply overwrite the old data. It is possible these are two completely different businesses, or the facility in our database has closed and a new one opened elsewhere.</li><li><strong>The Protocol:</strong><ol><li><strong>Do NOT overwrite</strong> the existing contact info with the new one found online if the address and phone vary significantly.</li><li><strong>Add a Note:</strong> Paste the link you found into the record&apos;s notes section.</li><li><strong>Flag for Call:</strong> Mark the record for manual verification.</li></ol></li></ul><h4 id="step-4-the-court-of-last-resort-calling">Step 4: The Court of Last Resort (Calling)</h4><p>When digital investigation hits a dead end, or when data is conflicting (e.g., MapQuest says closed, but Yelp says open), we use the Court of Last Resort: <strong>The Phone Call.</strong></p><ul><li><strong>When to call:</strong><ul><li>If a facility is listed as &quot;Permanently Closed&quot; online (to confirm).</li><li>If you find a website but the address/phone doesn&apos;t match our record.</li><li>If there is absolutely no digital footprint.</li></ul></li><li><strong>Why:</strong> A 30-second phone call is more accurate than 30 minutes of Google searching.</li></ul><hr><h2 id="summary">Summary</h2><ul><li><strong>Missing URLs</strong> are a signal to investigate, not just ignore.</li><li><strong>Verify Status:</strong> Use Google, Yelp, and MapQuest to see if a business is &quot;Permanently Closed.&quot;</li><li><strong>Handle Discrepancies with Care:</strong> If the website you find has a different address and phone number than your record, do not overwrite the data. Add the link to the <strong>Notes</strong> and flag it.</li><li><strong>Call to Confirm:</strong> When in doubt, or when evidence suggests a closure, calling the facility is the only way to be 100% sure.</li></ul>]]></content:encoded></item></channel></rss>