AIUNIFY CRM provides operational tools around an existing Contract for customer review, signing, comments, attachments, renewal, copying, email, and PDF output.
The exact actions available depend on Contract permissions and the Contract's current state.
The Contract preview includes a public Contract link used for the supported customer-facing Contract experience.
Review the Contract content before directing the Customer to that experience.
The customer-facing Contract workflow includes identity confirmation associated with Contract signing.
Once a Contract has been signed, its signature and acceptance information form part of the Contract history.
Treat signed information as significant agreement data rather than ordinary editable text.
When a Contract has not already been signed or marked as signed and your user account has edit permission, the CRM can provide a Mark as Signed action.
Use it only when your organization's actual Contract process justifies recording the agreement as signed outside the normal customer-signature workflow.
When the Contract was manually marked as signed rather than signed through the customer-signature workflow, an authorized user can be presented with an Unmark action.
Correct signing status only when the recorded status is genuinely wrong.
The Contract workflow supports comments associated with the agreement.
Comments can be used to maintain conversation or clarification around the Contract where the workflow permits it.
A staff user can remove their own Contract comment through the supported comment action. Keep useful Contract discussion intact when it forms part of the agreement history.
Where Contract attachments are available, attach files that belong to the agreement or its supporting documentation.
Before sharing or sending the Contract, review attachments for the correct Customer and Contract.
The Contract preview includes a send-to-Customer email workflow.
AIUNIFY CRM provides Contract PDF actions that can include:
Review the PDF before using it as an external representation of the agreement.
Users with Contract edit permission can use the supported Contract Renewal workflow.
The renewal form can request:
When the existing Contract is signed, the renewal workflow can also present an option to keep the signature.
Users with Contract creation permission can directly copy an existing Contract.
The copy becomes a new Contract rather than an extension of the original Contract.
The CRM deliberately resets signing and acceptance information on the copied Contract. A copied agreement must therefore be reviewed and processed as its own Contract.
After copying:
| Renewal | Use when extending or renewing the existing Contract through the supported renewal history. |
| Copy | Use when creating a separate new Contract based on the structure of an existing one. |