SkyCode Labs

Customers in FBM

Learn how customer records work in FBM, why the customer detail page is central to the workflow, and how customer information connects to projects, quotes, invoices, payments, notes, and follow-up.

FBM Help Center

Help Home Getting Started Customers Products Projects Quotes Invoices Payments Reports Portal Support Accounting AP

Customer Overview

The customer record is one of the most important operating anchors in FBM

In real usage, many workflows either start from the customer or become fully visible through the customer detail page. This is why customer organization, contact accuracy, notes, financial visibility, and related actions all matter at the customer level.

What to Learn Here

What the customer record is for
Why the customer detail page matters
How notes and follow-up visibility work
How customer activity connects to the rest of FBM

Core Responsibility

What the customer area is responsible for

Before using related modules, understand what the customer record represents inside the platform.

Identity

The record that represents the customer

The customer area stores the main business identity of the customer, including the contact person, communication details, and the base record that other workflows relate to.

Visibility

A central place for history and follow-up

Notes, reminders, financial visibility, statements, and related activity become easier to manage when the customer detail page is treated as a working center instead of a passive contact list.

Connection

A bridge to operational flow

Customers are not isolated records. They connect naturally to quotes, projects, invoices, payments, ledger visibility, statements, portal access, and other operational steps.

Practical Usage

How teams typically use the customer detail page

The customer detail page is useful because it brings multiple operational views into one place.

Common reasons teams open a customer record

Review the latest customer notes or reminders
Check related financial activity and payment status
Look at project and quote context before taking action
Prepare for follow-up, statement sending, or support communication

Why this matters operationally

When the customer page is complete and well maintained, users spend less time searching across disconnected screens. That reduces follow-up friction and makes the workflow easier to understand for both new and experienced team members.

Next Reading

Related areas you should review next

Customers make more sense when you continue into the next connected modules.

Products

Review Products next to understand what operational items and related structure the team works with after customer context is established.

Go to Products

Projects

Continue with Projects to see how real work moves forward after customer and job context are organized.

Go to Projects

Quotes

Then review Quotes to understand how customer-facing sales flow starts to become structured and trackable.

Go to Quotes