Send consistent overdue payment follow-ups
Use a Skill to keep reminder tone, timing, and escalation consistent across customers.
Outcome
Every overdue reminder follows the company’s tone and escalation rule while still using the right invoice and customer facts.
Main feature: Skills
The situation
Three people follow up overdue invoices. One sends a gentle note at day 30, another threatens to stop supply at day 10, and the owner has no clear record of what the customer was promised.
Before you start
Agree the stages with sales and finance. Decide who owns strategic customers, when an account manager must review a message, and what Jarvis must never promise.
Create the Skill
- Open Skills and choose New Skill.
- Name it
collections-follow-up. - Write the timing bands. For example: days 1 to 7, friendly reminder; days 8 to 21, ask for a payment date; days 22 to 30, include the account owner; over 30 days, draft an escalation for review.
- Require the invoice number, due date, amount, and existing promise in every draft.
- State the limits: do not threaten service suspension, change payment terms, or copy senior management without approval.
- Save, enable, and test the Skill on one ordinary customer and one disputed invoice.
Use it in Chat
Ask Jarvis to list overdue invoices, then call /collections-follow-up to draft the next message for each. Check the customer, invoice, amount, prior conversation, and tone.
Sending email is an important action and should wait for confirmation. Approve only the messages you would be comfortable receiving from a supplier yourself.
Done when
The timing and tone are consistent, each message uses the correct invoice facts, disputed items are separated, and every escalation has a person responsible.
The Skill should protect the relationship as well as collect the money. Write the rule for a difficult day, not only the easy reminder.
Use it again
Once the Skill is trusted, place it inside a weekly Macro. Use an Agent only when someone is committed to reviewing the prepared follow-ups. If the starting rule is unclear, use Choose the right automation before adding more moving parts.