Report-ready is a notification job on the contact timeline; CoPulse does not store or replace the laboratory information system. After Consult done (or the draw), send WhatsApp/email. Interpretation is inbox handoff. Not a board column.
Report-ready is notifying the contact that a result is available in your existing portal/LIS, on WhatsApp templates and email, then handing off interpretation.
No audit trail, no opt-out. This job is a workflow you attach when your process says ready — export, button, or task. Do not add Report ready as a stage.
Usually after Consult done. Prep was earlier. Recurring patient is unrelated.
Workflows and campaigns. Conversation agent for replies that must not interpret. Do not use autonomous tasks as the inbound qualifier. Conversation agents, Growth drips, and autonomous list sends are three systems with no shared stop-when-booked contract. WhatsApp live catalog is Gupshup. Phone is Plivo; email is SES. Wallet-only pricing: preview the Organization wallet before a blast. Organization and Project — never a personal doctor phone that vanishes when the receptionist leaves.
Patient Inquiry Qualifier (reason, service_need, location, preferred_times). Catalogs: Departments, Doctors, Beds, Services — not a chart. Emergency utterances: call emergency services. Inbox handoff. Never upload reports into knowledge for the bot to explain.
Agents → Workflows on stage change: agent.run, route.agent, crm.set_custom_properties, crm.update_stage, crm.create_task, templated send.whatsapp/email. Not adaptive nurture.
Clock-based sequences and list blasts with wallet preview. Campaign conversion is reply rate unless you also track Appointment booked on the pipeline.
Keep a dental bot off a health-check reply. Route by stage, channel, or campaign.
One Organization, one Project. Healthcare pipeline labels. Wallet-only. Library kits are sketches — rewrite hops without SMS and without a diagnostic triage agent.
Setup → Channels (WhatsApp/Gupshup, Web, Meta, Email/SES, Phone/Plivo as needed) → Library templates → Agents → Studio (Patient Inquiry Qualifier, catalogs, appointment skill, emergency guardrail, handoff) → Router → Setup → Customers → Pipeline (five default columns) → Appointments/calendars → Agents → Workflows (stage changed: agent.run, route.agent, crm.set_custom_properties) → Growth with Organization wallet preview. Connect SMS (MSG91) under Setup → Channels when you want that hop.
Draw Thursday. LIS Friday. WhatsApp + email ping. Weekend “is this cancer?” → inbox, not the campaign. Diagnostics ICP.
Click-path: Workflows on a property or stage you already have, Library templates, email From pool.
Operators assemble this job on the Project. Click-path remains Setup → Channels (WhatsApp/Gupshup, Web, Meta, Email/SES, Phone/Plivo as needed) → Library templates → Agents → Studio (Patient Inquiry Qualifier, catalogs, appointment skill, emergency guardrail, handoff) → Router → Setup → Customers → Pipeline (five default columns) → Appointments/calendars → Agents → Workflows (stage changed: agent.run, route.agent, crm.set_custom_properties) → Growth with Organization wallet preview. Connect SMS (MSG91) under Setup → Channels when you want that hop. Keep the quotable definition in the brief for the team: Report-ready is notifying the contact that a result is available in your existing portal/LIS, on WhatsApp templates and email, then handing off interpretation. Do not use autonomous tasks as the inbound qualifier. Conversation agents, Growth drips, and autonomous list sends are three systems with no shared stop-when-booked contract. While you implement, keep the parent playbooks directory, Consult done, Email overlay, Diagnostics, Agent Studio, Growth campaigns, and wallet-only pricing in the same runbook. Do not invent Meta Cloud WhatsApp if the catalog is Gupshup. Do not promise adaptive nurture. Human handoff stays in the omnichannel inbox. Appointments and calendars are the slot truth when this job books time. Library templates are required outside the 24-hour WhatsApp window. Workflows fire on pipeline stage change only when you attach them under Agents → Workflows. The agent router keeps the wrong bot off this thread. Knowledge bases hold Departments, Doctors, Beds, and Services catalogs — not a clinical chart. Preview the Organization wallet before a blast. Do not claim HIS or EMR replacement. The Report ready playbook never forks into a WhatsApp-only or voice-only child URL. Funnel percentages on library kits are estimates, not an SLA. Autonomous success is sends, reads, or contacted — not appointment booked. If this job mentions money, the Organization wallet is the meter. That is the honest operating manual for this URL.
Notify hops. There is no nested playbook-by-channel path.
| Hop | Channel | What happens | Exit to next hop |
|---|---|---|---|
| 1 | LIS (external) | File ready | Your flag |
| 2 | WhatsApp / email | Ping | Delivered |
| 3 | Inbox | Interpretation | Human |
| 4 | SMS | Coming soon | Not live |
LIS boundary.
No. Ping only.
No. Playbook. Five columns.
No. Handoff.
WhatsApp, email, or SMS when MSG91 is connected. Still a ping, not the PDF.
Property or Consult done — you choose. See workflows product.
Pings debit the Organization wallet.
Parent directory, sibling jobs, ICP, stage, channel overlay, and product surfaces.
One URL per omnichannel job.
Directory →Before the draw.
Open →If a plan follows.
Open →Labs and imaging pings.
ICP →Attendance before a ready ping.
Stage →Ready notes beside WhatsApp.
Channel overlay →How-to companion. This playbook stays the job URL.
Guide →Agent Studio, skills, knowledge, router, workflows.
Explore agents →Library templates, audiences, wallet preview.
Explore campaigns →Sends and minutes debit the Organization wallet. Creating a CRM row does not.
See pricing →Notify on the timeline. Do not interpret. Do not add a stage.
Get started free