Skip to content

Sales Workflows

Make follow-up part of the process

A proposal is out. Who follows up? ONE LOOP can create the next task, send a follow-up and prepare the handover after a deal closes — using the rules you configure.

Here’s what you can do.

Three examples show how you can use Sales Workflows.

01

Turn the proposal stage into a task

When an opportunity moves to your proposal stage, ONE LOOP can create a follow-up task. You choose the pipeline, stage, assignee and due date.

Example: moving to the proposal stage is connected to a follow-up task assigned to Lea.
Simplified product example · not a live product view
02

Check first. Then follow up.

After a delay you set, a condition checks whether this opportunity is still open and in the proposal stage. Only then is the prepared follow-up sent. The other branch ends without a message.

Example: after a delay, a sales workflow checks status and proposal stage and branches to a follow-up or the end.
Simplified product example · not a live product view
03

Keep things moving after the deal closes

When the status changes to Won, a separate workflow can prepare the handover. For example, it can create a task for the next person responsible. This is a separate trigger, not just a stage change.

Example: setting an opportunity to Won triggers a Prepare handover task assigned to Tom.
Simplified product example · not a live product view

What this changes for your day-to-day work.

The practical benefits of Sales Workflows.

Plan your follow-up in time

Set the due date in the task action. You can skip weekends; the preview shows the calculated date.

A follow-up task is due in two days, with skipping weekends enabled.

Send messages at suitable times

Limit messaging to the days and hours you choose. This sending window does not pause internal actions such as updating a field.

The message-sending window is configured for Monday to Friday, 9 am to 5 pm.

Stop after a reply

With Stop on Response enabled, the workflow ends for a contact who replies to a message from that specific workflow. Other conversations do not automatically trigger this stop.

With Stop on Response enabled, a reply to the workflow message ends that run.

Handle each deal in its own process

For a contact with multiple opportunities, choose whether each matching deal gets its own run. You can then check whether parallel messages are actually intended.

Consulting and Workshop are shown as separate opportunities with their own runs for one contact.

Check the process before launch

Use the execution history to review completed steps, waiting points and errors. Test contacts help you check the alternative branch before using real enquiries.

A test contact's execution history shows a created task and an active waiting step.

Simplified examples, not live account data.

What you need to get started.

We configure triggers, pipeline filters, actions and exit rules, then test them with test contacts. A published workflow processes matching events. Messaging requires a suitable channel, sender and permissions; we confirm access and any usage costs for your offer.

The workflow uses the opportunity in the pipeline, creates tasks for the contact and can send messages through configured channels. These steps must be explicitly connected. Lead routing handles the distribution of new enquiries; this feature handles the next steps in an ongoing sale.

Availability and any add-on or usage costs are confirmed for your ONE LOOP account before implementation.

Your questions, answered.

How do sales workflows differ from the Workflow Builder?

The Workflow Builder is the tool used to assemble processes. Sales workflows are specific uses of it: following up on a proposal, creating tasks or preparing a handover after a deal is won. They need matching triggers, filters and actions; they are not active without setup.

What happens when a contact replies?

When enabled, Stop on Response ends the run for that contact if the reply is to a message from that specific workflow. It does not just pause until the next message. Replies to other conversations or a personal handover need their own configured rules.

Can an opportunity trigger a workflow more than once?

Another matching stage change can trigger a new event. Whether another run starts depends in part on the re-entry rules. Multiple opportunities for the same contact have a separate setting for a run per deal. Test both so they do not create unwanted duplicate tasks or messages.

How do we check a workflow before using it?

Using test contacts, we check the matching trigger, each branch and the actions performed. This includes status changes, reply stops, delays and notifications. A draft is not an active workflow: publishing and reviewing the execution history are part of approval. A task being created does not mean it has been completed.

See it with your own use case.

Let’s explore your use case and what the setup requires.

Book a demo