Updated October 29, 2026

Messaging responsibilities

Callback is in development. Purchase and live messaging are unavailable. Paid-service policies below describe the approved planned subscription; they do not activate billing or unverified app controls.

Current status

Live messaging is not available from this public preview. The customer-owned Twilio integration has been tested with fake transports and disposable profiles, not activated with a real account or verified for end-to-end carrier delivery. No automatic messaging service is offered here.

Your provider account

The development integration supports one selected Twilio US1 account and SMS-capable number per local workspace. You pay Twilio separately for the account, number, usage, required registration and applicable carrier charges. Verify sender capability, registration and actual send permission. Setup read checks alone do not prove send eligibility. Existing-number compatibility, forwarding and same-number texting require provider confirmation.

Consent and business identity

Before sending, obtain appropriate recipient permission for the message purpose and retain its source, date and scope. A missed call is not permission to text. An inbound text supports a response to that exchange, not blanket permission for recurring promotion. Identify your actual business and provide truthful purpose/frequency and supported help/opt-out instructions. Requirements depend on your use, provider/carriers and jurisdiction.

Opt-outs and resubscription

Respect opt-outs promptly. The reviewed development code suppresses recognized STOP variants and provider opt-out errors. START/UNSTOP alone does not silently re-enable a suppressed contact; newer evidence and explicit owner review are required. Local checks cannot eliminate an opt-out arriving around a send attempt. Provider-side enforcement remains necessary. Custom opt-out words and other languages require review before support is claimed.

Delivery and limits

Manual replies and history/status polling run while the app is open; reopening catches up only from provider-retained history. Queued/sent status is not proof of delivery. The implementation records attempts, deduplicates action identifiers and requires review of uncertain sends instead of automatically retrying. These safeguards do not guarantee delivery or establish consent. Always-on missed-call automation, automatic acknowledgements, voice forwarding, hosted webhook provisioning, marketing campaigns and MMS transport are not implemented.

Provider rules

Follow Twilio’s Messaging Policy and applicable requirements. The business controls its recipients, content and provider account; Callback remains responsible for its own app and data practices. Live activation, real delivery, STOP handling and recovery must be separately verified. See setup and limits and privacy and data.