Agiled Docs

CRM settings control how sales and customer records are organized.

Configure CRM settings before importing a large spreadsheet, launching forms, or asking the team to follow a new sales process.

Pipelines

Configure deal pipelines and stages so they match your sales process. Keep stage names clear and avoid adding more stages than the team can maintain.

Use pipeline settings before importing deals or training the sales team. The pipeline and stage names become part of daily deal updates, reports, and saved views.

Write down the exit rule for each stage before adding it. If the team cannot explain when a deal should move out of a stage, the stage will become stale.

Review one active deal in each stage before changing pipeline structure. This helps you see whether the current stages describe real work or just old labels.

Avoid changing stage names during an active sales review. Make structure changes after the team agrees on definitions, then update open deals and reports together.

Attributes

Custom attributes let the workspace store extra structured data on supported entities.

Create attributes when contacts, accounts, deals, forms, or imports need fields that are not included by default.

Create attributes before building forms or imports so incoming data lands in the right fields from the start.

Use required attributes carefully. A required CRM field should be useful enough to justify blocking record creation, imports, or form submissions.

Attribute Planning

Create attributes only when the team will use the value for filtering, forms, reports, workflows, handoffs, or customer segmentation. Avoid adding fields that no one owns or reviews.

Setup Order

Configure pipelines.
Add or clean up pipeline stages.
Create required custom attributes.
Import or add CRM records.
Save views and filters for the team.

After setup, create one contact, account, deal, and ticket that follow the new process. This test set proves fields, stages, views, and workflows line up before imports or public forms create real records.

Before Changing Existing CRM Settings

Check whether the setting is used by forms, imports, saved views, workflows, reports, or team training. Renaming a stage or field can confuse active deals and reports if the team is not ready for the change.

For active workspaces, review open deals, public forms, active workflows, and saved views before renaming or removing stages and attributes. Make the change at a low-traffic time if sales or support teams work from those views daily.

After Changes

Create or update one test record and confirm the new pipeline, stage, or custom attribute appears where users expect it. Then update related forms, imports, saved views, and workflow conditions.

Tell the team what changed and which records need cleanup. Settings changes are only useful when the daily CRM process changes with them.

After a major settings change, review saved views and reports with the team so everyone uses the same definitions for pipeline, stage, status, and attributes.

Run one test import or form submission after CRM settings change. This confirms new fields and stages work before real customer data enters the system.

CRM Settings Checklist

Before launching a CRM change:

define each pipeline stage
review active deals in affected stages
create required attributes before imports and forms
update saved views and reports
test workflows and form submissions
tell the team how existing records should be cleaned up

CRM Settings

On this page