<?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>Sat, 04 Apr 2026 16:56:35 GMT</lastBuildDate><atom:link href="https://lmki.lumikha.co/rss/" rel="self" type="application/rss+xml"/><ttl>60</ttl><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><item><title><![CDATA[RADD - NAP+W Project: Troubleshooting Problematic Records]]></title><description><![CDATA[Techniques for addressing records where the provided website URL is not working.]]></description><link>https://lmki.lumikha.co/radd-nap-w-project-troubleshooting-problematic-records/</link><guid isPermaLink="false">6938b9b4e98662083b261832</guid><category><![CDATA[Back-office]]></category><dc:creator><![CDATA[Administrator]]></dc:creator><pubDate>Wed, 10 Dec 2025 00:14:09 GMT</pubDate><content:encoded><![CDATA[<p>This module provides practical techniques for addressing records where the provided website URL is not working or the information is difficult to verify. The core focus is maintaining momentum while thoroughly handling data discrepancies.</p>
<!--kg-card-begin: html-->
<iframe width="560" height="315" src="https://www.youtube.com/embed/qU6OkrQY5y0?si=BJ7beWPS69G0UKsk" 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="why-this-matters">Why This Matters</h3><ul><li><strong>Maintain Momentum:</strong> Having a system for dealing with &quot;dead links&quot; prevents you from getting stuck on a single record, allowing you to hit your daily goal of <strong>140+ records</strong>.</li><li><strong>Increase Data Quality:</strong> By using advanced verification techniques (like Google search), you can find the correct, active information, which improves the quality of the dataset for downstream use (dialing, marketing).</li><li><strong>Identify Status:</strong> You can reliably determine if a facility is <strong>active</strong> or <strong>permanently closed</strong>, which is critical for the client.</li></ul><h3 id="%F0%9F%9A%80-strategies-for-efficient-problem-solving">&#x1F680; Strategies for Efficient Problem Solving</h3><p>A key principle is to <strong>flag problematic records</strong> and set them aside to keep verifying other, easier records.</p><h4 id="general-techniques">General Techniques</h4><ul><li><strong>Flagging:</strong><ul><li><strong>Application:</strong> Use a clear visual marker (e.g., highlighting in <strong>yellow</strong>) on the sheet for records you need to return to.</li><li><strong>Why?</strong> Preserves momentum; you can quickly skip and return later.</li></ul></li><li><strong>VPN Usage:</strong><ul><li><strong>Application:</strong> If the site says it cannot be reached, <strong>install and activate a free VPN</strong> (like Urban VPN) set to a U.S. IP address.</li><li><strong>Why?</strong> Some U.S. websites block international IP addresses for security. This bypasses the block and allows verification.</li></ul></li></ul><div class="kg-card kg-callout-card kg-callout-card-red"><div class="kg-callout-emoji">&#x1F44D;</div><div class="kg-callout-text">Urban VPN </div></div><ul><li><strong>Google Search:</strong><ul><li><strong>Application:</strong> If the URL still won&apos;t load, <strong>copy the facility&apos;s name and address</strong> from the sheet and <strong>paste it into a search bar</strong> (Google search).</li><li><strong>Why?</strong> This is the fastest way to find the current, correct web presence and status for the location.</li></ul></li><li><strong>Strikethrough:</strong><ul><li><strong>Application:</strong> Use a <strong>strikethrough</strong> on the row when Google Maps or search results indicate the facility is <strong>permanently closed</strong>.</li><li><strong>Why?</strong> Clearly flags the record for follow-up (e.g., confirming status via phone) without deleting data.</li></ul></li></ul><h3 id="%F0%9F%94%8D-two-common-exception-scenarios">&#x1F50D; Two Common Exception Scenarios</h3><p>This section details how to manage the two most frequent types of non-working links:</p><h4 id="1-facility-is-permanently-closed-dead-link">1. Facility is Permanently Closed (Dead Link)</h4><ul><li><strong>Symptom:</strong> The provided URL is a dead link, and searching the name on Google Maps shows a <strong>&quot;Permanently Closed&quot;</strong> status.</li><li><strong>Action:</strong><ul><li><strong>Strikethrough</strong> the record on the sheet.</li><li><strong>Flag</strong> the record (e.g., mark in a specific color) to indicate a status change for management follow-up.</li></ul></li><li><strong>Rationale:</strong> Google Maps is a generally reliable indicator for closures, making the current data unusable.</li></ul><h4 id="2-incorrectchanged-url-active-facility">2. Incorrect/Changed URL (Active Facility)</h4><ul><li><strong>Symptom:</strong> The provided URL is wrong, but a <strong>Google search</strong> of the facility name quickly leads to a <strong>new, working website</strong>.</li><li><strong>Action:</strong><ul><li><strong>Copy the new, correct URL</strong> and paste it into the <strong>Web Update</strong> field.</li><li><strong>Verify all original data</strong> (Name, Phone, Address) against the new website. <strong>Crucially</strong>, check if the facility has changed its <strong>Name</strong> or <strong>Phone Number</strong> during the domain change (often indicates a change in ownership).</li><li><strong>Update any discrepancies</strong> (e.g., adding suite numbers like &quot;Suite 101&quot;).</li><li><strong>Remove the yellow flag</strong> once all corrections are made and verified.</li></ul></li><li><strong>Rationale:</strong> This effort fully verifies the record, converting a &quot;bad&quot; record into a <strong>high-quality, accurate</strong> one within the 3-minute time estimate.</li></ul><hr><h2 id="summary">Summary</h2><ul><li><strong>Productivity Focus:</strong> Complete a minimum of <strong>140 records per day</strong>. Use <strong>yellow highlighting</strong> to flag difficult records and maintain your flow.</li><li><strong>Website Access:</strong> If the URL doesn&apos;t load, first try activating a <strong>VPN</strong> set to a U.S. IP address.</li><li><strong>Data Recovery:</strong> If the link is dead, <strong>Google search</strong> the facility name to find a new URL or current status.</li><li><strong>Status Indicators:</strong><ul><li>If <strong>Permanently Closed</strong>, <strong>strikethrough</strong> the record.</li><li>If a <strong>new URL is found</strong>, update the sheet and <strong>re-verify all details</strong> (especially the name and phone number) against the new site.</li></ul></li><li><strong>Data Quality:</strong> Adding detail (like suite numbers) and correcting obsolete information improves data quality and increases customer confidence.</li></ul>]]></content:encoded></item><item><title><![CDATA[RADD - NAP+W Project Updates]]></title><description><![CDATA[<p>This training module summarizes the adjustments and key expectations for the data record verification project, focusing on <strong>production goals</strong>, <strong>accuracy</strong>, and <strong>process enhancements</strong>.</p>
<!--kg-card-begin: html-->
<iframe width="560" height="315" src="https://www.youtube.com/embed/fiGuUNnvpC8?si=rdn-NcUN7aYvjUxP" 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="%F0%9F%8E%AF-project-adjustments-and-goals">&#x1F3AF; Project Adjustments and Goals</h2><p>This section details the changes to the expected output and the rationale behind the new targets.</p><h3 id="why-the-adjustment">Why the Adjustment?</h3><p>The goal is</p>]]></description><link>https://lmki.lumikha.co/radd-nap-w-project-updates/</link><guid isPermaLink="false">6938b476e98662083b261817</guid><dc:creator><![CDATA[Administrator]]></dc:creator><pubDate>Tue, 09 Dec 2025 23:50:02 GMT</pubDate><content:encoded><![CDATA[<p>This training module summarizes the adjustments and key expectations for the data record verification project, focusing on <strong>production goals</strong>, <strong>accuracy</strong>, and <strong>process enhancements</strong>.</p>
<!--kg-card-begin: html-->
<iframe width="560" height="315" src="https://www.youtube.com/embed/fiGuUNnvpC8?si=rdn-NcUN7aYvjUxP" 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="%F0%9F%8E%AF-project-adjustments-and-goals">&#x1F3AF; Project Adjustments and Goals</h2><p>This section details the changes to the expected output and the rationale behind the new targets.</p><h3 id="why-the-adjustment">Why the Adjustment?</h3><p>The goal is to maintain a high-quality, sustainable pace while rapidly building the dataset. Initially aiming for a record every minute, the revised target is based on a more conservative estimate to ensure accuracy is maintained.</p><ul><li><strong>Time Per Record:</strong> <br>The assumption is adjusted to <strong>3 minutes per record</strong> to allow for careful, methodical work.</li><li><strong>Daily Production Minimum:</strong> <br>Each person is expected to complete a <strong>minimum of 140 records per day</strong>.</li><li><strong>Mark Your Last Record:</strong> <br>To prevent confusion and wasted time, you need a system to mark where you stopped each day.</li><li><strong>Flag Issues Clearly:</strong> <br>If a URL doesn&apos;t work or an issue arises (e.g., website down, potential unpaid bill), <strong>flag it clearly</strong> on the document.</li><li><strong>Effective Notes:</strong> <br>Use <strong>specific, helpful notes</strong> instead of vague comments like &quot;Not sure about this.&quot; Example: &quot;URL does not work.&quot;</li></ul><hr><h2 id="%E2%9C%85-importance-of-accuracy-and-verification">&#x2705; Importance of Accuracy and Verification</h2><p>Accuracy is the central objective of this project, as it creates <strong>downstream efficiencies</strong> for the dialing teams and reinforces the overall quality of the data.</p><h3 id="why-accuracy-is-paramount">Why Accuracy is Paramount</h3><ul><li><strong>Reduced Mistakes:</strong> High accuracy leads to fewer errors in subsequent processes.</li><li><strong>Downstream Efficiency:</strong> Having the correct phone numbers linked to the right location saves time for the teams that will be using the data (e.g., dialing teams).</li></ul><h3 id="%F0%9F%9B%A0%EF%B8%8F-verification-steps">&#x1F6E0;&#xFE0F; Verification Steps</h3><p>For <strong>each record</strong>, you must perform the following checks:</p><ol><li><strong>Check the Link:</strong> Click the provided link to ensure it&apos;s <strong>working</strong> and <strong>correct</strong> for the record.</li><li><strong>Verify Information:</strong> Double-check all associated data, specifically:<ul><li><strong>Street Address</strong></li><li><strong>City</strong> and <strong>State</strong> (less likely to change)</li><li><strong>Zip Code</strong> (Check carefully for potential single-digit transcription errors, even if rare).</li><li><strong>Phone Number</strong> (Verify against the link&apos;s information).</li></ul></li><li><strong>Verify Location Information:</strong> Ensure the location data (address, phone number) corresponds accurately to the linked facility.</li></ol><hr><h2 id="%F0%9F%92%BB-process-and-formatting-improvements">&#x1F4BB; Process and Formatting Improvements</h2><p>To support focus and minimize errors, a formatting change has been implemented in the document.</p><h3 id="enhanced-legibility">Enhanced Legibility</h3><ul><li><strong>Alternating Colors:</strong> The sheet now uses <strong>alternating colors</strong> for rows (color bands).</li><li><strong>Why?</strong> This improves <strong>legibility</strong>, makes the work <strong>less fatiguing</strong>, and <strong>reduces mistakes</strong> by clearly separating records.</li></ul><h3 id="tracking-progress">Tracking Progress</h3><ul><li><strong>Mark Your Last Record:</strong> To prevent confusion and wasted time, you need a system to mark where you stopped each day.<ul><li><em>How to Apply:</em> <strong>Count the number of records completed</strong> or <strong>mark the last finished record</strong> (e.g., by making the row <strong>red</strong>).</li><li><em>Why?</em> This ensures you don&apos;t redo work and helps management efficiently track daily progress.</li></ul></li></ul><h3 id="handling-exceptions">Handling Exceptions</h3><ul><li><strong>Flag Issues Clearly:</strong> If a URL doesn&apos;t work or an issue arises (e.g., website down, potential unpaid bill), <strong>flag it clearly</strong> on the document.</li><li><strong>Effective Notes:</strong> Use <strong>specific, helpful notes</strong> instead of vague comments like &quot;Not sure about this.&quot; Example: &quot;URL does not work.&quot;</li><li><strong>Follow-Up:</strong> Exceptions will be reviewed and researched by management; your job is to identify and flag them.</li></ul><hr><h2 id="summary">Summary<br></h2><p><strong>Productivity</strong> - Complete a <em>minimum</em> of 140 records per day.</p><p><strong>Accuracy</strong> - Be methodical and accurate; verify the link, address, zip, and phone number.</p><p><strong>Tracking</strong> - Mark your last completed record to start correctly the next day.</p><p><strong>Communication</strong> - Focus on the task; flag exceptions with clear, specific notes.</p>]]></content:encoded></item><item><title><![CDATA[RADD - Website Validation and NAP+W Data Hygiene Sprint]]></title><description><![CDATA[This module introduces the task designed to ensure the foundational Name, Address, Phone, and Website (NAP+W) data for radiology facilities is current and accurate.]]></description><link>https://lmki.lumikha.co/website-validation-and-nap-w-data-hygiene-sprint/</link><guid isPermaLink="false">6937a017e98662083b2617f2</guid><category><![CDATA[Back-office]]></category><dc:creator><![CDATA[Administrator]]></dc:creator><pubDate>Tue, 09 Dec 2025 04:21:14 GMT</pubDate><content:encoded><![CDATA[<p>This module introduces the <strong>Website Validation Sprint</strong>, a short-term, high-volume task designed to ensure the foundational Name, Address, Phone, and Website (NAP+W) data for radiology facilities is current and accurate.</p>
<!--kg-card-begin: html-->
<iframe width="560" height="315" src="https://www.youtube.com/embed/vZ7EKNx0wEo?si=fkq27gTx0KbfpbSW" 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="1-%F0%9F%8E%AF-context-and-module-goal">1. &#x1F3AF; Context and Module Goal</h2><ul><li><strong>Context:</strong> Data quality degrades rapidly due to facility acquisitions, mergers, and location changes. This sprint is a <strong>proactive data hygiene effort</strong> focused on correcting NAP+W details using the facility&apos;s website as the primary source of truth.</li><li><strong>Goal:</strong> To process <strong>500 records per day</strong> by confirming the active status of the website URL and updating any discrepancies found in the Name, Address, or Phone Number in the dedicated update fields.</li></ul><hr><h2 id="2-%F0%9F%A4%94-why-website-validation-is-essential">2. &#x1F914; Why Website Validation is Essential </h2><p><br><strong>Website Check for Mismatch	</strong><br>Confirms if a facility was acquired/merged, leading to a name change or redirection to a parent company&apos;s site.</p><p><strong>Address/Phone Discrepancy	</strong><br>Check Outpatient clinics rely on accurate contact info (phone/address) to book appointments. The website is the most current source.</p><p><strong>Data Familiarity	</strong><br>Be &quot;mindful&quot; of the data and peripheral information, to spot complex issues (e.g., chains with a single phone line).</p><hr><h2 id="3-%F0%9F%93%9D-how-to-apply-the-learning-the-validation-workflow">3. &#x1F4DD; How to Apply the Learning: The Validation Workflow</h2><p>The core task is to check the existing record against the facility&apos;s live website.</p><h4 id="31-the-daily-workflow-400-recordspersonday">3.1. The Daily Workflow (400 Records/Person/Day)</h4><ol><li><strong>Allocate:</strong> Receive your daily allocation of records. (color coded)</li><li><strong>Click &amp; Check URL:</strong> Click the existing URL in the record.<ul><li><strong>If the website is active and the name/branding matches the record:</strong> The website is confirmed. Check for quick Address/Phone confirmation.</li><li><strong>If the URL is dead, redirects, or the company name is different:</strong> This indicates a <strong>data mismatch</strong> (Acquisition, New Name, or Old URL).</li></ul></li><li><strong>Validate NAP+W:</strong> On the live website, cross-reference the four key fields from the record: <strong>Name, Address (physical location), Phone Number, and Website URL.</strong></li><li><strong>Update Only Discrepancies:</strong> <strong>NEVER edit the original record fields.</strong> Only input the <strong>NEW, correct information</strong> into the dedicated <strong>Update/Flag</strong> columns (e.g., <em>Name Update</em>, <em>Address Update</em>, <em>Phone Update</em>, <em>Web Update</em>).</li></ol><h4 id="32-key-validation-scenarios-and-actions">3.2. Key Validation Scenarios and Actions</h4><p><strong>Perfect Match</strong></p>
<ul>
<li>Name, Address, and Phone on the website match the record.</li>
<li>No action required in the update fields. Move to the next record.</li>
</ul>
<p><strong>Name Change/Acquisition</strong></p>
<ul>
<li>Original URL redirects to a new site (e.g., &quot;Kenai Orthopedics&quot; redirects to &quot;Independence Healthcare&quot;).</li>
<li>Input the New Name and New URL in the update columns. This flags the record for follow-up verification.</li>
</ul>
<p><strong>Missing URL</strong></p>
<ul>
<li>The original record has no URL.</li>
<li>Search by Name and Address (OPA method): Use Google to find the facility&apos;s website. If found, input the new, valid URL in the Web Update column and check the other fields.</li>
</ul>
<p><strong>Updated Contact Info</strong></p>
<ul>
<li>The website shows a different Phone Number or a more detailed Address (e.g., includes a Suite Number or updated Zip Code).</li>
<li>Input the updated Phone Number or complete Address detail into the respective Update column.</li>
</ul>
<p>3.3. <strong>Crucial Rule: The Source of Truth</strong></p><p>The <strong>physical location (Address)</strong> is the most stable and important data point.</p><ul><li><strong>Priority 1: Address:</strong> If the website confirms the address, this validates the facility&apos;s existence at that physical spot, even if the name or phone changed.</li><li><strong>Priority 2: Name &amp; URL:</strong> Use the website&apos;s branding as the source for the current name.</li><li><strong>Priority 3: Phone:</strong> Use the phone number listed on the website for that specific location (if available).</li></ul><blockquote>&#x23F1;&#xFE0F; <strong>Time Management:</strong> Aim for <strong>2 to 5 minutes maximum per record</strong>. If a record is confusing (e.g., an extremely complicated chain or multiple contradictory addresses), flag it for the QA team (Joy or Supervisor) and move on to maintain your daily allocation target.</blockquote><hr><h3 id="4-%F0%9F%92%A1-summary-and-key-takeaways">4. &#x1F4A1; Summary and Key Takeaways</h3><ul><li><strong>Primary Goal:</strong> Check URL validity and identify NAP+W discrepancies.</li><li><strong>Daily Target:</strong> 4<strong>00 records.</strong> Work quickly, but <strong>mindfully.</strong></li><li><strong>Actionable Rule:</strong> <strong>DO NOT</strong> edit the original data. Only fill in the <strong>Update/Flag</strong> columns with the <em>new, confirmed information</em>.</li><li><strong>Source Validation:</strong> Use the <strong>live website</strong> as the source of truth, and if the URL is missing, use Google Search by <strong>Name + Address</strong>.</li></ul>]]></content:encoded></item><item><title><![CDATA[RADD - Overview of Facility and Equipment Validation]]></title><description><![CDATA[The essential context, data targets, and core operational guidelines for the Radiology Data Campaign. It clarifies the type of facility being called and the three critical pieces of information required.]]></description><link>https://lmki.lumikha.co/radiology-data-campaign-facility-and-equipment-validation/</link><guid isPermaLink="false">69379ef1e98662083b2617dd</guid><category><![CDATA[Back-office]]></category><dc:creator><![CDATA[Administrator]]></dc:creator><pubDate>Tue, 09 Dec 2025 04:03:48 GMT</pubDate><content:encoded><![CDATA[<p>This module provides the essential context, data targets, and core operational guidelines for the Radiology Data Campaign. It clarifies the type of facility being called and the three critical pieces of information required.</p>
<!--kg-card-begin: html-->
<iframe width="560" height="315" src="https://www.youtube.com/embed/fIX47GHgqGo?si=sPI5FtsvoCnAZOgG" 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="1-%F0%9F%8E%AF-context-and-module-goal">1. &#x1F3AF; Context and Module Goal</h2><ul><li><strong>Context:</strong> <br>This campaign involves calling non-hospital, outpatient imaging centers (radiology facilities) that offer services like MRI scans, X-rays, and other diagnostic imaging. The goal is to update and validate core data points.</li><li><strong>Goal:</strong> <br>To enable Data Agents (for data processing/checking) and Call Agents (for validation) to efficiently and accurately capture the three main data categories: <strong>NAP+W, Equipment Details, and Decision Makers.</strong></li></ul><hr><h2 id="2-%F0%9F%A4%94-why-this-data-is-critical">2. &#x1F914; Why This Data is Critical </h2><ul>
<li>
<p><strong>Accurate NAP+W:</strong><br>
Essential for physically locating and contacting the facility. The URL (website) is key for deeper operational research.</p>
</li>
<li>
<p><strong>Equipment Details:</strong><br>
Identifies the capabilities and technological age of the facility&apos;s machinery (MRI, CT scanners).</p>
</li>
<li>
<p><strong>Decision Makers (DMs):</strong><br>
Provides the name and title of the person responsible for purchasing/operational decisions.</p>
</li>
</ul>
<hr><h2 id="3-%F0%9F%93%9D-how-to-apply-the-learning-the-three-data-buckets">3. &#x1F4DD; How to Apply the Learning: The Three Data Buckets</h2><p>The campaign focuses on collecting and validating three distinct types of data.</p><h4 id="31-facility-identity-napw">3.1. Facility Identity (NAP+W)</h4><p>This information is about where the facility is located and how to contact them.</p><ul>
<li>
<p><strong>Name:</strong> Full legal/operating name.	<br>
Be alert to name changes! If the facility answers the phone with a different name, always ask if the name has changed due to a sale/acquisition.</p>
</li>
<li>
<p><strong>Address:</strong>  Complete physical address.	<br>
Must be the facility&apos;s specific location, distinguishing it from a large group&apos;s headquarters.</p>
</li>
<li>
<p><strong>Phone Number:</strong> Direct line to the facility.	<br>
Should be the number used to contact them for data validation.</p>
</li>
<li>
<p><strong>Website (URL):</strong> The facility&apos;s online domain name.	<br>
Often referred to as URL or domain name; necessary for deeper context/research</p>
</li>
</ul>
<blockquote><strong>&#x26A0;&#xFE0F; Note on Acquisitions:</strong> Facilities, especially in big cities, frequently change ownership. If a facility has been bought by a larger group, the <strong>name and website</strong> are highly likely to change. AI Agents must be trained to flag and update records when new NAP+W data is acquired.</blockquote><h4 id="32-equipment-details">3.2. Equipment Details</h4><p>This information focuses on the technical assets within the facility.</p><ul><li><strong>Target Equipment:</strong> Primarily MRI machines and CT scanners.</li><li><strong>Required Data Points:</strong><ul><li>Brand Name</li><li>Model Name</li><li>Slices (for CT scanners - refers to imaging passes)<sup>1</sup></li><li>Age of the machine (if possible)</li></ul></li><li><strong>Probing for Change:</strong> Always inquire about recent/planned equipment changes:<ul><li>Did they <strong>recently inquire</strong> about new machinery?</li><li>Are they <strong>planning to acquire</strong> new machinery?</li><li>Are they <strong>planning to dispose of/remove</strong> machinery?</li></ul></li><li><strong>How to Ask (Focus on their operations):</strong> Frame questions from the perspective of the person answering. Do not ask &quot;Are you selling the equipment?&quot; (they may not know). Instead, ask: &quot;<strong>Is that equipment being removed from your facility?</strong>&quot; (They will likely know the answer to this as it affects their day-to-day work.)</li><li><strong>Rule of Thumb:</strong> Ask about <strong>one piece of equipment at a time</strong> to avoid overwhelming the contact person.</li></ul><h4 id="33-decision-makers-dms">3.3. Decision Makers (DMs)</h4><p>This requires a separate approach to identify the key contact.</p><ul><li><strong>Target:</strong> The person in charge of the department or facility manager.</li><li><strong>Methodology:</strong><ol><li>Ask to be transferred to the <strong>&quot;person in charge&quot;</strong> or <strong>&quot;manager.&quot;</strong></li><li>If transferred to <strong>voicemail</strong>, you can still capture the <strong>Name</strong> and <strong>Title</strong> (which is vital information).</li><li>If a live person answers, try to obtain the <strong>Email Address</strong> (if applicable).</li></ol></li><li><strong>Goal:</strong> Obtain the DM&apos;s Name and Title, which is sufficient for targeted marketing/sales outreach.</li></ul><hr><h2 id="4-%F0%9F%92%A1-summary-and-key-takeaways">4. &#x1F4A1; Summary and Key Takeaways</h2><p><strong>Be Attuned</strong></p>
<ul>
<li>Listen for changes in the facility name when the phone is answered, and compare it to the record.</li>
<li>Essential for maintaining data currency due to frequent acquisitions.</li>
</ul>
<p><strong>Probe Gently</strong></p>
<ul>
<li>Ask about one piece of equipment at a time and frame disposal questions around the impact on their daily operations.</li>
<li>Ensures the agent receives accurate information without overburdening the contact.</li>
</ul>
<p><strong>Capture All Three</strong></p>
<ul>
<li>Ensure all three data pillars (NAP+W, Equipment, DM) are addressed, even if it requires annotation in the notes.</li>
<li>Maximizes the value of the record for downstream AI segmentation and marketing efforts.</li>
</ul>
]]></content:encoded></item><item><title><![CDATA[Introduction to Gemini Gems]]></title><description><![CDATA[Treat Gems not as static tools, but as living documents and a Second Memory that evolves alongside the technology and the brand.]]></description><link>https://lmki.lumikha.co/introduction-to-gemini-gems/</link><guid isPermaLink="false">692e3adde98662083b26179a</guid><category><![CDATA[Automation]]></category><dc:creator><![CDATA[Administrator]]></dc:creator><pubDate>Tue, 02 Dec 2025 01:09:45 GMT</pubDate><content:encoded><![CDATA[<h2 id="the-living-gem-philosophy-%E2%80%93-iteration-second-memory">The Living Gem Philosophy &#x2013; Iteration &amp; Second Memory</h2>
<!--kg-card-begin: html-->
<iframe width="560" height="315" src="https://www.youtube.com/embed/AHTn4B_BvFg?si=-UxFBmjmREGs_WWr" 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="nothing-is-ever-finished">Nothing is Ever Finished</h2><p>In traditional software or documentation, you build it once, and you are done. <strong>That mindset fails in AI.</strong></p><p>The landscape of AI (Gemini, Anthropic, OpenAI) moves at breakneck speed. New features&#x2014;like Google&apos;s agentic &quot;Anti-Gravity&quot; solution&#x2014;are released constantly. Simultaneously, the brands we manage (like Lambent or Lumikha) are evolving. We learn new things about our audience every day.</p><p><strong>Our Goal:</strong> <br>To treat Gems not as static tools, but as <strong>living documents</strong> and a <strong>Second Memory</strong> that evolves alongside the technology and the brand.</p><hr><h2 id="part-1-the-beta-mindset">Part 1: The Beta Mindset</h2><p>Because the platforms change so fast, anything we build today might be obsolete in three months.</p><ul><li><strong>Expect change:</strong> We will continually revisit and rework Gems to reflect new AI capabilities.</li><li><strong>Don&apos;t aim for permanent perfection:</strong> Build for <em>now</em>, knowing you will improve it <em>later</em>.</li><li><strong>Flexibility is key:</strong> Our approach to prompting must be flexible enough to pivot when the underlying technology shifts.</li></ul><h2 id="part-2-gems-as-a-second-memory">Part 2: Gems as a Second Memory</h2><p>Developing a brand is a journey of discovery. Sometimes we learn from audience feedback, and sometimes we learn from silence (lack of feedback).</p><p>If we just keep that knowledge in our heads, it is lost. We use Gems to store this accumulated wisdom.</p><ul><li><strong>The Feedback Loop:</strong> When we discover a new keyword that works, or a tone of voice that resonates, we must feed that back into the Gem.</li><li><strong>The Result:</strong> The Gem becomes a &quot;Second Memory.&quot; It remembers the brand&apos;s history and evolution so you don&apos;t have to start from scratch every time.</li></ul><h2 id="part-3-the-capture-refine-workflow">Part 3: The Capture &amp; Refine Workflow</h2><p>How do we practically manage this evolution? We don&apos;t update the Gem every single minute, but we do capture insights constantly.</p><h3 id="step-1-capture-the-insight">Step 1: Capture the Insight</h3><p>When you have an idea or learn something about the brand, capture it immediately. Don&apos;t let the thought vanish.</p><ul><li><strong>Tools:</strong> Use whatever is fastest for you:<ul><li><strong>Capacities</strong></li><li><strong>Google Docs</strong></li><li><strong>Google Keep</strong>.</li></ul></li></ul><h3 id="step-2-the-retrofit">Step 2: The Retrofit</h3><p>At your leisure, take those captured notes and feed them back into the system.</p><ul><li>Update the <strong>First Principles</strong> logic.</li><li>Update the <strong>Brand-Specific Gem</strong> knowledge files.</li><li>Create a <strong>New Prompt</strong> if the insight reveals a gap in our toolkit.</li></ul><hr><h2 id="summary">Summary</h2><ul><li><strong>Embrace Impermanence:</strong> The video you watch today might be re-recorded in three months. That is normal.</li><li><strong>AI Moves Fast:</strong> Platforms like Gemini update constantly (e.g., adding agentic capabilities). Our Gems must update to match them.</li><li><strong>Brands Evolve:</strong> As we learn what works for a brand, we must update the Gem.</li><li><strong>Capture Everything:</strong> Use notes (Google Keep/Docs) to capture insights, then retro-fit them into the Gems later. This turns the Gem into a powerful &quot;Second Memory.&quot;</li></ul>]]></content:encoded></item><item><title><![CDATA[Creating Gems in Gemini #2]]></title><description><![CDATA[If you don't ground the AI, you get generic, hallucinated, or skewed results.]]></description><link>https://lmki.lumikha.co/creating-gems-in-gemini-2/</link><guid isPermaLink="false">692e38e5e98662083b26177c</guid><category><![CDATA[Automation]]></category><dc:creator><![CDATA[Administrator]]></dc:creator><pubDate>Tue, 02 Dec 2025 00:59:59 GMT</pubDate><content:encoded><![CDATA[<h2 id="building-high-impact-gems-with-the-first-principles-workflow">Building High-Impact Gems with the First Principles Workflow</h2>
<!--kg-card-begin: html-->
<iframe width="560" height="315" src="https://www.youtube.com/embed/NHuRhmn5Xxg?si=o5ut-1Dl2dHZoVW1" 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="avoid-zombie-mode">Avoid Zombie Mode</h2><p>Most people use AI like zombies. They lurch around, throwing generic requests into a Large Language Model (LLM), and accept whatever &quot;homogenized smoothie&quot; of information comes out.</p><p>The problem? LLMs are trained on the entire internet, and a lot of the internet is inaccurate or low-quality. If you don&apos;t ground the AI, you get generic, hallucinated, or skewed results.</p><p><strong>Our goal?</strong><br>To create consistent, high-quality, brand-specific outputs by using <strong>Gems</strong> (custom AI personas) grounded in <strong>First Principles Thinking</strong>.</p><hr><h2 id="part-1-the-two-types-of-gems">Part 1: The Two Types of Gems</h2><p>To organize our work, we categorize our Gems into two distinct buckets:</p><ol><li><strong>Generic / Prototyping Gems (The Tools)</strong><ul><li><strong>What they are:</strong> These are &quot;Prompt Builders.&quot; They don&apos;t know about a specific client yet. They are designed to help us generate high-quality instructions.</li><li><strong>Use case:</strong> A &quot;Master Prompt Builder&quot; that helps you structure a request for <em>any</em> client.</li></ul></li><li><strong>Brand-Specific Gems (The Workers)</strong><ul><li><strong>What they are:</strong> These are tailored for specific clients (e.g., &quot;Current Daily&quot;). They are pre-loaded with the client&apos;s &quot;brain.&quot;</li><li><strong>What&#x2019;s inside them:</strong><ul><li>Personas &amp; Content Pillars.</li><li>Unique Value Propositions (UVP).</li><li>Audience Profiles.</li><li>Background Research.</li><li>Style Guides.</li></ul></li></ul></li></ol><hr><h2 id="part-2-the-first-principles-workflow">Part 2: The &quot;First Principles&quot; Workflow</h2><p>We never just &quot;write a prompt.&quot; We follow a specific sequence to ensure quality.</p><h3 id="step-1-the-first-principles-analysis">Step 1: The First Principles Analysis</h3><p>Before creating a final output, we run the request through a &quot;First Principles&quot; Gem.</p><ul><li><strong>The Goal:</strong> Strip away assumptions and get to the core truth of the project.</li><li><strong>The Process:</strong> Ask <em>why</em> are we doing this? What is this product at its absolute essence?</li><li><strong>The &quot;Child Test&quot;:</strong> The output must be simple enough to explain to a six-year-old. If you can&apos;t explain it simply, you don&apos;t understand it (and neither will the AI).</li><li><strong>Why we do this:</strong> This acts as a filter to remove the &quot;internet noise&quot; and grounds the AI in reality before we start drafting marketing copy.</li></ul><h3 id="step-2-the-master-prompt-build">Step 2: The Master Prompt Build</h3><p>Once we have the First Principles analysis (the clear, simple truth), we feed that information into a <strong>Master Prompt Builder</strong>.</p><ul><li><strong>Input:</strong> The &quot;First Principles&quot; breakdown + specific project requirements (e.g., &quot;Build a website brief&quot;).</li><li><strong>Output:</strong> A sophisticated, structured prompt that defines the role, objective, and success metrics.</li></ul><h3 id="step-3-execution-the-brand-gem">Step 3: Execution (The Brand Gem)</h3><p>We take that Master Prompt and finally apply it to the Brand-Specific Gem.</p><ul><li>This is where we add the client&apos;s specific context (keywords, previous newsletters, specific documents).</li><li><strong>Result:</strong> A highly tailored output that sounds exactly like the brand, but is structurally sound because it was built on First Principles.</li></ul><hr><h3 id="part-3-organization-storage"><strong>Part 3: Organization &amp; Storage</strong></h3><p>To stay efficient, we don&apos;t let prompts float around randomly. We organize Gems and prompts into specific functional folders:</p><ul><li><strong>Foundation:</strong> Core brand elements (Research, Positioning, Voice).</li><li><strong>Operations:</strong> Day-to-day tasks (Job posts, SOWs).</li><li><strong>Search:</strong> SEO specific (Schema, Meta tagging, GEO playbooks).</li><li><strong>Content:</strong> Strategy for blogs, newsletters, and outreach.</li><li><strong>Web Development:</strong> Briefs and coding tasks.</li></ul><p><strong>Note:</strong> If a prompt is generic, it lives in the main folder. If it is for a specific client (like &quot;Lambit&quot;), it lives in that client&#x2019;s specific marketing folder.</p><hr><h2 id="summary">Summary</h2><ul><li><strong>Don&apos;t be a zombie:</strong> Stop blindly prompting. Ground your work in reality.</li><li><strong>First Principles is key:</strong> Break every problem down to its non-negotiable components. If you can&apos;t explain it to a child, start over.</li><li><strong>Structure leads to freedom:</strong> By using a rigid workflow (First Principles &gt;&gt; Master Prompt &gt;&gt; Brand Execution), we gain the freedom to create highly creative, accurate work.</li><li><strong>Centralize knowledge:</strong> Store specific client data (personas/pillars) in the Gem so you don&apos;t have to paste it in every time.</li></ul><hr>]]></content:encoded></item></channel></rss>