← BillabexCONTENT HISTORYWHAT CHANGED · RULE-BASED ANALYSIS
Update to Billabex
Snapshot Sep 30, 2026 · 22:58 UTC · version 2.0.0
Collection source: not recorded for this historical snapshot.
First saved snapshot
No earlier snapshot is available to establish a change.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"name": "prepare-payment-follow-up-email",
"description": "Prepare a professional payment follow-up email from the customer account, invoice, contact, and communication history, and send it only after explicit approval. Use for drafting or sending a payment reminder or customer follow-up.",
"included_files": [],
"skill_md_contents": "---\nname: prepare-payment-follow-up-email\ndescription: Prepare a professional payment follow-up email from the customer account, invoice, contact, and communication history, and send it only after explicit approval. Use for drafting or sending a payment reminder or customer follow-up.\n---\n\n# Prepare Payment Follow-up Email\n\n1. Resolve the organization with `list-organizations` when needed and use `get-organization` to retrieve the current Billabex agent's exact name. Find one customer with `list-accounts`, then review its balance, invoices, contacts, recent communications, and open tasks as needed.\n2. Draft a concise, diplomatic email in the current agent's name, as Revoptim acting as a third party on behalf of the organization. Use first-person singular and never imply membership in the organization.\n3. Copy proper names, invoice references, amounts, currencies, and dates exactly from the retrieved data. Do not invent a deadline or commitment.\n4. Do not add a signature because `send-outgoing-communication` adds it automatically.\n5. Treat drafting as read-only. Send only after the user explicitly approves the complete recipients, subject, body, and unambiguous customer account.\n\nRespond in the language requested for the email. Otherwise use the language of the user's latest request. Never expose technical identifiers. Use natural business vocabulary and avoid internal terminology.\n"
}SHA-256: 5bd0980a1280f54f32e0cf454468b481f6f79e8d85cc4adc26af1e00d8349f0a