ConnectWiz + İYS (Türkiye)

Live integration

İYS compliance as plumbing, not paperwork

If you market to Turkish customers, İYS isn’t optional. ConnectWiz pushes your consents to the registry as they happen, pulls registry-side opt-outs back daily, and keeps evidence on every consent record — so the audit answers itself.

Start free All integrations

Push on grant/revoke Daily opt-out pull Write-only credentials

İYS (Türkiye) × ConnectWiz

Consent granted → pushed to İYS

Registry RET → revoked here, daily

Evidence kept on every record

Evidence columns on every consent — time, text, version digest, locale, IP, agent, source and more

TR channels in İYS scope — email, SMS, phone; messaging apps are outside the regime and we say so

3×

Delivery attempts on every registry push — and a failure never rolls back your local record

Daily

Registry reconcile — opt-outs made at İYS come home and revoke locally

Compliance

What it does — precisely

Push, as it happens

A consent granted or revoked in ConnectWiz — from a form, a keyword, a widget checkbox — queues straight to İYS with your brand and dealer codes.

Opt-outs pull back

A daily reconcile reads registry-side opt-outs (RET) and revokes them locally — the customer who opted out at the registry stops receiving, everywhere.

Dimensioned, like the law

Consent is stored per channel, purpose and category — an SMS marketing opt-out silences SMS marketing, not order updates, and not WhatsApp.

Credentials, write-only

İYS username and password are write-only in the panel — enter once, never displayed again.

Under the hood

Registry mechanics, precisely

What a push carries

Recipient, channel type, source, ONAY or RET, the consent timestamp and recipient type (individual or merchant) — İYS’s own vocabulary, filled from the consent record, with the registry’s transaction ID written back on success.

General consent fans out

A general marketing consent pushes as all three registry types — email, message and call — against the identities the contact actually has. A channel-specific consent pushes exactly one.

The reconcile trusts the registry

The daily pull acts on registry RET only: an opt-out at İYS revokes locally, because for Turkish channels the registry is the source of truth. A failed status read changes nothing — no answer is never treated as consent.

Keywords that can’t hijack

KATIL and DUR (and their configurable siblings) match only when they are the entire message — a sentence that merely contains "stop" is never misread as an opt-out. Button replies match identically, and the customer’s own message is kept as evidence.

Dimensioned like the regulation

Consent is stored per channel (eight), purpose (marketing versus transactional) and category — an SMS marketing opt-out silences SMS marketing, not order updates, and not WhatsApp.

Versioned text, comparable forever

Every consent stores the text shown and a version digest — two grants stay comparable years later, even after you’ve edited the label they agreed to.

Setup

How it connects

Enter your İYS codes

İYS code, brand code and credentials — with a test-connection button that proves the pair before you rely on it.

Capture consent anywhere

Forms, keywords (KATIL/DUR), widget, imports, flows — every source records evidence.

Let the plumbing run

Grants and revokes push as they happen; the daily reconcile pulls registry opt-outs back.

Better together

What it composes with

SMS campaigns

Bulk SMS through Twilio or NetGSM checks consent per recipient at send time — İYS keeps that check registry-true for Türkiye.

Email marketing

Campaign audiences through Mailchimp, Brevo or Resend honor the same consent store the registry syncs.

The contact record

Consent lives on the CRM contact with its evidence — one consent state across channels, forms, keywords and imports.

Security & guarantees

The boring guarantees

Write-only credentials

İYS username and password are entered once, encrypted, and never displayed again — the status endpoint proves the connection without echoing the secret.

Half-configured is not enabled

A tenant who switched İYS on but hasn’t completed credentials is treated as not integrated — half-configured İYS is not permission, and the gate knows the difference.

Fail-open, deliberately

A registry push failure marks the record and retries — it never rolls back the customer’s local consent. The registry lags reality for minutes, not the other way around.

The honest fine print

Boundaries, stated

One-and-a-half-way, honestly

Consents you hold push out and registry opt-outs pull back — but a consent granted only at İYS isn’t discovered yet. We say "İYS-integrated", not "full two-way sync", because that’s what’s true.

İYS (Türkiye) FAQ

Straight answers

More in the full FAQ, or ask us directly.

Pushes each consent grant or revoke to the registry as it happens, and pulls registry-side opt-outs back daily, revoking them locally. Every consent record carries evidence: the text shown, version hash, time, source and context.

It stops what it means: consent is dimensioned by channel, purpose and category, so a marketing opt-out doesn’t block order updates or verification codes — matching how the regulation actually works.

Not yet, and we say so: grants made only at the registry aren’t discovered automatically today. Push-on-change and daily opt-out pull are live; the reverse direction is on the roadmap.

No — İYS governs email, SMS and voice calls. Messaging apps sit outside the registry’s scope, and this integration says so instead of vaguely implying blanket compliance. Consent for messaging channels is still stored and enforced locally, with the same evidence.

Recipient type is part of the push — individual (BİREYSEL) by default, merchant (TACİR) where you’ve set it — matching how the registry itself separates the two regimes.

Connected honestly beats connected loudly.

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