← RingCentral PhoneCONTENT HISTORY

Update to RingCentral Phone

Snapshot Oct 27, 2026 · 06:06 UTC · version 1.1.0

Collection source: downloaded plugin package.

WHAT CHANGED

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 JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Finds a specific recent call in the authenticated RingEX Phone user's own call history and recaps it with AI notes, transcript excerpts, and whether it was recorded. Use when the user asks to recap a call, summarize what was discussed, check if a call was recorded, or find a call about a specific topic or person.",
  "included_files": [],
  "name": "call-recap",
  "skill_md_contents": "---\nname: call-recap\ndescription: Finds a specific recent call in the authenticated RingEX Phone user's own call history and recaps it with AI notes, transcript excerpts, and whether it was recorded. Use when the user asks to recap a call, summarize what was discussed, check if a call was recorded, or find a call about a specific topic or person.\n---\n\n# Call Recap\n\n## Goal\n\nTurn \"what happened on that call\" into a quick answer: who it was with, when, what the AI notes\nor transcript say, and whether a recording exists. This is read-only — it never plays audio and\nnever exposes recording ids, URIs, or content locations, only whether a recording exists and in\nwhat mode.\n\n## Trigger examples\n\n- \"Recap my last call with Priya.\"\n- \"What did we discuss on the call with support this morning?\"\n- \"Was my call with the vendor yesterday recorded?\"\n- \"Find a call from last month where renewal pricing came up.\"\n- \"Summarize my calls from yesterday.\"\n\n## Scope boundary\n\n- Personal call history only — this skill never looks at anyone else's calls, and there is no\n  account- or team-wide call log on this server (that lives on RingEX Admin).\n- Read-only. Never claims to play, download, or attach recording audio — only\n  `get_my_call_recording_metadata`'s safe projection (recording exists, and in what mode) is ever\n  available.\n- Not every call has AI notes or a transcript — that depends on whether AI call notes were enabled\n  for that call. If neither is available, say so rather than fabricating a summary from the call's\n  metadata alone.\n\n## Workflow\n\n1. **Establish the search window and any filters.** Default to today unless the user names a\n   different range (\"yesterday,\" \"last month,\" \"this week\"). If the user names a person or a topic\n   (e.g. \"the call about renewal pricing\"), prefer `search_my_call_insights` with `dateFrom`,\n   `dateTo`, and `person` (phone number or extension) and/or `topic` — remember `topic` is a\n   literal substring match against searchable AI content, not a semantic query, so mention that if\n   the search comes up empty (\"try a different phrase\" rather than assuming nothing was said).\n\n2. **If no person/topic was given, browse by activity instead.** Call `get_my_call_activity` with\n   the resolved `dateFrom`/`dateTo` to get the aggregate view (recent/missed/returned calls) and\n   use it to identify candidate calls to recap.\n\n3. **Resolve names for candidates.** For each candidate call's counterpart number, try\n   `search_my_contacts` then `resolve_directory_person`; fall back to the raw number if neither\n   resolves.\n\n4. **Present candidates as a choice** if more than one call could match:\n      - 2–4 candidates → a structured multiple-choice control, when the client provides one, with\n        one option per call labeled with the resolved name, direction, and time.\n      - More than 4, or exactly one → a plain-text ranked list, or auto-proceed if there's only one\n        unambiguous match.\n      - No matches → say so and offer to widen the date range rather than guessing.\n\n5. **Pull the recap for the selected call.** Using that call's id:\n      - Call `get_my_call_insight` for AI notes and transcript text.\n      - Call `get_my_call_recording_metadata` to check whether the call has recording metadata and\n        in what mode (e.g. automatic/on-demand) — this never returns audio or a recording id/URI.\n\n6. **Render the recap.** Show who the call was with, when, direction, the AI notes/transcript\n   content if available, and a one-line recording status (\"Recorded — automatic\" / \"No recording\n   found\"). If AI notes/transcript weren't available for that call, say so plainly instead of\n   summarizing from call metadata alone.\n\n## Guidance\n\n- Never fabricate AI notes, transcript content, or recording status — report exactly what the\n  tools returned, including when a field is absent.\n- Never imply audio was accessed, played, or attached — recording metadata only confirms\n  existence and mode.\n- Treat `topic` searches as literal substring matches, not semantic search, when explaining\n  results (or the lack of them) to the user.\n- Stay within the user's own call history — this skill has no account- or team-wide scope.\n"
}

SHA-256 of public snapshot: d891f49db2f5a5a23204fb46981f08489b40f6b95550d61e94199e43ae376f59