DEPOSIT-PAYMENT-CONFIRMATION-READY
1) Copy/paste deposit confirmation card
Paste this into your CRM, booking system, payment follow-up queue, or dispatcher handoff note.
- Lead / job ID: estimate, invoice, booking, or CRM record number.
- Customer and location: name, service address, best contact channel, and consent status for SMS/email follow-up.
- Approved scope: exact service, option/package, quote version, exclusions, and estimate expiration date.
- Deposit/payment status: requested, link sent, customer says paid, proof received, payment processor confirmed, partial, failed, refunded, or disputed.
- Source proof: payment processor record, receipt, invoice, bank/card confirmation, screenshot, signed approval, email thread, or office note.
- Amount and terms: deposit amount, balance due, payment method, refund/cancellation policy reference, and who approved any exception.
- Schedule handoff: target date/window, required parts/materials, crew skills, access notes, permits/HOA steps, and customer constraints.
- Owner / next action: scheduler, estimator, office manager, bookkeeper, crew lead, or owner responsible for the next step.
- Customer-safe next message: confirmation, missing-proof request, scheduling hold, or owner-review note.
2) STOP AUTOMATION rules
STOP AUTOMATION and require human review before marking the job ready when:
- the payment processor has not confirmed the deposit, or the only proof is an unverified screenshot;
- the amount does not match the estimate, the payment failed, there is a chargeback/dispute, or a refund/cancellation question is open;
- the scope, price, warranty, balance due, schedule, permit, HOA, parts, or access requirements are unclear;
- the customer is asking for a policy exception, discount, financing change, refund, or credit;
- private payment data, card details, bank details, or sensitive customer information appears in the notes; or
- AI drafted wording that promises start dates, free work, refund eligibility, diagnosis, parts availability, or final pricing not shown in the source proof.
3) Customer-safe text snippets
Deposit confirmed:
Hi [First Name] — we received the deposit for [approved service/scope]. [Scheduler/office name] will confirm the next schedule step: [date/window or next action]. Reply here if any access details changed.
Proof needed before scheduling:
Hi [First Name] — thanks. I do not yet see the deposit confirmed in our system. Please send the receipt or use [approved payment link/process]. Once confirmed, [team member] can move this to scheduling.
Human review needed:
Hi [First Name] — I’m sending this to [owner/office manager] because the deposit/scope details need a quick review before we confirm the job. We’ll follow up with the approved next step.4) AI handoff prompt
You are helping a local service business prepare a deposit/payment confirmation handoff.
Use only the source details provided. Do not mark payment received, promise a start date, approve a refund, change pricing, or invent policy.
Deposit confirmation card:
[PASTE CARD]
Source proof:
[PASTE PAYMENT PROCESSOR NOTE, RECEIPT, ESTIMATE, CRM NOTE, OR CUSTOMER MESSAGE]
Return:
1. Confirmed facts only.
2. Missing proof or mismatched fields.
3. The safest CRM status label.
4. The next human owner and due time.
5. One customer-safe message: confirmed, proof needed, scheduling hold, or human review.
6. Any STOP AUTOMATION triggers.
Do not invent payment status, approvals, refund policy, cancellation terms, schedule windows, parts availability, diagnosis, warranty coverage, or final balance.5) CRM labels to add
| Label | Use when |
|---|---|
| deposit-link-sent | The customer has the approved payment link but no confirmed payment yet. |
| deposit-proof-needed | The customer says they paid but the team lacks processor proof. |
| deposit-confirmed-scheduling | Payment is verified and scheduling is the next owner. |
| deposit-mismatch-owner-review | Amount, scope, policy, or customer request does not match approved terms. |
| do-not-schedule-payment-risk | Failed payment, dispute, chargeback, refund, or sensitive payment-data issue exists. |
6) Weekly review questions
- How many approved estimates are waiting on deposit proof?
- Which jobs are marked paid but still missing a scheduler/crew owner?
- Which deposit messages create confusion about refund policy, balance due, or schedule windows?
- Which payment exceptions need an owner-approved template instead of ad hoc texts?
- Where could the CRM show deposit proof and schedule owner in one view?
NEEDS OWNER REVIEW: This checklist is an operations aid, not accounting, legal, payment-processing, financing, tax, or refund-policy advice. A qualified business owner, bookkeeper, payment processor, accountant, or attorney should review sensitive or disputed payment issues.
For more copy/paste lead response templates, estimate follow-up scripts, and CRM handoff worksheets, use Local Lead Rescue System.