← InsertChat AI ReceptionistCONTENT HISTORYWHAT CHANGED · RULE-BASED ANALYSIS
Update to InsertChat AI Receptionist
Snapshot Oct 8, 2026 · 12:02 UTC · version 1.1.0
Collection source: downloaded plugin package.
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
{
"description": "Prepare an InsertChat AI front desk briefing, triage conversations needing human attention, inspect leads, draft customer follow-ups, and review monthly performance. Use for shared-inbox handovers and frontdesk operations across customer channels.",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 207
}
],
"name": "ai-front-desk",
"skill_md_contents": "---\nname: ai-front-desk\ndescription: Prepare an InsertChat AI front desk briefing, triage conversations needing human attention, inspect leads, draft customer follow-ups, and review monthly performance. Use for shared-inbox handovers and frontdesk operations across customer channels.\n---\n\n# Run your front desk review\n\nStart with `get_front_desk_brief` for a workspace briefing. Omit `agent_uid` to cover every assistant the user can access, or supply the verified ID for an explicitly selected assistant. Use `channel` only when requested (`web`, `voice`, `whatsapp`, `email`, or `sms`). The first page includes queue totals; later cursor pages omit counts. Reuse the first-page totals rather than treating omitted counts as zero.\n\nExplain which conversations need attention and link to their returned `app_path` under `https://app.insertchat.com`. Counts overlap: urgent and unassigned may include the same conversation, so do not sum queues. These are current inbox counts, not a daily activity report. If `has_more`, continue with `next_cursor` as `cursor` and unchanged filters when needed for the requested coverage; otherwise label the listed items as a selection.\n\nFor a specific request, use `search_conversations` with its query, queue, channel, or `contact_uid`. This tool needs an assistant: resolve it using `list_agents` or use the user's configured default. Read selected conversations with `get_conversation` before summarizing or drafting. Preserve each result's assistant ID; never apply one assistant's ID to another assistant's conversation.\n\nFor a lead or callback, owners and admins can search `list_contacts` and read `get_contact` for the submitted inquiry. Use its `agent_uid` and `contact_uid` with `search_conversations` to review context. Identify missing information rather than inventing customer details, deadlines, prices, or appointments. A draft is not a sent message. Place it with `draft_reply` only when the host exposes that view tool; otherwise return the text and conversation link for the user to review and send.\n\nFor performance, use `get_report_summary` with the requested month and year. It requires an owner/admin and analytics access. Compare periods only after reading each requested period and preserve the returned period and scope. Do not extrapolate resolution or satisfaction from a few conversations. If access is denied, report which part is unavailable and continue the authorized inbox task.\n\nDeliver the requested brief, lead summary, draft, or comparison. Open the workspace with `open_insertchat` when the user wants to act there; do not interrupt an existing task with onboarding or preference questions.\n"
}SHA-256 of public snapshot: a389257bf190aa24c813247fc7b8c3954c20bc8b5e134ac294b5d3ded67f415b