ECM Journey Studio

Palette

Drag onto canvas, or click to add after the selected step

Journey

⚗ Simulation · demo only event for · Day 0 The prototype has no real clock or sends. Events run immediate steps at once; Timer and Wait steps move with "Advance 1 day". Not a product control.

✓ executed · ▶ current step · ● customers at step · drag to pan / move · orange port → connect · × on a step or Delete key removes it · click a link's label to remove the connection

Offer List

Marketing offer is its own entity: it maps to a Product Catalog offering, carries eligibility, priority, tags and channel content, and is linked to one or more journeys.

Offer	Catalog ref	Priority	Hierarchy / tags	Journeys	Status

Policies

Policies are objects attached to offers, journeys or groups of them — not global parameters. Existing communication rules (consent, overlap, cooldown, pre-sent) keep running underneath at delivery time.

Templates

Segments

Segments are built with the query builder on a DataMart (Main or Event/feedback) and belong to a Segment Group. A segment is a campaign's target audience, or an exclusion list that removes customers from deliveries on the chosen channels.

Segment	Group	Source · status	Customers	Actions

Audience

— customers

Filterscolumn · operator · value

combine with

Audience insight — updates as you edit the filters

Matching rows

Journey Monitor

Per-customer journey state, funnel by step, and point-in-time participant lists.

Journey

⚗ Simulation · demo only Day 0 The prototype has no real clock or sends — these buttons move a simulated clock so you can watch customers progress. In the product the monitor updates on its own.

Journeys — status, version and activation

Journey	Status	Version	Activated	Entry	Participants	Active	Goal

Selected journey

Funnel — customers who reached each step

Participants at a point in time

Show state as of Day 0 (now)

Customer	Segment	Current step(s)	Status	Open offers	Preferred channels	Since

Decision API

Contract sketch for channels (app, web selfcare, CSR, USSD) to ask what to show a customer and to report what happened. Responses are generated from the current journey state.

CustomerChannel

Parameters

Segment Groups

Every segment belongs to one group. Groups are defined here by the admin so the marketer's list stays organised; marketers pick a group when saving a segment.

Group	Description	Segments	Owner	Actions

Campaign form — optional Info-step fields, switched per customer / version

Communication rule defaults — applied to every campaign; a campaign only switches a rule on/off in its Communication rules step

Channels & senders — sender profile, gateway and receiver defaults live here, not in every campaign

Channel	Sender profile	Gateway	Max volume / day	Receiver column

Changing a sender or gateway here applies to every campaign and journey on that channel. Campaigns only pick the channel; they never ask for gateway or receiver settings again.

Release & licences

Version and environment facts live here, on an admin page — not next to dates on working screens. Marketers never need the technical release number; the admin does when talking to support.

Product release

ECM 26.1

commercial version shown to customers

Technical release

1.4.28

build 2026-09-15 · was shown next to dates before

Environment

Demo · EU-1

no messages are sent from here

Journey Studio

prototype

UX/UI redesign track

Third-party components

Component	Used for	Licence	Status	Decision
AG Grid	Data grids (Datamart, lists)	Enterprise (dev licence)	licence ending	Move to Community edition; grid styling and export to be re-done on our side.
Stripo	E-mail template editor	Free tier · one account per customer · ~100 templates per account	branding removed	Enterprise (~1,200 USD/yr) optional in the licence model. Decide in ~6 months: keep, Figma import, or AI-generated content.
LimeSurvey	Survey channel	Per customer	in review	No survey demand in recent RFPs; hidden from Templates. Check contract scope of the customer that renewed before retiring.