Start a workflow from an event in People, Channels, or OneCloud

Start a workflow from a new contact, a sent message, an uploaded file, or an event in a system that you connect. Automation logs each action that the workflow takes, so you can trace any step that fails.

Connect the steps between your Delalify apps

With Automation, an event in one Delalify app can start the next step in another. A workflow can send a contact a message through Channels as soon as someone tags that contact in People, for example, while another workflow can alert your team whenever a colleague uploads a file to OneCloud. You can build each workflow in a visual editor or start from a template. Automation continues every workflow through nights and weekends, so your team can keep its working hours for the cases that a colleague has to judge.

What a workflow can do

When each follow-up depends on a colleague remembering it, a new lead can wait in the inbox until someone checks it. Your team can also miss the deadline on a file that a partner uploads, unless a colleague opens that folder in time.

Pick the event that starts each workflow in People, Channels, or OneCloud, such as a new contact, a message that your team sends, a file that a colleague uploads, a tag that someone adds, or any other event that those apps record. Automation starts the workflow when that event occurs, so the workflow can reply to a new lead or alert the colleague who needs a partner's file.

A VIP customer who spends thousands with you each year needs a different message from a cold lead who is yet to buy anything. If one workflow sends one message to every contact, your best customers will receive the email that you write for a lead who signs up today.

Add if/then branches so that Automation can pick a path for each contact from their details, their behavior, or their earlier interactions with your team. At a branch, Automation can pick a message from a contact's tags in People, skip a step for contacts who fall outside the branch's condition, or assign the contact to a colleague when they match the criteria that you set. Each VIP customer then follows the VIP path, while each cold lead follows the path that you build for new leads.

Cross-product actions illustration

When one process involves People, Channels, and OneCloud, a colleague will have to copy details between them, tell the team when a partner uploads a file, and update the contact's record after each message. Whoever retypes those details by hand can also introduce a typo at every step.

A single workflow can look up a contact in People, send them a message through Channels, and then manage the related files in OneCloud. Each step uses the details from the step before it, so your team leaves the copying between apps to Automation.

You may want to space the messages in a welcome sequence over several days, so that each contact has time to read one before the next. If your team schedules each message by hand, it will have to add a set of send dates to its calendar for every new contact, which comes to hundreds of dates once a few hundred contacts are in a sequence.

Add a delay of minutes, hours, or days between any two steps of a workflow. With delays, Automation can send the first email of a welcome sequence as soon as someone signs up and a follow-up with next steps three days later. Automation times each delay to the minute, so every contact receives each message at the interval that you set.

Pre-built templates illustration

If you build each workflow from an empty canvas, you will have to work out every step, branch, and delay yourself, even for a common process such as welcoming a new contact. Your team will also have to test each of those choices before Automation puts the first contact through the workflow.

Start from a template for a common process, such as a welcome sequence for new contacts, a reminder campaign before an event, or an alert whenever a colleague uploads a document to OneCloud. Each template includes its steps, branches, and delays, so you can edit the parts that differ for your organization and then switch the workflow on.

A workflow operates while your team is busy with other work, so you can first learn about a failed step from a customer who asks where their email is. To fix the step, someone will have to find out which contact it fails for, which branch that contact follows, and what data the step uses.

Automation flags a step as soon as it fails and shows you the contact, the branch, and the data at that step. Open the failed run from the run history, correct the step, and repeat it for each contact whose run fails there.

Any tag

Can trigger a workflow

24/7

Workflows continue through nights and weekends

Zero

Follow-ups left to memory

What changes for your team

Let Automation repeat the routine steps

When your team repeats the same step for every new contact, such as sending a welcome email or adding a tag, you can make that step part of a workflow, which Automation then performs for each contact. Your colleagues can therefore spend their day on the conversations and decisions that only a person can take on.

Reply to a lead within seconds

Because Automation starts each workflow from the event itself, a lead who submits your contact form can receive your first follow-up within seconds, whatever the time of day. Your sales team can then continue the conversation from that first reply.

Enter each contact detail once

Automation copies each contact's details from People into the Channels and OneCloud steps of a workflow, so People is the one place where your team types them.

A different path for each kind of contact

In one workflow, Automation can put a new customer on an onboarding path and a lapsed customer on a win-back path, while it assigns each VIP to their account manager. Automation picks each contact's path from their tags and details at the branch.

How organizations use Automation

A form submission starts the follow-up

When a lead submits a contact form, People creates a contact from their answers and applies the New Lead tag. As soon as People applies the tag, Automation starts a workflow that sends the lead a welcome email through Channels to acknowledge their inquiry. Three days later, the workflow sends a follow-up email with a case study. If the lead opens both emails, Automation asks the assigned sales rep to schedule a call.

Result

Automation sends the welcome email and the case study to every new lead, so the sales rep phones only the leads who open both. Since each of those leads opens the case study before Automation alerts the rep, the rep can begin the call by asking about it.

A form submission starts the follow-up

Renewals start 90 days before a contract lapses

Once a day, Automation checks the contract expiration date on each contact profile in People. When a contract is 90 days from expiring, the workflow emails the renewal terms to the client's account owner through Channels and creates a task for the account manager to schedule a discussion. The workflow then sends a reminder 60 days and 30 days before the contract expires.

Result

Automation tracks every expiration date, so the account manager receives a task for each renewal while the client has 90 days left on the contract. The account manager can prepare for that conversation from the client's profile in People, which includes the notes and messages from the whole contract term.

The approver hears about each contract on upload

When a colleague uploads a document to the approval folder in OneCloud, Automation emails each designated approver through Channels. The workflow also updates a tracking tag on the submitter's contact profile in People, so managers can follow the pending approvals across their team.

Result

Each approver opens the approval folder when Automation emails them about a new document, so approvers can drop their routine checks of that folder. Managers can find every pending approval from the tracking tag on each submitter's profile, so they can chase a slow approval before it delays the next piece of work.

The approver hears about each contract on upload

Each new customer receives 14 days of onboarding emails

When someone applies the New Customer tag to a contact in People, Automation starts an onboarding workflow. The workflow sends a welcome email through Channels with access credentials and next steps, creates a shared folder in OneCloud for project documents, and asks the assigned account manager to schedule a kickoff call. On days 3, 7, and 14, the workflow sends a follow-up email about the features that match the customer's use case.

Result

Automation sends each onboarding email on its day, so the account manager's part of onboarding starts with the kickoff call. When the account manager schedules that call, the customer already has their access details and a shared folder in OneCloud.

Each new customer receives 14 days of onboarding emails

A dental clinic invites overdue patients back

A dental clinic tags each patient in People whose last cleaning is more than six months ago. As soon as the clinic applies the tag, Automation starts a workflow that sends the patient a recall message through Channels with an invitation to book. A branch in the workflow then checks for a reply. When a patient books, the workflow sends a confirmation and removes the tag, while a patient who stays quiet for a week receives one more reminder before the clinic moves them to a low-priority list.

Result

Automation sends the recall message and the reminder to every patient who is overdue for a cleaning, so the front desk can spend its day with the patients in the clinic. Because the workflow removes the tag from each patient who books, the front desk can filter by that tag to find the patients who remain overdue.

A dental clinic invites overdue patients back

Start workflows from your other systems

Integration connects the tools that your team already uses to Delalify, so Automation can work with their data.

Common questions about Automation

Set up each follow-up once

Automation performs each workflow whenever its event occurs in People, Channels, or OneCloud, whether you build the steps yourself or start from a template.