eengage.
A PRODUCT DESIGN EXPLORATION Explore the concept
Engage / Redesign concept / 202601 / 07

Every journey.
More considered.

Engage connects player events, audiences and omnichannel journeys in one iGaming CRM. This concept gives that powerful system a calmer, clearer workspace.

Enter the workspace Explore the thinking ↓

Understand the player

Normalize operator events and build dynamic or curated audiences.

Orchestrate the journey

Durable workflows with delays, branches and gamification triggers.

Connect across channels

Email, SMS, WhatsApp, push and in-app through unified adapters.

Keep control in view

AI Concierge assistance, consent and responsible gambling suppression.

Platform facts: RESEARCH.md §1 — Functionality. All screens and metrics in this presentation are fictional design concepts.

The platform underneath02 / 07

An event at the edge.
A connected experience.

The brief describes an API-first platform with durable execution and database-enforced tenant isolation. The redesign makes this flow easier for operators to understand.

01 · Operator events

Registrations, deposits, bets and KYC webhooks

02 · Cloudflare edge

Per-tenant Workers verify signatures and normalize events

03 · Fastify API

Validate, deduplicate and upsert recipients · Fly.io

04 · Journey workers

Postgres-backed pg-boss queue · Railway or Fly.io

05 · Channel adapters

Dispatch to five channels and record delivery + journey events

Neon Postgres · forced row-level securityAPI → transaction pooler   /   Workers → direct session connection
Operator workspace

Next.js 14 dashboard on Vercel · API-backed controls

Content & client delivery

Cloudflare R2 assets · Cloudflare CDN for the client SDK

Event analytics

ClickHouse Cloud · high-volume telemetry pipeline

Current platform as described in RESEARCH.md §3; simplified diagram. §4 notes SDK bundle consolidation is still a modernization target. This concept site is independently hosted as static files.

Where clarity can improve03 / 07

Less interpretation.
More understanding.

Four documented gaps become tangible design opportunities. These are proposals grounded in the brief, not a visual audit of the current product.

01

From records to a visible path

Today: execution history is presented as flat activity and delivery records.

Concept → trace a sample player directly on the journey canvas.

02

From static previews to context

Today: the composer relies on a static preview context.

Concept → inspect sample player data beside a rendered message.

03

From locale logic to visible languages

Today: localization uses inline Liquid logic or raw locale JSON.

Concept → explicit language tabs with completion states.

04

From desktop-only to anywhere

Today: administration is desktop-only; the mobile app is a planned phase.

Concept → responsive monitoring and editing, plus visible AI approval controls.

Documented gaps: RESEARCH.md §4 — Improvement opportunities, including deferred AI autonomy controls. Incremental segmentation and performance rollups remain separate backend work.

The design direction04 / 07

Familiar foundation.
A more focused experience.

Keep Engage’s dark surfaces and red identity. Bring hierarchy, context and player care into the moments where operators make decisions.

Make the next step clear

Four core destinations, a deliberate type scale and a clear primary action on every screen.

Keep context close

Audience rules beside counts. Node settings beside paths. Sample player data beside content.

Make care visible

Surface suppression, channel consent and human review as part of everyday operations.

Engage red / dark slate12px cards / 8px controlsSystem type / zero font downloadsMobile-first / keyboard accessible

Proposed direction using RESEARCH.md §2 — Design tokens and UX principles. Radius and typography are deliberate concept adaptations; navigation is a four-screen subset.

01 / The overview05 / 07

Start with the whole picture.

A focused overview connects engagement health, recent activity and journeys that need attention. Try the sample reporting-period selector.

Open overview
engage / overview · interactive concept

Signal before detailFour metrics establish a readable daily starting point.

Activity with meaningDelivery, audiences and suppression share a single feed.

A useful next actionConcierge suggestions link straight to the message library.

02 / The journey workspace06 / 07

See the path. Understand the why.

The vertical workflow stays familiar. Select a step, inspect its settings or trace a fictional player through an eligible branch.

Open journey
engage / journeys · interactive concept

Visible player lineageA proposed path overlay explains the sample execution.

Settings within reachA contextual inspector becomes a stacked panel on mobile.

Explicit operator controlDemo draft edits and AI approval mode remain visible.

03 / Audiences & messages07 / 07

Know who. Consider what.

Readable audience rules meet reusable, localized content. Switch screens below, or open the full workspace to explore.

Open this screen
engage / segments

Audience confidenceSearch segments and change rules to see a sample estimate.

Content in contextFilter five channels and preview fictional player personalization.

Languages made visibleExplore English, German and Finnish welcome messages.

Take the concept for a spin.

Four connected screens. Fictional data. No live sends or backend.

Explore the interactive mockup

Mockup interactions illustrate proposals. They do not implement the production engine, live counts, full template rendering or safety enforcement. Factual grounding: the supplied research brief.