Enter Access Password

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.

4
Sub-Accounts
9
Total Pipelines
32
Total Stages
20
Total Workflows

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.
Key Principle Each sub-account owns one piece of the funnel. Automation routes leads between them. Your job is to manage your piece and know when to hand it forward.

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

  1. External partners are recruited and onboarded in MAPP Network.
  2. Families from partner funeral homes are texted via the Family Lead Intake pipeline and routed to the Call Center.
  3. The Call Center qualifies families and routes them to MAPP Wealth (financial) or BOK Pre-Need (preneed).
  4. BOK Pre-Need receives mail house batches and routes financially qualified leads to MAPP Wealth.
  5. 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-AccountIntegration
Call CenterClaude/Mistral API, Make.com
MAPP WealthRedtail CRM
MAPP Network
BOK Pre-NeedMail House API (Pel Hughes)

Data Flow: Call Center → MAPP Wealth → Redtail → MAPP Wealth

  1. Funeral home sends family list email → Make.com mailhook parses → Claude API normalizes → webhook to Call Center Family Lead Intake.
  2. Call Center texts families, filters interested → webhook to Call Center Outbound Calls Pipeline.
  3. Call Center specialist qualifies family → marks Call Outcome → webhook to MAPP Wealth or BOK Pre-Need.
  4. MAPP Wealth assigns advisor → advisor works deal → webhook to Redtail on Lead Qualified.
  5. 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

B2B

Lead 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.

3
Pipelines
13
Workflows
4
Lead Sources

Pipelines at a Glance

PipelinePurposeStages
Funeral Home RecruitmentRecruit & onboard funeral home partners8
Care Planning Agent RecruitmentRecruit & manage care planning agents6
Healthcare Partner RecruitmentRecruit retirement communities, hospitals7
Critical Handoff Partners you onboard in MAPP Network generate leads that flow into Call Center → MAPP Wealth → Redtail.

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 NameMeaningUpdated ByTrigger

Workflows

Key Custom Fields

FieldNotes
Interest LevelHot / Warm / Cold — manual entry. Drives follow-up cadence at Conversation Held stage. Team must update based on conversation.
Contact StatusOK 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 NameMeaningUpdated ByTrigger

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 NameMeaningUpdated ByTrigger

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.

Text Program Note Currently, a specialist is sending texts manually. The goal is to move to full automation or AI. First contact is via text. If no reply after 48 hours, family is contacted by call.

Stage Overview

#Stage NameMeaningUpdated ByTrigger

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)

FieldNotes
case_number
facility_locationCity and state of funeral home
descendant_nameDecedent primary name
descendant_dodMM/DD/YYYY
purchaser_nameFamily contact name
purchaser_address
purchaser_city_state_zip
purchaser_phoneInternational format: +1XXXXXXXXXX
purchaser_relationshipRelationship to decedent
funeral_director
batch_dateYYYY-MM-DD — from filename or metadata
funeral_home_nameFrom 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 LevelAutomated Response
HotHot follow-up email sent; task "Follow up in 2 days" created.
WarmWarm follow-up email sent; task "Follow up in 5 days" created.
ColdCold follow-up email sent; task "Follow up in 14 days" created.
BlankContact 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

FieldType / OptionsUsed In
Contact Status OverrideDropdown: OK to Contact / Do Not ContactAll pipelines
Interest LevelDropdown: Hot / Warm / ColdFH, HC, Care Agent recruitment
Care Need TypeTextCare planning referrals
SMS CountNumberFamily Lead Intake
Total Contact AttemptsNumberFamily 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

B2C

Lead 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.

3
Pipelines
2
Workflows
2
Queue Types
Critical Rule Call Outcome is the nerve center of the entire system. If Call Outcome is not marked, the lead routes nowhere. Always mark outcome before closing the call task.

Pipelines at a Glance

PipelineData SourceStages
Family Lead IntakeReceive families from partners, text outreach, route to Call Center queues5
Inbound QueueFamilies calling in directly on local phone numbers3
Outbound CallsTasks created from Family Lead Intake when family responds to SMS3

Call Center · Pipeline 1

Inbound Queue

Families call in directly on local phone numbers. Specialist answers, logs call, marks outcome.

Stage Overview

