1. Confirm the work before creating the receipt
A receipt should reflect completed work. Check the service description, completion date, amount, taxes when applicable, payment status, and client contact details. Correct the source appointment first so every later view uses the same information.
2. Include useful receipt details
- Business name and contact information.
- Client name and the service provided.
- Transaction or receipt reference.
- Amount, currency, taxes, and payment status.
- Service and issue dates.
- A support contact for questions or corrections.
Receipt requirements differ by location and industry. Business owners remain responsible for tax, recordkeeping, and consumer-law obligations that apply to them.
3. Record delivery without exposing provider errors
The owner should be able to see whether a receipt email was sent, delivered, or failed. Show a safe status and a useful next step. Raw provider responses, secret identifiers, and internal error details should stay in protected logs.
4. Follow up with a clear purpose
Do not send several unrelated messages after the same job. A concise follow-up can confirm that the receipt is available, invite the client to contact support, offer a review after completion, and provide a book-again path. Respect the client's communication preferences and applicable consent rules.
5. Keep support connected
If the client questions the receipt or service, keep the conversation connected to the business and client record. The client should see their own thread while the owner sees the business support queue. Internal notes should never appear in the client portal.
6. Review the workflow monthly
Look for failed deliveries, receipts waiting to be sent, unresolved support questions, and completed jobs without follow-up. This operational review is more useful than sending more messages automatically.