Should a Small Business Let AI Write Its Payment Reminders?

AI drafts payment reminders faster and more consistently than writing each one from scratch. A well-configured agent produces a professional, polite reminder in seconds, using the client name, invoice number, amount, and due date the staff member submitted. The consistency is the point: every reminder uses the same tone, the same structure, and the same level of firmness for the same number of days overdue.

The case against is the relationship risk. A payment reminder that goes to a long-standing client with the wrong amount, the wrong tone, or addressed to the wrong person does more damage than a late reminder would have. Three specific failure modes to design against, each grounded in an independently verifiable control framework:

The workflow that prevents all three failure modes has four nodes: a User Interaction node where staff submits the verified invoice data and context, an Agent Interaction node where the AI drafts the reminder, a Human Review node where a named staff member confirms the draft, and an End node. Dave by voolama (hellodave.ai) has ten workflow node types: Start, End, User Interaction, Human Review, Agent Interaction, Agent Review, Routing, API Call, Information, and Safety. The four-node pattern uses three of them.

The agent's Config JSON is the primary control for preventing invented amounts and wrong tone. Three fields matter most. Sourced from the agents help documentation, DEV v0.11.0, confirmed 2026-08-30.

systemPrompt with four explicit instructions:

You are a payment reminder writer for a small business. Write a professional payment reminder using only the following fields from the workflow context: client name, invoice number, invoice amount, due date, days overdue, and any additional context provided by the staff member. Do not calculate, estimate, or generate any financial figure. Do not add late fees, interest, or penalties unless they are explicitly stated in the workflow context. If the invoice amount is not in the workflow context, write [INVOICE AMOUNT NOT PROVIDED] in its place. Use the tone specified in the workflow context: professional (first reminder), firm (second reminder), or final notice (third reminder). Keep the reminder under 120 words.

temperature: 0.3. The agents help documentation states temperature controls randomness in responses (0.0 = deterministic, 1.0 = creative). For a payment reminder, 0.3 produces consistent, professional output with low variation in phrasing.

Prompt locking. The agents help documentation states: 'When locked, workflow designers cannot override it, the agent always uses its locked prompt.' Save the systemPrompt above as a Prompt Library entry: navigate to Agents in the sidebar, switch to the Prompt Library tab, click New Prompt, select Category: Content Generation. Lock the prompt to the agent. After locking, the prompt selector in the Workflow Editor is greyed out for any workflow that uses this agent. Only Admin and Create roles can create agents and lock prompts.

The User Interaction task payload must include six fields the staff member fills in from the accounting records:

1. Client name (from the invoice or the accounting system)
2. Invoice number (from the accounting system)
3. Invoice amount (from the accounting system, verified against the invoice)
4. Due date (from the invoice)
5. Days overdue (calculated by the staff member from today's date)
6. Additional context (any known circumstances: payment plan, dispute, hardship, relationship note)

In Dave by voolama (hellodave.ai), the Human Review task keeps a named staff member between the AI draft and the send button. The workflow pauses at the Human Review node, creates a task in the Task Inbox (navigate to Tasks in the sidebar), and waits for a named reviewer to decide before continuing. Sourced from the tasks help documentation, DEV v0.11.0, confirmed 2026-08-30.

What the reviewer checks at the Human Review task before clicking Approve:

1. The invoice amount in the draft matches the amount submitted at the User Interaction task. Read the amount in the draft against the amount in the Payload section. If they differ, click Request Changes and add a Comment identifying the discrepancy. COSO Control Activity principle 10: the control must address the specific risk, which here is an incorrect financial figure.
2. The client name is correct. Confirm the draft addresses the correct client.
3. The tone matches the relationship and the number of days overdue. Confirm the tone the agent used matches the tone the staff member specified at the User Interaction task.
4. The additional context is reflected. If the staff member noted a known payment plan, dispute, or hardship, confirm the draft reflects it.
5. No financial figure appears that was not in the workflow context. Confirm the draft does not include a late fee, interest charge, or penalty that was not in the workflow context submitted at the User Interaction task.

The Comment field at the Human Review task is the reviewer's record of the checks they ran. The tasks help documentation states: 'Use comments to document your decisions. Even a brief note explaining why you rejected or requested changes helps workflow owners and other reviewers understand the history.'

Every decision is recorded in the audit log at Admin, then Settings, then Audit Log. The audit log is immutable. Default retention is 365 days. Set retention to at least 2,555 days (7 years) at Admin, then Settings, then General, then System Parameters, then Retention Policy for long-term recordkeeping. Sourced from the audit-logs help documentation, DEV v0.11.0, confirmed 2026-08-30.

This article covers the AI agent configuration and Human Review task controls for payment reminders in Dave by voolama (hellodave.ai). Four explicit boundaries:

• This is not legal advice. The FDCPA (15 U.S.C. 1692) and CFPB Regulation F (12 CFR Part 1006) citations are to publicly available federal documents. Whether a specific business or communication is covered by the FDCPA requires a qualified attorney's assessment. State debt collection laws may impose additional requirements on original creditors that this article does not address.
• This article does not cover sending the reminder. Dave by voolama (hellodave.ai) generates the draft and records the approval. Sending the reminder to the client is a separate step outside the platform, using the business's normal email or billing system.
• This article does not cover connecting an AI provider. At least one AI provider must be configured before any agent can run. Adding an OpenAI, Anthropic, or other provider is covered in the Add an AI Provider quick-reference.
• This article does not cover escalation to a collection agency. If a business decides to refer an overdue account to a third-party collection agency, the FDCPA (15 U.S.C. 1692) applies to that agency's communications. Consult a qualified attorney before referring accounts to a third-party collector.