Compliant Collection Notices Without the Legal Risk

1. Get MultiMail ready: read https://multimail.dev/llms.txt, connect the MCP server, create a free inbox, and set up a verified sender. 2. Connect to QuickBooks Online and use QuickBooks webhooks for Invoice and Payment changes, plus a daily check of open invoices, to find customers with invoices past the due date and no matching payment. 3. For each overdue invoice, draft a formal collection notice with the customer name, invoice number, amount due, due date, payment options, required debt-collection disclosures, and clear dispute-resolution instructions; exclude any account marked disputed, bankrupt, represented by counsel, or do-not-contact. 4. Use a conservative cadence: initial notice after the configured grace period, one follow-up 7 days later, and a final pre-escalation notice 14 days later unless QuickBooks shows payment, dispute, or manual hold. 5. Run every notice in MultiMail gated_send mode so legal or compliance approves the complete message before sending; ask me only for QuickBooks access, MultiMail credentials, sender/domain details, brand voice, and the approved disclosure language to go live.

1. Get MultiMail ready: read https://multimail.dev/llms.txt, connect the MCP server, create a free inbox, and set up a verified sender. 2. Connect to Stripe Billing and listen for real Stripe webhook events such as invoice.payment_failed and customer.subscription.updated, then use Stripe invoice and customer records to identify unpaid invoices that remain open after the allowed retry or grace period. 3. Draft collection notices that reference the unpaid invoice, amount, service or subscription, payment link or payment instructions available from Stripe, required debt-collection disclosures, and dispute-resolution information; suppress notices for disputed, refunded, canceled, or manually paused accounts. 4. Personalize the cadence by account status: first notice after failed collection remains unresolved, second notice after retry failure, and final notice before suspension or escalation, stopping immediately when Stripe shows the invoice paid or voided. 5. Run the workflow in MultiMail gated_send mode so each collection email is reviewed before delivery; ask me only for Stripe access, MultiMail credentials, sender/domain details, brand voice, escalation timing, and approved legal disclosure text to go live.

1. Get MultiMail ready: read https://multimail.dev/llms.txt, connect the MCP server, create a free inbox, and set up a verified sender. 2. In Salesforce, use a Record-Triggered Flow on the object your team uses for collections, such as Account, Opportunity, Case, or a custom Invoice object, to trigger when a balance becomes overdue, enters a collections stage, or is assigned to a collections queue. 3. Pull the debtor contact, account owner, balance, invoice references, delinquency stage, prior contact history, and any compliance flags from Salesforce, then draft a formal collection notice with required disclosures, payment options, and dispute instructions. 4. Respect Salesforce controls before drafting or sending: skip records marked disputed, legal hold, represented by counsel, bankruptcy, deceased, do-not-contact, or missing a valid debtor email, and create a Salesforce activity note for every drafted notice. 5. Run every message in MultiMail gated_send mode for legal and compliance review before sending; ask me only for Salesforce access, MultiMail credentials, sender/domain details, approved templates/disclosures, brand voice, and the collections-stage rules to go live.