Dental missed-call workflow

A clear next step after a missed dental call.

PulpPing evaluates signed missed-call events against each clinic’s office hours, consent, opt-out rules, and saved message template. Eligible events create queued reply intents. No telephony source or SMS transport is connected in this workspace.

Ask about setupSee how it works
Built for dental clinic teamsClinic-scoped, auditable decisions

Workflow connections

Current status

Not connected

Telephony source

No call provider is connected.

Unavailable

Signed missed-call intake

Endpoint ready to evaluate clinic policy.

Available

SMS transport

Queue intents only; no message is sent.

Not configured

Inbound SMS receiver

Patient STOP texts cannot be received automatically.

Not configured

Queue state

Intent only

Delivery state

Unavailable

A safer handoff

Make the decision visible before sending anything.

PulpPing records why a signed event can be queued or was blocked. A telephony source and SMS transport still need to be connected.

Review connection status
Signed missed-call intake
The endpoint validates a signed event and records it once per clinic and event key. No telephony source is connected here.
Idempotent, clinic-scoped intake

Office-hours and holds

Set each day’s interval in the clinic time zone and choose whether after-hours calls block or wait in the queue.

Consent and opt-outs

Require current confirmed consent, retain recorded withdrawals, and suppress configured keywords when signed event text includes them.

How it works

From signed event to policy decision.

A connected source can submit a call event. The clinic rules decide whether a reply intent is queued or blocked; queueing does not confirm delivery.

01

Connect a call source

A telephony source can send signed missed-call events to the webhook. No source is connected in this workspace yet.

02

Apply clinic policy

Check the saved time zone, office hours, current consent, opt-out state, and active reply template.

03

Queue a reply intent

Eligible events keep a versioned message in the clinic queue. SMS delivery remains unavailable until a transport is connected.

Auditable policy

Every event has a recorded next step.

Clinic policy records whether a signed call event was queued or blocked, including the reason. Queued content keeps the active template version; provider acceptance and delivery are separate states.

Clinic-local office hours
Confirmed-consent checks
Recorded caller opt-outs
Versioned reply templates
Current connections
Queue only
Provider not configured
Telephony sourceNot connected
Signed intakeEndpoint available
SMS transportNot configured
Reply decisionsQueued or blocked

Inbound text handling

Unavailable

No receiver connected

Connections required before live use

Bring your telephony and SMS setup into the conversation.

PulpPing can evaluate signed events and queue eligible reply intents. A call source, an outbound SMS transport, and an inbound SMS receiver are not connected yet.

Talk to PulpPing

pulpping@polsia.app