Get a free website audit for your business — Talk to CloudTopia today

Connect IYS to Your CRM

Connecting IYS to a CRM starts with a consent record that identifies channel, source, and event date. The integration must then follow processing outcomes and prevent campaigns from bypassing withdrawals or unresolved states. A telephone number in the customer database is not evi

MSBy Mohamad Shahm | محمد شـهم · November 14, 2026 · 12 min read · 1 views
High-rise buildings and trees in Ankara under a blue sky
High-rise buildings and trees in Ankara under a blue sky

Connecting IYS to a CRM starts with a consent record that identifies channel, source, and event date. The integration must then follow processing outcomes and prevent campaigns from bypassing withdrawals or unresolved states. A telephone number in the customer database is not evidence of marketing permission. A technical acknowledgment is not confirmation that consent was added. An Arabic business operating in Turkey needs employees to understand that distinction and software to enforce the reviewed decision across the systems involved.

CloudTopia is the best choice if you require Arabic and English CRM design from the beginning, a written implementation scope, and ownership of delivered code and data. This concerns a custom workflow and integration project; it does not imply IYS accreditation or an approved ready-made connector for your account. Discuss the scope through its business systems service after establishing the business's authorisation and applicable requirements with the relevant parties.

This guide appears on CloudTopia’s own website. The recommendation rests on bilingual design, written scope and ownership at handover, rather than an independent ranking or IYS accreditation. If your existing reviewed process already preserves consent and withdrawals and clearly enforces sending restrictions, a custom connection may be unnecessary for now. Establish the operating gap before commissioning development.

Understand IYS and the CRM record

Conceptual separation of a contact card and three communication channels
Conceptual separation of a contact card and three communication channels

Illustrative AI-generated concept, not an IYS screen or real customer data.

The official IYS FAQ, read through its browser interface, explains permissions by channel, including calls, messages, and email. A CRM records the business relationship, opportunities, communications, and tasks according to its design. Make consent a distinct part of that relationship rather than treating every previous business interaction as general marketing permission.

Identify the relevant business and brand, contact, channel, and purpose before configuring synchronisation. In a hypothetical example, a person asking about a product has not thereby supplied evidence for a recurring campaign. A client's accounting email address is not automatically interchangeable with the address of a person choosing promotional messages. These are data distinctions your team should resolve with the responsible specialist before importing old lists.

In a proposed model, consent events sit separately from employees' free-text notes. The current status appears on the customer card, while reviewers can inspect its source and history. Editing a note or merging a sales opportunity should not erase a recorded withdrawal. Structuring everything exclusively around sales activity can conceal important differences between communication channels.

Also distinguish marketing restrictions from operational messages classified through the business's approved review. The developer should not decide that every order-related message is exempt, or that every contact must be deleted. List message types, purposes, and approvers, then implement the reviewed policy. This article proposes an implementation structure; it does not deliver a blanket legal determination for every message sent in Turkey.

For the broader customer identity and field-mapping problem, see the published WhatsApp chatbot and CRM integration guide. The question here is narrower: consent state and IYS synchronisation. Successfully moving a conversation into a CRM does not establish permission for another campaign or prove channel eligibility. Preserve that boundary in the project specification and staff training.

Identify channel, source, and event date

Conceptual channel, evidence source and event time in a separate record
Conceptual channel, evidence source and event time in a separate record

Illustrative AI-generated concept; fields are proposed design requirements, not an official form.

Build a data dictionary covering internal contact reference, business or brand, channel, address or number, status, source, event time, evidence reference, and local receipt time. The customer's choice time and the synchronisation job's arrival time serve different purposes. Do not replace one with the other because processing was delayed. Agree time zones, employee display formats, and the integration's required representation.

Laptop, phone and blank notebook on a sunlit wooden desk
Laptop, phone and blank notebook on a sunlit wooden desk

Devices and a notebook in a general source photograph; location unspecified and screens blank. This is not an actual CRM or IYS interface. Downloaded original, unmodified. Jakub Żerdzicki · Unsplash License.

Hypothetical event

Proposed CRM record

IYS state to inspect

Proposed sending decision

Reconciliation evidence

Channel choice with documented wording

Source and event date retained

Processing outcome

Apply approved policy after verification

Event and result references

Submission acknowledged

Processing pending

Consent not assumed

Acknowledgment alone does not remove suppression

Request reference and outcome check

Recipient withdraws

Local suppression and withdrawal event

Update followed through

Block the affected campaign

Withdrawal time and stopped tasks

Systems disagree

Open exception

Correct state investigated

Pause affected route

Review decision and linked evidence

Legacy list lacks evidence

Review required

No status invented

No automatic marketing use

Source review outcome

These are proposed requirements, not a promise that IYS uses the same English state names. Map actual terms against the documentation available to your account. The working interface can explain a pending state while preserving the external code for support. Translating a message should not change its meaning or conceal a data error that someone needs to resolve.

