Brilliance One Automations

Trigger the work. Keep the business moving.

Build event-driven workflows that send communications, apply actions, notify teams, and move records through repeatable business processes.

Brilliance One Automations uses clear, rule-based sequences designed to be easier to build, review, maintain, and understand as customer and operational workflows grow.

Explore Automations View Automation Controls

Triggers • Email • SMS • Workflow Actions

Brilliance One automation workflow management

Rule-Based Automation

Automation without the visual clutter.

Brilliance One focuses on practical sequences that define when a workflow begins, what steps occur, how long the process waits, and what actions should happen next.

Triggers

Start From Real Business Activity

Begin supported workflows from customer actions, milestones, form submissions, status changes, operational events, or other configured triggers.

Communications

Email & SMS Sequences

Coordinate email and SMS steps within the same workflow so communication can follow the timing and business rules defined for the sequence.

Operations

Actions Beyond Messaging

Apply supported actions such as tags, notifications, record updates, and other workflow steps as the automation progresses.

Workflow Model

Trigger. Sequence. Action.

Start the Workflow

A supported event, rule, status change, form submission, or manual action begins the automation.

Run the Sequence

Execute configured email, SMS, notification, tagging, delay, or other supported steps in the defined order.

Continue or End

Move through the remaining workflow steps or stop when the automation reaches its configured endpoint.

Event-Driven Workflows

Automations should begin because something happened.

Instead of relying only on manual follow-up, supported business events can start the next sequence of communication or operational actions.

New customer or lead activity
Form submissions
Status changes
Customer milestones
Workflow completion
Operational events
Manual enrollment
Module-specific triggers where supported

Trigger Logic

Start the right workflow from the right event.

The goal is not to automate everything. It is to automate repeatable processes where a clear business event should consistently lead to a defined next action.

Sequence Steps

Build workflows from understandable actions.

Each automation can be built from individual steps that define what should happen next and when it should occur.

Email

Send configured email content as part of a customer, internal, or operational sequence.

SMS

Send supported text messages at defined points in the workflow.

Delay

Wait for a configured period before the next workflow step executes.

Tag

Apply supported tags or classifications to help organize records and downstream workflows.

Notify

Notify the appropriate user or team when a workflow reaches an important operational point.

End

Stop the sequence intentionally when the workflow has reached its configured conclusion.

Personalization

Use business context inside the message.

Where supported, automation content can use customer and account data to make messages more relevant to the recipient and the workflow that triggered the communication.

Customer information
Account information
Contact details
Workflow context
Module-related data
Business-specific content variables
Configured message templates
Dynamic communication content

Contextual Communication

Automation should still feel relevant.

Dynamic values can help transform a generic sequence into communication that reflects the customer, account, workflow, or business event behind it.

Connected Automation

Automation becomes more useful when it understands the rest of the platform.

Brilliance One Automations can participate in broader CRM, communication, financial, project, content, scheduling, and operational workflows as supported capabilities are enabled.

Accounts

Customer & Lead Workflows

Use customer, lead, account, status, and relationship activity to support automated follow-up.

Communications

Email & SMS

Coordinate supported communication steps within broader automation sequences.

Accounting

Financial Follow-Up

Use supported invoice, payment, balance, or financial events in operational follow-up where configured.

Projects

Project Activity

Connect supported project, task, milestone, or delivery events with notifications and follow-up workflows.

CMS & Forms

Digital Actions

Use supported form submissions and public interactions as entry points into downstream workflows.

Scheduling

Appointment Workflows

Use supported scheduling events for reminders, notifications, follow-up, or other configured actions.

Performance Visibility

Know what ran. Understand what happened.

Automation and communication activity can provide operational visibility into sequence execution and supported engagement data.

Automation Logs

Review supported execution history to understand which workflows and steps were processed.

Communication Activity

Review supported email and SMS activity associated with automated sequences.

Engagement Data

Use available delivery, open, click, reply, or other provider-supported engagement information where configured.

Workflow History

Maintain context around how records moved through configured automation processes.

Operational Review

Identify workflows that require adjustment when timing, content, or process behavior is not producing the expected result.

Audit Visibility

Use available logs and operational history to help understand when supported actions occurred.

Execution Standards

Speed matters. Control matters too.

Automated communication and operational actions should remain understandable, maintainable, permission-aware, and subject to the same business rules that govern manual work.

Personalization

Dynamic Business Context

Use supported account and workflow data to make automated communications more relevant to each recipient.

Measurement

Engagement & Execution Data

Review supported workflow and communication data to understand what is working and what may need refinement.

Communication Controls

Consent & Suppression Workflows

Opt-in status, unsubscribe handling, suppression rules, and related communication safeguards can help organizations apply their messaging policies.

Maintainability

Clear Sequence Design

Build workflows from understandable triggers and steps instead of forcing teams to manage unnecessarily complicated visual logic maps.

Human Control

Automate the repetitive work. Keep people responsible for the process.

Automation should reduce repetitive effort without removing accountability. Teams remain responsible for workflow design, message content, consent, business rules, configuration, and the decisions that determine how automated actions are used.

Defined workflow ownership
Clear triggers
Reviewable sequence steps
Controlled activation
Communication governance
Operational logging
Defined stopping points
Human review when appropriate

Automation Without Administration

Build the workflow once. Let the system handle the repeatable steps.

The goal is to remove repetitive administration while keeping the underlying process understandable enough that a business can still explain what the automation does and why.

Brilliance One Core

Automation is part of the Core foundation.

Brilliance One Core provides the account data, users, permissions, communications, settings, security, and shared platform services that allow automation workflows to participate across the broader system.

Core Workspace

Workspace modules. The shared foundation of Brilliance One.

Manage the core relationship, communication, automation, security, administration, and user capabilities that support the rest of your Brilliance One workspace.

Accounts

Centralize customers, leads, vendors, partners, organizations, and contacts in one connected relationship record with communication history, activity, documents, tasks, financial context, and operational workflows.

Learn about Accounts

Automations

Build repeatable workflows that handle routine follow-up, trigger communications, apply actions, and move work forward based on defined business events and timing.

Learn about Automations

Addresses

Store and organize physical locations for customers, vendors, facilities, offices, service locations, and other business relationships so address data stays connected to the records and workflows that use it.

Learn about Addresses

Communications

Manage email, SMS, MMS, replies, templates, campaigns, delivery activity, and communication history while keeping conversations connected to the customers, contacts, and workflows behind them.

Learn about Communications

Security

Protect business and customer data with authentication, role-based permissions, security groups, controlled access, audit visibility, privacy-oriented controls, and security practices that extend across the Brilliance One platform.

Learn about Security

Settings

Configure organization-wide preferences, branding, defaults, system behavior, connected services, and other administrative options that shape how Brilliance One works across your business.

Learn about Settings

Tools

Access practical utilities for imports, exports, validation, data management, operational cleanup, and other administrative workflows that help teams maintain accurate information and work more efficiently.

Learn about Tools

Users

Manage user identities, roles, permissions, security access, and workspace responsibilities so each person can access the Brilliance One capabilities and information appropriate to their role.

Learn about Users

Brilliance One Automations

Define the process. Let Brilliance handle the repetition.

Build clear sequences that respond to business activity, coordinate email and SMS, apply workflow actions, connect modules, maintain execution history, and keep repeatable work moving without constant manual follow-up.

Build an Estimate Discuss Automations

Brilliance One • Automations • Workflows • Connected Operations