Week 3 of 8

Communication Points and Lead Entry Map

Communication planning starts with knowing where leads actually enter the CRM. Map every entry point and every touchpoint before you build a single automation.

A lead entry point is any place a new contact can arrive: a form, a calendar, a phone call, a chat widget, an import, a QR code, a manual add, or an integration.

A communication point is any message the CRM sends or receives after a contact arrives: confirmations, reminders, follow-ups, internal notifications, and long-term nurture. You cannot plan communication until you know every entry point it must respond to.

This week is not about writing every final email or building every workflow. It is about mapping the moments that require communication. Before you automate anything, you need to know who should hear from you, what they should receive, when they should receive it, and what should happen if they reply, book, ignore, cancel, or no-show.

Why This Matters

Workflows are just a delivery mechanism. If the messages, tone, and timing are not planned, the workflow will faithfully deliver a bad experience.

What Usually Goes Wrong

Confirmation emails written inside the workflow, on the fly
Reminders that overlap or contradict each other
No plan for no-show follow-up
Internal notifications go to the wrong person, or no one at all
No consent language anywhere in the flow
Two entry points that quietly trigger the same nurture, doubling every message

Lead Entry Points to Map

Website forms
Landing page forms
Calendar bookings
Chat widgets
Phone calls and missed calls
SMS opt-ins
Manual contact adds by the team
CSV imports
Integrations from ads, funnels, or third-party tools
QR codes
Payments, order forms, and signed documents
Social DMs from connected channels

Lead Entry Point Examples

A lead entry point is not only a website form. Leads can enter the CRM from many places, and each source may require a different response.

Website form

Someone fills out a contact form, quote request, lead magnet form, or consultation request.

Calendar booking

Someone books a call, consultation, demo, service visit, or appointment.

Chat widget

Someone starts a conversation from the website.

Phone call or missed call

Someone calls the business number, leaves a voicemail, or misses the team.

Inbound SMS

Someone texts the business number first.

Social DM

Someone sends a message from a connected social channel.

Manual add

A team member adds a contact after a real-world conversation, networking event, phone call, or referral.

CSV import

A list is imported from a previous CRM, spreadsheet, event, or existing database.

Ad integration

A lead arrives from a Facebook, Google, TikTok, LinkedIn, or other lead form integration.

QR code

Someone scans a QR code from a flyer, sign, event, table tent, business card, or print material.

Payment, order, or document

Someone becomes a contact by paying, requesting a quote, completing an order form, or signing a document.

Note

If a person can enter the CRM from that place, it needs to be mapped.

Communication Point Categories

External to the contact

Confirmation, reminder, follow-up, nurture, re-engagement, and thank-you messages sent by email, SMS, or voicemail.

Internal to the team

Notifications when a lead arrives, when an appointment is booked, when a no-show happens, and when a stage changes.

Conditional

Messages that only send in certain cases: booked vs not booked, showed vs no-show, replied vs no reply.

Human handoff

A human handoff happens when the CRM should notify, assign, or alert a real person instead of sending another automated message. Not every touchpoint should be automated. Some moments need a team member to call, review, approve, assign, or personally reply.

Channel and Timing Rules

Pick one primary channel per moment. If email confirms the booking, SMS is only for a short reminder. Do not send both a full email and a full SMS for every event.

Timing rules to follow: confirmations send immediately, reminders send 24 hours and 1 hour before, follow-ups after a no-show send within 2 hours, and long-term nurture starts only after the immediate sequence ends.

Message Map Example

Here is a simple example for a consultation form. This is the level of thinking that should happen before the workflow is built.

Entry point

Consultation request form.

Immediate contact message

Confirmation email thanking the lead and explaining the next step.

Immediate team message

Internal notification to the assigned user with the contact name, phone, email, source, and requested service.

If the lead books

Appointment confirmation email, short SMS reminder, and pipeline move to Appointment Booked.

If the lead does not book

Follow-up email after 1 day, SMS reminder after 2 days if consent exists, and pipeline stays in New Lead or Follow-Up Needed.

If the appointment is completed

Internal task to record notes, pipeline move to Appointment Completed, and follow-up email with next step.

If the appointment is missed

No-show follow-up within 2 hours and internal notification to review.

If there is no response

Long-term nurture starts only after the immediate follow-up sequence ends.

Consent and Compliance Basics

Every form and opt-in should state what the contact will receive.
Every outbound email must include a physical address and unsubscribe link.
SMS messages must include opt-out instructions (STOP to unsubscribe).
Do not import a list into an active nurture without a valid consent source.
Consent and compliance rules can vary by country, state, industry, message type, and platform requirements. Treat this as a planning baseline, not legal advice.

What to Build

A full list of lead entry points
A journey map from first contact to long-term nurture
A list of every external message
A list of every internal notification
A list of human handoff moments
A timing plan for confirmations, reminders, follow-ups, no-shows, and nurture
A channel plan for email, SMS, calls, voicemail, tasks, and internal alerts
A basic consent and compliance approach
A note showing where pipeline stages, tags, and fields connect to the journey

