DOCTOR PROMOTION / CONSIDERED SCOPE
Follow-up Automation
Build consent-based follow-ups around a defined process.

FOLLOW-UP AUTOMATION / EXAMPLE OUTPUTS
Follow-up needs an owner and a stopping rule
Build consent-based follow-ups around a defined process.
Task and message rules
Stopping-rule tests
Illustrative output types; the accepted proposal confirms the actual inclusions.
Explore the scope
Know what your project involves.
Swipe through services or use the arrows. Select a card to explore.
ILLUSTRATIVE EXAMPLE · NOT CLIENT WORK OR RESULTSFollow-up Automation / PROJECT DETAILS
The agreed starting scope
Build consent-based follow-ups around a defined process.
ILLUSTRATIVE EXAMPLE · NOT CLIENT WORK OR RESULTSFollow-up Automation / PROJECT DETAILS
The proposed work
Trigger and communication map
Agreed email or WhatsApp workflow configuration
Opt-out, exception and human handoff checks
End-to-end testing and documentation; messaging/provider charges separate
ILLUSTRATIVE EXAMPLE · NOT CLIENT WORK OR RESULTSFollow-up Automation / PROJECT DETAILS
What we need from you
Accurate practice details, approved source materials, brand assets you have permission to use and a named approval contact.
ILLUSTRATIVE EXAMPLE · NOT CLIENT WORK OR RESULTSFollow-up Automation / PROJECT DETAILS
Separate costs and work
Related services, advertising spend, licences, subscriptions, usage charges, paid placements and additional production are separate unless expressly included.
ILLUSTRATIVE EXAMPLE · NOT CLIENT WORK OR RESULTSFollow-up Automation / PROJECT DETAILS
Feedback and revisions
The accepted proposal specifies the included consolidated review rounds. Additional rounds require an agreed change.
ILLUSTRATIVE EXAMPLE · NOT CLIENT WORK OR RESULTSFollow-up Automation / PROJECT DETAILS
Delivery planning
The written proposal confirms the schedule and the inputs required before work begins.
ILLUSTRATIVE EXAMPLE · NOT CLIENT WORK OR RESULTSFollow-up Automation / PROJECT DETAILS
Service period
Only the accepted project or service period is included. No automatic renewal.
ILLUSTRATIVE EXAMPLE · NOT CLIENT WORK OR RESULTSFollow-up Automation / PROJECT DETAILS
Cancellation
Refer to the published refund/cancellation policy and your accepted proposal.
Follow-up Automation
Build consent-based follow-ups around a defined process.
Deliverables that can be included
- Trigger and communication map
- Agreed email or WhatsApp workflow configuration
- Opt-out, exception and human handoff checks
- End-to-end testing and documentation; messaging/provider charges separate
Scope and onboarding
Your written proposal or published service description must state quantities, turnaround, required access, review rounds and exclusions before checkout is enabled. Provide approved practice details, brand materials and a named review contact. Clinical statements require your clinical approval.
How the work is delivered
We confirm the brief, prepare the agreed work, collect your feedback and deliver the approved outputs. Any extra platforms, production, licences, advertising spend or additional revisions are quoted separately.
What to expect
Progress is reported against the agreed deliverables. Search rankings, publisher acceptance, advertising results and patient enquiries depend on factors beyond a single service and are not guaranteed.
Follow-up Automation
Build consent-based follow-ups around a defined process.
Follow-up needs an owner and a stopping rule
Define the acknowledgement, staff task and permitted follow-up sequence for a new enquiry. Specify when contact stops because a person replies, opts out or reaches the agreed end state.
Example outputs to discuss
- Follow-up state map
- Task and message rules
- Stopping-rule tests
These are possible planning outputs. Your accepted proposal identifies the selected items, quantities and formats; this example list does not expand an existing order.
Illustrative working example
An acknowledgement creates a staff task; the follow-up sequence stops when the person replies or opts out.
This is a hypothetical example, not a client case study or promised result.
Check exceptions and overdue work
Test task assignment, duplicate records and missed responses. Automation should make unresolved enquiries visible rather than send indefinitely.
THE WORK, EXPLAINED
A clear path from brief to delivery.
Swipe through services or use the arrows. Select a card to explore.
ILLUSTRATIVE EXAMPLE · NOT CLIENT WORK OR RESULTSThe work, explained / STEP 01
Enquiry stages
Follow-up Automation — Enquiry stages
ILLUSTRATIVE EXAMPLE · NOT CLIENT WORK OR RESULTSThe work, explained / STEP 02
Tasks and follow-up rules
Follow-up Automation — Tasks and follow-up rules
ILLUSTRATIVE EXAMPLE · NOT CLIENT WORK OR RESULTSThe work, explained / STEP 03
Stop and exception tests
Follow-up Automation — Stop and exception tests
Useful questions before you begin.
What does Follow-up Automation cover?
Build consent-based follow-ups around a defined process. The full description lists scope options. The accepted proposal specifies exact outputs and quantities.
Can this be combined with other services?
Yes. Related services can be combined in a defined proposal. Included package components and overlapping tasks should be checked before purchase.
Are fees and delivery dates confirmed automatically?
No. Final selling prices, revision allowances, inputs and schedules are confirmed in the accepted scope before payable checkout is enabled.
Let’s bring your digital presence together.
Tell us about your practice, priorities and ambitions.