How is this different from a mass WhatsApp platform?

COCO doesn't just send messages: it prioritizes by clinical criteria, manages retries, books the appointment in the client system via API and then confirms or rescues it.

Is the institution's own WhatsApp line used?

Yes. In this pilot campaigns are sent from Compensar's official line so patients recognize the sender.

Does it integrate with SAP or other systems?

Yes. Every module connects by API to the existing system. Here the scheduling generated by the campaign goes straight into SAP.

How much does a pilot like this cost?

The model is event-based: each contact, booking or confirmation consumes events. We size the package to your database and the modules enabled.

Patient reading a WhatsApp appointment message

Pilot in progress · COCO × Compensar

Reach the patient who should book, don't wait for them to call.

Q: What if the database is outdated?

COCO cleans and standardizes the base before launch: duplicates, invalid numbers and incomplete records. Real reachability is measured during the pilot.

Compensar activates COCO's patient engagement module on a real base of 2,000 patients, from its official WhatsApp line.

See expected impact

2,000

Patients in the pilot

85%

Expected reachability

SAP

Scheduling via API

+600

Institutions using COCO

Figures on this page are references from other COCO implementations. The pilot is running: final results depend on data quality and on SAP interoperability.

Explore

Starting point

Coverage doesn't fail on capacity. It fails on contact.

Patient engagement means identifying who should access a service and making sure they receive it. Today that depends on manual work or generic messaging.

Low effective reachability

Mass channels don't tell a delivered message from a booked appointment, and don't handle retries.

Coverage targets missed

Screenings, mammograms, vaccination and chronic follow-ups depend on patients booking and showing up.

Unused installed capacity

The schedule, clinical team and SAP already exist. The bridge between identifying and booking is missing.

Why COCO

Not mass messaging. Patient engagement built for healthcare.

Six differences against a generic mass contact tool.

Modular

Campaigns, scheduling, confirmation, OCR, payments and telehealth. Only what is needed is enabled.

API-first

Direct SAP integration to push scheduling, with no intermediate spreadsheets.

Healthcare expertise

Flows built on prevention pathways, screenings and follow-ups, not marketing templates.

No-show experts

We recover up to 83% of appointments that would otherwise be lost.

Data cleansing

Duplicates, invalid numbers and incomplete records cleaned before launch.

Live analytics

Delivered, read, answered, booked and confirmed in a results dashboard.

How the pilot works

From the database to the confirmed appointment.

Step 01 / 06

Kickoff and access

Base of 2,000 patients and technical documentation of the APIs.

Expected impact

What we have seen in other implementations.

Figures on this page are references from other COCO implementations. The pilot is running: final results depend on data quality and on SAP interoperability.

85%

85% reachability with a clean, updated database.

80%

80% appointment recovery with stable interoperability.

<10%

Single-digit no-show rate.

80%

80% self-service after stabilization.

300%

Up to 300% more uptake in prevention and chronic care.

3x to 20x

3x to 20x return when appointments are billed per event.

Multichannel contactScheduling via APIAutomated confirmationReal-time dashboard

Patient data under clinical standards

The pilot database is processed only for its purpose, under Colombian Law 1581 of 2012.

HIPAA ComplianceISO 27001AWS Quality CertifiedPeriodic ethical hackingResolution 256 of 2016

FAQ

What people usually ask us.

You have the schedule, but not the contact

We'll show you what a patient engagement pilot would look like on your own patient base.