Documents and Forms

Documents and Forms Overview

Documents and Forms allow you to create, send, and manage structured paperwork directly within Tiquo. The implemented document associations are customers, companies, and enquiries.

Documents are typically used for agreements, contracts, and confirmations, while Forms are used to collect structured information from customers or internal teams.

Creating Documents & Forms

Documents can be created for:

• Customer pages
• Company pages
• Enquiries

When creating a document, you can define its content, recipients, and whether signatures are required. Documents automatically retain a full audit trail and version history.

Forms are used to capture structured data such as preferences, onboarding information, waivers, or questionnaires.

Forms can be:

• Sent to customers or staff
• Embedded into customer flows
• Linked to bookings, memberships, or enquiries

Submitted form data is stored directly on the related customer or entity, making it immediately usable across CRM, segmentation, and operations.

Each form can have its own confirmation heading and message. These are shown after a successful submission, so the wording can explain what happens next instead of using a generic success screen.

Using Fields and Signatures

Documents and Forms support dynamic fields that can be completed manually or automatically populated from existing data, such as:

• Customer details
• Company information
• Enquiry context

A document is sent to one recipient per send operation. The recipient can complete the document's signature field through the secure link. Multiple-recipient signing order is not currently part of the document model.

Form field options

Form fields can be marked as required and can use full or compact widths. For a long option list, use a searchable dropdown so the respondent can find a value without scanning the entire list. Checkbox fields can store a true or false answer and can be linked to a compatible customer field.

Fields can bind to customer data or to fields configured for an enquiry type. When the form is submitted, Tiquo writes the answer to that stable binding rather than relying on the field's position in the form. Compound customer parameters use a nested field path. Dropdown and multi-select bindings need compatible options on both sides.

File uploads

Add a file-upload field when a public form needs evidence or supporting material. A submitted file is stored with the related form submission and its customer, company, or enquiry context.

Accepted formats are PDF, DOCX, XLSX, PPTX, CSV, TXT, JPEG, PNG, GIF, WebP, ODT, ODS, and ODP, up to 25 MB per file. Tiquo validates the filename extension, declared content type, stored content type, and file contents before accepting the upload. Empty files, mismatched types, unsafe archives, and unsupported formats are rejected.

Address fields

Use the structured address mode when the individual parts of an address are needed elsewhere in Tiquo. Choose which parts to collect, including address line 1, address line 2, city, region or state, postal code, and country. A single address search field is also available when only the selected address is needed.

Terms and payment details

Terms fields record when the respondent accepted the statement. Keep the label specific enough that the stored acceptance still makes sense when staff review the submission later.

A standalone payment details block securely saves a payment method through Stripe. It does not collect raw card details in Tiquo and does not start a charge by itself. In a membership application, the saved method can be used after staff approve the application. If a charge needs customer authentication, Tiquo sends a secure payment step.

Creating Document Templates

Document templates allow you to standardise commonly used documents such as contracts, waivers, or agreements.

Templates can include:

• Predefined text and structure
• Dynamic fields
• Signature placeholders

Once created, templates can be reused across customers, companies, and locations, ensuring consistency while reducing manual work.

Sending a Document for Signature

Documents can be sent for signature directly from the platform.

When sending a document, you can:

• Choose one recipient
• Send that recipient a secure link
• Track when the document is sent, viewed, or signed

Recipients receive a secure link and do not need an account to sign.

Forms as Enquiry Entry Points

Forms are also used as customer-facing entry points for enquiries, including membership application flows. A submitted form can create or link a customer profile and land the submission in the matching enquiry pipeline for staff review.

Membership forms can also securely collect a payment method through Stripe so that, on approval, the membership can be assigned and billing can begin. If the saved payment method can be charged off-session, Tiquo charges it; if additional customer action is required, Tiquo sends the customer a secure payment step.

See Enquiries for the full form-to-approval flow.

Document and Form Status

Each document and form has a clear status, allowing teams to track progress at a glance.

Common statuses include:

• Draft
• Sent
• Viewed
• Signed

These are the stored document states. Completed, Cancelled, and Expired are not separate document statuses. Status updates can be shown with the related customer, company, or enquiry context where that association is available.