#Stage NameMeaningUpdated ByTrigger
1Call ReceivedIncoming call loggedManualSpecialist answers call
2Call Outcome MarkedSpecialist selected outcomeManualSpecialist updates dropdown
3ArchivedCall routed or archivedAutoWorkflow 1 processes
Shared Workflow The Call Outcome Updated workflow (WF-01) runs for both Inbound Queue and Outbound Calls pipelines. See Call Outcome Routing for full logic.

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 NameMeaningUpdated ByTrigger
1Task CreatedCall task received from MAPP NetworkAutoWebhook 2 receives from MAPP Network
2Call Outcome MarkedSpecialist completed call, marked outcomeManualSpecialist updates dropdown
3ArchivedCall routed or archivedAutoWorkflow 1 processes

Call Center

Call Outcome Routing

Critical Call Outcome is the nerve center of the entire system. If it is not marked, the lead does not route anywhere. Always mark outcome before closing the call task.

The same Call Outcome custom field is used for both Inbound and Outbound pipelines so the team is not confused.

Call Outcome ValueWhat Happens

Workflow: Call Outcome Updated

Trigger: Call Outcome field updated by specialist (runs for both pipelines)

  1. Check outcome value.
  2. If Preneed Interested → Send webhook to BOK Pre-Need OR originating funeral home. Include contact data, call transcript URL, source tags. Move to Archived.
  3. If Financial Consultation Interested → Send webhook to MAPP Wealth. Move to Archived.
  4. If Not Interested / Wrong Number → Tag not_interested. Move to Archived.
  5. If Unable to Reach → Keep for retry OR move to Archived based on retry count.
  6. If Connected with Professional Partner → Tag with partner type. Create task. Move to Archived.
  7. If Completed DC Checklist → Log completion. Move to Archived.
Future Feature: PreNeed Referral Back to FH When outcome = Preneed Interested and lead originated from a funeral home, the estate specialist tags the contact as "PreNeed Referral" which triggers an automated email back to the FH of origin. This process is planned but not yet implemented.

Call Center

Custom Fields

FieldType / Options
Call OutcomeDropdown: Preneed Interested / Financial Consultation Interested / Not Interested / Connected with Professional Partner / Completed DC Checklist / Unable to Reach / Wrong Number / Left Voicemail / Other
Call Transcript URLText — Auto-populated by LC Phone
Call NotesText — 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

B2C

Central 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.

2
Pipelines
4
Workflows
1
External Integration
Redtail is the System of Record Once a deal is in Redtail, that is the official record. Do not manually update plan details in GHL — update in Redtail first. GHL mirrors Redtail status hourly.

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 NameMeaningUpdated ByTrigger
1Batch Lead ReceivedMail house batch lead arrived from BOKAutoWebhook from BOK Pre-Need
2Data CleanedContacts validated and ready for advisorAutoValidation complete

Workflows

WF-01: Batch Validation

Trigger: Contact enters Stage 1 (Batch Received)
  1. Validate required fields: name, phone, email
  2. Check for duplicate by phone number
  3. If duplicate → Tag duplicate_entry, archive
  4. If valid → Move to Stage 2 (Data Cleaned)
  5. Workflow 2 fires

WF-02: Auto Move Valid Contacts to Pipeline 2

Trigger: Contact enters Stage 2
  1. Create Opportunity in Financial Qualification Pipeline Stage 1 (Lead Qualified)
  2. 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 NameMeaningUpdated ByTrigger
1Lead QualifiedContact ready for advisorAutoWebhook from Call Center OR Workflow 1 from BOK Pre-Need
2Meeting ScheduledAdvisor has set appointmentAuto (Redtail)Redtail syncs back
3Plan PresentedAdvisor completed meeting, outcome recordedAuto (Redtail)Redtail syncs back
4Closed WonDeal closed, preneed plan soldAutoWorkflow 3 when Redtail syncs "Won"
5Closed LostFamily declined planAutoWorkflow 3 when Redtail syncs "Lost"
6ArchivedNo-show or no longer validAutoWorkflow 3 when Redtail syncs "No Show"

Workflows

MAPP Wealth

Redtail CRM Sync

Redtail is the System of Record Once a deal is in Redtail, that is the official record. Update plan details in Redtail first — GHL mirrors Redtail status hourly.

GHL → Redtail (on Closed Won or Closed Lost)

