← Busymate AICONTENT HISTORY
WHAT CHANGED
Update to Busymate AI
Snapshot Nov 13, 2026 · 00:10 UTC · version 1.1.1
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save Busymate AI and check future changes in Following.
Up to 3 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Work through a Busymate AI workspace's open handoff requests, where the assistant asked for a person. Use when the user asks what needs attention, wants to clear their support queue, or asks to reply to customers in Busymate.",
"included_files": [],
"name": "inbox-triage",
"skill_md_contents": "---\nname: inbox-triage\ndescription: Work through a Busymate AI workspace's open handoff requests, where the assistant asked for a person. Use when the user asks what needs attention, wants to clear their support queue, or asks to reply to customers in Busymate.\n---\n\n# Inbox triage\n\n1. Find the workspace. If the user has more than one, list them with `list_tenants` and the open counts from `get_tenant_inbox_counts`, then ask which one to work on.\n2. Gather the queue with `list_tenant_interventions`: the open handoff requests.\n3. Present a short list, oldest first: customer first name, topic, how long they have waited. Do not show internal IDs.\n4. For each item the user picks, read the full context with `get_tenant_intervention`, and the whole conversation with `get_tenant_conversation_transcript` when the request alone is not enough.\n5. Draft the reply in the business's voice, using `search_knowledge` for facts such as policies, prices or delivery times. Never invent a policy; if the knowledge does not cover it, say so and ask the user.\n6. Show the draft and wait for the user's approval. Then send it with `reply_tenant_intervention`. A sent reply cannot be recalled.\n7. Resolve the handoff with `resolve_tenant_intervention` only when the user confirms the customer's question is settled. Use `add_tenant_intervention_note` for internal context the team should see; customers never see notes.\n8. Finish with a summary: what was answered, what is still open, and anything the knowledge base could not answer.\n"
}SHA-256 of public snapshot: 8928f02ef8771f3b7906ab3e2efb291ecc845fc8e4bb3cff4a563293e34c4b9a