Skill instructions
call-followup-email8.05 KB
View saved version →
---
name: call-followup-email
description: >-
Turns a recent RingEX phone call into a drafted (and optionally sent)
follow-up email. Pulls the call from the user's RingEX call history,
resolves who was on the other end and their email address, drafts a
follow-up that references the call (using the AI call summary/insight when
one exists), and sends it through whatever email tool is actually
available — or hands back a ready-to-send draft if none is connected. Use
this whenever the user wants to follow up on a phone call by email —
phrases like "email them about that call", "send a follow-up to the
person I just talked to", "draft a recap for my call with [name]", "I told
a customer I'd send them something after we hung up", or "can you write a
follow-up for my 2pm call" — even if they don't mention RingCentral, call
history, or name a specific email tool. Do not use this for drafting
emails unrelated to a phone call, or for logging/summarizing a call
without producing an email (that's ringex-calls or ringex-meetings).
---
# Call Follow-Up Email
## What this does
Bridges two things that don't naturally talk to each other: RingEX call history and whatever email tool the user happens to have. The workflow is always the same shape — find the call, find the person and their email, draft something specific (not generic), then get it out the door however is actually possible for this user, today, with whatever they have connected.
The email-sending step is the part most likely to vary between users, so treat "send an email" as a capability to be discovered at runtime, not a specific tool to assume. See "Step 4" below — this is the crux of the skill.
## Step 1: Find the call
Pull recent call activity with `get_my_call_activity`. Default to the last 10 calls across both directions (inbound and outbound) — that covers "the call I just had" and "that call from earlier" without over-asking. If the user already named a person, a rough time ("this morning," "yesterday"), or said "the call I just finished," narrow to that instead of showing a full list.
Before presenting the list, enrich each candidate with whether it has a **recording** (`get_my_call_recording_metadata`) and a **transcript/AI summary** (`get_my_call_insight`) — one call to each tool per candidate, using the call id from `get_my_call_activity`. This costs a handful of extra tool calls up front, but it's worth it: whether a call has a transcript is the single biggest predictor of whether Step 3 can write something specific versus something generic, so the user should see that signal *before* they pick, not discover it after. Show it plainly next to each call, e.g. "🎙️ recorded, 📝 transcript" or "no recording/transcript — call notes only," so the user can weigh that against "this is the call I actually want to follow up on."
Present the candidates and let the user pick one (use a structured choice control, when the client provides one, if there's more than one plausible match — phone number, name if known, date/time, duration, direction, and the recording/transcript indicator). If there's exactly one obvious match to what the user described, don't force a pointless confirmation click; just proceed and say which call you picked — but still mention its recording/transcript status so they know what kind of follow-up to expect.
## Step 2: Resolve the other party and their email
This is the step to be honest about, because the tools don't fully cooperate here:
- `search_my_contacts` (RingEX personal address book) can look up the counterpart's **name** by phone number, but its output explicitly excludes email addresses — it's a phone-focused projection only. It will never hand you an email, no matter who's in the address book.
- If a CRM-style connector is connected (Salesforce, HubSpot, Google Contacts, etc.), check there next — a contact record with a phone number often carries an email too. Don't assume one is connected; check what's actuallPreview of the first 4,000 characters. Read full instructions →
call-recap4.13 KB
View saved version →
---
name: call-recap
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.
---
# Call Recap
## Goal
Turn "what happened on that call" into a quick answer: who it was with, when, what the AI notes
or transcript say, and whether a recording exists. This is read-only — it never plays audio and
never exposes recording ids, URIs, or content locations, only whether a recording exists and in
what mode.
## Trigger examples
- "Recap my last call with Priya."
- "What did we discuss on the call with support this morning?"
- "Was my call with the vendor yesterday recorded?"
- "Find a call from last month where renewal pricing came up."
- "Summarize my calls from yesterday."
## Scope boundary
- Personal call history only — this skill never looks at anyone else's calls, and there is no
account- or team-wide call log on this server (that lives on RingEX Admin).
- Read-only. Never claims to play, download, or attach recording audio — only
`get_my_call_recording_metadata`'s safe projection (recording exists, and in what mode) is ever
available.
- Not every call has AI notes or a transcript — that depends on whether AI call notes were enabled
for that call. If neither is available, say so rather than fabricating a summary from the call's
metadata alone.
## Workflow
1. **Establish the search window and any filters.** Default to today unless the user names a
different range ("yesterday," "last month," "this week"). If the user names a person or a topic
(e.g. "the call about renewal pricing"), prefer `search_my_call_insights` with `dateFrom`,
`dateTo`, and `person` (phone number or extension) and/or `topic` — remember `topic` is a
literal substring match against searchable AI content, not a semantic query, so mention that if
the search comes up empty ("try a different phrase" rather than assuming nothing was said).
2. **If no person/topic was given, browse by activity instead.** Call `get_my_call_activity` with
the resolved `dateFrom`/`dateTo` to get the aggregate view (recent/missed/returned calls) and
use it to identify candidate calls to recap.
3. **Resolve names for candidates.** For each candidate call's counterpart number, try
`search_my_contacts` then `resolve_directory_person`; fall back to the raw number if neither
resolves.
4. **Present candidates as a choice** if more than one call could match:
- 2–4 candidates → a structured multiple-choice control, when the client provides one, with
one option per call labeled with the resolved name, direction, and time.
- More than 4, or exactly one → a plain-text ranked list, or auto-proceed if there's only one
unambiguous match.
- No matches → say so and offer to widen the date range rather than guessing.
5. **Pull the recap for the selected call.** Using that call's id:
- Call `get_my_call_insight` for AI notes and transcript text.
- Call `get_my_call_recording_metadata` to check whether the call has recording metadata and
in what mode (e.g. automatic/on-demand) — this never returns audio or a recording id/URI.
6. **Render the recap.** Show who the call was with, when, direction, the AI notes/transcript
content if available, and a one-line recording status ("Recorded — automatic" / "No recording
found"). If AI notes/transcript weren't available for that call, say so plainly instead of
summarizing from call metadata alone.
## Guidance
- Never fabricate AI notes, transcript content, or recording status — report exactly what the
tools returned, including when a field is absent.
- Never imply audio was accessed, played, or attached — recording metadata only confirms
existence and mode.
- Treat `topic` searches as lPreview of the first 4,000 characters. Read full instructions →
colleague-lookup6.12 KB
View saved version →
---
name: colleague-lookup
description: Looks up a colleague by name, department, job title, or phone number across the company directory and the authenticated RingEX Phone user's personal contacts, disambiguating when more than one match is found. Use when the user asks for someone's extension, title, department, or availability, or wants to find a colleague in the directory or their own contacts.
---
# Colleague Lookup
## Goal
Answer "who is this person / how do I reach them" quickly and correctly, being explicit about
which pool of data an answer came from — the company directory is not the same thing as the
user's personal address book, and the two tools that read them accept different selectors.
## Trigger examples
- "What's John's extension?"
- "Is Sarah available right now?"
- "Find Ada Lovelace in the directory."
- "What team is Priya on?"
- "Do I have a personal contact saved for +1 415 555 1234?"
- "Who's the manager of the support department?"
## Scope boundary
- Read-only lookup. This skill never edits, adds, or removes a contact or directory entry — there
is no such tool exposed on this server.
- `resolve_directory_person` (company directory) only accepts a `name`, `department`, or `role`
(job title) selector — it does **not** accept a phone number. `search_my_contacts` (personal
address book) accepts `name` or `phone_number`. If the user gives a phone number and wants to
know whose it is, this skill can only check the personal address book — say so rather than
implying a directory-wide reverse lookup exists.
- Presence (availability) is only returned by `resolve_directory_person` when the selector
resolves to exactly one exact match — never guess at someone's presence from an ambiguous match
or a department/role roster. When the first call can't return presence for that reason, this
skill proactively resolves the specific person by exact name afterward so presence can still be
shown by default — see the Workflow below.
## Workflow
1. **Classify the query.** Determine whether the user gave a name, a department, a job title
("role"), or a phone number.
2. **Name query.** Call `resolve_directory_person` with `{ "kind": "name", "value": "…" }` and
`includePresence: true` — presence is a default part of this skill's answer, not something the
user has to ask for separately.
- Single exact match → presence comes back on this same call; use it directly.
- Multiple candidates → disambiguate using a structured multiple-choice control as the
preferred method whenever the client provides one and there are 2–4 candidates: one option per
candidate, each labeled with its distinguishing detail (department/title, and phone number
if titles/departments collide). Only fall back to a plain-text ranked list when
a structured control isn't available or there are more than 4 candidates. Once the user picks
one, issue a follow-up `resolve_directory_person` call with
`{ "kind": "name", "value": "<that person's exact full name>" }` and `includePresence: true`
to fetch their presence — the first, ambiguous call never carries presence, so this
follow-up is required, not optional.
- No match in the company directory → fall back to `search_my_contacts` with
`{ "kind": "name", "value": "…" }` in case it's a personal contact rather than a colleague,
and say clearly which pool the result (or lack of one) came from. Note that
`search_my_contacts` never returns presence, regardless of match count.
3. **Department or job-title query.** Call `resolve_directory_person` with
`{ "kind": "department", "value": "…" }` or `{ "kind": "role", "value": "…" }` — "role" means job
title, not an administrative permission. This typically returns a roster of more than one
person, which never carries presence. Present the roster rather than picking one arbitrarily;
if the user then singles out one person from thPreview of the first 4,000 characters. Read full instructions →
communications-brief5.84 KB
View saved version →
---
name: communications-brief
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.
---
# Communications Brief
## Goal
Help the user prepare for the day (or catch up after time away) by reviewing personal RingEX
Phone communications over a window they choose, and turning them into a prioritized action report.
Focus on what needs attention, not on exhaustively listing every record.
## Trigger examples
- "Give me my communications brief."
- "Give me my daily communications digest."
- "What did I miss in RingEX?"
- "Summarize my calls, texts, and voicemails since yesterday morning."
- "What communications do I need to follow up on today?"
- "Show me unresolved calls, SMS, and voicemail from the past week."
- "Catch me up on my phone since last Monday."
## Workflow
1. **Ask how far back to look before pulling any data.** Don't assume a fixed window — the right
lookback depends on when the user last checked in. Ask using a structured choice control if the client provides one
(plain text otherwise), offering:
- Last 24 hours
- Last 3 days
- Last week
- Other (let the user specify, e.g. "since last Wednesday" or an explicit date range)
For "Other," interpret whatever the user gives you into a concrete date range before continuing.
2. **On a "Last 24 hours" choice, check for gaps a strict 24-hour window would miss.** These two
checks only apply to the 24-hours case — the longer windows already cover this ground:
- If today is Monday, a straight 24-hour lookback starts Sunday morning and misses Friday
evening and the weekend, which likely haven't been triaged yet. Ask: "Since it's Monday,
want me to also include the weekend (from Friday evening) so nothing from Friday or the
weekend slips through?" If yes, move `dateFrom` back to Friday evening (or Friday morning if
the user prefers the full day).
- Separately, ask: "Was there a holiday in the last few days that should be included too?" The
skill has no calendar access, so rely on the user's answer. If yes, ask which day(s) and
extend `dateFrom` to cover them.
These two checks are independent — the user may say yes to one, both, or neither.
3. Convert the final window to ISO-8601 date-times with offset for `dateFrom`/`dateTo`.
4. Call `get_my_call_activity` (`dateFrom`, `dateTo`) for recent inbound, outbound, and missed
calls, total talk time, and outstanding callbacks.
5. Call `get_my_communication_inbox` (`dateFrom`, `dateTo`, `messageTypes: ["SMS"]`) for recent
text messages.
6. Call `get_my_communication_inbox` (`dateFrom`, `dateTo`, `messageTypes: ["VoiceMail"]`) for
recent voicemail records.
7. Use `get_my_message_detail` (`messageId`) when a specific SMS or voicemail needs its full body
or verified transcription to understand the action item. Use `get_my_sms_thread` (`messageId`,
`dateFrom`, `dateTo`) when the full back-and-forth of a text conversation is needed for context.
8. Use `resolve_directory_person` (company directory, by name/department/role) or
`search_my_contacts` (personal address book, by name/phone number) only when useful to identify
a caller or contact. For Team Chat person resolution, use RingEX Chat's `find_person` instead —
`team_messaging_get_person` no longer exists.
9. Use `get_my_phone` only when the user's own presence, business hours, or call-handling rules
help decide whether to cPreview of the first 4,000 characters. Read full instructions →
daily-communications-digest3.32 KB
View saved version →
---
name: daily-communications-digest
description: Produces a daily RingEX Phone communications digest from recent calls, SMS, voicemail, contacts, presence, and message-store data. Use when the user asks for a daily digest, morning briefing, catch-up report, missed communications, unresolved calls or texts, voicemail follow-up, or what to work on today.
---
# Daily Communications Digest
## Goal
Help the user prepare for the day by reviewing personal RingEX Phone communications from the last
24 hours and turning them into a prioritized action report.
Focus on what needs attention, not on exhaustively listing every record.
## Trigger examples
- "Give me my daily communications digest."
- "What did I miss in RingEX over the last 24 hours?"
- "Summarize my calls, texts, and voicemails since yesterday morning."
- "What communications do I need to follow up on today?"
- "Show me unresolved calls, SMS, and voicemail from the past day."
## Workflow
1. Use the past 24 hours by default unless the user gives a different time range.
2. Call `list_user_call_log` for recent inbound, outbound, and missed calls.
3. Call `list_message_store_records` with SMS-focused filters for recent text messages.
4. Call `list_message_store_records` with voicemail-focused filters for recent voicemail records.
5. Use `read_message_store_record` and `read_message_store_content` when voicemail or message
details are needed to understand the action item.
6. Use `search_directory_entries`, `platform_list_contacts`, `platform_read_contact`,
`read_extension_profile`, or `team_messaging_get_person` only when useful to identify people.
7. Use `read_user_presence` or `platform_read_user_presence_status` only when presence helps decide
whether to call, text, or defer.
8. Summarize patterns across all records before writing the report.
## What to identify
- Missed inbound calls without a later outbound call to the same person or number.
- Inbound SMS messages without a later user reply.
- Voicemail that has not clearly been addressed.
- Repeated contact attempts from the same person or number.
- Communications that mention urgency, deadlines, blockers, scheduling, customer issues, or needed
decisions.
- Follow-ups that can be batched by person, account, customer, or topic.
## Output format
```md
# Daily Communications Digest
## Top Priorities
- [Most important follow-up and why it matters.]
- [Second most important follow-up.]
## Unreturned Calls
- [Caller/contact] called at [time]. Action: [call back, text, defer, or no action].
## Unanswered SMS
- [Contact/number] sent: [brief summary]. Action: [suggested response or next step].
## Voicemail Needing Attention
- [Caller/contact] left voicemail at [time]. Key point: [summary]. Action: [follow-up].
## Other Notable Activity
- [Useful context that is not urgent.]
## Suggested Plan
1. [Highest-priority response or call-back.]
2. [Next follow-up.]
3. [Lower-priority cleanup.]
```
## Guidance
- Be concise, practical, and action-oriented.
- Avoid dumping raw logs unless the user asks for them.
- Group related calls, texts, and voicemail from the same person together.
- State uncertainty when identity matching is unclear.
- Do not invent message contents, call outcomes, voicemail transcripts, or follow-up status.
- If tool results are empty, say that no relevant activity was found for the time range.
fax-inbox3.97 KB
View saved version →
---
name: fax-inbox
description: Presents the authenticated RingEX Phone user's fax inbox as a clickable list of recent faxes, then reads back the selected fax's sender, time, and cover-page text when available. Excludes SMS and voicemail, and cannot retrieve the fax document body itself. Use when the user asks to see their faxes, check for a new fax, or find out who sent a fax.
---
# Fax Inbox
## Goal
Give the user a browsable view of recent faxes — who sent one, when, and any cover-page text —
without making them dig through a phone app. This skill has a hard limitation worth stating
up front: no tool on this server can retrieve or OCR the actual fax document content, only
metadata and cover-page text. Be upfront about that rather than implying more access than exists.
## Trigger examples
- "Do I have any new faxes?"
- "Show me my fax inbox."
- "Who sent that fax this morning?"
- "Any faxes from this week I haven't seen?"
## Scope boundary
- Fax only. Never include SMS or voicemail records, even if the user says "messages" generically —
if they explicitly ask for SMS or voicemail, say this skill doesn't cover that and point to
`sms-inbox` or `voicemail-inbox` instead of quietly including it.
- Read-only. This skill never deletes, marks read/unread, or forwards a fax — there is no tool
exposed on this server for those actions.
- **Cannot read the fax document itself.** `get_my_message_detail` never returns attachment ids,
URIs, or binary/base64 content, and `get_my_communication_inbox`'s `keyword` filter only matches
fax cover-page text — it does not search the fax PDF/OCR content. If the user wants the actual
document contents, say plainly that this skill only surfaces metadata and cover-page text, and
suggest they open the fax directly in the RingCentral app or online account.
## Workflow
1. **Pull recent fax activity.** Call `get_my_communication_inbox` with `messageTypes: ["Fax"]`
(SMS and voicemail are separate `messageTypes` values and must not be requested). Default the
window to the last 14 days unless the user asks for a different range, and pass
`readStatus: "Unread"` only if the user specifically asked for unread/new faxes.
2. **Resolve sender names.** For each fax's sender number, try `search_my_contacts` (personal
address book) then `resolve_directory_person` (company directory); fall back to the raw phone
number if neither resolves.
3. **Sort and present as a choice.** Sort newest first.
- If there are 2–4 recent faxes, use a structured multiple-choice control, when the client
provides one: one option per fax, labeled with the resolved
sender name, with the timestamp (and page count, if the record includes one) as the
description.
- If there are more than 4, or fewer than 2 (zero or one), list them as a plain-text ranked
list instead — a multiple-choice prompt can't show more than 4 options, and a single fax
doesn't need a picker at all (just confirm and proceed to step 4).
- If nothing was found in the window, say so and offer to check a wider date range instead of
guessing at prior activity.
4. **Fetch the selected fax's detail.** Take the `messageId` of the chosen fax and call
`get_my_message_detail`. This returns metadata and, if the fax had one, cover-page text — never
the document's page images, PDF, or OCR'd body text.
5. **Render the result.** Show the sender (resolved name or raw number), the timestamp, and the
cover-page text if present. If there's no cover-page text, say so plainly, and remind the user
this skill can't surface the fax's actual document content — that requires opening it directly
in RingCentral.
## Guidance
- Never invent a fax's sender, timestamp, or cover-page text — if a field is missing, say it's
unavailable.
- Never imply the fax document itself was read, summarized, or searched — only metadata and
cover-page text are ever available through this skill.
-Preview of the first 4,000 characters. Read full instructions →
send-sms4.6 KB
View saved version →
---
name: send-sms
description: Sends a single person-to-person SMS on behalf of the authenticated RingEX Phone user, resolving the recipient, disambiguating the sending number, and confirming the exact message before sending. Use when the user asks to text someone, send an SMS, message a phone number, or reply to a text via RingEX Phone.
---
# Send SMS
## Goal
Send one personal SMS from a number the authenticated user owns, with the exact sender,
recipient, and message text confirmed before anything is sent. `send_sms` is a write tool and is
customer-facing and irreversible once delivered — this skill exists to make the required
guardrails automatic rather than optional.
## Trigger examples
- "Text John and tell him I'm running late."
- "Send an SMS to +1 415 555 1234 saying the meeting moved to 3pm."
- "Reply to that text from Sarah with 'sounds good, see you then.'"
- "Message +14085559876 on RingEX."
## Scope boundary
- This skill is for one-off, person-to-person texting only — never bulk, campaign, marketing, or
A2P messaging. If the request mentions "campaign," "bulk," "opt-out," "consent," "template," or
"brand," this is the wrong tool; tell the user this skill doesn't cover business/A2P messaging
rather than attempting a workaround.
- One recipient, one message, per invocation.
## Workflow
1. **Resolve the recipient's phone number.**
- If the user gave a raw phone number, use it directly in E.164 format.
- If the user named a person, resolve them first: try `search_my_contacts` (personal address
book), then `resolve_directory_person` (company directory) if not found there. Never
fabricate a phone number — if resolution is ambiguous or comes up empty, ask the user to
clarify or provide the number directly.
2. **Determine the sending number.**
- Call `get_my_phone` to see which of the authenticated user's numbers are SMS-capable.
- If there is exactly one SMS-capable number, use it without asking.
- If there are 2–4 SMS-capable numbers, ask which one to use with a structured
multiple-choice control, when the client provides one — one question
("Which number should this text be sent from?"), one option per number, each labeled with
the phone number and any friendly name/type (e.g. "Personal line," "Business number"). If
one number is clearly the user's primary/default, list it first and mark it
"(Recommended)."
- If there are more than 4 SMS-capable numbers, a structured multiple-choice prompt can't
list them all (max 4 options) — instead list the numbers as plain text and ask the user to
state which one to use.
- On a platform without a structured multiple-choice/button tool, fall back to listing the
numbered options as plain text and asking the user to pick one.
3. **Draft the exact message text.** Preserve the user's intended meaning and tone — don't
editorialize, expand, or add signatures/disclaimers they didn't ask for.
4. **Preview and confirm before sending — never send silently.**
- Echo back, verbatim: the sender number, the recipient number, and the exact message text.
- Wait for an explicit yes/confirm. A vague continuation of the conversation is not
confirmation.
5. **Send.**
- Generate a fresh UUID for `requestId`.
- Call `send_sms` with `senderPhoneNumber`, `recipientPhoneNumber`, `text`, and `requestId`.
6. **Handle the result.**
- On success, confirm briefly: who it was sent to, from which number, and the text.
- On failure, report it plainly. If the error suggests the number isn't SMS-capable, note
that this is usually a number-type or carrier registration (TCR/10DLC) issue on that
number, not something to retry blindly.
- On an unknown/ambiguous result (timeout, unclear response), tell the user the delivery
status is unconfirmed. Do not retry the same intended send with the same or a nePreview of the first 4,000 characters. Read full instructions →
sms-inbox5.37 KB
View saved version →
---
name: sms-inbox
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.
---
# SMS Inbox
## Goal
Give the user a browsable view of their personal text conversations: first a list of who they've
recently exchanged SMS/MMS with, then — once they pick someone — that conversation rendered like a
text-message stream. Voicemail and fax are never part of this skill. This is read-only; sending a
new message is a different skill (`send-sms`).
## Trigger examples
- "Show me my SMS inbox."
- "Who have I been texting recently?"
- "Open my text conversation with Sarah."
- "Show me that group text with the sales team."
- "Catch me up on my texts from this week."
## Scope boundary
- SMS and MMS only. Never include voicemail or fax records, even if the user says "messages" or
"inbox" generically — if they explicitly ask for voicemail or fax, say this skill doesn't cover
that instead of quietly including it.
- Read-only. This skill never sends, replies, marks read/unread, or deletes anything — hand off to
`send-sms` if the user wants to reply.
- A group text (more than one other participant) is its own distinct conversation. Never merge a
group thread into a participant's 1:1 thread just because they share a person, and never split a
group thread into separate per-person conversations.
## Workflow
1. **Pull recent SMS/MMS activity.** Call `get_my_communication_inbox` with
`messageTypes: ["SMS"]` (this covers both plain SMS and MMS text records — voicemail and fax
are separate `messageTypes` values and must not be requested). Default the window to the last
14 days unless the user asks for a different range.
2. **Group records into conversations.** A conversation's identity is the exact set of other
participants (phone numbers) on the message, not a single number:
- One other participant → a 1:1 conversation with that person.
- More than one other participant → a group conversation, keyed by that whole set. A group
thread with Sarah + Mike is a different conversation from a 1:1 thread with Sarah alone,
even though Sarah is in both.
- Sort conversations by their most recent message time, newest first.
3. **Resolve display names.** For each participant number, try `search_my_contacts` (personal
address book) then `resolve_directory_person` (company directory); fall back to the raw phone
number if neither resolves. Label a group conversation by joining participant names/numbers
(e.g. "Sarah Kim, Mike Chen"); if there are more than 3 participants, show the first two names
followed by "+N more".
4. **Present the conversation list as a choice.**
- If there are 2–4 recent conversations, use a structured multiple-choice control, when the
client provides one: one option per conversation, labeled with the
resolved name(s), with the most recent message snippet and timestamp as the description.
- If there are more than 4, or fewer than 2 (zero or one), list them as a plain-text ranked
list instead — a multiple-choice prompt can't show more than 4 options, and a single
conversation doesn't need a picker at all (just confirm and proceed to step 5).
- If nothing was found in the window, say so and offer to check a wider date range instead of
guessing at prior activity.
5. **Fetch the selected conversation.** Take any `messageId` belonging to that conversation and
call `get_my_sms_thread` (`messageId`, `dateFrom`, `dateTo`), oldest message first. If the
default window doesn't return at least ~10 messages, widen `dateFrom` further back (e.g. in
30-day steps) and re-fetch rather than presenting a thin conversation aPreview of the first 4,000 characters. Read full instructions →
voicemail-inbox3.88 KB
View saved version →
---
name: voicemail-inbox
description: Presents the authenticated RingEX Phone user's voicemail inbox as a clickable list of recent messages, then reads back the selected voicemail's caller, time, and verified transcription when available. Excludes SMS and fax. Use when the user asks to see their voicemails, check for new voicemail, read a voicemail transcript, or catch up on missed voicemail.
---
# Voicemail Inbox
## Goal
Give the user a browsable view of recent voicemails — who called, when, and what they said —
without making them dig through a phone app. This is read-only and text-based: there is no audio
playback, only the message's metadata and, when available, a verified transcription.
## Trigger examples
- "Do I have any new voicemails?"
- "Show me my voicemail inbox."
- "Read me that voicemail from earlier today."
- "Any unread voicemail from this week?"
- "What did Sarah say in her voicemail?"
## Scope boundary
- Voicemail only. Never include SMS or fax records, even if the user says "messages" generically —
if they explicitly ask for SMS or fax, say this skill doesn't cover that and point to `sms-inbox`
or `fax-inbox` instead of quietly including it.
- Read-only. This skill never deletes, marks read/unread, or replies to a voicemail — there is no
tool exposed on this server for those actions.
- Text-based only. There is no audio playback tool — never imply the assistant "played" anything;
it read the transcription.
## Workflow
1. **Pull recent voicemail activity.** Call `get_my_communication_inbox` with
`messageTypes: ["VoiceMail"]` (SMS and fax are separate `messageTypes` values and must not be
requested). Default the window to the last 14 days unless the user asks for a different range,
and pass `readStatus: "Unread"` only if the user specifically asked for unread/new voicemail.
2. **Resolve caller names.** For each voicemail's sender number, try `search_my_contacts`
(personal address book) then `resolve_directory_person` (company directory); fall back to the
raw phone number if neither resolves.
3. **Sort and present as a choice.** Sort newest first.
- If there are 2–4 recent voicemails, use a structured multiple-choice control, when the
client provides one: one option per voicemail, labeled with the
resolved caller name, with the timestamp (and duration, if the record includes one) as the
description.
- If there are more than 4, or fewer than 2 (zero or one), list them as a plain-text ranked
list instead — a multiple-choice prompt can't show more than 4 options, and a single
voicemail doesn't need a picker at all (just confirm and proceed to step 4).
- If nothing was found in the window, say so and offer to check a wider date range instead of
guessing at prior activity.
4. **Fetch the selected voicemail's detail.** Take the `messageId` of the chosen voicemail and
call `get_my_message_detail`. This may return a verified transcription; it never returns
attachment ids, URIs, or audio/binary content.
5. **Render the result.** Show the caller (resolved name or raw number), the timestamp, and the
transcription text if one came back. If no transcription is available for that voicemail, say
so plainly rather than guessing at the content or leaving the field blank without explanation.
6. **Offer to continue.** If the user was checking unread voicemail and more than one came back,
offer to go through them one at a time rather than dumping every transcription at once.
## Guidance
- Never invent a voicemail's caller, timestamp, or transcription content — if a field is missing,
say it's unavailable.
- Never fold SMS or fax into this view, and never claim to have played audio — this skill only
reads text-based metadata and transcription.
- Keep the voicemail list step fast and skimmable; save full transcription rendering for after a
voicemail is chosen.