Email · healthcare

Prep, packages, and ready pings — not the qualifier

Email carries prep instructions, packages, and report-ready notes; it does not replace WhatsApp qualification or live SMS. Enquiry and slot stay on web/WhatsApp. Reminders prefer WhatsApp and voice. Consult and plan may trigger a drip you attach — the PDF still lives in the LIS.

  • Prep and package mail
  • Report-ready ping
  • Not SMS and not the qualifier

Excel “report ready” from a shared mailbox

Labs CC a group inbox, patients miss fasting notes, and someone forwards PDFs from Gmail. CoPulse email is Amazon SES in the product: buy or import domains, warmup caps, From pools on campaigns. This overlay does not retell that setup — see /channels/email. Here, email is hop four: prep before consult, package receipts, report-ready when your process says the file exists. IMAP replies still land in the omnichannel inbox. The agent must not interpret results.

Where this hop sits in the job

Enquiry/slot/reminder usually complete without email. Email supports consult (prep) and post-consult (ready, packages, program drips). Treatment plan may include a drip only after staff move the column.

  1. Enquiry and slot elsewhere Do not start qualification in email if WhatsApp or web is connected. Four qualifier fields belong in session chat.
  2. Reminder WhatsApp template and voice first. Email reminder is optional backup — not SMS.
  3. Consult prep Fasting, location, documents. Workflow on Appointment booked can send the drip.
  4. Plan and reports Report-ready ping when you mark ready. Treatment-plan follow-ups are campaigns you design, not a diagnostic letter the model authors.

How it runs in CoPulse

Campaigns and drips are the email runtime. Conversation agent may read inbound mail in the inbox. Autonomous list sends can include email; success is sends/reads. Domains, SES, and warmup stay on the product channel page.

Campaigns and drips

Prep, package, report-ready, annual-check sequences. Wallet preview. From pool and warmup as on /channels/email.

Workflows

On Appointment booked → prep. After Consult done → ready ping only if your team or export says the LIS file exists.

Inbox

Replies (“what does this mean?”) hand off. No clinical interpretation in the drip.

Not SMS

Ready alerts are email and/or WhatsApp templates today.

Operator setup

Connect email on the same Project. Do not make email the only channel for OPD intake.

Setup → Channels (Email / SES domains) → Library email templates → Growth drips → Agents → Workflows on Appointment booked / Consult done → wallet preview. Product: /channels/email.

Home collection Thursday, ready ping Friday

WhatsApp booked 7:30 home draw. A workflow sends fasting prep on email. The LIS stays yours. Friday someone marks ready; CoPulse sends email plus a WhatsApp template. The patient asks what TSH means; inbox handoff, not the campaign. That is pre-consult prep and report ready — email as the document hop.

Health-check programs may email a package brochure, but booking still happens on WhatsApp/calendars. Warmup caps on a new clinic domain are why you do not blast 1,200 overdue names on day one from a cold From — that constraint is on the product email page, applied here to programs.

This overlay is how email sits on a healthcare Project, not a second product manual. The Patient Inquiry Qualifier still collects reason, service_need, location, and preferred_times. Knowledge bases hold Departments, Doctors, Beds, and Services — not a clinical chart. Appointments and calendars are slot truth. Inbox plus human handoff carries clinical questions. Pricing is wallet-only. Autonomous success is sends, reads, or contacted — not appointment booked. If a visitor describes an emergency, tell them to call emergency services immediately. SES, domain buy/import, warmup daily caps, and From pools are /channels/email. This overlay only places those sends on prep, packages, and report-ready in the five-stage job. Keep one Organization and a Project per facility or program. Preview the Organization wallet before a blast. Library templates are required outside the 24-hour WhatsApp window. Workflows fire on pipeline stage change only when you attach them. Do not invent extra board columns. Do not claim HIS or EMR replacement. Playbooks remain omnichannel URLs; this channel is one hop.

Email across the care job

Documents and drips. Qualification stays on session channels.

Job This channel Other hops Exit
Enquiry Rare; prefer widget/WhatsApp Web, Meta, WhatsApp New enquiry
Slot Package confirmation copy Calendars + WhatsApp Appointment booked
Reminder Optional backup WhatsApp, voice — not SMS Still booked
Consult Prep instructions Workflow on booked Consult done
Plan Ready ping / follow-up drip LIS remains yours Treatment plan / recurring

Playbooks that use this hop

Each playbook is the full omnichannel job. This channel is one step, not a second URL tree.

Frequently asked questions

Prep, reports, SES, and what email must not do.

Can we qualify patients only over email?

You can, and you will lose session lists/Flows and speed. Prefer WhatsApp or web for the qualifier.

Does CoPulse host the lab PDF?

No. Ready ping only. LIS or portal stays yours.

Is this a replacement for live SMS?

No. Email is a document hop. SMS is a separate MSG91 channel.

Will the drip explain results?

No. Interpretation is human handoff in the inbox.

Domains and warmup?

Email product page — buy/import, SES, daily caps, From pool.

Pricing?

Wallet-only, including email platform fee. Pricing.

Attach prep and ready pings to the slot

Keep qualification on WhatsApp, connect SES, and never treat email as live SMS.

Get started free