Brilliance One Accounts

Every relationship. One connected record.

Brilliance One Accounts provides the relationship foundation for customers, leads, vendors, suppliers, partners, organizations, and the people your business works with every day.

Bring communication, activity, tasks, documents, financial history, projects, marketing, service, scheduling, automation, and other operational context together around the same account instead of spreading that information across disconnected systems.

Explore Accounts View Account Capabilities
Customers • Leads • Vendors • Partners
Brilliance One account and relationship management

Relationship Foundation

One place to understand who your business works with.

Accounts centralizes organizations, people, prospects, customers, vendors, partners, suppliers, and other business relationships so connected workflows can operate from shared context.

Master Records

Organizations & People

Maintain organizations, contacts, leads, customers, vendors, suppliers, partners, and other relationship types within one broader account structure.

Access

Relevant Data for the Right Users

Roles, permissions, and enabled modules can help determine which account information and operational capabilities are appropriate for different users.

Context

The Relationship History Around the Record

Communications, tasks, invoices, documents, notes, activities, projects, and other supported workflows can remain connected to the relationship behind them.

Shared Business Context

Stop rebuilding the same customer everywhere.

In disconnected software stacks, the same customer may exist separately in CRM, accounting, project management, marketing, support, scheduling, and billing systems. Brilliance One is designed so multiple workflows can reference the same relationship foundation.

  • Organization information
  • Contacts and people
  • Addresses
  • Email addresses
  • Phone numbers
  • Relationship classifications
  • Custom attributes
  • Communication history
  • Activity history
  • Connected module context

One Relationship Record

Customer data should become more useful as the platform grows.

When additional modules are enabled, the account record can gain more operational context instead of requiring the organization to recreate the same customer or company in another application.

Relationship Types

More than customers and leads.

Businesses interact with many kinds of organizations and people. Accounts is designed to support the broader relationship network behind daily operations.

Leads & Prospects Track potential customers and the relationship activity leading toward future business.
Customers Maintain customer information, history, communication, and connected operational activity.
Vendors Manage organizations that provide products, services, or other resources to the business.
Suppliers Maintain supplier relationships alongside relevant purchasing, product, or operational context where configured.
Partners Track strategic, referral, implementation, marketing, or other business relationships.
Organizations Represent companies, nonprofits, agencies, associations, departments, households, or other organizational entities where appropriate.

Relationship Lifecycle

Follow the relationship as it changes.

1

Create the Relationship

Add a lead, organization, contact, vendor, supplier, partner, or other relationship and capture the information relevant to that record.

2

Build the History

Connect communication, notes, activities, tasks, opportunities, documents, financial records, projects, and other supported workflows over time.

3

Grow the Relationship

Use the accumulated business context to support service, retention, sales, marketing, operations, reporting, and future opportunities.

People & Organizations

Understand both the company and the people inside it.

Business relationships often involve multiple people with different responsibilities. Accounts can maintain the organization while connected people provide the individual context needed for communication and operations.

  • Primary contacts
  • Multiple contacts per organization
  • Titles and roles
  • Email addresses
  • Phone numbers
  • Addresses
  • Relationship notes
  • Communication preferences
  • Operational relationships
  • Contact history

Relationship Structure

A company is not a contact. A contact is not the company.

Separating the organization from the people associated with it helps maintain clearer relationships when employees change, multiple contacts participate, or different roles interact with different parts of the business.

Connected Communication

Conversations should remain connected to the relationship.

Communication becomes more useful when users can understand who the message involved, why it was sent, what happened previously, and which business workflow the conversation supports.

Email

Connect supported email activity with the account or contact behind the conversation.

SMS & Messaging

Keep supported text and messaging activity connected to customer and contact history.

Notes

Maintain internal context that helps teams understand the relationship beyond formal communication.

Tasks

Connect follow-up activity and internal work to the account requiring attention.

Automations

Use account context in supported automated communication and workflow processes.

