Approve or decline lines
Customers can approve, decline, or decide later on recommended work without confusing the invoice.
Customer approvals
Customers get a clean portal. Shops get signed decisions, approval totals, proof records, invoice visibility, card consent, and declined-work follow-up paths.
Approval flow
Customers can approve, decline, or decide later on recommended work without confusing the invoice.
Approval records store customer decisions, signature, consent, timestamp, and privacy-safe audit metadata.
Customer-facing invoice pages include shop branding, totals, payment context, and print/save paths.
Collect authorization for processor-vaulted card setup without storing raw card data in TorqueLedger.
Turn declined estimate lines into follow-ups instead of letting future work disappear.
Queued, sent, failed, retried, and manually handled customer communications stay visible for staff.
Start approvals
Reserve a package and we will map approvals, invoices, messaging, and payment setup.
Approval integrity
A customer approval is most useful when each decision stays tied to the exact labour or part line the customer reviewed. TorqueLedger records approved, declined, and pending choices with typed-signature consent, timestamps, totals, and an audit trail. Duplicate submissions are rejected so a refresh or repeated tap does not create conflicting decisions.
Approval links are scoped to the repair order, validated against the customer contact and invoice code, and protected with rate limits. The customer portal shows only the shared job context rather than the shop workspace.
Approved work can move toward invoice closeout while declined work remains visible for responsible service-history and follow-up. Shops still need to configure their own wording and operating process for applicable consumer, authorization, messaging, and payment requirements.