Product · Auto-generated contracts
Lawyer-shaped contracts.
On every booking.
No DocuSign redirect, no “send me a contract” email chain. The contract is built into the same page where your prospect picked the price — signed, hashed, and stored before they close the tab.
What gets signed
A real contract, not a checkbox.
BookNox renders a per-vertical service contract from a template you can edit. Defaults cover the clauses every service vendor needs — you tune the specifics once.
- Service scope
- Package, hours, deliverables, location, date and time. Pulled from the quote your prospect built.
- Payment terms
- Deposit amount, balance schedule, accepted methods, late-payment fee.
- Cancellation policy
- Refund windows, rescheduling rules, force-majeure (postponement vs. cancellation).
- Per-vertical add-ons
- Photo/video release for photographers. Rehearsal-dinner scope for planners. Setup window for venues. Whatever your vertical needs.
How signing works
From quote to signed PDF, one page.
- 01
Tokenized link
Each proposal gets a unique URL with an access code. Only the prospect who received it can open it.
- 02
Signature canvas
Your prospect draws their signature with finger or mouse, or types their full name in a script font. Either path captures the same legal weight under ESIGN-Act §7001.
- 03
PDF render + immutable storage
The signed contract renders to PDF server-side and lands in immutable Vercel Blob storage. The SHA-256 hash of the document is embedded in the PDF for tamper evidence.
- 04
Counter-sign + delivery
Your pre-saved signature counter-signs automatically. Both parties receive the signed PDF by email; you also see it in your BookNox dashboard.
Compliance
Built on the three legal pillars.
Electronic signatures bind under U.S. federal law (ESIGN-Act, 15 U.S.C. §7001) and state law (UETA, adopted in 49 states). BookNox implements every pillar.
- Intent to sign
- Explicit checkbox + signature canvas action. No ambiguous “click here to continue.”
- Consent to do business electronically
- Timestamped before any sign step. The consent record travels with the document.
- Association with the record
- Signature, timestamp, IP, user-agent, and document hash are bound to the PDF itself — not stored in a separate database row.
- Record retention
- Immutable Blob storage means the signed PDF can’t be silently modified after the fact.
Audit trail
Every signed contract leaves a paper trail.
If a dispute happens, you have everything a judge or mediator would ask for. Stored alongside the PDF in your BookNox dashboard.
- Client name + email at time of signing
- IP address of the signing device
- User-agent string (browser + OS)
- Consent-to-electronic timestamp
- Signature timestamp
- SHA-256 hash of the rendered PDF
- Token ID linking back to the original proposal
The contract is the booking.
Pair it with the payment so the signed PDF and the deposit land at the same moment.