25.1 Managing Existing Estimates

AIUNIFY CRM provides list and Pipeline workflows for managing Estimates after they are created.

The functions visible to you depend on your Estimate permissions and the state of the individual Estimate.

25.2 Switching Between List and Pipeline

The Estimate workspace supports switching between the standard list and the Estimate Pipeline.

Use the list when you need a table-oriented review. Use the Pipeline when a status-based visual representation is more useful.

25.3 Searching the Pipeline

The Estimate Pipeline contains search and sorting capabilities and can search using the Estimate information available to the pipeline, including tagged information where applicable.

Search before creating a new Estimate when you are uncertain whether the record already exists.

25.4 Estimate Status

Estimate status communicates the current lifecycle state of the Estimate.

Where your account has Estimate editing access, the CRM can provide status actions for moving the Estimate into another valid state.

Change status only when the real transaction state has changed.

25.5 Sending an Estimate by Email

Authorized users can send an Estimate to the Customer through the CRM's Estimate email workflow.

The send process can include:

  • The Estimate email message.
  • An option to attach the Estimate PDF.
  • A CC value.

Before sending, review the Customer, Estimate content, totals, and recipient information.

25.6 Estimate PDF

The CRM can generate a PDF for an Estimate that the user is permitted to view.

After generating the PDF, review the Customer identity, dates, items, totals, and terms before distributing it externally.

25.7 Copying an Estimate

Users with Estimate creation access can copy an existing Estimate.

The copy becomes a new Estimate, so review all inherited information before saving or sending it.

Pay particular attention to Customer, Project, dates, items, prices, discounts, and notes.

25.8 Customer Acceptance and Decline

An Estimate can progress through customer-facing acceptance or decline behavior when that workflow is available for the Estimate.

As an operational user, review the Estimate's displayed status and acceptance information to understand what has occurred.

Do not manually alter unrelated fields merely to imitate an accepted or declined state.

25.9 Acceptance Information Is Historical Transaction Data

Customer acceptance information and signatures, when present, form part of the transaction history.

This User Operations Manual does not instruct ordinary tenant users to clear or reset protected acceptance information. Use only the normal actions presented to your permitted account.

25.10 Estimate Actions After Acceptance

When an Estimate has progressed to the point where billing is appropriate, use the supported conversion workflow instead of manually recreating the transaction as a separate Invoice.

This preserves the relationship between the Estimate and the resulting Invoice.

25.11 Estimate Workflow Best Practices

  • Use Pipeline status to reflect reality.
  • Review the Estimate before emailing it.
  • Verify PDFs before external distribution.
  • Review all data after copying.
  • Treat acceptance information as transaction history.
  • Use the normal conversion workflow when moving from Estimate to Invoice.
  • Use only actions made available by your permissions.
Write Your Comment