← 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": "Presents the authenticated RingEX Phone user's SMS and MMS inbox as a clickable list of recent conversations, then renders the selected conversation as a formatted text-message stream. Excludes voicemail and fax. Use when the user asks to see their texts, SMS inbox, message threads, who they've been texting, or to open a text conversation with someone.",
  "included_files": [],
  "name": "sms-inbox",
  "skill_md_contents": "---\nname: sms-inbox\ndescription: Presents the authenticated RingEX Phone user's SMS and MMS inbox as a clickable list of recent conversations, then renders the selected conversation as a formatted text-message stream. Excludes voicemail and fax. Use when the user asks to see their texts, SMS inbox, message threads, who they've been texting, or to open a text conversation with someone.\n---\n\n# SMS Inbox\n\n## Goal\n\nGive the user a browsable view of their personal text conversations: first a list of who they've\nrecently exchanged SMS/MMS with, then — once they pick someone — that conversation rendered like a\ntext-message stream. Voicemail and fax are never part of this skill. This is read-only; sending a\nnew message is a different skill (`send-sms`).\n\n## Trigger examples\n\n- \"Show me my SMS inbox.\"\n- \"Who have I been texting recently?\"\n- \"Open my text conversation with Sarah.\"\n- \"Show me that group text with the sales team.\"\n- \"Catch me up on my texts from this week.\"\n\n## Scope boundary\n\n- SMS and MMS only. Never include voicemail or fax records, even if the user says \"messages\" or\n  \"inbox\" generically — if they explicitly ask for voicemail or fax, say this skill doesn't cover\n  that instead of quietly including it.\n- Read-only. This skill never sends, replies, marks read/unread, or deletes anything — hand off to\n  `send-sms` if the user wants to reply.\n- A group text (more than one other participant) is its own distinct conversation. Never merge a\n  group thread into a participant's 1:1 thread just because they share a person, and never split a\n  group thread into separate per-person conversations.\n\n## Workflow\n\n1. **Pull recent SMS/MMS activity.** Call `get_my_communication_inbox` with\n   `messageTypes: [\"SMS\"]` (this covers both plain SMS and MMS text records — voicemail and fax\n   are separate `messageTypes` values and must not be requested). Default the window to the last\n   14 days unless the user asks for a different range.\n2. **Group records into conversations.** A conversation's identity is the exact set of other\n   participants (phone numbers) on the message, not a single number:\n      - One other participant → a 1:1 conversation with that person.\n      - More than one other participant → a group conversation, keyed by that whole set. A group\n        thread with Sarah + Mike is a different conversation from a 1:1 thread with Sarah alone,\n        even though Sarah is in both.\n   - Sort conversations by their most recent message time, newest first.\n3. **Resolve display names.** For each participant number, try `search_my_contacts` (personal\n   address book) then `resolve_directory_person` (company directory); fall back to the raw phone\n   number if neither resolves. Label a group conversation by joining participant names/numbers\n   (e.g. \"Sarah Kim, Mike Chen\"); if there are more than 3 participants, show the first two names\n   followed by \"+N more\".\n4. **Present the conversation list as a choice.**\n      - If there are 2–4 recent conversations, use a structured multiple-choice control, when the\n        client provides one: one option per conversation, labeled with the\n        resolved name(s), with the most recent message snippet and timestamp as the description.\n      - If there are more than 4, or fewer than 2 (zero or one), list them as a plain-text ranked\n        list instead — a multiple-choice prompt can't show more than 4 options, and a single\n        conversation doesn't need a picker at all (just confirm and proceed to step 5).\n      - If nothing was found in the window, say so and offer to check a wider date range instead of\n        guessing at prior activity.\n5. **Fetch the selected conversation.** Take any `messageId` belonging to that conversation and\n   call `get_my_sms_thread` (`messageId`, `dateFrom`, `dateTo`), oldest message first. If the\n   default window doesn't return at least ~10 messages, widen `dateFrom` further back (e.g. in\n   30-day steps) and re-fetch rather than presenting a thin conversation as if it were complete.\n6. **Trim and render.** Keep only the most recent ~10 messages. Render them as a text-message\n   stream, oldest at the top, in this shape:\n\n   ```\n   Sarah Kim · Tue 2:14 PM\n   Running 10 min late, sorry!\n\n   You · Tue 2:15 PM\n   No worries, see you soon\n\n   Sarah Kim · Tue 2:16 PM\n   😊\n   ```\n\n   - Label the user's own messages \"You\"; label others by their resolved name (or number if\n     unresolved). In a group conversation, label each message with the specific sender — never\n     collapse multiple participants under one label.\n   - Put a blank line between each message so the stream reads like a chat log, not a wall of text.\n   - `get_my_sms_thread` never returns MMS binary content — if a message carried an attachment,\n     say so in place of the media (e.g. \"[MMS attachment]\") rather than omitting it silently or\n     inventing a description of it.\n   - If there are more than ~10 messages in the window, note that older messages exist and offer\n     to go further back rather than silently truncating without saying so.\n\n## Guidance\n\n- Never invent a message's content, sender, or timestamp — if a field is missing, say it's\n  unavailable.\n- Never fold voicemail or fax into this view.\n- Never merge or split conversations incorrectly — participant-set identity is the rule, not a\n  single phone number.\n- Keep the conversation list step fast and skimmable; save full message rendering for after a\n  conversation is chosen.\n"
}

SHA-256 of public snapshot: 8c54464151bcdaef678f96abb8d491a4291a941f94a9ef4d7bc733a584d4b1b1