Insurance. Content that follows status.
Control policy, claim and renewal guidance across changing customer states.
Insurance content changes as policies approach renewal and claims move through assessment, documentation and settlement stages. Customers need timely, consistent guidance without static app copy falling behind operational status.
Content that follows status.
One change, end to end.
A customer who has not given consent for a channel is skipped on that channel.
Illustrative interface content. It shows what the platform supports, not an insurer configuration.
What makes it hard.
Renewal timing pressure
Renewal content must follow policy dates, cancellation status and configured contact windows without continuing after eligibility changes.
Claim journey trust
Policyholders expect clear instructions when claim stages, document requirements or assessment statuses change.
Regional wording variation
Arabic insurance terminology can vary across Saudi Arabia and neighbouring markets, requiring controlled locale-specific wording.
Four things a team could build.
Update claim guidance
An insurer could change the guidance block shown at each stage of a motor claim. Dynamic Blocks would supply the eligible instructions without requiring a new app release for every copy change.
Dynamic BlocksCoordinate claim follow-up
An insurer could guide a policyholder from claim submission through document completion and assessment updates. Journeys would advance when the insurer supplies the corresponding claim events.
JourneysControl renewal campaigns
An insurer could run a campaign for policies approaching their expiry dates. Campaigns would limit eligibility using supplied policy status and stop serving content after the configured window.
CampaignsSend renewal reminders
An insurer could send a reminder when an eligible policy enters its configured renewal period. Messaging Channels would apply the selected template and route using consent data supplied by the insurer.
Messaging ChannelsWhat does the work.
Dynamic Blocks
It keeps in-app claim guidance aligned with the policy or claim context supplied by the insurer.
Journeys
It coordinates claim follow-up through event-based entry, waits, and conditions.
Campaigns
It controls renewal timing, policy eligibility, approvals and campaign lifecycle states.
Messaging Channels
It routes approved renewal and claim notices through configured providers for eligible recipients.
Residency, certification and the Insurance Authority.
Data residency. Today ContentFlow runs as a single deployment on infrastructure located in Riyadh, Saudi Arabia, so production content and end-user data are processed in the Kingdom; that is a property of how we are currently deployed rather than a control the product enforces, encrypted backups and some third-party processors are handled outside the Kingdom, and an in-Kingdom-only arrangement is something we agree in writing on an Enterprise plan rather than something this page can promise.
Certifications. Our controls are built around the requirements of the Saudi PDPL. Backups are encrypted with AES-256 and restore-tested. HTTPS is enforced across the site. SOC 2 Type II and ISO 27001 are planned.
Production integration today uses the REST API. Native SDKs for React Native, iOS, Android and Web are in preview and are not generally available. The @contentflow/cli package is not published yet.
One engineering integration up front. After that your team publishes content changes without a new app build and without a new app store submission.
Publishing content through ContentFlow does not require a new build or a new store submission. Any change to your app's own code still goes through Apple and Google review, and remotely delivered content has to stay inside the purpose your app already declares and the store policies that apply to it.
Insurance Authority. ContentFlow has not been assessed against the Insurance Authority's outsourcing or cloud computing rules and does not claim compliance with them. Those rules sit with you as the regulated entity. What we can put in front of your assessment is the deployment location, the sub-processors involved, the data flows, the retention behaviour and the access controls in place; ask and we will send them.
The Free plan is for evaluation. Our terms do not permit real production, personal or regulated end-user data in evaluation or sandbox environments, so a pilot carrying real customer data runs under a signed agreement.
What teams ask.
Can claim guidance change with claim status?
Yes. The insurer supplies the claim context or event, and Dynamic Blocks or Journeys select the configured approved content.
Can renewal content stop after a policy changes?
Yes. Campaign eligibility and journey conditions can respond when the insurer supplies a cancellation, renewal or other relevant policy event.
Can policy wording vary by market and language?
Yes. Localization can link Arabic and English locale variants to the same content item with approval-gated publishing and configured fallback behaviour.
Five sectors, one platform.
Production integration today uses the REST API. Native SDKs for React Native, iOS, Android and Web are in preview and are not generally available. The @contentflow/cli package is not published yet.