Build each workflow once for every Delalify product

Beryl Orchestrate performs each step of a workflow that you define once, across People, Channels, OneCloud, Teams, and the rest of Delalify. At every step that you mark as sensitive, Orchestrate pauses the workflow until an approver signs off.

One workflow across every Delalify product

Beryl Orchestrate starts a workflow when an event happens in a Delalify product, such as a new contact in People. At a decision point, Orchestrate follows the branch that matches Beryl's classification of the input. At a sensitive step, it pauses until an approver signs off, then resumes on its own. If a server crashes partway through, Orchestrate resumes the workflow from the step that the crash interrupts. Orchestrate completes an onboarding sequence in seconds, with the same steps in the same order for every new customer, so your team stops coordinating each one by hand.

Define a workflow once and let Orchestrate carry out every step

Each workflow in Orchestrate starts from a trigger, performs its steps across your Delalify products, and pauses at the steps that you mark for approval. The steps below show how you build one, from the trigger to a recurring schedule.

What Orchestrate does at each step of a workflow

Cross-product flows on relationship events illustration

To onboard a new customer, your team will have to create a contact, send a welcome sequence, set up a shared drive, assign a team member, and schedule the kickoff. Each of those steps happens in a different product, so someone will have to move between products and remember the order.

Once you build the workflow, Orchestrate performs the whole sequence each time a new contact appears in People. It starts the welcome series in Channels, creates the shared drive in OneCloud, sets up a client portal in Builder, adds the right members in Teams, issues the first invoice in Wallet, and books the kickoff on the calendar. Orchestrate completes the sequence in seconds and repeats it identically for every new customer.

Your incoming leads can need different follow-up depending on their source, their question, and their industry. A set of fixed rules can route the cases that you plan for; however, a lead that matches none of those rules will have no path to follow.

You can add an AI decision at any step of a workflow, at which Beryl classifies the intent of the incoming message so that Orchestrate can choose the matching path. Because Beryl classifies each message by its meaning, it can send a message down the right path even when the message uses none of the keywords that a fixed rule checks for.

Approval gates on sensitive steps illustration

You will want the routine steps of a workflow to happen automatically, while a person checks the sensitive ones, such as sending a contract, granting access to someone outside your organization, or refunding a large invoice. If your workflow tool can only automate a whole workflow, you will have to choose between automating the sensitive steps and doing every step by hand.

When you mark a step as needing approval, Orchestrate pauses the workflow at that step until an approver signs off. The approver sees the contact, the proposed action, the history, and Beryl's reasoning from the AI step that leads to the pause, then approves the step or sends it back with one click.

If a network error stops a workflow at step seven of nine, the first six steps are complete and the last three are not. If your tool does not resume the workflow, you can first learn about the gap when the customer asks about the kickoff meeting that is missing from their calendar.

Orchestrate saves each step of a workflow as it completes and retries a step automatically after a temporary failure. If the system crashes at step seven, Orchestrate resumes the workflow from step seven once the system restarts, so every workflow that you start finishes, even through a deployment or an outage.

A weekly account review, a quarterly compliance check, or a monthly invoice reconciliation will happen only if someone remembers to start it. If that person leaves your organization, the process can stop until someone else notices the gap.

You can schedule any workflow to start on a repeating schedule in the time zone that you choose, or when an external system sends a trigger. Orchestrate logs every missed start, retries it automatically, and records each execution in an audit trail, so your finance, compliance, and operations teams can confirm that each workflow starts on time.

Onboarding, offboarding, re-engagement, incident response, compliance reviews, and contract expiration reminders can follow similar steps from one organization to the next. If you design each of those workflows from a blank page, you will have to work out and test every step yourself.

Orchestrate includes templates for new customer onboarding, employee offboarding, re-engagement campaigns, compliance reviews, and contract expiration reminders. Start from the template closest to your process, change the steps that differ, and launch the workflow.

Why teams build their processes in Orchestrate

Every product in one workflow definition

A single workflow definition can include steps in People, Channels, OneCloud, Teams, and any other Delalify product, so your team maintains one definition for a process that involves several products.

A person approves every sensitive step

Orchestrate pauses at every step that you mark for approval and shows the approver the proposed action with its context. The routine steps complete automatically, while the approver decides on each step that needs judgment.

Workflows finish after a failure

When a crash, an outage, or a deployment interrupts a workflow, Orchestrate continues it from the last saved step once the system is back.

Start from a template for common processes

Orchestrate's templates for onboarding, offboarding, re-engagement, and compliance include the usual steps of each process, so your team edits only the steps that differ for your organization.

How organizations use Beryl Orchestrate

A university sets up each newly admitted student with one workflow

When a student accepts admission, Orchestrate creates their profile in People, sends the welcome and housing information through Channels, creates their document folder in OneCloud, assigns an advisor in Teams, adds the enrollment record in Tables, issues the tuition invoice in Wallet, and schedules the orientation meeting. Orchestrate pauses before it sends the financial aid summary, until the admissions director approves it.

Result

Every admitted student receives the same setup, whether the incoming class has 50 students or 5,000, because Orchestrate performs each step for every acceptance. The admissions team reviews the financial aid summaries and spends the rest of its time on the conversations that need a person.

A university sets up each newly admitted student with one workflow

Every quarter the compliance team rebuilds the same review packet

Each quarter, a financial firm's compliance team lists its high-value transactions, checks each customer's profile against watchlists, collects the supporting documents from OneCloud, and produces a signed review packet for the regulator. Orchestrate performs the listing, checking, and collecting steps, while the compliance officer approves each review before Orchestrate files the packet with its audit trail.

Result

The compliance team spends each quarterly review on approving the packets that Orchestrate assembles. Each packet includes an audit trail with timestamps, approvers, and source citations, so the regulator can check how the firm prepares every quarterly review.

Every quarter the compliance team rebuilds the same review packet

When a clinic discharges a patient, one workflow schedules every follow-up

When the clinic discharges a patient, Orchestrate updates the patient's profile, sends the discharge summary to the referring physician through Channels, uploads the care plan to OneCloud with the right access controls, schedules a follow-up call for 14 days later, and notifies the care team in Teams. Orchestrate holds the discharge summary until the attending physician approves it.

Result

The attending physician reviews and approves the discharge summary, while Orchestrate completes the rest of the paperwork. Every discharged patient has a follow-up call on the care team's calendar, because Orchestrate schedules the call as part of the discharge.

When a clinic discharges a patient, one workflow schedules every follow-up

A brokerage launches each new listing with one workflow

When an agent adds a new listing to the brokerage's database, Orchestrate creates the property contact in People, uploads the photos and floor plans to a new OneCloud folder that the listing team can open, matches the listing against the active buyer groups, drafts a personal message for each matching buyer, and schedules the messages in Channels. Orchestrate sends the messages once the listing agent approves the final buyer list.

Result

The listing agent reviews the buyer list for each launch, while Orchestrate prepares the folder, the contact, and the messages. Each matching buyer receives a message about the listing as soon as the agent approves the list.

A brokerage launches each new listing with one workflow

Build each process once across every Delalify product

Beryl Orchestrate performs every step of a workflow that you define across your Delalify products and pauses for approval at the steps that you mark.