Mobile appDocumentation

The reply changes.
Your workflow adapts.

Build follow-ups around what your customer actually does. Pulse connects your data, messages, calls and conditions in a visual workflow you can inspect.

Map your first workflowSee how it works
  • Visual workflow builder
  • Branches based on outcomes
  • A history for each run
Pulse workflowInteractive example
Cart enrolledCustomer + checkout details
Wait 2 hours
Send a reminderShare the checkout link
Reply received
Check the orderAsk the store for purchase evidence

A verified purchase reaches the recovery goal. An unverified order takes the help path.

The work between conversations

A fixed sequence only knows the next date.

Customers reply, go quiet, ask for help or complete a purchase. Treating every response the same leaves your team stitching the steps together.

Give each outcome its own path. Pulse can wait, check a condition, send a message, make a call or end the run based on the flow you configure.

01 / Start with context

Bring the details into the flow.

Start with a data source and carry the information into each step. Give the workflow the contact details, fields and links it needs to act.

  • Start from imported data or a configured API source.
  • Use source fields and earlier node outputs in later steps.
  • Connect an external status check through a webhook node.
02 / Choose the next step

Let the outcome decide the path.

Connect the actions your journey needs. Use waits and conditions to respond to a message reply, a timeout, a call outcome or a returned field.

  • Combine supported messaging and voice actions.
  • Set delays and follow-up windows.
  • Give success, no-response and failure outcomes explicit paths.
03 / See what happened

Follow the run to its outcome.

Inspect the route each run took and the events behind it. Define what counts as success, and use evidence when a goal depends on a real-world action.

  • Review the current step and run history.
  • Configure failure handling for the workflow.
  • Use returned data to verify a goal such as an order.
Before you launch

Make it work
for your business.

Connect the systems, check the details and try the journey with sample data.

  1. 01

    Choose a journey

    Start from a relevant preset, such as cart recovery or feedback collection, and adapt it to your process.

  2. 02

    Connect the actions

    Configure the data source, channels, API lookups, messages, waits and outcome branches your flow needs.

  3. 03

    Check it with sample data

    Walk through the possible paths, verify the connections and inspect the results before enrolling your audience.

A few practical details

Questions,
answered.

How are workflows different from campaigns?

A campaign helps you reach an audience on a chosen channel. A Pulse workflow connects multiple actions and chooses the next path using replies, timeouts, conditions and other supported outcomes.

Can I start from a template?

Pulse includes presets for journeys such as cart recovery, failed-payment follow-up and post-checkout feedback. A preset still needs your data, channel connections, messages and any required status APIs.

Do I need a developer?

You build the flow visually. Importing data and configuring messages may be straightforward, while connecting a store or custom status API can require technical help. The work depends on the systems your journey uses.

What happens if a step fails?

Pulse records failures and applies the configured failure policy. Give failures an explicit path and review the run history; the available branches vary by node type.

Does a successful call count as a completed goal?

Only if that is the goal you deliberately configured. For cart recovery, positive intent is not a verified purchase. The cart preset uses an order-status field as evidence before recording a recovery.

Put it to work

Turn your follow-up process into a flow.

Bring your process and the questions your customers ask. We’ll help you find the right starting point.

Map your first workflowExplore pricing