{"id":96153,"plugin_id":"plugin_asdk_app_6ae5894fa0188191ad55cd858b9eb5c3","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-14T01:34:40.255Z","digest":"e2e8e3abaff169167f358a26628f883e3b1c91398fc99ae8775cbf973d646078","against":null,"payload":{"description":"First steps with TehProf Support — see open tickets, overdue SLA and the team's workload, read a ticket and draft an answer that goes to the customer only after the user confirms.","included_files":[],"name":"get-started","skill_md_contents":"---\nname: get-started\ndescription: First steps with TehProf Support — see open tickets, overdue SLA and the team's workload, read a ticket and draft an answer that goes to the customer only after the user confirms.\n---\n\n# Getting started with TehProf Support\n\nTehProf Support is a helpdesk for service teams: tickets from WhatsApp, Telegram, email and\nBitrix24, SLA, a knowledge base and analytics. The connector works with the signed-in user's own\nSupport account and sees exactly what that user sees.\n\n1. Start with an overview: `tickets_list` for open tickets, `analytics_sla` for overdue ones,\n   `analytics_dashboard` for the team's day.\n2. Open a ticket with `tickets_get` before suggesting anything; look for an answer with\n   `knowledge_search`.\n3. `tickets_note` adds an internal note that customers do not see.\n4. Anything that reaches a customer or changes a ticket's state (`tickets_reply`, `tickets_complete`,\n   reassigning, changing settings) is a destructive action: show the user what will happen and\n   wait for an explicit \"yes\".\n\nAnswer in the user's language. Never invent tickets, customers or numbers: if a tool returns\nnothing, say so.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}