One customer record across CRM, Tracker, and Invoice

A customer should not need a different identity in every app. In a Klaq workspace, CRM contacts and companies provide the shared customer directory used by Tracker projects and Invoice documents.

The short version

Search for the existing customer, update the shared identity when needed, and select that customer in the relevant project or billing workflow. Issued invoices keep their original snapshots even when the working customer record changes.

Search before creating another record

Look for the person or company in the shared directory. Compare the actual contact details rather than assuming a similar name proves it is the same customer.

Choose the record type carefully. A contact represents a person; a company represents a business. The record type cannot be casually switched after creation, so start with the identity you intend to manage.

Klaq checks active email duplicates within the same type when new customer data is written. That does not mean it automatically merges every similar name or matching email across imported histories.

Reuse identity, keep each app's work distinct

Link the customer to the Tracker project for the engagement. Select the same shared customer when preparing an estimate or invoice.

The shared directory avoids maintaining a separate editable billing copy of the same customer. It does not automatically turn a CRM deal into a project or generate an invoice when project work ends.

Use each app's workflow for the job it performs while keeping the customer relationship consistent.

Understand the customer views

The Customers pages can show the broader directory or customers used in the selected app. That filter helps you answer whether you are looking at everyone or at the customers connected to a particular part of the work.

App-specific metrics remain subject to permissions. A shared customer identity does not grant every member access to all project or financial detail.

Preserve history when details change

Update contact or billing information for future work. Issued invoices and estimates retain the customer details and PDF stored at finalization.

Archiving a customer applies across the apps in the workspace. It keeps historical documents, projects, and time rather than erasing the engagement. Check the active work before archiving a shared customer merely to tidy one app's list.

Common questions

Does editing a customer fix a previously issued PDF?

No. The issued document remains a historical snapshot.

Does a shared directory combine customers across every workspace I belong to?

No. Customer identity and permissions are scoped to the selected workspace.

Use the client onboarding checklist to connect the customer with delivery and billing deliberately.