Patients request medical certificates through a structured form instead of phoning the front desk. Eligible requests pre-fill from the visit record, land in the physician's one-click approval queue, and go out as signed PDFs with a verification code — usually within ten minutes.
Typical results
1 click
Physician approval
-77%
Front-desk certificate calls
100%
Certificates verifiable online
Figures reflect typical results for this kind of automation.
The challenge
Sick notes ate the clinic alive: dozens of daily calls for a one-line certificate, patients booking full appointments just to get paperwork, and physicians interrupting consultations to type dates into a template. Employers phoned to verify authenticity, and a handful of forged notes had already circulated with the clinic's letterhead.
Before and after
Certificate turnaround
−99%Front-desk certificate calls per day
−77%Physician minutes per certificate
−92%The automation
We built a structured request form that asks for the visit reference, absence dates, and reason. A Make scenario checks eligibility against the visit record — recent visit, diagnosis on file, dates within policy — and pre-fills the certificate draft. Eligible drafts queue for the physician, who approves with one click between patients. The system generates a signed PDF with a verification code employers can check online, delivers it by WhatsApp and email, and logs every certificate.
How it works
- 01
Patient requests
The patient fills a short structured form: visit reference, absence dates, and reason.
- 02
Eligibility check
Make cross-checks the request against the visit record; ineligible requests route to booking a visit.
- 03
Draft pre-filled
The certificate drafts itself from the visit record — dates, diagnosis code, physician name.
- 04
One-click approval
The physician reviews the queue between patients and approves or edits with one click.
- 05
Signed & delivered
A signed PDF with a verification code goes out by WhatsApp and email, and logs to the file.
Starts from
- Structured request form
- Visit records
Delivers
- One-click physician approval
- Signed PDF certificate
- Delivery with verification code
The impact
Certificates now go from request to signed PDF in about ten minutes during clinic hours, and front-desk certificate calls dropped from roughly 35 a day to eight. Physicians spend seconds approving instead of minutes typing, no-value appointments freed real slots, and the verification code ended the forgery problem outright.
Questions about this automation
How does the system decide if a certificate request is eligible?
A Make scenario compares the request with the visit record: a recent visit, a diagnosis on file and absence dates that fall within the clinic's policy. Requests that pass get a pre-filled draft. Requests that fail are steered to booking a visit, so the physician only sees cases that can be signed.
How do employers verify that a certificate is genuine?
Each signed PDF carries a unique verification code. Employers enter it on a simple online check page, which confirms the certificate exists and shows its dates. Because every issued certificate is logged, a note that does not match the log fails the check, which makes forged letterhead easy to spot.
What does a clinic need to set this up?
The clinic needs read access to its visit records, its certificate template and its eligibility policy written as clear rules, plus WhatsApp and email for delivery. Physicians approve from a queue with one click between patients. Simple automations like this are usually live within days once the eligibility rules are agreed.