Activity History

Preserve a broader operational timeline so users can understand what has happened across the relationship.

Module-Aware Accounts

The account becomes richer as the platform expands.

When additional Brilliance One modules are enabled, related information can become part of the broader account experience rather than existing in an unrelated application.

Accounting

Quotes, Invoices & Payments

Connect appropriate customer financial activity with the account and relationship history.

Projects

Work & Delivery

See supported projects, tasks, milestones, and delivery activity associated with the account.

Scheduling

Appointments & Activity

Connect scheduled activity and appointments with the customer or organization behind them where configured.

Marketing

Campaign & Engagement Context

Use account classifications and relationship context in supported marketing and engagement workflows.

Documents

Files & Records

Associate relevant documents and files with the account or business relationship where appropriate.

Service

Support & Operational History

Connect supported service, support, request, or operational activity with the broader customer history.

Business-Specific Data

Your relationships do not all look the same.

Custom attributes, classifications, tags, and business-specific information can help Accounts reflect the way an organization actually manages relationships instead of forcing every business into one rigid record structure.

  • Custom fields
  • Account classifications
  • Relationship types
  • Tags
  • Business-specific attributes
  • Industry information
  • Priority
  • Service categories
  • Opportunity context
  • Operational metadata

Flexible Structure

Adapt the record to the relationship.

Different industries and organizations may need different information about customers, members, donors, vendors, residents, patients, partners, clients, or other relationships. Flexible account data can support those differences.

Organization & Segmentation

Find the relationships that matter right now.

Tags, classifications, filters, attributes, and relationship information can help teams organize large account lists and identify records relevant to a specific business objective.

Relationship Type

Separate customers, leads, vendors, suppliers, partners, and other relationship categories.

Industry

Organize accounts according to industry, market, business type, or other relevant classifications.

Priority

Identify important, strategic, urgent, high-value, or otherwise prioritized relationships.

Services

Group relationships according to the products, services, programs, or operational areas associated with them.

Lifecycle

Organize relationships according to lead, prospect, customer, inactive, partner, or other configured lifecycle states.

Custom Logic

Use business-specific attributes and classifications when standard categories are not enough.

Relationship Security

Not every user needs every piece of data.

Account records can contain financial, personal, contractual, communication, operational, or otherwise sensitive information. Brilliance One uses the broader platform security model to help organizations control appropriate access.

  • User authentication
  • Role-based permissions
  • Security groups
  • Module-based access
  • Administrative controls
  • Customer data separation
  • Audit-oriented activity
  • Operational history
  • Privacy-related controls
  • Organization-defined access policies

Appropriate Visibility

Show users what they need to do their job.

The broader goal is not to expose every available field to every employee. Permissions and module access can help keep the account experience relevant to the user’s responsibilities.

Account Architecture

Flexible enough for the business. Structured enough to stay useful.

Connected

Module-Aware Relationships

Accounting, communication, automation, documents, projects, scheduling, service, and other supported modules can connect back to the account record.

Flexible

Custom Business Attributes

Use custom fields, classifications, tags, and relationship data to model information specific to your organization.

Organized

Tagging & Segmentation

Group and filter accounts by relationship type, stage, priority, industry, service category, tags, or custom business criteria.

Scalable

Built for Growing Relationship Data

Support expanding account lists, additional users, growing history, new relationship types, and more connected workflows as the organization grows.

Brilliance One Core

Accounts are part of the Core foundation.

Brilliance One Core provides the shared users, security, settings, communications, automation, permissions, and platform infrastructure that allow account relationships to connect with broader business workflows.

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

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

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

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

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

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

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

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

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 Accounts

Know the relationship. See the business around it.

Centralize customers, leads, vendors, suppliers, partners, organizations, contacts, communication, financial activity, documents, projects, tasks, and operational history around the relationships that drive your business.

Build an Estimate Discuss Brilliance One

Brilliance One • Accounts • CRM • Connected Relationships