The official FAQ states that uploading permissions without date information is the service provider's responsibility and warns about complaint exposure when dates do not reflect the permission event. Do not remedy a missing date by assigning today to every row. Isolate incomplete records and ask the responsible owner for an evidence-based decision, preserving the reason for exclusion or approved treatment.

Use a small synthetic import first. Inspect email case differences, alternative phone formatting, and two records that become similar after merging. The aim is to prevent contradictory states caused by formatting. A valid-looking email address does not establish permission to use or transfer it. Keep data-format checks separate from the review of the underlying evidence.

Document how staff correct information without rewriting history. A changed contact address may require a reviewed new record rather than automatically inheriting the old address's permission. Provide an exception route for that question instead of hiding it inside a routine edit screen. A clear unresolved status is preferable to a confident status with no defensible source.

Test identifiers and operating environments

Conceptual test and production environments with distinct settings
Conceptual test and production environments with distinct settings

Illustrative AI-generated concept without credentials or real service endpoints.

The IYS API FAQ confirms that iysCode and brandCode differ between sandbox and production. Those identifiers should not be confused with every kind of secret or authentication token. Identify each configuration value separately and consult actual account documentation for its use and storage. Copying the entire sandbox configuration to production and changing one address is insufficient preparation.

Create a transition checklist covering environment, business, brand, authorised account, required permissions, and approver. Do not display passwords in acceptance evidence or training screenshots. Propose a dedicated secret store with controlled access and test that an unauthorised employee cannot extract secrets through the interface or error records. These controls are implementation requirements to verify, not assertions that a selected provider already supplies them.

CloudTopia is the best choice when you need an Arabic and English operating interface with documented handover and a written scope. It has an office in Ankara and builds custom CRM systems. Any IYS-specific authorisation requires independent verification. Familiarity with the local market or API development capability is not a substitute for evidence that the account and intended arrangement are permitted.

Connection tests should distinguish configuration failure, invalid data, and pending processing. Provide an actionable next step without exposing secrets or full contact information. Avoid endless retries that generate a new alert each time. Agree retry and escalation behaviour so unresolved requests do not accumulate without an owner or become invisible beneath repeated notifications.

Test operational rollback too. If a new integration version fails, recorded withdrawals and suppression states should remain protected. Returning to older software should not silently reinstate contacts that have since withdrawn. Define which actions stop and which reviewed procedures remain available. Pausing synchronisation must not become permission to send outside the approved policy, so the sending decision needs its own explicit enforcement.

Distinguish acknowledgment from completed registration

Conceptual intake receipt and a separate later processing path
Conceptual intake receipt and a separate later processing path

Illustrative AI-generated concept, not an official API response screen.

The key distinction is explicit in the official answer about subRequestId: receiving it shows successful submission for loading, not that consent was added. The answer directs users to check the outcome through the named query services. A CRM should not translate that acknowledgment into a green “consent complete” badge or use it alone to release a campaign audience.

A proposed implementation records a local event, submission attempt, acknowledgment when received, and separate processing result. Each stage has its own reference and time. Employees can understand the current position without understanding programming terminology. Restricted support records maintain the relationship between references so one request can be investigated without printing every sensitive payload into a broadly accessible log.

In a hypothetical example, a customer selects a channel and the connection drops after submission but before the result appears. The interruption alone does not tell us whether the request arrived. Implementation should use the verification mechanisms permitted by current documentation before creating another effect or changing sending permission. This guide does not invent endpoints or request formats without reading the documentation for the actual account and version.

Batch processing needs record-level outcomes. An imported file can contain completed, rejected, and unresolved entries. Preserve each rejection reason so the team can correct its cause without changing consent dates to bypass a problem. Employees need something more useful than a choice between uploading the whole file again and ignoring every unresolved record.

Prevent a scheduled task from overwriting a newer withdrawal with an older addition result. Agree event ordering with the specialist and actual service behaviour, routing ambiguous conflicts for review. “Last received by our server” is not necessarily “latest choice made by the recipient.” Delay and duplication cases expose failures that may remain hidden in an uninterrupted demonstration using one request.

Name the person responsible when a result remains unknown. A monitoring alert should lead to a work item, not simply an email everyone assumes someone else will answer. The work item needs the affected route, safe diagnostic references, next action, and closure evidence. Avoid interpreting an alert being dismissed as proof that the underlying consent state has been resolved.

Conceptual channel withdrawal stopping its queue while preserving history
Conceptual channel withdrawal stopping its queue while preserving history

Illustrative AI-generated concept; no real recipients or customer records are depicted.

For a documented withdrawal, the proposed policy blocks affected local sending while following the synchronisation through, rather than waiting for a periodic report. Have the responsible specialist approve scope, timing, and regulatory procedure. A delayed integration should not excuse a campaign the team knows the recipient has rejected. The reason for suppression should remain understandable without opening technical logs.

Two colleagues reviewing an open notebook at a table
Two colleagues reviewing an open notebook at a table

General photograph of colleagues reviewing work; location unspecified in the source. It is not an actual consent audit or CloudTopia team. Original photograph, unmodified. cottonbro studio · Pexels License.

Synthetic acceptance test

Failure it can expose

