GHL Operations Guide
MAPP System Overview
MAPP is a four-part GoHighLevel system designed to capture, nurture, and convert leads into funeral planning, preneed, and financial advising services. Four distinct sub-accounts handle different business functions and lead sources. Data flows between them via webhooks, with Redtail CRM serving as the system of record for all closed deals.
Sub-Account Summary
| Sub-Account | Type | Purpose |
|---|---|---|
| MAPP Network | B2B | Recruit, onboard, and manage external partners (funeral homes, care agents, healthcare orgs) who generate leads for MAPP. |
| Call Center | B2C | Nurture leads from partners via SMS, qualify them, and route to preneed or financial pipelines. |
| BOK Pre-Need | B2C | Receive mail house lead batches, clean and qualify contacts for immediate advisor contact or 30-day nurture. |
| MAPP Wealth | B2C | Central hub for financial conversion: receive qualified leads, assign advisors, track to close, sync to Redtail CRM. |
Lead Sources
- BOK Pre-Need — Internal direct mail and marketing campaigns
- Funeral Homes — External partners submitting aftercare families
- Care Planning Connect — Medicare agents and care planning professionals (external)
- Healthcare Partnerships — Retirement communities, hospitals, clinics (external)
All external partners are recruited and managed through the MAPP Network sub-account.
How Leads Flow
- External partners are recruited and onboarded in MAPP Network.
- Families from partner funeral homes are texted via the Family Lead Intake pipeline and routed to the Call Center.
- The Call Center qualifies families and routes them to MAPP Wealth (financial) or BOK Pre-Need (preneed).
- BOK Pre-Need receives mail house batches and routes financially qualified leads to MAPP Wealth.
- MAPP Wealth assigns advisors, tracks to close, and syncs all closed deals to Redtail CRM.
System Architecture
System Map
The MAPP system operates as four interconnected sub-accounts. Each has a specific role in the funnel.
Sub-Account Switching
To switch between sub-accounts in GHL: click the sub-account name in the top-left corner, then search for or select the desired account from the dropdown.
The four sub-accounts are:
- BOK Pre-Need — 911 Porter Ave, Ocean Springs, Mississippi
- Call Center — 2511 Pass Rd, Biloxi, Mississippi
- MAPP Network — 911 Porter Ave, Ocean Springs, Mississippi
- MAPP Wealth — 911 Porter Ave, Ocean Springs, Mississippi
Integration Points
| Sub-Account | Integration |
|---|---|
| Call Center | Claude/Mistral API, Make.com |
| MAPP Wealth | Redtail CRM |
| MAPP Network | |
| BOK Pre-Need | Mail House API (Pel Hughes) |
Data Flow: Call Center → MAPP Wealth → Redtail → MAPP Wealth
- Funeral home sends family list email → Make.com mailhook parses → Claude API normalizes → webhook to Call Center Family Lead Intake.
- Call Center texts families, filters interested → webhook to Call Center Outbound Calls Pipeline.
- Call Center specialist qualifies family → marks Call Outcome → webhook to MAPP Wealth or BOK Pre-Need.
- MAPP Wealth assigns advisor → advisor works deal → webhook to Redtail on Lead Qualified.
- Redtail manages client → syncs status back to MAPP Wealth hourly.
Interactive Reference
Stage Router
Select a sub-account and pipeline to explore what happens at each stage.
Sub-Account 1
MAPP Network
B2BLead intake hub + partner relationship recruitment & management. MAPP Network receives leads from Funeral Homes, Healthcare Partners, and Care Planning Agents. It manages recruitment and partnerships with these sources, cleans incoming data, and routes contacts to the Call Center.
Pipelines at a Glance
| Pipeline | Purpose | Stages |
|---|---|---|
| Funeral Home Recruitment | Recruit & onboard funeral home partners | 8 |
| Care Planning Agent Recruitment | Recruit & manage care planning agents | 6 |
| Healthcare Partner Recruitment | Recruit retirement communities, hospitals | 7 |
MAPP Network · Pipeline 1
Funeral Home Recruitment
Recruit funeral home partners, manage processes, onboard them, and track partnership status. KPI reporting required.
Stage Overview
| # | Stage Name | Meaning | Updated By | Trigger |
|---|
Workflows
Key Custom Fields
| Field | Notes |
|---|---|
Interest Level | Hot / Warm / Cold — manual entry. Drives follow-up cadence at Conversation Held stage. Team must update based on conversation. |
Contact Status | OK to Contact / Do Not Contact. Controls whether contact can be messaged. |
MAPP Network · Pipeline 2
Care Planning Agent Recruitment
Recruit care planning agents who will send families to the Call Center. Track agent performance. Link agent-sourced families back for KPI tracking.
Stage Overview
| # | Stage Name | Meaning | Updated By | Trigger |
|---|
Workflows
MAPP Network · Pipeline 3
Healthcare Partner Recruitment
Recruit healthcare partners — retirement communities, hospitals, clinics — who can refer families to MAPP. KPI reporting required.
Stage Overview
| # | Stage Name | Meaning | Updated By | Trigger |
|---|
Workflows
Call Center · Pipeline 3
Family Lead Intake
Receives family contact lists from funeral homes, healthcare partners, and care planning agents. Data cleaning happens in Make.com before the webhook arrives. Routes cleaned contacts to the Call Center.
Stage Overview
| # | Stage Name | Meaning | Updated By | Trigger |
|---|
SMS Follow-Up Cadence
- Attempt 1: SMS sent, wait 24 hours
- Attempt 2 (no response): Follow-up SMS, wait 48 hours
- Attempt 3 (no response): Final follow-up, wait 48 hours → Archive
Workflows
Canonical 12-Field Schema (from Make.com)
| Field | Notes |
|---|---|
case_number | — |
facility_location | City and state of funeral home |
descendant_name | Decedent primary name |
descendant_dod | MM/DD/YYYY |
purchaser_name | Family contact name |
purchaser_address | — |
purchaser_city_state_zip | — |
purchaser_phone | International format: +1XXXXXXXXXX |
purchaser_relationship | Relationship to decedent |
funeral_director | — |
batch_date | YYYY-MM-DD — from filename or metadata |
funeral_home_name | From document or filename — never null |
MAPP Network
Automation Logic
FH Recruitment — Stage 1: Prospect Identified
- Tag applied: fh_prospect
- Initial partnership email sent automatically
- Contact auto-moved to "Initial Outreach Made"
- Task created: "Follow up in 3 days"
FH Recruitment — Stage 3: Conversation Held (manual move required)
Workflow checks the Interest Level field:
| Interest Level | Automated Response |
|---|---|
| Hot | Hot follow-up email sent; task "Follow up in 2 days" created. |
| Warm | Warm follow-up email sent; task "Follow up in 5 days" created. |
| Cold | Cold follow-up email sent; task "Follow up in 14 days" created. |
| Blank | Contact tagged do_not_contact and moved to Archive. |
FH Recruitment — Stages 4–6: Proposal → Agreement → Active
- Team manually moves through each stage
- "Agreement Signed" triggers FH Onboarding workflow
- Tasks created for DID assignment and credential delivery
- Relationship manager manually moves to "Partnership Active" after setup
Family Lead Intake — Deduplication
Phone number is the deduplication key. Workflow 1 checks: does a contact with this phone number already exist?
- If yes → Tag duplicate_entry, archive, stop
- If no → Create contact, apply source tags, proceed with SMS outreach
MAPP Network
Custom Fields
| Field | Type / Options | Used In |
|---|---|---|
Contact Status Override | Dropdown: OK to Contact / Do Not Contact | All pipelines |
Interest Level | Dropdown: Hot / Warm / Cold | FH, HC, Care Agent recruitment |
Care Need Type | Text | Care planning referrals |
SMS Count | Number | Family Lead Intake |
Total Contact Attempts | Number | Family Lead Intake |
MAPP Network
Reporting Dashboard
- Active partners this month vs. last month — by type (Funeral Home, Care Agent, Healthcare)
- Leads generated by each partner — bar chart
- Proposal-to-signed conversion ratio — pie chart (flag if <30%)
- Total leads in each stage — bar chart
- Active vs. inactive partners — count
- Family Lead Intake: response rate and routing distribution
Sub-Account 2
Call Center
B2CLead qualification and routing hub. The Call Center receives family contacts from MAPP Network, qualifies families for preneed or financial advising, and routes qualified leads to the appropriate destination.
Pipelines at a Glance
| Pipeline | Data Source | Stages |
|---|---|---|
| Family Lead Intake | Receive families from partners, text outreach, route to Call Center queues | 5 |
| Inbound Queue | Families calling in directly on local phone numbers | 3 |
| Outbound Calls | Tasks created from Family Lead Intake when family responds to SMS | 3 |
Call Center · Pipeline 1
Inbound Queue
Families call in directly on local phone numbers. Specialist answers, logs call, marks outcome.
Stage Overview
| # | Stage Name | Meaning | Updated By | Trigger |
|---|---|---|---|---|
| 1 | Call Received | Incoming call logged | Manual | Specialist answers call |
| 2 | Call Outcome Marked | Specialist selected outcome | Manual | Specialist updates dropdown |
| 3 | Archived | Call routed or archived | Auto | Workflow 1 processes |
Call Center · Pipeline 2
Outbound Calls
Specialists call families who responded to SMS or were referred by care agents/healthcare partners. Qualification and routing happens here.
Stage Overview
| # | Stage Name | Meaning | Updated By | Trigger |
|---|---|---|---|---|
| 1 | Task Created | Call task received from MAPP Network | Auto | Webhook 2 receives from MAPP Network |
| 2 | Call Outcome Marked | Specialist completed call, marked outcome | Manual | Specialist updates dropdown |
| 3 | Archived | Call routed or archived | Auto | Workflow 1 processes |
Call Center
Call Outcome Routing
The same Call Outcome custom field is used for both Inbound and Outbound pipelines so the team is not confused.
| Call Outcome Value | What Happens |
|---|
Workflow: Call Outcome Updated
Trigger: Call Outcome field updated by specialist (runs for both pipelines)
- Check outcome value.
- If Preneed Interested → Send webhook to BOK Pre-Need OR originating funeral home. Include contact data, call transcript URL, source tags. Move to Archived.
- If Financial Consultation Interested → Send webhook to MAPP Wealth. Move to Archived.
- If Not Interested / Wrong Number → Tag not_interested. Move to Archived.
- If Unable to Reach → Keep for retry OR move to Archived based on retry count.
- If Connected with Professional Partner → Tag with partner type. Create task. Move to Archived.
- If Completed DC Checklist → Log completion. Move to Archived.
Call Center
Custom Fields
| Field | Type / Options |
|---|---|
Call Outcome | Dropdown: Preneed Interested / Financial Consultation Interested / Not Interested / Connected with Professional Partner / Completed DC Checklist / Unable to Reach / Wrong Number / Left Voicemail / Other |
Call Transcript URL | Text — Auto-populated by LC Phone |
Call Notes | Text — Specialist notes |
Call Center
Reporting Dashboard
- Total leads received — 30-day trend line chart
- Total calls placed by agent — bar chart
- Total leads routed to each destination (BOK, MAPP Wealth, archive)
- Average call duration by agent — inbound vs. outbound
- Leads in each stage — volume at a glance
- Routing distribution — are leads flowing to MAPP Wealth, BOK, and MAPP Network appropriately?
Sub-Account 3
MAPP Wealth
B2CCentral hub for financial conversion. Receives qualified leads from Call Center and BOK Pre-Need, assigns advisors, tracks opportunities through close, syncs all closed deals to Redtail CRM, and provides executive KPI reporting.
MAPP Wealth · Pipeline 1
Mailhouse Intake (Temporary Holding)
Receives pre-need leads from BOK Pre-Need (already qualified). Validates data and transfers to the Financial Qualification pipeline.
Stage Overview
| # | Stage Name | Meaning | Updated By | Trigger |
|---|---|---|---|---|
| 1 | Batch Lead Received | Mail house batch lead arrived from BOK | Auto | Webhook from BOK Pre-Need |
| 2 | Data Cleaned | Contacts validated and ready for advisor | Auto | Validation complete |
Workflows
WF-01: Batch Validation
Trigger: Contact enters Stage 1 (Batch Received)- Validate required fields: name, phone, email
- Check for duplicate by phone number
- If duplicate → Tag duplicate_entry, archive
- If valid → Move to Stage 2 (Data Cleaned)
- Workflow 2 fires
WF-02: Auto Move Valid Contacts to Pipeline 2
Trigger: Contact enters Stage 2- Create Opportunity in Financial Qualification Pipeline Stage 1 (Lead Qualified)
- Remove from previous workflow
MAPP Wealth · Pipeline 2
Financial Qualification & Conversion
Main sales and reporting pipeline. Receives qualified leads from Call Center and BOK Pre-Need. Tracks lead status as advisor works in Redtail. Reports outcomes.
Stage Overview
| # | Stage Name | Meaning | Updated By | Trigger |
|---|---|---|---|---|
| 1 | Lead Qualified | Contact ready for advisor | Auto | Webhook from Call Center OR Workflow 1 from BOK Pre-Need |
| 2 | Meeting Scheduled | Advisor has set appointment | Auto (Redtail) | Redtail syncs back |
| 3 | Plan Presented | Advisor completed meeting, outcome recorded | Auto (Redtail) | Redtail syncs back |
| 4 | Closed Won | Deal closed, preneed plan sold | Auto | Workflow 3 when Redtail syncs "Won" |
| 5 | Closed Lost | Family declined plan | Auto | Workflow 3 when Redtail syncs "Lost" |
| 6 | Archived | No-show or no longer valid | Auto | Workflow 3 when Redtail syncs "No Show" |
Workflows
MAPP Wealth
Redtail CRM Sync
GHL → Redtail (on Closed Won or Closed Lost)
The following sequence fires automatically when a deal is marked Closed Won or Closed Lost:
- Webhook 1 → Redtail: Create Contact (First Name, Last Name, Phone, Email, Address, Lead Source). Redtail returns Contact ID.
- GHL saves Contact ID to
redtail_contact_idcustom field. - Webhook 2 → Redtail: Create Account (Preneed Plan) linked to Contact ID. Data: Plan Name, Plan Value, Plan Details.
redtail_sync_statusset tosync.- Hourly sync begins: GHL queries Redtail for latest contact/account status and updates
redtail_statusandredtail_last_sync_date.
Redtail → GHL (Hourly Sync)
| When | What | Fields |
|---|---|---|
| Advisor updates status in Redtail | Webhook sends status update back to GHL | Status, meeting date, plan value, advisor, outcome |
Key Custom Fields
| Field | Purpose |
|---|---|
redtail_contact_id | Contact ID in Redtail, saved after Webhook 1 |
redtail_sync_status | sync / pending — current sync state |
redtail_status | Latest status pulled from Redtail (e.g., Active, Pending) |
redtail_last_sync_date | Timestamp of last successful sync |
MAPP Wealth
Custom Fields
| Field | Type / Options |
|---|---|
Lead Source | Dropdown: fh_[name] / care_[agent_name] / source_healthcare / source_bok_preneed / source_referral / source_fca |
Meeting Date | Date |
Plan Value | Currency — synced from Redtail |
Plan Details | Text |
Advisor Name | Contact field |
Lead Status | Dropdown: In Progress / Closed Won / Closed Lost / No Show — synced from Redtail |
redtail_contact_id | Text — auto-populated by webhook |
redtail_sync_status | Text: sync / pending |
redtail_status | Text — latest from Redtail |
MAPP Wealth
Reporting Dashboard
- Total qualified leads — 30-day trend vs. prior month
- Leads by stage — bar chart distribution across pipeline
- Closed Won vs. Closed Lost ratio — target >40% close rate
- Leads by source — which sources are most productive
- Advisor leaderboard — leads closed and average deal value per advisor
- Redtail sync status — all deals should sync within 1 hour of close
Sub-Account 4
BOK Pre-Need
B2CPre-need lead qualification and nurturing. Receives pre-need mail house batches from Pel Hughes and internal marketing, qualifies which families are financially ready for advisor contact, routes qualified leads to MAPP Wealth, and nurtures non-qualified leads internally.
Lead Sources
- Survey Direct Mail — mailhouse (Pel Hughes)
- Lunch and Learn Events — mailhouse and online form submissions via Facebook marketing
- Website Appointment Setter — online submission
- Website Calendar of Events — online form submission
- Referrals
BOK Pre-Need · Pipeline 1
Pre-Need Lead Qualification
Receives mail house batches, validates data, qualifies financial readiness, routes qualified leads to MAPP Wealth, and nurtures non-qualified leads.
Stage Overview
| # | Stage Name | Meaning | Updated By | Trigger |
|---|---|---|---|---|
| 1 | Batch Received | Mail house batch imported | Auto | File upload or webhook from Pel Hughes API |
| 2 | Data Cleaned | Validated and qualified | Auto | Validation logic complete |
| 3 | Qualified | Lead qualified for MAPP Wealth | Manual | Team manually moves here |
| 4 | Not Qualified | Lead does not qualify for MAPP Wealth yet | Manual | Team manually moves here |
Workflows
WF-01: Batch Data Validation
Trigger: Contact enters Stage 1 (Batch Received)- Contact received from Mailhouse API webhook or Call Center inbound webhook
- Validate required fields: name, phone, email, address
- Check for duplicate by phone number
- If valid → Move to Stage 2 (Data Cleaned)
- Workflow 2 fires
WF-02: Qualify and Route to MAPP Wealth
Trigger: Contact moves to Stage 3 (Qualified) or Stage 4 (Not Qualified)- Check which stage contact is in
- If Qualified → Tag qualified_financial, send webhook to MAPP Wealth (Mail House Intake) with all contact fields and source tag source_bok_preneed
- If Not Qualified → Tag nurture_later, contact remains in BOK for internal nurturing. Create task: "Follow up with [Name] for preneed interest in 30 days"
BOK Pre-Need
Custom Fields
| Field | Type / Options |
|---|---|
Batch ID | Text |
Batch Date | Date |
Data Valid | Yes / No — whether phone, email, name are correctly formatted |
Duplicate Detected | Yes / No |
BOK Pre-Need
Reporting Dashboard
- Total leads routed to MAPP Wealth — 30-day trend
- Qualified vs. Not Qualified ratio — pie chart (flag if <20%)
- Lead intake trend — batches arriving per week
- Stage distribution — leads in each stage
Integrations
Make.com + Claude/Mistral AI API Integration
Handles document extraction and normalization before data enters GHL. Triggered when a funeral home sends an email with an attachment to aftercare@mappnw.com.
Process Flow
- Funeral home sends email with attachment (CSV, XLSX, or PDF) to
aftercare@mappnw.comwhich automatically triggers a mailhook in Make.com. - Make.com extracts and temporarily stores the attachment.
- Data parsed: CSV/XLSX parsed directly to JSON; PDF converted to text, then Claude/Mistral AI API extracts structured data.
- Each contact processed: phone formatted to international format (+1XXXXXXXXXX), date formatted MM/DD/YYYY, metadata appended (source_type, batch_date).
- Make.com sends one webhook per contact to the MAPP Network Family Lead Intake pipeline.
- GHL receives, creates contact, fires Workflow 1 (dedup check, tagging, SMS outreach).
API Extraction
API returns a JSON array — one entry per contact, 12 fields each:
case_numberfacility_location(city and state)descendant_namedescendant_dod(MM/DD/YYYY)purchaser_namepurchaser_addresspurchaser_city_state_zippurchaser_phone(+14155552671 format)purchaser_relationshipfuneral_directorbatch_date(YYYY-MM-DD from filename or metadata)funeral_home_name(never null)
Deduplication
MAPP Network Workflow 1 checks: does a contact with this phone number already exist?
- If yes → Tag duplicate_entry, archive, stop
- If no → Create contact, proceed
Integrations
Redtail CRM Integration
Two-way sync between MAPP Wealth and Redtail CRM. Advisors manage clients in Redtail; status updates sync back to GHL automatically.
GHL → Redtail
| Attribute | Detail |
|---|---|
| When | Contact reaches MAPP Wealth "Closed Won" or "Closed Lost" stage |
| What | Webhook sends contact data to Redtail, first webhook created a contact and get back contact id to save in custom field in GHL and second webhook use that redtail contact id to create account in redtail for that contact. |
| Fields | firstName, lastName, phone, email |
Redtail → GHL
| Attribute | Detail |
|---|---|
| When | "Redtail Sync Status" custom field is set to "Synced" |
| What | Wait for 1 hour for each contact and send GET request to redtail to find updated fields |
| Fields | Redtail Status, Redtail Status ID, Last Sync Date |
System Reference
Important Custom Fields — All Sub-Accounts
MAPP Network
| Field | Type / Options |
|---|---|
Contact Status Override | Dropdown: OK to Contact / Do Not Contact |
Interest Level | Dropdown: Hot / Warm / Cold |
Call Center
| Field | Type / Options |
|---|---|
Call Outcome | Dropdown: Preneed Interested / Financial Consultation Interested / Not Interested / Connected Professional / DC Checklist / Unable to Reach / Wrong Number / Left Voicemail / Other |
Call Transcript URL | Text |
Call Notes | Text — Specialist notes |
MAPP Wealth
| Field | Type / Options |
|---|---|
Lead Source | Text |
Advisor Name | Contact field |
Lead Status | Dropdown: In Progress / Closed Won / Closed Lost / No Show — Synced from Redtail |
BOK Pre-Need
| Field | Type / Options |
|---|---|
Batch ID | Text |
Batch Date | Date |
Data Valid | Yes / No |
System Reference
Golden Rules
These rules keep the system working. Breaking any of them creates downstream data loss, missed leads, or broken reporting.
System Reference
Troubleshooting
A contact appears twice in my pipeline
Check whether phone numbers are identical. Different phones = two separate people, no problem. Same phone = should never happen. Contact Admin to dedup and investigate.
I marked Call Outcome but the lead didn't arrive in MAPP Wealth
Wait 2–3 minutes for webhook processing, then search MAPP Wealth by phone number. If not found, contact Admin with a screenshot of the marked Call Outcome — the webhook may have failed.
A contact is marked "Do Not Contact" but they want to hear from us
Change the Contact Status field from "Do Not Contact" to "OK to Contact." You can then resume texting or calling.
A contact moved to Archive but I'm not done with them
Contact Admin to move them back to an active stage. Or create a manual task outside the pipeline to follow up.
A contact in Call Center is missing plan details
Look in MAPP Wealth under that phone number. If the advisor has not completed Meeting Notes and Plan Details, create a task for them to fill it in.
Redtail sync stopped — last sync was 2+ days ago
Contact Admin. The hourly sync workflow may have failed. Admin will check the integration status and restart if needed.
BOK Qualified rate is under 20%
This signals a data quality issue from the mail house OR qualification criteria may be too strict. Flag for review with the team.
System Reference
KPI Reports
Report Overview
| Report Name | Description | Type |
|---|---|---|
| Top Lead Sources | Rank all sources (FH, Care Planning, Healthcare, BOK) by volume, conversion rate, and plan value | Dashboard |
| Conversion Funnel | Track leads from intake → Call Center → MAPP Wealth → Closed Won | Funnel Chart |
| Best Performing Funeral Homes | Rank FHs by families referred, qualification rate, conversion to closed won, avg plan value | Leaderboard |
| Call Center Performance | Specialist outcomes: total calls, qualification rate, transfer rate to MAPP Wealth | Scorecard |
| Lead Status Breakdown | Qualified leads, meetings scheduled, plans presented, closed won/lost, no-shows by advisor | Pipeline Report |
| Redtail Sync Health | Leads sent to Redtail, status updates received, sync errors, data quality metrics | Health Report |
| Pre-Need vs Financial | Split between preneed and financial paths, conversion rate by type, avg plan value by type | Comparative |
| Lifetime Value by Source | Avg LTV of a customer from each source | Financial |
| Churn Rate | Partners inactive after onboarding, family no-show rate, lost deals by reason | Risk Report |
Key Dashboards
MAPP Network Dashboard
- Active partners count — should be growing or stable
- Leads by partner — identify high-volume partners
- Proposal-to-signed ratio — flag if <30%
Call Center Dashboard
- Daily lead intake trend — spot when batches arrive
- Calls per agent — identify capacity constraints
- Routing distribution — are leads flowing to MAPP Wealth, BOK, and MAPP Network appropriately?
BOK Pre-Need Dashboard
- Batch intake frequency — when are mail house batches arriving?
- Qualified/not-qualified ratio — flag if <20%
MAPP Wealth Dashboard
- Closed Won / Closed Lost ratio — target >40% close rate
- Leads by source — which sources are most productive?
- Advisor leaderboard — performance management data
- Redtail sync status — all deals should sync within 1 hour of close
Text Program KPIs
- Leads entered into text program
- Response rate — % of leads that reply
- Conversation rate — % that go beyond 1 reply
- Appointments set via text
- Texts converted to calls — after 48hr no response
- Opt-out rate
Call KPIs
- Contact rate — % of leads successfully reached
- Speed to first contact
- Qualification rate — % moved to Pre-Need ready / Financial interest / Nurture
- Appointment set rate + show rate
- Lead leakage rate — % that never get contacted or stall out