Brilliance One Automations

Define the process. Let Brilliance handle the repetition.

Build repeatable workflows that respond to business activity, send email and SMS, apply tags, notify teams, wait between steps, and move through clearly defined sequences.

Brilliance One Automations is designed around understandable workflow logic that can support customer communication and operational processes without turning every automation into an unnecessarily complicated diagram.

Explore Automations View Workflow Actions
Triggers • Email • SMS • Delays • Notifications
Brilliance One business workflow automation

Automation Without Administration

Automate the repeatable work. Keep the process understandable.

Brilliance One focuses on practical sequences that define how a workflow begins, what should happen next, when the system should wait, and where the process should end.

Start

Respond to Business Activity

Begin supported workflows from configured business events, record activity, forms, status changes, milestones, or manual enrollment.

Sequence

Define What Happens Next

Arrange communication, delays, tags, notifications, and other supported actions in the order required by the workflow.

Execute

Let the System Repeat It

Once the process is configured and active, Brilliance can handle the repeatable sequence while teams retain responsibility for the workflow itself.

Why Automate

People should handle judgment. Software can handle repetition.

Many business processes do not require a person to manually perform every step every time. When the trigger, action, timing, and outcome are predictable, automation can reduce repetitive administration.

  • Routine follow-up
  • Customer notifications
  • Internal notifications
  • Scheduled communication
  • Record tagging
  • Workflow delays
  • Lead and customer sequences
  • Operational reminders
  • Repeatable business processes
  • Defined stopping points

Automation Philosophy

The goal is not to automate everything.

Good automation removes unnecessary repetition while preserving the decisions and accountability that still belong with people.

If a process cannot be clearly explained, it may not be ready to automate.

Workflow Model

Trigger. Sequence. Action.

Brilliance One workflows follow an understandable model: something starts the process, configured steps run in order, and the workflow eventually reaches its intended end.

1

Start the Workflow

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

2

Run the Sequence

Execute configured email, SMS, tagging, notification, delay, or other supported actions in their defined order.

3

Reach the End

Continue through the remaining steps until the configured sequence reaches its conclusion or stopping point.

Workflow Triggers

Start the process because something happened.

Automation becomes more useful when business activity can consistently initiate the next appropriate communication or operational process.

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

Trigger Logic

A clear event should lead to a clear next step.

A submitted form might require a confirmation. A customer status change might require internal notification. A business milestone may require follow-up.

The trigger establishes why the workflow started so the steps that follow remain tied to a real business event.

Workflow Actions

Build the sequence from clear actions.

Automations are assembled from individual steps that define exactly what should happen and when.

Communicate

Email

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

Communicate

SMS

Send supported text messages at defined points in the workflow.

Timing

Delay

Wait for the configured period before continuing to the next step in the sequence.

Organize

Tag

Apply supported tags or classifications to help organize records and provide context for downstream business processes.

Alert

Notify

Notify an appropriate user or team when the workflow reaches an important point requiring awareness or action.

Complete

End

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

Automated Communication

Follow up consistently. Without manually sending every message.

Email and SMS steps can be combined with timing, tagging, notifications, and workflow context to support structured customer and internal communication.

  • Welcome sequences
  • Lead follow-up
  • Customer communication
  • Appointment-related messaging
  • Internal notifications
  • Operational reminders
  • Post-event follow-up
  • Status communication

Consistency

The customer should not depend on someone remembering the next step.

When a business process requires the same communication repeatedly, automation can help ensure that step occurs consistently.

Teams remain responsible for deciding what should be sent, when it should be sent, and which customers or workflows should receive it.

Personalization

Automate the message. Keep the business context.

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

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

Contextual Communication

Automated should not have to mean generic.

Dynamic values can allow a reusable message to reflect the customer, organization, workflow, or business event behind the communication.

The workflow remains repeatable while the message can still use appropriate record context.

Beyond Marketing Automation

Automate customer communication. Then connect the operational workflow.

Marketing and lead nurturing are important automation use cases, but Brilliance One is designed as a broader business operating system. As supported modules participate in automation, workflows can increasingly reflect activity beyond the sales funnel.

CRM

Lead & Customer Follow-Up

Respond to supported account, lead, customer, form, status, and relationship activity with appropriate follow-up.

Accounting

Financial Follow-Up

Use supported financial events for communication, notifications, reminders, or related operational follow-up where configured.

Projects

Project Activity

Connect supported project, task, milestone, or delivery activity with notifications and workflow processes.

Scheduling

Appointment Workflows

Use supported scheduling activity for reminders, notifications, follow-up, and other configured workflow actions.

CMS & Forms

Digital Entry Points

Use supported forms and public interactions as entry points into customer or operational workflows.

Communications

Email & SMS

Coordinate supported email and SMS communication with the broader workflow rather than treating messaging as a disconnected activity.

Connected Automation

Automation becomes more valuable as the platform becomes more connected.

A workflow is only as useful as the data and business context it can understand. Brilliance One's broader CRM + ERP + CMS architecture creates opportunities for automation to participate in more of the business as supported capabilities expand.

Accounts

Relationship Context

Use customer, lead, contact, account, classification, and relationship information inside supported workflows.

Communications

Message Delivery

Use email, SMS, templates, content variables, and communication history in automated processes where supported.

Accounting

Financial Context

Connect supported invoice, payment, balance, or financial activity with appropriate follow-up and notifications.

Projects

Operational Context

Use supported project and task activity as part of repeatable operational workflows.

Scheduling

Time-Based Context

Connect supported appointments and scheduling activity with customer and internal workflow processes.

CMS

Digital Context

Connect supported forms and digital interactions with downstream communication and operational workflows.

