DripTell’s Customer Journey reporting preview can show the recorded path from a clinic enquiry to replies, an accepted handoff, a booking and a checked outcome. It cannot prove revenue, a clinical result or an appointment from a reply or assignment. This is a limited pilot for eligible workspace owners and managers. Does your clinic record enough reliable administrative events for it?
What the preview can show today
Customer Journey reads existing records and journal events. A manager can filter by channel, WhatsApp number and source, then open one journey. The preview limits the period to 31 days and the timeline to the latest 200 events.
Qualification, handoff, booking and completed appointment are separate. Recording a checked result adds history; it sends no message and changes no lead stage. Sales and revenue remain not connected.
Keep this work administrative. The healthcare use case supports appointment enquiries and ownership, but it is not a clinical record, diagnosis tool or booking system.
Define the journey before opening the report
Start with one ordinary request, such as an adult asking about a non-urgent consultation slot. Write down the evidence required at each step instead of working backwards from a desired conversion rate.
| Reported event | Evidence worth accepting | What does not prove it |
|---|---|---|
| Enquiry started | Recorded source, time and conversation | A campaign impression |
| Qualified | Required administrative details were checked | A lead stage changed automatically |
| Handoff accepted | A named person explicitly accepted the work | Assignment alone |
| Appointment booked | A booking event exists in the recorded journey | A positive reply or proposed time |
| Outcome checked | A teammate verified and recorded the result | Silence after the appointment date |
This prevents a fast reply from becoming a booking and a routed conversation from becoming a completed handoff.
Keep assignment and acceptance separate
In the shared inbox, assignment shows who owns the conversation now. It does not prove that person accepted responsibility. Customer Journey counts acceptance only when explicitly recorded.
Test the difference internally. Assign an enquiry without accepting the handoff; the report should not upgrade assignment into acceptance. Then record acceptance and check that it appears separately. If a message asks for medical judgment, follow the clinic administration and clinical-routing guide and use the clinic’s approved clinical route.
Prepare the records before requesting the pilot
Sample ten administrative enquiries from a recent 31-day period. Confirm the source, customer identity, owner, qualification, handoff status, booking record and checked outcome. The CRM and lead record should contain only what the next authorised teammate needs.
Missing events may mean the process never recorded the decision. Name the authoritative booking system and who may record a result. If that source is not connected, label the outcome unknown rather than inferring it from chat tone.
The preview reads records; it does not repair them. Use automation only after the team agrees what each event means. A reminder must not invent acceptance or completion.
Read the report without overstating the result
Compare enquiries, qualified journeys, accepted handoffs, bookings and checked outcomes in order. A large gap between assignment and acceptance suggests an ownership problem. A gap before booking may reflect availability, customer choice or missing evidence; the report alone cannot identify the cause.
Do not call every booking a conversion caused by WhatsApp or DripTell. The preview proves neither revenue attribution nor attendance or treatment success.
Keep clinic data deliberately small
The WhatsApp Business Messaging Policy still governs permission and stop requests. Reporting does not widen that permission. Collect only what the clinic has approved for the administrative purpose and review local privacy duties separately.
Prefer administrative facts such as service category, contact route, owner and booking state. Do not copy symptoms, diagnoses or treatment notes merely because a free-text field exists. Privacy and clinical owners should define the approved record.
Decide whether the controlled pilot is useful
The pilot fits when the clinic has a defined administrative journey, stable events and an owner for result checks. Bring an anonymised journey to a DripTell walkthrough. Ask which records the preview reads and which outcomes remain unknown.
Frequently Asked Questions
Is Customer Journey generally available in DripTell
No. It is currently a controlled preview with limited availability for eligible workspace owners and managers.
Does assigning a clinic conversation count as an accepted handoff
No. Assignment and explicit handoff acceptance are separate events in the current preview.
Can the report prove that a WhatsApp enquiry created revenue
No. Verified sales and client revenue are currently not connected, so the report does not infer them from activity or lead stages.
Does Customer Journey replace the clinic booking or medical record system
No. It reports recorded customer-journey evidence in DripTell. Treat booking and clinical systems as separate authoritative records according to the clinic’s approved process.
Want help applying this guide?Ask the DripTell team
From reading to action
Want help applying this to your business?
Share your details. We will read the article you are on and start with a useful answer for your team.
DripTell Editorial
Practical guidance reviewed by the DripTell product and customer workflow team.
See how DripTell checks product claims, uses primary sources and handles corrections.
Editorial and source policy
