Journeys

A journey is how Oblic reaches your contacts: a campaign's one message, an automation started by a contact action, date or email event, a WhatsApp bot's conversation, or a journey of its own, built step by step on any channel. Journeys lists them all, and opens each in its own editor.

Kinds of journeys

KindWhat starts itWhere you make it
CampaignYou send it now, or at a time you scheduleThe campaign editor
AutomationA contact signing up for email, joining or leaving a list, a tag added or removed, a date, or an email sent, opened or clickedThe automation editor
WhatsApp botA WhatsApp message with your keywordThe bot editor
JourneySomething that happens, for each contactThe journey editor, step by step

Journeys shows every kind in one list. Filter it by kind, open each one in its editor, and see each one's insights on a page of its own.

Make a journey

In Journeys, choose New journey, give it a name, then choose how it starts:

  • Send now or at a time makes a campaign.
  • When something happens makes an automation.
  • When someone messages you on WhatsApp makes a WhatsApp bot, with the keyword that starts its conversation.
  • Step by step, on any channel makes a journey of its own.

Steps

A journey of its own starts on one trigger, then runs its steps for each contact who enters:

  • A start: a date (a birthday, an anniversary, a specific or recurring date, or the day they signed up for email); signing up for email, joining or leaving a list, or a tag added or removed; one of your emails sent, opened or clicked; or something they did in your store, such as an order (Events).
  • A wait: hours, days or weeks.
  • A send: an email, a WhatsApp template from your organization's connected number, or an SMS where Oblic sends SMS for you.
  • A branch: an if/else on the contact's fields, or a split.
  • An end.

Each step's settings open beside the canvas. Send a test, in the editor's header, sends one of the journey's emails or WhatsApp templates to you, or to a few others, before it goes live. This sends a real message, not a simulation; review the selected sender, template, recipients and billing before you send it.

A WhatsApp conversation

A journey reaches a contact with a WhatsApp template. When they reply, it can carry on the conversation as a WhatsApp bot does, with the editor's WhatsApp conversation steps:

  1. Wait for a reply, right after a WhatsApp message. It waits up to the hours you set, from 1 to 168 (a week), or 24 when you set none, and can save the reply to a variable. When the contact replies in time, the journey goes on by Replied, into the conversation; when they don't, it goes on by No reply. If no template was sent, or the newest template was held back, this wait takes No reply without waiting for a message that was not sent.
  2. After Replied, a bot's steps, each set up as in the bot editor:
    • Send a message: your own text, not a template.
    • Ask a question: answered by text, or by up to three buttons, the answer saved to a variable.
    • Set a variable: a value the next steps can use.
    • Branch by a variable: Yes or No, as a variable's value is, is not, contains, starts with, is greater than or is less than the value you give.
    • Hand to a person: anyone in the workspace, or one member, with a message to the contact first if you write one. The person replies from the inbox, and when they hand the conversation back, the journey carries on from this step.

In a message or a question, type @ to insert one of the contact's fields, and write a variable as {{variable}}, such as {{reply}}.

  • A reply goes to the journey waiting for it, even when it also has a bot's keyword.
  • The journey's replies are billed as a bot's, at your plan's price for bot replies.
  • The conversation shows by the journey's name: on the contact's timeline, and in the inbox for a hand-over.

The inbox

A conversation handed to a person waits in the inbox, the Inbox view of WhatsApp Bots > Chats, which counts the conversations waiting on someone. Search it by number, name or email, and show the conversations by their state and by whom they're assigned to.

With incoming capture configured, a message that no bot, journey or person answers can open a conversation in the organization's default workspace, marked as started by the contact; later messages join it. Check the inbox and channel configuration rather than assuming every provider delivery has already appeared. Until someone replies in it or it's assigned, a bot or a journey that answers the contact takes the conversation over: it ends as Taken by a bot, or, at a bot's Hand to a person step, continues as that bot's hand-over. Once someone has replied or it's assigned, it's theirs, and no bot answers the contact until it ends.

  • Open a conversation to read what the bot and the contact said, and reply. You can submit a free-form reply only within 24 hours of the contact's last message; the provider may still refuse it.
  • Assign it to yourself, to anyone in the workspace, or to a member who can reply there.
  • Hand it back to the bot or journey, which carries on from its step, or close it. A conversation the contact started has no bot to hand it back to, so it can only be closed.
  • It checks for updates while it's in front of you: an open conversation checks about every 3 seconds, and the inbox's list about every 10 seconds. A contact's new message, a reply's status or another change appears after a successful read, not by a guaranteed deadline. A tab in the background checks nothing until you come back to it.

Publishing

A journey runs once you publish it. Publishing checks the graph and the runtime's current capabilities, and names steps that are not configured to run, such as:

  • a send without its sender, template or values;
  • a wait for a reply that isn't right after a WhatsApp message, or that waits anything but a whole number of hours from 1 to 168;
  • a conversation's step that a wait's Replied doesn't lead to, on every way to it;
  • a conversation's step without what it needs to run: its message, its question and buttons, its variable, or the member it hands to.

Publish again to take your changes live: the published version runs until you do. Publishing does not guarantee provider acceptance or delivery. Pause holds runs where they are and prevents new entries; Resume continues on the published version. Pausing does not recall messages already submitted. The list offers deletion for a draft or a paused journey; deleting a paused journey ends the runs it holds.

Insights

Each journey has a page of insights from the counters and ledger its kind records. Campaigns show running totals, not a selected date range. Automations, WhatsApp bots and journeys of their own can show results so far or over the last 7, 30 or 90 days. Channel figures appear when that source has something to count; an entry count appears only when journey-runtime entries are recorded. Missing figures are not proof of zero activity or message delivery, and these insights are not downstream conversion attribution.

Was this page helpful?