Use Case

Personalize every journey

Each customer gets the products their recommendations rank first, with the offer your rules allow, on the channels their consent allows. Dan sets it up; you approve before anything is sent.

Recommend

The products each customer is most likely to buy.

Respect

Your discount rules and each customer’s consent.

Deliver

Every morning, in the tools your journeys use.

Dan at work

Each customer’s products, in the tools you use

You ask Dan to send the high-value customers to win back to your CRM tool every morning. Dan reads the audience, the destination and your email consent rule, then maps each customer’s email, first name and three recommended products. Nothing is sent before you approve.

Approval: Create this activation and send 2,610 contacts to Salesforce every day at 7:00?

  • Readsthe audience, your destinations and your consent rules.
  • Proposesthe fields each message needs, the schedule and who goes to each tool.
  • Waits for your yesbefore anything leaves your warehouse.

Every change Dan prepares waits for your review before it runs.

Meet Dan
In this use case

The problem

One message for everyonefits no one

A journey sends the same email to thousands of customers. Personalizing it means knowing, for each one, which products they are likely to buy, which offer your rules allow, and which channels they agreed to. That knowledge sits in different places, and rarely reaches the message in time.

What Dan prepares

The right products, the right offer,the right channel

Dan reads your customer context and the predictions of DinMo Intelligence, then prepares what each step of the journey needs:

01

Audience

The customers the journey speaks to, with what DinMo knows of each: recommended products, sensitivity to a discount, consent.

02

Journey

Consent picks the channel: who subscribed gets the email, everyone else goes to your ad platforms. The email shows each customer’s offer and recommended products, and the offer follows your discount rules.

03

Activation

Dan maps the fields each tool needs, the email, the first name and three recommended products, and schedules the sync every morning at 7:00. In the example, 2,610 of the 3,380 customers can be emailed; the 770 others stay out of the email.

04

Measure

A holdout receives nothing, so the personalized journey is measured against customers who were not contacted.

What you approve

Personal for each customer.Approved once.

Every change Dan prepares waits for your review before it runs. Dan shows the mapping, the consent rule and the schedule in one card; nothing is sent before you confirm.

01

Dan proposes

The fields, the schedule and who goes to each tool.

02

DinMo verifies

Your consent rule and your discount rules, before anything is sent.

03

You approve

“Create this activation and send 2,610 contacts every day at 7:00?” One confirmation.

04

Every action is logged

Each action keeps who approved it and when.

Modules

The modulesbehind it

01

Intelligence

The recommended products and the predictions of each customer.

Explore Intelligence

02

Context Manager

Your consent rule and your discount rules, read before every step.

Explore Context Manager

03

Journeys

The channel for each customer, the message, the wait for an order.

Explore Journeys

04

Activation

The fields and the schedule of every tool the journey uses.

Explore Activation

FAQ

Questions,answered

Where do the recommendations come from?

From DinMo Intelligence, trained on your own orders in your warehouse. Each customer gets the products it ranks first, and Dan maps them as fields your messages can use.

How is consent respected?

Through the consent rule of your customer context. Dan reads it before it proposes a step: customers who have not agreed to email never receive one.

Do we need to change our CRM tool?

No. DinMo sends the fields to the tools you already use, and your messages read them there.

More use cases

Your next use case.With your data.

Let’s discuss your data, your tools and the use cases you want to build.