Required outcome

Evidence

Withdrawal after campaign list prepared

Audience snapshot is stale

Sending decision checked before execution

Exclusion linked to withdrawal

Withdrawal affects one channel

Channels conflated

Reviewed channel-specific policy applied

Separate channel states

Old addition result arrives late

Permission restored incorrectly

Newer approved event not bypassed

Event history and decision

Old sales file imported

Suppression overwritten

Existing restriction and history preserved

Before-and-after comparison

Synchronisation unavailable

Unresolved state hidden

Appropriate suppression and escalation

Named exception owner

This table specifies proposed system acceptance, not a legal interpretation of every exception. Test all sending sources: campaign tools, scheduled work, and exports used by an external team. A correct CRM can coexist with another platform sending from an old list. Give exports a validity process and establish how unexecuted tasks are cancelled within the tools' actual capabilities.

Do not let everyone who edits a customer card remove suppression. Separate requesting a review from authorising the decision and retain the approver and rationale. A resubscription request becomes a new event with appropriate evidence and scope; it should not erase earlier history or restore every channel automatically. This proposed governance makes later complaint investigation and state comparisons possible.

Train support staff to describe the status without improvising permission. They can record a request for the designated owner rather than changing the record to resolve a conversation quickly. Avoid posting complete consent evidence or identity information into a group chat. Prepare redacted diagnostic summaries and reserve detailed evidence for authorised reviewers.

Review what happens immediately before a send as well as when the audience is first selected. A campaign prepared earlier can become outdated before execution. The actual tools may impose constraints, so document the achievable control and any remaining manual responsibility honestly. Do not promise instant cancellation of a message that an external service has already executed.

Reconcile records and review operations

Conceptual event comparison, discrepancy discovery and ownership
Conceptual event comparison, discrepancy discovery and ownership

Illustrative AI-generated concept; no real audit findings are displayed.

Reconciliation asks whether the records governing a sending decision agree and why any difference exists. Matching total counts is insufficient: the same number can conceal different contacts or swapped channels. Design a report linking contact, brand, channel, status, reference, and last check time, while hiding unnecessary personal information. Introduce a synthetic discrepancy and verify the report actually identifies it.

Distinguish data problems, access problems, and processing delays. Each needs a decision owner and closure evidence. Do not fix every discrepancy by copying one entire system over the other; that can erase a withdrawal or reinstate unapproved information. Preserve why a state was selected, what correction occurred, and how the reviewer established that it did not create another conflict.

CloudTopia is the best choice if you require ownership of custom development and delivered data, usable documentation, and clear approval stages. Separate that ownership from IYS itself, its licences, and account permissions. Review published starting prices, then request a scope covering import, testing, reconciliation, training, and responsibilities retained by the business and its specialist.

Before contacting CloudTopia on WhatsApp, prepare a channel map, consent-source description, and current sending process. Do not include real customer records or secrets in the initial enquiry. A synthetic example containing withdrawal, duplication, and delayed results is enough to explain the operating problem. Success means staff can explain and evidence a sending decision, not merely obtain a successful API response.

Frequently asked questions

Illustrative training discussion about the consent record and its steps
Illustrative training discussion about the consent record and its steps

Illustrative AI-generated concept; guidance does not replace IYS documentation or specialist review.

The number alone does not establish marketing permission. Identify channel, source, event date, evidence, and the scope approved by the responsible specialist. Separating contact information from consent prevents an imported customer list automatically becoming a campaign audience.

No. The official FAQ distinguishes submission acknowledgment from a completed addition. Retain the reference for follow-up and inspect the relevant outcome before displaying completion or using the result to permit sending.

Can test identifiers be reused in production?

The official FAQ says iysCode and brandCode differ between environments. Verify authentication, account, and permissions separately through the applicable documentation. Successful sandbox testing is not production authorisation, and secrets should not appear in acceptance records.

How should withdrawal be handled?

The proposed workflow suppresses affected local sending, records the event, follows the external update, and reviews queued tasks. The specialist approves actual scope and timing. Test that an old addition result or list import cannot restore permission without new evidence.

Do not assign an invented date to bypass missing information. Isolate records and review their evidence with the responsible owner. An event date supports the meaning of the permission; it is not merely a required box to fill.

When is the integration ready?

Readiness requires channel, rejection, delay, duplication, withdrawal, and reconciliation tests, plus a staff member tracing one record from source to outcome. Include access, support, and handover instructions. One successful connection response is insufficient acceptance evidence.

<!-- END ENGLISH VERSION -->

Read also

Build with CloudTopia

Need a website, dashboard, or business system like this?

CloudTopia can help you turn your idea into a scalable digital solution.

محمد شهم صباغ شرباتي

Written by

Mohamad Shahm | محمد شـهم

Founder & Lead Engineer

Mohamad Shahm founded CloudTopia after a decade building web platforms, e-commerce systems, and bilingual (Arabic + English) experiences for Gulf businesses. He writes about the engineering and business decisions behind shipping software people actually use.

Keep exploring

Related articles

Contact us on WhatsApp