Sort customer replies to payment reminders by intent
Replies to overdue invoice reminders are read by a decision model and sorted into paid, promise to pay, dispute, wrong contact, or out of office, so the person handling receivables acts on each one quickly.
An example pattern written by Agents Lookup. We have not yet found a public build of this exact job.
The use case
Sending payment reminders is easy to automate; reading the replies is not. Customers answer with already paid, will pay Friday, this invoice is wrong, or an out-of-office note, and each needs a different next step. Jev reads each reply and picks one intent from a fixed list. Replies with a confidence of 0.85 or higher pause or adjust the reminder sequence for that invoice and are logged. Disputes always go to a person, and lower-confidence replies are queued for review. Jev never marks an invoice paid, offers terms, or writes off a balance. The person handling receivables checks payments, answers disputes, and decides on any change to terms. Test the labels on a few months of past replies first, so you know how often each intent is confused with another.
Example workflow
- Replies to reminder emails land in an accounts inbox in Gmail.
- Zapier sends each reply and the related invoice number to Jev as the state.
- Jev answers a Choice question, what does this reply say, with the allowed answers says already paid, promise to pay, disputes the invoice, wrong contact, out of office, and other.
- Code pauses further reminders for that invoice when the answer is already paid or promise to pay, and logs the reply in a Google Sheet.
- Disputes and low-confidence replies are posted to Slack for the person handling receivables.
- That person checks the bank for claimed payments, answers disputes, and updates the invoice in the accounting system.
Tools
- Jev (TypeSafe AI)
- Gmail
- Zapier
- Google Sheets
- Slack
- QuickBooks Online
Risks and guardrails
- A customer who says paid may not have — guardrail: reminders are only paused for a few days and resume unless a person confirms payment.
- A dispute labelled as a promise to pay gets ignored — guardrail: any reply mentioning wrong, error, or credit is sent to a person.
- Replies could trigger automatic responses that annoy customers — guardrail: this step sends nothing; it only sorts.
Related recipe
B2B Invoice AR Reminder Agent with Approval Gate: An agent reads open invoices from QuickBooks or Xero, skips blocked accounts, and drafts tiered payment reminders in Gmail that a person approves one by one before anything is sent.
Want it set up for you? Request a quote.
Sources
Written by Agents Lookup. Credits and official pages for the tools this use case names:
- Gmail (official page): developers.google.com/workspace/gmail (checked 2026-11-19)
- Zapier MCP (official page): zapier.com/mcp (checked 2026-11-09)
- Slack MCP server (official page): docs.slack.dev/ai/slack-mcp-server (checked 2026-11-09)
- QuickBooks Online MCP server (official page): github.com/intuit/quickbooks-online-mcp-server (checked 2026-11-09)