Missed-Call Text Back

Missed-call text-back · instant reply to website enquiries · two-way SMS

An Azuvyn recurring service. When someone calls a client's business and the line is missed — or they fill in a web form — they get a text back within seconds from the client's own number, the conversation continues by text, and every message lands in the unified client record. This page is only a status surface; the product is the API.

Is it on?

Ask GET /api/health. Nothing is sent unless SPEED_TO_LEAD_LIVE is "1" and that client's enabled flag is true in client_settings. Either one shut means silence; a flag set to anything other than "0" or "1" reads as misconfigured and is treated as off.

Endpoints

POST /api/voice/incoming — Twilio "a call comes in"
POST /api/voice/completed — Dial action → missed-call text-back
POST /api/sms/incoming — "a message comes in" (STOP/HELP + two-way)
POST /api/sms/status — Twilio delivery callback. A 201 from the send API means queued, not delivered; this is what makes a carrier rejection visible.
POST /api/web-lead — website form → instant text-back
GET /api/health — config, gate verdict, roster (no secrets)

Adding a client

A database row, not a deploy. The roster is client_settings['speed-to-lead'], read at request time: npm run provision -- <slug> projects the canonical client record into it. Provisioning never arms anyone — a human flips enabled after A2P 10DLC covers that number.