The following sequence fires automatically when a deal is marked Closed Won or Closed Lost:

  1. Webhook 1 → Redtail: Create Contact (First Name, Last Name, Phone, Email, Address, Lead Source). Redtail returns Contact ID.
  2. GHL saves Contact ID to redtail_contact_id custom field.
  3. Webhook 2 → Redtail: Create Account (Preneed Plan) linked to Contact ID. Data: Plan Name, Plan Value, Plan Details.
  4. redtail_sync_status set to sync.
  5. Hourly sync begins: GHL queries Redtail for latest contact/account status and updates redtail_status and redtail_last_sync_date.

Redtail → GHL (Hourly Sync)

WhenWhatFields
Advisor updates status in RedtailWebhook sends status update back to GHLStatus, meeting date, plan value, advisor, outcome

Key Custom Fields

FieldPurpose
redtail_contact_idContact ID in Redtail, saved after Webhook 1
redtail_sync_statussync / pending — current sync state
redtail_statusLatest status pulled from Redtail (e.g., Active, Pending)
redtail_last_sync_dateTimestamp of last successful sync

MAPP Wealth

Custom Fields

FieldType / Options
Lead SourceDropdown: fh_[name] / care_[agent_name] / source_healthcare / source_bok_preneed / source_referral / source_fca
Meeting DateDate
Plan ValueCurrency — synced from Redtail
Plan DetailsText
Advisor NameContact field
Lead StatusDropdown: In Progress / Closed Won / Closed Lost / No Show — synced from Redtail
redtail_contact_idText — auto-populated by webhook
redtail_sync_statusText: sync / pending
redtail_statusText — 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

B2C

Pre-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.

1
Pipeline
2
Workflows
MAPP Wealth
Downstream

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
Critical Handoff Marking a contact Qualified sends it to MAPP Wealth. The advisor handles everything from there.
Watch This Metric If the Qualified rate is under 20%, that signals a data quality issue or that qualification criteria may be too strict. Flag for review.

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 NameMeaningUpdated ByTrigger
1Batch ReceivedMail house batch importedAutoFile upload or webhook from Pel Hughes API
2Data CleanedValidated and qualifiedAutoValidation logic complete
3QualifiedLead qualified for MAPP WealthManualTeam manually moves here
4Not QualifiedLead does not qualify for MAPP Wealth yetManualTeam manually moves here

Workflows

WF-01: Batch Data Validation

Trigger: Contact enters Stage 1 (Batch Received)
  1. Contact received from Mailhouse API webhook or Call Center inbound webhook
  2. Validate required fields: name, phone, email, address
  3. Check for duplicate by phone number
  4. If valid → Move to Stage 2 (Data Cleaned)
  5. Workflow 2 fires

WF-02: Qualify and Route to MAPP Wealth

Trigger: Contact moves to Stage 3 (Qualified) or Stage 4 (Not Qualified)
  1. Check which stage contact is in
  2. If Qualified → Tag qualified_financial, send webhook to MAPP Wealth (Mail House Intake) with all contact fields and source tag source_bok_preneed
  3. 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

FieldType / Options
Batch IDText
Batch DateDate
Data ValidYes / No — whether phone, email, name are correctly formatted
Duplicate DetectedYes / 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

  1. Funeral home sends email with attachment (CSV, XLSX, or PDF) to aftercare@mappnw.com which automatically triggers a mailhook in Make.com.
  2. Make.com extracts and temporarily stores the attachment.
  3. Data parsed: CSV/XLSX parsed directly to JSON; PDF converted to text, then Claude/Mistral AI API extracts structured data.
  4. Each contact processed: phone formatted to international format (+1XXXXXXXXXX), date formatted MM/DD/YYYY, metadata appended (source_type, batch_date).
  5. Make.com sends one webhook per contact to the MAPP Network Family Lead Intake pipeline.
  6. 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_number
  • facility_location (city and state)
  • descendant_name
  • descendant_dod (MM/DD/YYYY)
  • purchaser_name
  • purchaser_address
  • purchaser_city_state_zip
  • purchaser_phone (+14155552671 format)
  • purchaser_relationship
  • funeral_director
  • batch_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

AttributeDetail
WhenContact reaches MAPP Wealth "Closed Won" or "Closed Lost" stage
WhatWebhook 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.
FieldsfirstName, lastName, phone, email

