How-to guide

Use customer groups

Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.

Segment customers for reporting, pricing context and operational organisation.

Audience: AdministratorFeature: CustomerPermission-aware

Plain textJump to steps

Learn with Pixie CRM

Video walkthroughs for this guide

Follow real application screens at your own pace, with English captions and a matching written guide.

All video tutorials

1:33 English captions

Create and verify a customer group

Create a customer group in Pixie CRM with live clicks. Open the group creator from a customer profile, enter a clear name, save and verify that the group remains available after reopening.

Chapters & transcript Watch on YouTube

Explore 1 more tutorial for this workflow

1:23 English captions

Assign and verify a customer group

Assign an existing group to a customer in Pixie CRM. Select the group, save the customer profile and reopen it to verify the retained membership with live clicks.

Chapters & transcript Watch on YouTube

Recorded in a demonstration workspace; available options depend on your plan and permissions.
Visit the Pixie CRM YouTube channel

Where to goSetup → Customers → Customer Groups

Before you startThe screen or action may be hidden when your role lacks permission, the related module is inactive, or a required setting has not been configured. Ask an administrator to review access rather than using another person’s account.

What this guide helps you do

Segment customers for reporting, pricing context and operational organisation. Pixie CRM keeps the result connected to the relevant customer, staff member and operational history where the feature supports those relationships. That connection is important for search, reporting, client portal visibility and future automation.

Follow these steps

Go to Setup → Customers → Customer Groups using an administrator or appropriately permitted account.
Check the current value and understand which users, records or automated processes it affects.
Enter or select the new configuration values. Keep labels concise and use the approved business terminology.
Where credentials, email, webhooks or cron are involved, begin with a test or sandbox configuration.
Save the change and confirm that Pixie CRM reports success.
Test the affected workflow with a non-critical record and with a restricted user where permissions are relevant.
Document the operational change and use the available reset or rollback option if the result is not correct.

Settings to check

Company or individual nameCheck this value against the source record before saving. If the field is optional and no verified value is available, leave it blank rather than entering placeholder data.

Primary contactCheck this value against the source record before saving. If the field is optional and no verified value is available, leave it blank rather than entering placeholder data.

Billing and shipping addressCheck this value against the source record before saving. If the field is optional and no verified value is available, leave it blank rather than entering placeholder data.

Country, currency and languageCheck this value against the source record before saving. If the field is optional and no verified value is available, leave it blank rather than entering placeholder data.

Customer groupCheck this value against the source record before saving. If the field is optional and no verified value is available, leave it blank rather than entering placeholder data.

Assigned staff and portal settingsCheck this value against the source record before saving. If the field is optional and no verified value is available, leave it blank rather than entering placeholder data.

Checks before you finish

Search for duplicates first.
Use a shared business email only when appropriate.
Check contact permissions before sending portal access.
Check whether the result should be visible to a customer contact or only to staff.
Confirm the final status, activity entry, generated document or notification before leaving the record.

Permission and data safetyDeletion, refunds, signature clearing, module changes, payment configuration and privacy actions can affect linked records or legal history. Use the least destructive action available and follow your organisation’s approval process.

Browse connected topics:payment check report currency approval provider client portal reminders notifications email customers leads

Was this guide useful?Your response is stored only in this browser.