# Dunning Emails

> Use when drafting payment reminder or dunning email sequences from invoice, account, dispute, and customer context while preserving customer trust and requiring human approval before sending.

- **Type:** Skill
- **Install:** `agentstack add skill-loopfour-finance-skills-dunning-emails`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [loopfour](https://agentstack.voostack.com/s/loopfour)
- **Installs:** 0
- **Category:** [Communication](https://agentstack.voostack.com/c/communication)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [loopfour](https://github.com/loopfour)
- **Source:** https://github.com/loopfour/finance-skills/tree/main/skills/dunning-emails

## Install

```sh
agentstack add skill-loopfour-finance-skills-dunning-emails
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# Dunning Emails

Use this skill to draft polite, accurate, and escalation-aware payment reminder messages.

## Inputs

- Customer name, contact, invoice number, amount, currency, due date, and payment link or remittance instructions.
- Prior outreach history and any promised payment date.
- Dispute status, service issues, credit memos, or unapplied cash.
- Brand voice and escalation policy.

## Workflow

1. Verify whether the invoice is actually due and collectible.
2. Choose the correct tone based on aging stage:
   - Pre-due: helpful reminder.
   - 1-15 days overdue: operational nudge.
   - 16-45 days overdue: firmer request and ask for payment date.
   - 46+ days overdue: escalation with internal owner copied only if policy allows.
3. Include only facts supported by the input.
4. Provide subject line options and a concise email body.
5. If multiple invoices are involved, summarize totals and attach a statement table.

## Output

Return:

- Suggested stage and rationale.
- Email subject line.
- Email body.
- Internal note for the collector.
- Missing data or approval needed before sending.

## Guardrails

- Never send the email directly.
- Do not imply service suspension, collections agency referral, late fees, or legal action without explicit policy support.
- Do not expose internal notes, customer health scores, or blame language in customer-facing drafts.
- If there is an unresolved dispute, draft a resolution-focused message rather than a payment demand.

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [loopfour](https://github.com/loopfour)
- **Source:** [loopfour/finance-skills](https://github.com/loopfour/finance-skills)
- **License:** MIT

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-loopfour-finance-skills-dunning-emails
- Seller: https://agentstack.voostack.com/s/loopfour
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.