Before You Build in the CRM

Map the communication journey before opening the workflow builder. A workflow should not be where you figure out what to say. The workflow should only deliver a communication plan that already exists.

Start outside the CRM. Use a document, spreadsheet, whiteboard, Figma board, or your preferred AI assistant to map the full journey. Put each lead entry point on the left, then map what the contact receives, what the team receives, what happens if the contact takes action, and what happens if they do nothing.

Your communication map should answer:

?Where did the lead enter?
?What should the contact receive immediately?
?What should the team receive immediately?
?What pipeline stage should this affect?
?What tag or field should be applied?
?What happens if the contact books?
?What happens if the contact does not book?
?What happens if the contact replies?
?What happens if the contact no-shows?
?What happens if the contact becomes a client?
?What happens if the contact is not a fit?
?When does immediate follow-up stop?
?When does long-term nurture begin?
?What consent language is needed at the entry point?
?Which messages should be email, SMS, call, voicemail, task, or internal notification?

Note

Suggested AI prompt: “I am mapping communication points for my CRM before building workflows. Help me create a lead entry and communication map. For each entry point, identify the immediate contact message, internal team notification, pipeline stage, tags or fields, follow-up timing, conditional paths, no-show handling, reply handling, and long-term nurture handoff. Point out duplicate messages, missing consent steps, and places where a human handoff is better than automation.” The goal is to make the communication clear before the automation exists. If the journey does not make sense on paper, it will not make sense inside the workflow builder.

Step-by-Step Training

1
List every place a lead can enter the CRM.
2
Group entry points by type: forms, calendars, calls, chat, imports, integrations, payments, QR codes, and manual adds.
3
For each entry point, define what the contact expects to happen next.
4
For each entry point, define what the team needs to know internally.
5
Map the first external message the contact should receive.
6
Map the first internal notification the team should receive.
7
Decide which pipeline stage should be created or updated.
8
Decide which tags or fields should be applied.
9
Decide what happens if the contact books, replies, ignores, no-shows, cancels, or becomes a client.
10
Choose the best channel for each message: email, SMS, call, voicemail, task, or internal notification.
11
Write the timing for each message.
12
Add consent, unsubscribe, and opt-out requirements where needed.
13
Review the map for duplicate or conflicting messages.
14
Only then begin planning the workflows that will deliver the communication.

Practical Exercise

Part 1: Map Every Lead Entry Point

Write down every current and planned entry point:

1
Website forms
2
Landing pages
3
Calendar bookings
4
Chat widget
5
Inbound SMS
6
Phone calls
7
Missed calls
8
Manual adds
9
CSV imports
10
Ads and integrations
11
QR codes and offline sources
12
Payments, order forms, documents, or contracts
13
Social DMs if connected

Part 2: Draft One Communication Journey

Choose one entry point and map the full journey:

1
Immediate confirmation to contact
2
Immediate internal notification
3
Pipeline stage created or updated
4
Tags or fields applied
5
Reminder plan for any scheduled event
6
What happens if the contact books
7
What happens if the contact does not book
8
What happens if the contact replies
9
What happens if the contact no-shows
10
What happens if the contact becomes a client
11
Handoff to long-term nurture

Part 3: Find Duplicates and Gaps

Review the journey and look for:

1
Two messages saying the same thing
2
Email and SMS both sending too much information
3
Missing internal notification
4
Missing no-show plan
5
Missing unsubscribe or opt-out language
6
No clear stop point before long-term nurture
7
No human handoff where one is needed
8
Two entry points triggering the same nurture by accident

Done Means Done Checklist

✓Every lead entry point is listed
✓Every touchpoint is mapped
✓External messages are separated from internal notifications
✓Human handoff moments are identified
✓Appointment communication is planned
✓No-show and no-reply logic is documented
✓Long-term nurture handoff is documented
✓The preferred channel is chosen for each message
✓Timing is defined for each message
✓Pipeline stage updates are mapped
✓Tags and fields are mapped where needed
✓Consent language is planned for every entry point
✓Unsubscribe and SMS opt-out requirements are included where needed
✓Duplicate messages have been removed
✓Messages are planned before workflows are built

Common Mistakes

Watch for these

Writing message copy inside the workflow builder
Sending both an email and an SMS confirmation for every event
Forgetting internal notifications completely
No unsubscribe or opt-out language in outbound messages
Two entry points quietly firing the same nurture and doubling every message
Treating the workflow builder like a writing tool
Forgetting to map what happens when someone replies
Forgetting to stop immediate follow-up before long-term nurture starts
Sending the same message from two different entry points
Automating moments that should be human handoffs
Using SMS for long messages that should be email
Building no-show logic after appointments are already live
Not connecting communication points back to pipeline stages

Related SOPs

Conversations
Email Campaigns
SMS and A2P Awareness
Workflows
Calendars

Next lesson

Week 4: Calendars and Appointment Flow

Start Week 4