🌸 万物焕新春季特惠 年度计划立减 30% 🌸 优惠码：SPRING2026
总结某人的功能请求
Prompt detail
总结上个月所有提及名为 {{Person_name}} 的人员的功能请求工单的状态。
What the prompt does
When a stakeholder, customer, or colleague is tied to multiple feature requests, it's hard to manually track which tickets they're mentioned in and what those requests actually say. This prompt eliminates that legwork entirely.
Provide a person's name, and remio searches your past month of feature request tickets — across Slack threads, email conversations, and support tools — to surface every mention. You get a clear, consolidated summary of each ticket's status, so you can instantly understand what features matter most to that individual.
When to use
• Preparing for a quarterly business review where you need to show a specific customer what feature requests are in progress on their behalf
• A sales rep asks support for an update on everything a key account has requested recently
• Escalation meetings where leadership wants to know which open requests involve a particular stakeholder
• Onboarding a new support lead who needs context on a VIP contact's outstanding feature needs
• Prioritization sessions where product managers need to understand one person's full request landscape
Prompt examples
Input: Summarize the status for all feature request tickets from the past month that mention the person named Sarah Kim.
remio responds:
Over the past month, Sarah Kim is mentioned in 4 feature request tickets. Ticket #4821 ("Bulk export for audit logs") is currently marked as Under Review by the product team, with a last update on June 3rd. Ticket #4856 ("Custom role permissions for sub-accounts") is In Progress and assigned to the platform squad with a target release in Q3. Ticket #4890 ("API rate limit increase option") was Closed — Declined on June 10th, citing infrastructure constraints. Finally, Ticket #4902 ("SSO support for SAML 2.0") is Open and awaiting prioritization in the next sprint planning cycle. Sarah's most urgent concern appears to be the custom role permissions request based on follow-up frequency.
Tip 1:
Include the person's full name and company if they're an external contact — this helps remio distinguish between people with common names across different ticket sources.
Tip 2:
After reviewing the summary, follow up by asking remio to draft a status update email to that person, saving you from rewriting the information manually.
Tip 3:
Narrow results by adding a product area (e.g., "tickets related to billing features") if the person has a high volume of requests.
More tips
remio满足您对知识的所有需求
了解更多功能
从网站、本地文件夹和文件中获取资源。
从您的整个知识库中获取即时、可靠的答案。
您的工作助手，可在台式机、浏览器和移动设备上使用。
无限次免费录音和转录，非机器人操作。