ConnectWiz + Twilio

Live integration

Your Twilio. Our inbox, brains and brakes.

Keep the Twilio account, numbers and rates you already negotiated — and give SMS a routed inbox, an AI that answers concisely, campaigns with real consent checks, and receipts that tell the truth.

Start free All integrations

Your account — no markup Real delivery receipts Consent at send time

Twilio × ConnectWiz

Sent — 1 segment, stamped

Delivered — carrier receipt

Consent re-checked at send

100%

Of inbound proven — every webhook is signature-verified against your own token

160→153

GSM segment sizes, single versus concatenated — computed server-side, before you send

70→67

The same sizes once a single non-GSM character enters the message

Markup — Twilio bills you directly at your negotiated rates

SMS

What it does — precisely

Credentials, encrypted

Your Twilio SID and token are stored encrypted and never shown again; your sender IDs, messaging services and registrations stay exactly as you set them up.

Genuinely two-way

Inbound texts arrive through cryptographically signed webhooks and land as routed conversations; status callbacks walk each message up the forward-only sent→delivered ladder — a confirmed delivery never regresses.

Segments on the thread

Every send records how many SMS segments actually left — your Twilio bill is explainable from inside the conversation.

Verification built in

One-time-code phone verification rides Twilio Verify — Twilio generates, delivers and checks the code; we store nothing.

Under the hood

Segment math is money — so it lives server-side

One source of truth for cost

Segment counting runs on the server, in exactly one place. A client-side copy would drift from what’s actually billed — and the direction it drifts is always the reassuring one.

The ş that triples your bill

One character outside the GSM alphabet drops the whole message to 70-character segments. The composer knows this before you send — 161 GSM characters costs two segments of 153, not 160 plus one.

Even the escape pairs

Characters like ^, {, } and € cost two units each in GSM encoding, and emoji cost two in UCS-2 — the counter charges them the way the carrier does.

Messaging Services first

When you’ve configured a Twilio Messaging Service, sends prefer it over a bare number — inheriting your pool, sticky sender and compliance setup instead of bypassing them.

Verify, the managed way

Phone verification uses Twilio Verify: the code is generated, delivered and checked by Twilio, localized to the customer’s language — no OTP secrets to store, no codes to leak.

Failures return named

A refused send comes back with Twilio’s real reason — auth, geo-permissions, unverified trial number — surfaced to the operator, not laundered into a generic error.

Setup

How it connects

Paste your credentials

SID and token, encrypted at rest, verified at setup.

Pick your senders

Your numbers and sender IDs appear as channels, routable per department.

Text with brakes on

Campaigns check consent per recipient at the moment of sending — a Tuesday opt-out is skipped on Wednesday, recorded with its reason.

Better together

What it composes with

Campaigns

SMS campaigns run with consent re-checked per recipient at the moment of sending — see the SMS channel page for the full send pipeline.

İYS (Türkiye)

Turkish commercial SMS stays registry-clean through the İYS integration — grants push, registry opt-outs pull back daily.

Flows

Booking reminders, order updates and re-engagement sequences send SMS through flow steps — same consent gates, same segment math.

Security & guarantees

The boring guarantees

Inbound is cryptographically yours

Every inbound webhook is verified with Twilio’s signature scheme — an HMAC over the full URL and sorted payload, keyed by your account token. An unsigned "inbound SMS" is an open door into somebody’s inbox; this one stays shut.

Secrets handled like secrets

SID and token are encrypted at rest, sent only in authentication headers, and never logged or echoed into error messages.

Consent, twice

Campaign sends check consent at audience build and again per message at send time — a Tuesday opt-out is skipped on Wednesday, with the skip recorded and reasoned.

Even the receipts are signed

Delivery status callbacks are signature-verified exactly like inbound messages, with your own key — an unsigned status endpoint would let anyone mark your messages "delivered", which is quieter than a fake message and worse, because nobody goes looking.

The honest fine print

Boundaries, stated

No MMS

Picture messaging isn’t implemented — an attachment fails with a named reason instead of being silently dropped, but it fails, and we say so.

Alphanumeric = one-way

A branded text sender can’t receive replies — that’s SMS physics, and the composer knows it.

Twilio FAQ

Straight answers

More in the full FAQ, or ask us directly.

No. Twilio bills you directly at your negotiated rates; the platform adds no per-message toll. Segment counts are stamped on every send so the bill is never a mystery.

Yes — replies land in the team inbox as conversations, routed and answered by AI or your team. A reminder that gets a question back becomes a booking, not a dropped thread.

Twice on campaigns: at audience build and again at the moment each message sends. STOP-style keywords are honored instantly with the customer’s own message kept as evidence.

It implements the actual encoding rules: GSM 160/153, UCS-2 70/67, double-cost escape characters, surrogate-pair emoji. It reports segments, not prices — your cost depends on destination and your Twilio contract, and inventing a number would be worse than showing none.

Yes — it’s preferred: when a Messaging Service is configured, sends route through it, keeping your sender pool, sticky sender behavior and registered compliance exactly as Twilio has them.

Connected honestly beats connected loudly.

Every integration here is described by what it really does — direction, ownership and limits included.