Diagnostics

Sample slots and report-ready pings, not an LIS

Labs book sample slots and send report-ready pings on WhatsApp and email without claiming to replace the LIS or the radiologist’s report system. The qualifier still collects reason, service_need, location, and preferred_times. Catalogs list Services (panels, imaging). Emergencies: call emergency services immediately.

  • Home collection / centre slots
  • Report-ready on WhatsApp + email
  • Not an LIS or PACS

Why labs spam “report ready” from a personal number

Collection centres lose home-visit windows on paper, and report-ready messages go from a tech’s WhatsApp with no opt-out trail. Replacing the LIS in marketing copy is a lie. CoPulse books the sample slot from Services and preferred_times, reminds on WhatsApp/voice/email, and sends a report-ready ping when your team (or a workflow you attach after an export) says the file is ready. The PDF still lives in the LIS.

Omnichannel journey

Website and doctor referrals in; WhatsApp books the draw; voice recovers missed home visits; email carries prep and the ready notice.

  1. Web and referral capture Centre site and partner doctors create New enquiry. Duplicate names are still one contact if you merge.
  2. WhatsApp booking Service panel, location (home vs centre), preferred_times against calendars. Fasting prep from knowledge — not a clinical interpretation.
  3. Voice for missed draws Home collection no-shows get a later window. Replied is not drawn.
  4. Email + WhatsApp ready ping When the report is ready in your LIS, send the ping. CoPulse did not generate the report.

How it runs in CoPulse

Conversation agent books the slot. Campaigns send ready pings. Workflows can fire when you move stage. Autonomous is for overdue annual panels — sends/reads, not booked.

Conversation agent

Qualifier + Services catalog + appointment skill for home/centre windows. Handoff for billing disputes.

Campaigns

Report-ready and prep templates on WhatsApp (Gupshup) and email. Wallet preview. No live SMS.

Workflows

On Appointment booked, send fasting prep. After you mark Consult done, you may queue a ready-ping drip you control.

Calendars

Phlebotomy windows are Appointments/calendars — not a hidden LIS schedule CoPulse magically reads.

Operator setup

Project per brand or city cluster so pin-code calendars do not collide.

Setup → Channels (WhatsApp via Gupshup, email, phone, web, Meta if you run ads) → Library templates → Agents → Studio (qualifier + catalogs + appointment skill + emergency guardrail) → Agents → Router → Setup → Customers → Pipeline → Appointments/calendars → Growth campaigns with Organization wallet preview.

Home collection week without claiming the LIS

A website form asks for thyroid panel. Qualifier stores service_need and a 7am preferred window. Calendar offers 7:30. Prep email goes out. The phlebotomist marks the visit; your team later flags the report ready in the process you already have, and CoPulse sends the ping on WhatsApp plus email. If the visitor asks “is this cancer,” the agent hands off — it does not interpret the PDF. Autonomous might later ping last year’s panel list; success is sends and reads until someone books.

Do not upload radiology reports into knowledge and ask the bot to explain them. Services catalog is names and prep, not findings.

Patient Inquiry Qualifier fields are reason, service_need, location, and preferred_times. The agent does not invent a clinical finding. Knowledge bases hold Departments, Doctors, Beds, and Services catalogs — not a clinical chart. Appointments and calendars are the slot truth; the Appointment booked column is not inferred from a campaign send. The omnichannel inbox keeps WhatsApp, voice, email, and web on one contact so a nurse or desk can take human handoff with the thread. Pricing is wallet-only — no seat fees. Autonomous tasks, when used, count sends, reads, or contacted until a human or workflow moves the pipeline. If a visitor describes an emergency, the agent must tell them to call emergency services immediately; CoPulse is not an emergency line and not an HIS or EMR. Playbooks: report-ready, appointment reminder, appointment booking. Imaging centres use the same five pipeline columns — do not add a PACS stage. The radiologist’s system stays yours. For diagnostic labs and imaging, keep one Organization and a Project per facility or program cluster. Preview wallet cost before any blast. Library templates are required outside the 24-hour WhatsApp window. Workflows fire on stage change only when you attach them under Agents → Workflows. The agent router keeps a specialty bot off a billing thread. Funnel percentages on library kits are estimates, not an SLA.

Lab hop sequence

Slot truth on CoPulse calendars; report truth in the LIS.

Hop Channel What happens Owner
1 Web / referral New enquiry Capture
2 WhatsApp Panel + window Qualifier
3 Phone Missed home visit Voice
4 Email + WhatsApp Prep / ready ping Campaign
5 Inbox Billing or “what does this mean” Human

Playbooks for this team

Jobs are omnichannel. Each link is one URL, not a WhatsApp-only clone.

Frequently asked questions

Labs, imaging, and systems CoPulse will not replace.

Will CoPulse generate or host the lab report?

No. You send a ready ping. The file stays in the LIS or patient portal you already run.

Can the agent explain results?

No. Interpretation is human handoff. Knowledge may hold prep and panel names only.

Do we get a Report ready pipeline column?

No. Use the five default columns. Ready is a message job, not a new board stage.

SMS for ready alerts?

Coming soon. Use WhatsApp templates and email today.

Autonomous annual panel blasts — when do they stop?

They count sends and reads. Booking is a separate hop on calendars and Appointment booked.

Pricing?

Wallet-only. Pricing.

Book draws without pretending to be the LIS

Load Services, connect calendars, and ping when your reports are actually ready.

Get started free