← RingCentral PhoneCONTENT HISTORY
WHAT CHANGED
Update to RingCentral Phone
Snapshot Oct 27, 2026 · 06:06 UTC · version 1.1.0
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save RingCentral Phone 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": "Produces a RingEX Phone communications brief from recent calls, SMS, voicemail, contacts, presence, and message-store data, over a time window the user chooses (last 24 hours, last 3 days, last week, or a custom range). Use when the user asks for a communications digest or brief, a daily digest, morning briefing, catch-up report, missed communications, unresolved calls or texts, voicemail follow-up, or what to work on today. Always asks the user up front how far back to look rather than assuming a fixed window, and on a Monday 24-hour lookback, checks whether the weekend or a recent holiday should be folded in too.",
"included_files": [],
"name": "communications-brief",
"skill_md_contents": "---\nname: communications-brief\ndescription: Produces a RingEX Phone communications brief from recent calls, SMS, voicemail, contacts, presence, and message-store data, over a time window the user chooses (last 24 hours, last 3 days, last week, or a custom range). Use when the user asks for a communications digest or brief, a daily digest, morning briefing, catch-up report, missed communications, unresolved calls or texts, voicemail follow-up, or what to work on today. Always asks the user up front how far back to look rather than assuming a fixed window, and on a Monday 24-hour lookback, checks whether the weekend or a recent holiday should be folded in too.\n---\n\n# Communications Brief\n\n## Goal\n\nHelp the user prepare for the day (or catch up after time away) by reviewing personal RingEX\nPhone communications over a window they choose, and turning them into a prioritized action report.\n\nFocus on what needs attention, not on exhaustively listing every record.\n\n## Trigger examples\n\n- \"Give me my communications brief.\"\n- \"Give me my daily communications digest.\"\n- \"What did I miss in RingEX?\"\n- \"Summarize my calls, texts, and voicemails since yesterday morning.\"\n- \"What communications do I need to follow up on today?\"\n- \"Show me unresolved calls, SMS, and voicemail from the past week.\"\n- \"Catch me up on my phone since last Monday.\"\n\n## Workflow\n\n1. **Ask how far back to look before pulling any data.** Don't assume a fixed window — the right\n lookback depends on when the user last checked in. Ask using a structured choice control if the client provides one\n (plain text otherwise), offering:\n - Last 24 hours\n - Last 3 days\n - Last week\n - Other (let the user specify, e.g. \"since last Wednesday\" or an explicit date range)\n\n For \"Other,\" interpret whatever the user gives you into a concrete date range before continuing.\n\n2. **On a \"Last 24 hours\" choice, check for gaps a strict 24-hour window would miss.** These two\n checks only apply to the 24-hours case — the longer windows already cover this ground:\n - If today is Monday, a straight 24-hour lookback starts Sunday morning and misses Friday\n evening and the weekend, which likely haven't been triaged yet. Ask: \"Since it's Monday,\n want me to also include the weekend (from Friday evening) so nothing from Friday or the\n weekend slips through?\" If yes, move `dateFrom` back to Friday evening (or Friday morning if\n the user prefers the full day).\n - Separately, ask: \"Was there a holiday in the last few days that should be included too?\" The\n skill has no calendar access, so rely on the user's answer. If yes, ask which day(s) and\n extend `dateFrom` to cover them.\n\n These two checks are independent — the user may say yes to one, both, or neither.\n\n3. Convert the final window to ISO-8601 date-times with offset for `dateFrom`/`dateTo`.\n4. Call `get_my_call_activity` (`dateFrom`, `dateTo`) for recent inbound, outbound, and missed\n calls, total talk time, and outstanding callbacks.\n5. Call `get_my_communication_inbox` (`dateFrom`, `dateTo`, `messageTypes: [\"SMS\"]`) for recent\n text messages.\n6. Call `get_my_communication_inbox` (`dateFrom`, `dateTo`, `messageTypes: [\"VoiceMail\"]`) for\n recent voicemail records.\n7. Use `get_my_message_detail` (`messageId`) when a specific SMS or voicemail needs its full body\n or verified transcription to understand the action item. Use `get_my_sms_thread` (`messageId`,\n `dateFrom`, `dateTo`) when the full back-and-forth of a text conversation is needed for context.\n8. Use `resolve_directory_person` (company directory, by name/department/role) or\n `search_my_contacts` (personal address book, by name/phone number) only when useful to identify\n a caller or contact. For Team Chat person resolution, use RingEX Chat's `find_person` instead —\n `team_messaging_get_person` no longer exists.\n9. Use `get_my_phone` only when the user's own presence, business hours, or call-handling rules\n help decide whether to call, text, or defer.\n10. Optionally use `get_my_call_insight` (`callId`) for AI notes/transcript on a specific call, or\n `get_my_call_recording_metadata` (`callId`) to check whether a call was recorded, when the call\n log alone doesn't give enough context.\n11. Summarize patterns across all records before writing the report.\n\n## What to identify\n\n- Missed inbound calls without a later outbound call to the same person or number.\n- Inbound SMS messages without a later user reply.\n- Voicemail that has not clearly been addressed.\n- Repeated contact attempts from the same person or number.\n- Communications that mention urgency, deadlines, blockers, scheduling, customer issues, or needed\n decisions.\n- Follow-ups that can be batched by person, account, customer, or topic.\n\n## Output format\n\n```md\n# Communications Brief\n\n## Window\n[The date range actually used, and whether the weekend/holiday extension was applied.]\n\n## Top Priorities\n- [Most important follow-up and why it matters.]\n- [Second most important follow-up.]\n\n## Unreturned Calls\n- [Caller/contact] called at [time]. Action: [call back, text, defer, or no action].\n\n## Unanswered SMS\n- [Contact/number] sent: [brief summary]. Action: [suggested response or next step].\n\n## Voicemail Needing Attention\n- [Caller/contact] left voicemail at [time]. Key point: [summary]. Action: [follow-up].\n\n## Other Notable Activity\n- [Useful context that is not urgent.]\n\n## Suggested Plan\n1. [Highest-priority response or call-back.]\n2. [Next follow-up.]\n3. [Lower-priority cleanup.]\n```\n\n## Guidance\n\n- Be concise, practical, and action-oriented.\n- Avoid dumping raw logs unless the user asks for them.\n- Group related calls, texts, and voicemail from the same person together.\n- State uncertainty when identity matching is unclear.\n- Do not invent message contents, call outcomes, voicemail transcripts, or follow-up status.\n- If tool results are empty, say that no relevant activity was found for the time range.\n"
}SHA-256 of public snapshot: 3804e3f7a7fb519e7cb041d03f85803c8796f7b25b2aa7788d438714115e902d