ConnectWiz + NetGSM
Live integrationNetGSM, twice: your SMS gateway and your phone line
One Turkish carrier, two integrations: SMS campaigns and conversations on your own NetGSM account, and a SIP trunk that makes your existing number ring inside the ConnectWiz call center — IVR, queue, recording, voice AI and all.
SMS & telephony (TR)
What it does — precisely
SMS, Türkiye-grade
Sender IDs and tariffs stay on your NetGSM account; campaigns run with last-moment consent checks and İYS integration for registry compliance.
The SIP trunk
Your existing number rings inside ConnectWiz — verified live in both directions — with the full call stack behind it: IVR trees, queue with callback, recording policy, captions and the voice AI.
Honesty about inbound SMS
NetGSM inbound SMS is deliberately switched off until its callback format is verified against live traffic — the panel says so by name instead of silently eating messages.
İYS next door
Türkiye’s consent registry integration pushes your consents and pulls opt-outs daily — commercial SMS stays registry-clean.
Under the hood
Türkiye-grade details, handled
Turkish encoding, declared
Every send declares Turkish encoding to NetGSM so ş, ğ and ı are billed under the Turkish alphabet tariff rather than silently flipping the message to expensive unicode segments.
Your approved headers
Sends go out under the sender headers NetGSM has approved for your account — the integration uses your registration, never a shared identity.
Acceptance is checked, not assumed
NetGSM’s acceptance code and job reference are read on every send — a rejected message fails with the carrier’s own reason on the thread, never a silent drop.
The trunk is the phone system’s front door
The SIP trunk feeds the full ConnectWiz call stack: IVR trees, queueing with callback, recording policy, live captions and the voice AI — your number, our machinery.
Two-way needs a number
A channel is two-way only when inbound is verified and the sender is numeric — customers can’t reply to an alphanumeric header, and the composer knows it rather than letting you find out.
Setup
How it connects
Add your NetGSM account
Credentials encrypted, senders appear as channels.
Order the SIP trunk
Enable the trunk at NetGSM for your number — noting their switch is not reversible via API, which we surface before you click.
Route and answer
Calls hit your IVR and queue; texts hit the inbox; both share the customer record.
Better together
What it composes with
Voice platform
The trunk powers the call center — IVR, queue, recording, captions, voice AI on your own number.
İYS
Commercial SMS to Turkish numbers runs beside the consent registry integration — the pairing Turkish law effectively requires.
Campaigns & flows
Bulk sends and flow-triggered messages use the same consent gates and the same encoding discipline.
Security & guarantees
The boring guarantees
Credentials encrypted
Your NetGSM account credentials are stored encrypted and used only against the carrier’s API.
Off means signed off
Inbound SMS is disabled by an explicit, named decision — turning on an unverified callback would mean either an endpoint nobody calls or an unsigned one anybody can call. Neither is a feature.
The one-way switch, in writing
NetGSM’s SIP trunk switch routes all calls for the number and is not reversible through their API — shown as a warning before you order it, not discovered after.
The honest fine print
Boundaries, stated
The one-way switch
Enabling SIP Trunk at NetGSM routes all calls for that number to ConnectWiz and can’t be undone through their API — a carrier fact we show as a warning, not a footnote.
No price claims
Your NetGSM tariff is your contract; we assert no rates and add no markup.
Connected honestly beats connected loudly.
Every integration here is described by what it really does — direction, ownership and limits included.