What this guide covers
What you’ll be able to do
- Record purpose separately from contact details
- Make changed preferences operational
- Rehearse the actual sending route
Intimacy depends on a welcome conversation. A familiar practice respects the context in which a person chose to connect.
Skip to a section
Chapter 01
Know which conversation you are continuing
A person asking for an appointment, downloading a guide and returning after a long absence are in different situations. Each interaction has a purpose and an expectation. Keep those differences visible before putting people into a common follow-up group.
- 01
Name the relationship
Distinguish a new inquiry, information request, appointment and past-patient connection. They do not automatically support the same communication purpose.
- 02
Name the message’s job
Explain why this particular message belongs in that relationship. A useful purpose is more specific than “keep them engaged.”
- 03
Check the practice’s decision
Use the practice’s approved requirements for that purpose and channel. This worksheet organises evidence; it does not determine legal eligibility.
The R.O.I. Method calls for relevant, useful encounters. Relevance includes the reason a person expects to hear from you. A good message sent into the wrong relationship can feel intrusive even when the writing is warm.
See it in action
Keep the invitation with the contact.
Recognition of your practice does not establish messaging permission.
Make the person's contact preferences clear to the team.
Carry stop requests through the relevant workflow.
Sample creative. Fictional practices; no client results implied.
Examples & steps
Write the reason for the message before selecting the list
A clear communication purpose makes the record useful. “Appointment information” should describe the actual administrative exchange. “Practice updates” should describe what the person chose to receive. “Downloaded a guide” records an event; it does not by itself explain every future message the practice might want to send.
Use a purpose statement that somebody outside the campaign can understand: who is contacting whom, about what, through which channel and why that contact fits the relationship. Keep it alongside the selection rules. This makes it easier to spot when a new campaign quietly changes the original purpose.
Do not treat a checkbox label as a complete legal analysis. The practice must determine its requirements for each jurisdiction, channel and communication type. This register organises the evidence and operational choices so those requirements can be applied consistently.
The useful test is practical: when a person asks why they received a message, can the team find the actual context without guessing? A defensible record should answer that question with facts rather than a broad label such as “marketing contact.”
| Event | What it establishes | What still needs checking |
|---|---|---|
| Appointment request | A specific request was made | The permitted administrative response and actual appointment state |
| Guide request | A particular resource was requested | Any separate ongoing communication choice |
| Practice-update preference | A recorded choice about updates | Channel, wording, date and later changes |
| Imported contact | A record entered the system | Source, purpose, current status and eligibility |
Chapter 02
Record the invitation and the choice
A practical contact record should let the team explain where the details came from, what the person requested, the channel involved and any later change in preference. Preserve the applicable form or wording when it matters to that explanation.
- 01
Keep the original request
Record where and when the relationship began and retain the relevant wording or source evidence through the practice’s maintained process.
- 02
Record purpose and channel
Show what the person requested or agreed to and the affected communication route. Do not make staff infer the whole relationship from one checkbox.
- 03
Record later changes
Make preference updates, replies and stop requests visible with their timing. The current decision needs the history of what changed.
The practice’s qualified owner determines which communications are appropriate under its obligations. The marketing team’s job is to keep the facts clear enough to apply that decision consistently, rather than treating a populated email field as the whole answer.
Examples & steps
Keep the record small, but keep the important evidence
A useful register is not a second patient chart. It stores the information needed to understand communication choices: contact identifier, purpose, channel, source, relevant wording or version, recorded date, current status and any change. Use the practice’s approved system and access controls.
Where a choice came through a form, preserve the relevant wording and version rather than relying on the current page. A form may change later. The record should reflect what was presented at the time, where that is part of the practice’s requirements. Avoid collecting extra information simply because a field is available.
Separate a source event from the present sending status. A person may have opted into one type of update and later changed that preference. Both events can matter to the history, while the latest applicable status controls the current route.
Use a visible uncertainty state for incomplete imports. “Unknown” is more honest than a guessed date or an inherited positive checkbox. Assign the uncertain group for appropriate review and keep it out of campaigns that require evidence the record does not contain.
Communication-context record
Illustrative template · adapt the facts before use
Contact reference: [approved identifier]. Purpose: [specific conversation]. Channel: [channel]. Source event: [form/request/import and date]. Relevant wording/version: [reference]. Current preference: [status]. Last change: [date and source]. Applicable practice rule: [approved process]. Unresolved question: [if any]. Owner: [role].
Chapter 03
Do not turn one request into every campaign
In this fictional example, the visitor asks the practice to email first-visit information. The team can see that request and the information already sent. Before adding her to a different recurring campaign, it checks whether that purpose is supported by the practice’s process and the choice she made.
- 01
Match the new purpose
Before adding a different campaign, compare its job with the original request and the practice’s current approved requirements.
- 02
Keep service and promotion distinct
Preparation for an agreed appointment and a general promotional message serve different purposes. Record them clearly rather than treating every email as interchangeable.
- 03
Resolve uncertainty before entry
When evidence is missing or ambiguous, route the decision to the responsible practice owner. Do not ask staff to guess because the contact looks promising.
If the visitor later books, preparation has a different job from promotion. If she changes a communication preference, the relevant future messages need to reflect it. Keeping purpose visible makes these decisions easier for the team.
See it in action
Make their choices easy to follow.
Show what the person is agreeing to.
Make contact choices easy to understand.
Examples & steps
Separate the common situations that look alike in a database
Two records can both contain an email address while representing very different expectations. One person may be waiting for appointment information; another may have chosen a periodic educational update. A third may have asked to stop promotional messages while still needing an administrative response about an existing request. The operational route should preserve those distinctions.
A new export or integration can flatten the record. If only the address transfers and the context does not, the receiving tool may treat everybody alike. Map the required fields before moving a list. Confirm that changes and exclusions travel with the contacts, not only the original positive status.
Do not infer a private clinical situation from campaign behaviour. A click on an educational page should not become a diagnosis field or an advertising audience label. Keep measurement focused on the appropriate marketing events and the practice’s approved data boundaries.
Where purposes overlap, ask the practice to define the handling rule. The goal is not to make the marketing team improvise legal judgments. The goal is to make the actual choice and context visible enough for the approved rule to work.
| Situation | Operational question |
|---|---|
| An inquiry asks to stop updates | Which messages stop, and what specific request still needs an appropriate response? |
| A person changes channel preference | Do all sending tools receive that change? |
| An old list is imported | What evidence and exclusions arrive with it? |
| A duplicate record exists | Can one record remain sendable after the other is suppressed? |
| A campaign purpose changes | Does the original context still support the new message? |
Chapter 04
Connect preferences to the sending route
A preference saved in one screen is not useful if a separate sequence ignores it. Check how an updated choice reaches the systems and people sending messages. Include scheduled steps and imported records, not just the next manual email.
- 01
Find every affected sender
Identify the systems, scheduled steps and people that may send the relevant message. A preference change in one screen may not reach them all.
- 02
Test the changed choice
Use a fictional record to check what happens after a stop or channel change. Inspect queued steps as well as the immediate response.
- 03
Verify the exception route
Include imports and reintroduced records in the review. A later data change should not silently restore a communication the person chose to stop.
Give staff a clear route when the evidence is missing or the purpose changes. Hold the affected campaign entry while the responsible person resolves it. Do not ask staff to guess based on how promising the lead looks.
Examples & steps
Test suppression as a route, not a checkbox
A preference change must affect the systems that can send. Updating one contact screen is insufficient if a queued sequence, exported list or duplicate record continues independently. Map the path from the person’s request to every relevant sending destination.
Use approved test contacts to check a change. Record the status before the request, the event that changes it, the resulting state in each relevant tool and what happens to queued communication. Include a duplicate-record case and a recently exported list if those exist in the practice’s process.
Make failure visible. If a sync fails, assign the issue and prevent the affected route from silently continuing as though the record were current. A manual exception process may be needed while a technical issue is resolved. The person’s choice should not depend on the team noticing an obscure log.
Do not claim a system is compliant because a test succeeded. The test verifies a specific operational behavior. The applicable requirements and the complete implementation still need the practice’s appropriate review.
- Identify the real sending routes and relevant queued messages.
- Use an approved test record to change one preference.
- Inspect the resulting state in each route, including duplicates and exports.
- Confirm what happens to already-queued communication.
- Record any failure, owner and temporary handling rule.
- Retest the repaired route and retain the observation date.
Chapter 05
Keep the record useful, not bloated
Retain what the team needs to understand the relationship and apply the practice’s requirements. Avoid turning a permission record into a store of unnecessary clinical detail. Access and retention belong to the practice’s established information-handling process.
- 01
Keep necessary evidence accessible
Give authorised staff the facts needed for the communication decision without exposing unrelated information. Follow the practice’s established access and retention process.
- 02
Review when the purpose changes
A new campaign, channel or integration can change the questions the record must answer. Review the process at that point rather than assuming earlier checks cover it.
- 03
Audit a small complete route
Choose a fictional or appropriately de-identified case and explain the original request, intended message, later choice and observed sending result together.
Test a fictional new enquiry, a changed preference and a record reintroduced from an old list. Ask whether the intended message is allowed by the practice’s decision and whether the actual sending route honours that choice. Review the answer whenever the campaign purpose or connected system changes.
See it in action
Continue the right conversation.
Let the person's stated preferences guide the next contact.
Examples & steps
Use the register to improve the relationship
A clear record helps the team answer questions, honour changes and avoid irrelevant contact. It can also reveal a confusing form, a vague invitation or an integration that loses context. Review those patterns at the process level rather than repeatedly correcting individual records without fixing the cause.
Give maintenance a named owner. When a new form, channel or campaign is introduced, update the record mapping and test the route. When a tool is retired, check for remaining exports and scheduled communication. A register is useful because it stays connected to the work.
Keep reporting proportionate. A campaign manager may need an aggregate count of eligible recipients and excluded records, not access to every private detail. Use the minimum information necessary for the decision and preserve the appropriate separation between marketing and clinical systems.
The tone of the message and the care of the process should agree. A warm sentence cannot compensate for ignoring a person’s preference. Reliable follow-through is one of the clearest ways a practice shows respect.
Put it to work
Trace one communication choice from form to send
Find the places where context can be lost and make the person’s choice operational.
Choose one existing journey
Select a real administrative or marketing route already used by the practice. Do not begin by redesigning every system. Write the purpose and the current approved requirements. List the form or source event, the record created, the tools involved, the message and the receiving team.
Walk the journey with a test record. Capture what the person sees and what the team receives. Compare the wording at the point of choice with the status recorded in the system. A technically successful submission can still produce an ambiguous record.
Build a field map
For each relevant field, record its meaning, source, destination, update rule and owner. Avoid a map made only of internal field names. Someone should be able to understand the decision represented by the field without knowing the software’s terminology.
Include changes. If the person revises a preference, which value should control and how is that update passed along? If two systems disagree, who resolves the conflict? A field map that describes only the first submission misses the part of the relationship most likely to change.
| Field or event | Meaning | Source of truth | What a change should do |
|---|---|---|---|
| Purpose | Why this communication fits | Approved source/context record | Change selection if purpose changes |
| Channel preference | Where communication is wanted | Latest applicable recorded choice | Update relevant sending routes |
| Suppression | Where communication must stop | Approved preference-handling record | Affect queues and duplicates |
| Source version | What wording was shown | Retained form/message version | Preserve history, not overwrite it |
| Uncertainty | Evidence is incomplete | Review queue | Prevent unsupported inclusion |
Rehearse three failures
First, imagine an old list arriving without the preference fields. Decide whether it can enter the route and who reviews it. Second, imagine a person changing their preference after an export but before the campaign sends. Check how the export is refreshed or excluded. Third, imagine a duplicate record carrying a different status. Follow the actual resolution process.
These exercises are valuable because they expose the joins between systems. The fix may be a clearer import rule, a pre-send refresh or a better identity-resolution step. It should address the cause instead of relying on the same colleague to remember every exception.
Finish with a usable operating note
Document the one journey, the verified behavior and the unresolved issues. Name the owner and the next review trigger. The note should tell the next operator what to check when the form, tool or campaign changes.
Keep the result factual: which test record was used, which routes were inspected, what happened and what remains untested. This is stronger than a blanket assurance because it gives the practice a clear basis for maintenance and further review.
Journey verification note
Illustrative template · adapt the facts before use
Purpose and route: [description]. Approved requirements used: [reference]. Test date: [date]. Source wording/version: [reference]. Systems checked: [list]. Preference change tested: [change]. Queued-message behavior: [observation]. Exceptions: [issues]. Owner and next action: [role/action]. Recheck when: [trigger].
Notes aren't saved automatically. Download them before leaving. Don't include patient details.
06 / Put it to work
Make the reason for one message visible
Permission is part of a respectful patient relationship. This worksheet supports the practice’s decisions; it does not replace qualified legal or platform review.
Which part of the contact record needs work?
Your next move
We only have the contact details
Find the original request and the relevant wording or evidence. Record purpose, channel and later preferences in a form the team can explain. Missing context needs a decision from the responsible practice owner.
- Choose one planned communication purpose.
- Locate the relevant request and evidence.
- Resolve missing context before campaign entry.
Put your plan in motion
Put PowerPANEL to work. Start with 21 days free.
Bring the handoff you want to improve. Apply to evaluate PowerPANEL around your practice’s response, booking and follow-through.
21 days free for qualifying chiropractic practices in available cities. Trial scope and terms are confirmed before access.
Explore my 21-day free trialThe method behind the work.
Continue with the original guides and the source material behind this lesson. Worked examples are teaching illustrations unless explicitly attributed.
R.O.I. Method for Chiropractors ↗Open the complete original guide.The R.O.I. Method for Chiropractors ↗Teaching foundation: PDF pages 11–12 (printed pages 10–11), Intimacy: connection, community and conversation. The worked examples are fictional applications, not client results.
