Menu
OneTrace.pro
Stores, delivery, services with sign-in codes and order statuses← All solutions

The important message gets through — via the channel that worked

An order confirmation, a sign-in code or a delivery status cannot be sent “somehow”. Transactional messages use a separate queue, and a cascade tries channels in turn and does not spend money on SMS if the customer has already read the message in a messenger.

The challenge

Order notifications and cascades

  • Notifications are scattered across the site code, the CRM and different gateways
  • SMS goes to everyone, although half of your customers read messengers
  • It is unclear whether the message arrived and through which channel
The important message gets through — via the channel that worked
How we solve it
  1. 01

    Send with one call

    POST /messages from your server: a template, a recipient and order data. The recipient profile is created or updated automatically, and the message goes out at once through a separate queue.

  2. 02

    Define a cascade

    For example, WhatsApp, then SMS if not delivered within 2 minutes, then email. For each step you choose what to wait for — sent, delivered or read — and for how long.

  3. 03

    Use it in journeys too

    The same cascade is a journey node: a cart reminder or a reorder prompt goes through the cheapest channel that gets through.

  4. 04

    Track the status

    The status of every message and cascade is available via the API, and deliveries, reads and errors land in the customer profile and the channel report.

What you get
  • All notifications in one place with shared templates and statuses
  • The expensive channel is used only when the cheap one did not work
  • For every customer you can see which message they got and where

Built on

Try it on your own data

14 days on the Growth plan, no card required: up to 1,000 profiles and 500 emails a day.

Start free trial