An estimate sent is not an estimate accepted.
Keep the stages clear. A customer can read the proposal without choosing an option, sign without paying, or pay a deposit while materials are still pending. Review the actual state of each step before promising the next one.
What this looks like in practice.
Send a clear proposal
Review the line items, options, and contract language in the customer-facing view. Explain the next action when sharing the portal link. Answer scope questions before relying on a signature as evidence that both sides mean the same work.
Check approval and deposit
Review the selected option, signature, and payment history. If the customer changes the scope, revisit the proposal and amount due. Keep the record consistent before the office hands the job to scheduling.
Follow through after completion
At closeout, check the remaining balance and any unresolved work. Use the job’s payment history to support a clear conversation with the customer. Reconcile exceptions and processor activity through the established office routine.
Example: a customer approves after office hours.
The customer can use the portal link to review the proposal and take the configured next steps. When the office returns, it checks the job’s selection, signature, and payment before confirming the installation. This illustrates the workflow; payment success and processing timing still depend on the processor.
Keep the handoff clear
- Clear proposal and next action
- Approval and deposit reviewed separately
- Remaining balance checked at closeout
Before you get started.
Does sharing a link collect money automatically?
No. The customer must complete the applicable payment steps, and the processor must successfully handle the transaction. Check the actual payment status.
What if the customer pays by check?
The product supports recording checks with a photo. Follow your office’s deposit and reconciliation process so the job record matches the payment received.