AI Assistant (Leat MCP)
July 20
→
Next best time and channel
Choose the timing and permitted channel for each customer as part of the same decision as the action itself. Leat learns from individual visit and response patterns while respecting stated preferences, consent, quiet periods, and frequency limits.
Leat can learn when each customer usually opens messages, visits, browses, and returns. It can also recognize when their usual gap between visits has become longer than expected. An action might arrive before a regular weekend visit, at the time the customer normally browses, or when their behavior first suggests they are becoming inactive. Timing can also relate to an event, such as two days before points expire or on the morning of a birthday.
Email, wallet notifications, and other channels can perform differently for each customer. Leat considers previous response behavior while honoring declared preferences first. A channel without the required consent is never selected. If one channel is close to its frequency limit, another permitted channel can be considered without exceeding the rules that protect the customer.
What to send, when to send it, and where to deliver it are treated as one decision. A €5 voucher sent by email on Sunday evening and the same voucher delivered through a wallet notification on Saturday morning are different options with different expected results. For an immediate decision at the POS, the current time and channel are already fixed, so the engine chooses within that context.
The first available moment is not always the most effective one. Leat can hold an action until the customer is more likely to notice and use it, such as before their usual visit or after an appropriate period without contact. Waiting for a stronger moment can reduce unnecessary messages while giving the selected action a better opportunity to work.
Campaign calendars
Launches, seasonal openings, and other time-sensitive communications can remain fixed while other actions use per-customer timing.
Quiet period boosters
Teams can define days and hours when proactive messages should not be sent, including late nights, public holidays, or periods following a service issue.
Reactivation timing
Win-back actions can begin when a customer moves beyond their usual return pattern rather than after the same fixed period for everyone.
Peak season scheduling
Timing rules can change during busy periods when sending a message a day earlier or later may affect whether it is noticed.
Channel performance review
Response can be compared by channel and customer group to identify where a channel should receive less priority or stop being used.
Timing effectiveness check
A fixed-schedule customer group can be compared with per-customer timing to measure whether personalized delivery improves results.