Workflow Clarity

Powerful does not have to mean difficult to understand.

Visual workflow builders can become increasingly complex as processes branch, loop, wait, reconnect, and accumulate actions. Brilliance One emphasizes clear sequences that teams can understand and maintain.

  • Clear starting point
  • Ordered workflow steps
  • Defined delays
  • Understandable actions
  • Visible workflow status
  • Defined stopping points
  • Execution history
  • Maintainable business logic

Maintainability

Someone should be able to explain what the automation does.

Workflow complexity is not automatically a feature.

The more critical an automated process becomes, the more important it is for the organization to understand why it starts, what actions it performs, and when it stops.

Execution Visibility

Know what ran. Understand what happened.

Automation and communication activity can provide operational history that helps teams understand what workflows executed and which supported actions occurred.

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.

Workflow History

Maintain context around how records participated in configured automation processes.

Execution Review

Investigate workflow behavior when timing, content, or process execution does not produce the expected result.

Operational Context

Connect available automation history with the underlying customer or business activity where supported.

Audit Visibility

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

Communication Governance

Automation does not remove communication responsibility.

Automated messaging still requires appropriate audience selection, content, consent, suppression handling, communication policies, and business judgment.

  • Consent-aware processes
  • Opt-in management
  • Unsubscribe handling
  • Suppression controls
  • Appropriate message content
  • Relevant audience selection
  • Communication policy enforcement
  • Workflow ownership

Responsible Automation

Being able to send a message does not mean it should be sent.

Organizations remain responsible for how automated communications are configured and for applying their legal, regulatory, customer, and business requirements.

Automation should support good processes rather than bypass them.

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 information to make automated communication relevant to the recipient and process.

Visibility

Execution History

Review available workflow and communication history to understand what ran and where a process may require investigation.

Communication

Consent & Suppression

Use applicable opt-in, unsubscribe, suppression, and communication safeguards to support organization messaging policies.

Maintainability

Clear Sequence Design

Build workflows from understandable triggers and actions so teams can maintain the process without unnecessary complexity.

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, business rules, communication policies, configuration, and the decisions determining how automation is used.

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

Automation Without Administration

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

The purpose of automation is to remove repetitive administration without making the business lose control of the underlying process.

Teams should still be able to understand what the automation does, why it does it, and when human involvement is necessary.

Automation Strategy

Workflow builders are powerful. Business context makes them useful.

Modern CRM platforms can provide extensive workflow builders with large libraries of triggers, conditions, actions, templates, AI assistance, integrations, and branching logic. Brilliance One's opportunity is to connect automation with an increasingly broad CRM + ERP + CMS operating environment.

Start Simple

Clear Business Sequences

Use understandable triggers, ordered actions, delays, communications, notifications, and stopping points for repeatable processes.

Stay Connected

Use Shared Platform Context

Let supported automation draw from the same customer, communication, financial, project, scheduling, and operational foundation.

Expand

Grow With the Operating System

As additional Brilliance One modules and workflow actions become available, automation can expand without requiring the business to abandon its shared platform foundation.

Included in Brilliance One Core

Automation belongs in the platform foundation.

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

Brilliance One Core

One shared foundation. Used throughout the platform.

Core provides the relationship, communication, automation, identity, security, configuration, and administrative capabilities that support the broader Brilliance One Business Operating System.

CRM & Relationships

Accounts

Manage customers, prospects, leads, organizations, contacts, vendors, suppliers, partners, and relationship history through one connected business record.

Explore Accounts

Locations

Addresses

Maintain billing, shipping, service, customer, employee, vendor, job-site, and operational locations as reusable records connected to the business activity that depends on them.

Explore Addresses

Email, SMS & Messaging

Communications

Connect email, SMS, MMS, campaigns, templates, lists, replies, delivery activity, and communication history with the customers and business records behind every conversation.

Explore Communications

Workflow Automation

Automations

Automate supported email, SMS, tagging, notifications, delays, follow-up, and repeatable processes so people can focus on decisions while software handles routine work.

Explore Automations

Identity & Access

Users

Manage identities, roles, permissions, security groups, profiles, account relationships, module access, authentication, and operational responsibilities across Brilliance One.

Explore Users

Platform Protection

Security

Protect business information with authentication, authorization, roles, permissions, security groups, encryption, session controls, logging, monitoring, and administrative safeguards.

Explore Security

Platform Configuration

Settings

Configure organization defaults, branding, permissions, communication providers, payment services, AI preferences, integrations, module behavior, and shared platform settings.

Explore Settings

Data Operations

Tools

Import, export, map, validate, review, migrate, clean, and maintain supported business information with administrative workflows designed for controlled data operations.

Explore Tools

Core Platform

Automation starts with Brilliance One Core.

Automation participates in the Brilliance One Core foundation rather than operating as a separate per-user workflow product. Add additional modules as your organization needs more operational context and capability.

  • Automation included with Core
  • No per-user platform pricing
  • Email and SMS workflow actions
  • Tags, notifications, delays, and end steps
  • Connected business context
  • Founders 400 alternative available

Build Your Platform

Automate the customer side. Expand into operations.

Use the Brilliance One pricing estimator to start with Core, add the business modules your organization needs, and estimate applicable communication and other usage separately.

Build Your Estimate Explore Founders 400

Brilliance One Automations

Define the process. Let Brilliance handle the repetition.

Build understandable workflows that respond to business activity, coordinate email and SMS, apply tags, notify teams, wait between steps, maintain execution history, and increasingly connect customer and operational processes across the Brilliance One platform.

Build Your Estimate Discuss Automations

Brilliance One • Automations • Workflows • Automation Without Administration