{"id":78790,"plugin_id":"plugin_asdk_app_6a26d97bd46081918642a70d07cf07d4","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-03T18:39:18.749Z","digest":"4a20519c205dbf57365babdfbb9c34de8873a557ce66af5c9f0241f7c51dff3c","against":null,"payload":{"description":"Find open WhatsApp chats where the customer has not replied after the team's last message, and draft a short follow-up for each. Use when the user asks to chase quiet chats, follow up on unanswered messages, or find chats with no reply in a number of days.","included_files":[],"name":"follow-up-stale-chats","skill_md_contents":"---\nname: follow-up-stale-chats\ndescription: Find open WhatsApp chats where the customer has not replied after the team's last message, and draft a short follow-up for each. Use when the user asks to chase quiet chats, follow up on unanswered messages, or find chats with no reply in a number of days.\n---\n\nUse this skill to find chats that went quiet after we wrote last, and to help the user follow up. Drafting is free. Sending always needs the user's confirmation, message by message.\n\n1. Ask for the quiet period if the user did not give one. Default to 2 days.\n2. Call `list_chats` with `closed` set to false, narrowed by `whatsapp_account_id`, `labels` or `responsible` (a teammate email from `workspace_team`) if the user named any. Results come 50 per page. `list_chats` has no last-activity filter, so the quiet period is checked in the next step.\n3. For each candidate call `chat_history` and read only the last few messages. Use `from_me` to tell our messages from the customer's. Keep a chat only when our message is the latest and its timestamp is at least the quiet period old. Skip chats the user labelled as hands-off and chats where the customer clearly ended the conversation.\n4. Checking every chat is slow. If there are many, check the most recently created or the ones matching the user's filters first, stop at about 30 chats, and tell the user how many you checked and that more may exist.\n5. For each kept chat, draft one short follow-up in the language the customer used. Refer to what was actually discussed. Do not invent promises, prices or dates.\n6. Show the user a table: contact, number, days quiet, our last message and the draft.\n7. Send only after the user approves the exact text of each message. Before the first send, call `workspace_quotas`; if `near_full` or `full` is true, warn the user and wait for their confirmation. Then use `chat_send_message`, or `message_reply` when replying to a specific message. A text message uses one quota unit and an attachment about two. Check delivery with `message_details` before sending anything else into the same chat.\n8. Do not send to a number the user has not confirmed, and do not start new conversations with this skill.\n\nSends are real and immediate. Never send a batch on a single \"yes\" to the table; confirm which drafts are approved. For WhatsApp Business API chats, free text is only allowed while `service_window_is_open` is true in `waba_chat_details`; otherwise use the waba-template-send skill.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}