Customer forms
Collect the information needed for a request or service through configured forms. Keep required fields meaningful and avoid asking customers to provide information that the process does not need.
Forms and documentsDocuments inside the workflow
The document belongs to the work.
Not an employee's downloads folder.
Keep customer forms, order information, PDF documents and signature steps within the SABSUS business workflow. Use the customer and agreed work as the reference, rather than retyping the same details into unrelated files.
- 01 · Collect the informationUse the appropriate customer form and required fields.
- 02 · Prepare the documentWork from the relevant customer and order context.
- 03 · Review and completeCheck the content and required signature step.
- 04 · Keep the connectionRetain the document with the work it describes.
A consistent document starts with consistent business data.
When a customer changes a service or the scope of a job, an old attachment can become misleading. SABSUS connects document and form workflows to the business context so the team can identify the customer, order and purpose of the document instead of relying on a filename alone.
PDF templates
Build the document around the information your team needs to present. Check the resulting PDF with realistic names, long descriptions and several order lines before making it part of daily operations.
PDF document builderSignature steps
Use the configured electronic-signature workflow where a document requires customer acceptance. Define what is being agreed and who needs access to the completed record.
Electronic signaturesOperational handoff
Connect the document to the order and responsible team. A service employee should be able to find the agreed scope, while the office can review the corresponding customer and payment history.
Order managementExample: a service changes after the first request
The customer adds work before the appointment. The team reviews the updated order, prepares the appropriate document and completes any required acceptance step before starting. The original agreement should not be silently treated as approval of new work. This is an illustrative procedure, not a claim that every legal document can use the same signing method.
A generated document is not proof of payment, physical delivery or regulatory compliance. Signature requirements, invoice rules and retention obligations depend on the document and jurisdiction; verify them for the actual business process.
Document workflow questions
Does generating a PDF charge the customer?
No. Document generation and payment collection are different actions. Confirm payment through the configured payment workflow and provider result.
Can the documents reflect our brand?
Use the available template and document-design tools to present the business information consistently. Test the final layout and required fields with your actual content before rollout.
Should every employee have access to every document?
No. Define access around the employee's role and the information needed for the work. Customer records and attachments should not be exposed simply to make a link convenient.
Bring the document your team fills in repeatedly.
Review the source data, customer fields, layout, acceptance and handoff as one process.
Discuss connected documents