Enrol & run campaign
Refill-due calls
- protocol
- refill-due@1.0.0
- hash
- cb54c618…0802
- window
- 8:00–21:00 patient-local
- ceilings
- 1/day · 3/week per patient
1Patient file
What the file must contain (the context contract)
| column | example | rule |
|---|---|---|
| patient_id | p_1001 | Required, unique in the file |
| given_name | Carol | Required |
| phone_e164 | +16175550142 | Required, +1 followed by 10 digits |
| phone_ref_id | ph_a41c | Required — the stable reference for this number |
| timezone | America/New_York | Required for dialling — an unknown timezone blocks the row |
| dob | 1959-12-03 | Required, YYYY-MM-DD — used as an identity factor |
| rx_ids | rx_8814;rx_8815 | Required, semicolon-separated |
| automated_dialing_consent | yes | yes or no — no blocks the row |
| number_provenance | patient_provided_at_registration | Where this number came from — third-party or unknown numbers are never called |
| enrolment_status | active | active · paused · completed · withdrawn · failed |
Upload the patient file to see, before anything is dialled, exactly which rows would be called and why any row would be held — an unknown timezone, a missing consent, a stop request on record. The guard never guesses: a row it cannot check is a row it holds.