Task Guide: Create Your First Customer

Overview

This task guide walks a new user through creating the first customer record in OneSuite. A complete customer record is the starting point for calls, emails, SMS messages, tasks, deals, invoices, and service history.

Business Value and Typical Use Cases

Onboard a new customer.
Prepare for billing or sales follow-up.
Train new staff on CRM basics.

Before You Begin

Confirm you can log in to OneSuite and access the module described in this article.
Make sure your organization has completed any required setup, such as license activation, user permissions, payment settings, or connected email accounts.
Use production records or approved test records when learning a workflow so you do not accidentally change live customer information.

Prerequisites and Permissions

Active OneSuite installation or trial.
User account with the appropriate role or permission.
Current production release interface.
Stable browser session.

Concepts

CRM stands for customer relationship management. In OneSuite, CRM is the shared record of people, companies, opportunities, tasks, and customer history. The purpose is not only to store names. It helps the business remember who the customer is, what has happened, what needs to happen next, and which records connect to invoices, emails, calls, SMS messages, deals, and activities.

How This Feature Fits Into OneSuite

Getting Started establishes the foundation for every later workflow. License state, user permissions, company settings, and connected services determine which CRM, communications, payments, POS, workforce, and marketing functions appear for a user.

A successful first-day setup should end with a user who can sign in, reach the correct Workspace, open the modules required for the job, and create or locate a safe test record.

Screen Orientation

Begin from the OneSuite sign-in and Workspace experience. The first objective is not to memorize every module; it is to understand how the main navigation, profile controls, search, notifications, and module entry points are organized so later instructions are easier to follow.

When a guide refers to a module, look for the corresponding Workspace navigation item or the module launcher available to your role. If a module is not visible, treat that as a permissions or licensing question before assuming the feature is missing.

Use approved production records or a clearly identified test customer when learning. This keeps onboarding safe and makes it easier to distinguish training activity from live business activity.

Open the area described in this guide and pause before editing. Identify the page heading, primary action button, search/filter controls, record list or detail panel, status indicators, and any related-record or history areas. This quick orientation prevents users from applying instructions to the wrong record or module.
When the page contains both a list and a record/detail view, use the list for discovery and the detail view for action. Search or filter first, then open the exact record and verify identifying information before making changes.

Role-Specific Guidance

Business owners and administrators should complete setup and licensing topics first, then validate user access before inviting staff to work in the system.
Managers should learn Workspace navigation, CRM, communications, and reporting areas that they supervise before training employees.
End users should focus first on the tasks they perform every day and return to administrator documentation only when their job requires configuration access.

Step-by-Step Instructions

Open Workspace and go to CRM.
Select Contacts for an individual person or Companies for an organization.
Search first to confirm the customer does not already exist.
Select Add Contact or Add Company.
Enter the customer name and reliable communication details.
Save the record.
Open the saved customer and confirm the details.
Create a task or invoice if the next action is known.

Expected Results

When completed, the record, action, or workflow described in this guide should be visible in OneSuite, searchable from the appropriate module, and connected to the related customer, company, invoice, payment, communication, or activity history where applicable.

Verification Checklist

Confirm the correct OneSuite user is signed in and the expected role/permissions are active.
Confirm the customer, company, invoice, product, message, appointment, employee, or other record shown on screen is the one intended for the task.
After saving or completing the action, refresh or return to the relevant list and verify the new status, history entry, balance, message, appointment, or record appears where expected.

Business Workflow

Search → Create customer → Verify details → Add next action → Use customer history for future work.

Real-World Business Scenarios

New lead: search by name, email, or phone first; create the contact only when no appropriate record exists; then add the business information needed for follow-up.
Existing customer calls: open the existing record, review recent activity and related history, then create the next task, message, appointment, invoice, or note from the correct customer context.
Ecommerce customer: where WooCommerce context is available, use the existing commerce/customer relationship to understand online activity rather than creating an unnecessary duplicate CRM identity.

Advanced Operational Guidance

For repeatable business work, standardize naming, ownership, tags/statuses, and staff responsibilities before increasing volume. Consistency makes OneSuite search, reporting, history, and handoffs substantially more useful.
When multiple modules participate in the workflow, verify each handoff. Do not assume that completing one screen automatically proves the customer, payment, communication, or reporting outcome is correct elsewhere.
Use one authoritative customer identity whenever possible. Duplicate prevention is one of the most important habits for preserving useful CRM, billing, communication, and WooCommerce history.

Screenshots

Production screenshots appear here only after approved OneSuite captures are attached. Written instructions are complete without screenshots.

Best Practices

Collect accurate email and phone information.
Use companies for organizations.
Never skip the search step.

Common Mistakes

Creating duplicates.
Adding an invoice before the customer is correct.
Saving incomplete details when more information is available.

Troubleshooting

Symptom: the page or button is not visible. Cause: your role may not include access to this module or the current license may not include the feature. Solution: ask an administrator to review your role, workspace access, and license status. Verification: sign out, sign back in, and confirm the menu item appears.
Symptom: a saved record cannot be found. Cause: filters, search terms, ownership, or status views may hide records. Solution: clear filters, search by name, email, phone, invoice number, or company, and check active versus archived views. Verification: open the record and confirm the latest information appears.
Symptom: a workflow stops before completion. Cause: required fields, connected account setup, payment configuration, or missing customer details may be incomplete. Solution: review the required fields shown on the page and complete setup items before retrying. Verification: repeat the step and confirm the expected success message or updated status appears.

Frequently Asked Questions

Should I create contact or company first?: Create the record that matches the customer type.
Can I add more details later?: Yes, but enter core details now.

Next Steps

Continue with the Related Articles section to follow the workflow into the next OneSuite function instead of returning to the homepage after every task.

Last Updated: August 21, 2026
Version: 0.3.2-Phase2B-SHORTCODE-RENDER-RECOVERY
Verified Public Source Baseline: PASS35H66DN RC1 GOLD R63.97
Documentation Revision: Phase 2B Enterprise Detail Expansion