Redtail → GHL

AttributeDetail
When"Redtail Sync Status" custom field is set to "Synced"
WhatWait for 1 hour for each contact and send GET request to redtail to find updated fields
FieldsRedtail Status, Redtail Status ID, Last Sync Date

System Reference

Important Custom Fields — All Sub-Accounts

MAPP Network

FieldType / Options
Contact Status OverrideDropdown: OK to Contact / Do Not Contact
Interest LevelDropdown: Hot / Warm / Cold

Call Center

FieldType / Options
Call OutcomeDropdown: Preneed Interested / Financial Consultation Interested / Not Interested / Connected Professional / DC Checklist / Unable to Reach / Wrong Number / Left Voicemail / Other
Call Transcript URLText
Call NotesText — Specialist notes

MAPP Wealth

FieldType / Options
Lead SourceText
Advisor NameContact field
Lead StatusDropdown: In Progress / Closed Won / Closed Lost / No Show — Synced from Redtail

BOK Pre-Need

FieldType / Options
Batch IDText
Batch DateDate
Data ValidYes / No

System Reference

Tagging System

Tags are auto-generated by workflows. Do not delete system tags — removing them breaks downstream reporting and lead attribution.

Source Tags

source_bok source_funeral_home source_care_agent source_healthcare batch_[date]

Partner-Specific Tags

fh_prospect care_prospect hc_prospect care_active_agent hc_active_partner

Qualification Tags

qualified_preneed qualified_financial nurture_later duplicate_entry

Routing Tags

sent_to_call_center sent_to_bok sent_to_wealth from_call_center

Outcome Tags

not_interested unable_to_reach wrong_number do_not_contact appointment_set appointment_completed sale_closed sale_preneed sale_wealth closed_won closed_lost redtail_synced advisor_assigned

Text Program Tags

text-engaged text-no-response text-to-call call-only appointment-set-text appointment-set-call

System Reference

Golden Rules

These rules keep the system working. Breaking any of them creates downstream data loss, missed leads, or broken reporting.

Rule 1: Phone number is the deduplication key. The system checks phone number before creating any contact. If the phone already exists, the contact is skipped. Always verify phone numbers are correct before import.
Rule 2: Three SMS attempts maximum. Families are texted no more than 3 times before archiving. Do not manually re-text after auto-archive without admin approval.
Rule 3: Call Outcome is mandatory. If Call Outcome is not marked in Call Center, the lead routes nowhere. Always mark outcome before closing the call task.
Rule 4: Tags are auto-generated — do not delete. Tags like fh_routsong, source_bok_preneed, and care_jane_smith are system-created. Deleting them breaks downstream reporting and lead attribution.
Rule 5: Lead Source attribution on every lead. Every contact must carry source tags. Reporting depends on these for source ROI analysis. Missing tags make the lead invisible in dashboards.
Rule 6: Redtail is the truth after Closed Won/Lost. Once a deal is in Redtail, that is the official record. GHL mirrors Redtail status hourly. Update plan details in Redtail first.
Rule 7: Manual moves are required at key decision points. MAPP Network: Conversation Held through Agreement Signed. Call Center: Call Outcome marking. BOK: Qualified vs. Not Qualified decision. MAPP Wealth: stage progression. The system does not auto-guess your next move.

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 NameDescriptionType
Top Lead SourcesRank all sources (FH, Care Planning, Healthcare, BOK) by volume, conversion rate, and plan valueDashboard
Conversion FunnelTrack leads from intake → Call Center → MAPP Wealth → Closed WonFunnel Chart
Best Performing Funeral HomesRank FHs by families referred, qualification rate, conversion to closed won, avg plan valueLeaderboard
Call Center PerformanceSpecialist outcomes: total calls, qualification rate, transfer rate to MAPP WealthScorecard
Lead Status BreakdownQualified leads, meetings scheduled, plans presented, closed won/lost, no-shows by advisorPipeline Report
Redtail Sync HealthLeads sent to Redtail, status updates received, sync errors, data quality metricsHealth Report
Pre-Need vs FinancialSplit between preneed and financial paths, conversion rate by type, avg plan value by typeComparative
Lifetime Value by SourceAvg LTV of a customer from each sourceFinancial
Churn RatePartners inactive after onboarding, family no-show rate, lost deals by reasonRisk 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