← BillabexCONTENT HISTORYWHAT CHANGED · RULE-BASED ANALYSIS
Update to Billabex
Snapshot Sep 30, 2026 · 22:57 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": "adjust-scheduled-follow-ups",
"description": "Review and adjust future Billabex payment follow-up emails for selected customer accounts. Use to change a scheduled send date, recipient, subject, language, wording, or tone before an email is sent.",
"included_files": [],
"skill_md_contents": "---\nname: adjust-scheduled-follow-ups\ndescription: Review and adjust future Billabex payment follow-up emails for selected customer accounts. Use to change a scheduled send date, recipient, subject, language, wording, or tone before an email is sent.\n---\n\n# Adjust Scheduled Follow-ups\n\n1. Resolve the organization if needed, find the customer with `list-accounts`, then use `list-outgoing-communications-by-account` and `get-outgoing-communication` to identify the exact unsent email.\n2. Show the customer, current scheduled date, recipients, subject, and content before proposing a change.\n3. Treat a tone request as an edit to the selected scheduled emails, not as a persistent account preference. Preserve facts, amounts, invoice references, commitments, and the agent's third-party identity.\n4. Preview the exact new date or email content. Do not include a signature because Billabex adds the current agent's signature automatically.\n5. Use `update-outgoing-communication` only after explicit approval of the unambiguous email and exact changes. Update multiple emails one by one only when the user clearly approves the full list.\n6. If no future email exists, explain that this workflow cannot create one and do not send an immediate email instead.\n\nRespond in the language of the user's latest request. Copy proper names exactly. Never expose technical identifiers. Use natural business vocabulary and avoid internal terminology.\n"
}SHA-256: c681e4fb53538a038383067f4308c8ee5ceb29a9134a9b550154f33d423abd67