Refunds & Notifications · Article 6.3

Email: "Signed — [proposal title]"

Fires the instant the client signs. Two recipients, two slightly different bodies — yours has the audit summary, your client's has the deposit invoice and a payment CTA.

Where this fits in the lifecycle

Tap any card to open its detail article.

The signature moment is the legal pivot — the offer becomes a contract. Both parties need a written confirmation immediately, and the client needs to be told exactly how to pay the deposit so momentum isn't lost. This single dispatch event handles both.

Step by step

Client signs.
A Timeline event "Signed at HH:MM by [client name]" is recorded with their IP and User-Agent.
PDFs render in parallel.
AGR (signed Service Agreement) and DEP (deposit invoice) generate concurrently — typical end-to-end is 5-8 seconds.
Both emails dispatch.
As soon as both PDFs are in R2, the freelancer-copy and client-copy tasks fire. You see "Signed and confirmed" on your dashboard.

Green Signed badge. Timeline gains three events: "Signed", "AGR generated", "DEP generated". Documents dropdown gains AGR-XXXX and DEP-XXXX. Inbox: one email from Clozo with the signed AGR attached. Action menu shows Mark deposit as paid manually, Resend deposit invoice, Issue final invoice (greyed until deposit lands).

Why this works this way

The freelancer copy is your archive — Subject line includes the proposal number for searchability ("Signed: PRO-2026-0042"), body has the client name, the timestamp in UTC, the signed amount, and a link back to the proposal in Clozo. The signed Service Agreement (AGR-2026-NNNN) is attached so you have an immediate offline copy.

The client copy is action-oriented — it leads with "Thank you for signing", attaches the same signed AGR plus the deposit invoice (DEP-2026-NNNN), and ends with the payment CTA. CTA logic ([D-088]): - If your account has stripe_charges_enabled = true, the CTA is a Pay €X by card button linking to app.useclozo.com/p/{slug}/pay?stage=deposit (the Clozo-hosted Stripe checkout). - If Stripe is not connected, the CTA is replaced by a SEPA payment block: your IBAN, BIC, beneficiary name, exact reference text (PRO-2026-NNNN-DEP), and an EPC QR code inline. - If both rails are available (Stripe enabled + IBAN on file), both options appear with Stripe at the top.

Troubleshooting

Keep reading

Lifecycle

Status: Signed — legally binding, audit trail captured

The client clicked Sign. Clozo collects an eIDAS-compliant evidence stack, generates the signed Service Agreement PDF, fires confirmation emails to both parties, and queues the deposit invoice. The proposal is now a contract.

Refunds & Notifications

Email: "Deposit received — receipt enclosed"

Dispatched the moment Clozo confirms the deposit landed (Stripe webhook or your manual mark-as-paid). Carries the deposit receipt PDF and confirms the project can begin.

Configuration

Stripe Connect: enabling card payments end to end

Five minutes through Stripe's onboarding turns on card payments for every future proposal — no extra config, no separate Stripe dashboard to manage, payouts land in your IBAN.