CloudTalk
CloudTalk v0.3.2
Phone system for AI and humans
From the developer
Declared capabilities
- Read
- Write
Cost & access
CloudTalk does not sell products or process payments in this plugin.
Declared limitations
- Unsupported payment
- Unsupported deletion
- Access outside the connected account
Onboarding example
Who called yesterday that we missed, and who should we call back first?
Sources & dates
Developer declarations; not independently tested. Listing last checked Nov 18, 2026. Package observed Nov 18, 2026.
Description
From the marketplace listing
Build an AI Voice Agent that answers your support line and calls your customers, then see every call it handled. Give your team what it needs to resolve and close: who called, who is waiting for a callback, and how your agents and queues are doing. CloudTalk is the agent-first phone system: AI agents answer first, humans close. AI Voice Agents. Build and update agents, with the knowledge bases and tools they use to answer questions, and send one to call a customer for a reminder, a confirmation or a follow-up. Your phone system. Search every call by agent, number, tag or sentiment, watch your queues live, and start a call or send an SMS from your CloudTalk numbers. Conversation Intelligence. Get the summary, sentiment, topics and action items of any call, and find the calls with unhappy customers, open requests or risks. Your customers. Look up anyone's full call history, add notes and tags, and create or update contacts. Agent-first outbound sales campaigns. Your AI assistant builds a campaign from your contact tags, starts it once you approve, and reports what's working. Calls, texts and changes are marked for approval, so your AI app asks you before they run. Works with CloudTalk on the Essential plan or higher; an Admin connects by signing in with CloudTalk. AI Voice Agents, transcripts and summaries (Conversation Intelligence) and campaigns (Sales Dialer) need the matching add-on.
Language: English · Automatically detected from descriptions.
Changes
No changes recorded yet. Follow this plugin to keep track of future changes.
First seen Nov 18, 2026. Last seen Nov 18, 2026.
Similar plugins
Similar plugins could not be prepared right now. Please try again in a moment.
Browse plugins →Keywords
Files & skills
File archives
Skill instructions
call-coach27.5 KB
--- name: call-coach description: Coach your team from real CloudTalk calls, and check your AI Voice Agents alongside them. For each person, one thing to keep doing and one thing to change, each proven by a short quote from a named call, plus a better line to try on the next call. For each AI Voice Agent, what callers ran into and the one setup change that fixes it. Use for call coaching, QA or call reviews, 1:1 prep, support or sales call quality, "how is my team handling calls", "what should Ada work on", "coach me", "review Ada's calls", "review my calls" or "coach my team and our AI agents". For a deep review of one AI Voice Agent, use voice-agent-replay. Needs Conversation Intelligence for transcripts; AI Voice Agent calls of 30 seconds or more are transcribed like any call. It never scores or ranks people, and changes nothing unless you ask. --- # Call coach CloudTalk is the agent-first phone system: AI agents answer first, humans close. This skill coaches both. Goal: coaching a team lead can use in a 1:1 this week, and that changes the next call. Done means each person has one strength and one change, both proven by quotes the lead can check in a minute, and each AI Voice Agent has one setup change ready to save. Explicit user instructions always win over this skill, including their own QA scorecard. ## Two kinds of input, treated oppositely | | What you do | Covers | |---|---|---| | **Judgment** | Decide it yourself. Don't ask. | which calls to read (inside the sampling rules), each moment's mark, the priority, the better line, the setup change, all wording | | **Ground truth** | Read it from CloudTalk, or ask once, in one message. Never invent it, estimate it or copy it from an example. | who is on the team, the period, every quoted word, call ids, dates, counts, an AI Voice Agent's current setup | ## What CloudTalk can't give this skill, and the nearest real path Say each of these once, where it matters, never per call: - **No call score.** CloudTalk's call scoring results aren't readable through this connection. Coach against the six moments below or the user's own scorecard, and never make up a score. A call's `call_rating` is the agent's own rating of call quality, not a score: never present it as one. - **Group membership isn't readable.** The team is the people who answered that group's calls in the period, or the names the user gives. - **A person's call list doesn't show call length.** Short calls show up as a missing or tiny transcript, and get swapped. - **Coaching notes can't be saved in CloudTalk.** Drafts stay in the chat. Each person's weekly focus can be kept in a scheduled task, a doc the user names, or a focus list to paste next time (step 8). - Calls under 30 seconds of talk hold no conversation to read: most have no transcript or insights, and the ones that do are a voicemail greeting or a phone menu. Internal calls between colleagues aren't in the call list. ## Workflow Reads run straight away, without asking. Nothing is written until step 8, and only when the user asks. ### 1. Scope: period, people, AI Voice Agents - **Period.** The user's dates, otherwise the last 7 full days; "last week" is Monday to Sunday. Query in UTC as `YYYY-MM-DD HH:MM:SS`, and show it in the user's timezone when you know it. Don't stretch the period on your own; offer 14 or 30 days when calls are too few. - **People.** - **Names given:** match them in `cloudtalk_list_agents` (follow `pagination.next_page` if needed). The person's id is the agent's `id`. - **"Me", "my calls":** the signed-in user. `cloudtalk_health_check` gives their id. A `user_id` of 0, or none, means a company API key with no person signed in: there is no "me", so ask once which person or team to coach. Otherwise `cloudtalk_list_agents` with `id` set to it gives their name. Not an agent: say they have no calls of their own to coach, and offer their team instead. - **A team or group given:** find its id with `cloudtalk_list_groups`, the
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 1 — file references are metadata, not package contents.
conversation-insights16.4 KB
--- name: conversation-insights description: Turn recent CloudTalk conversations into insights you can act on. It finds the open loops, meaning questions not answered, promises not kept, callers not called back and risks not handled, and says who should close each one, a person or an AI Voice Agent. Use when the user asks what needs attention, what's still open, what the team owes customers, who to follow up with, or for a daily or weekly call digest. It reads first and changes nothing until the user picks a loop to close, and it is not a call-volume report. Summaries need Conversation Intelligence; texts need a number with SMS enabled; callbacks need AI Voice Agents. --- # Conversation insights CloudTalk is the agent-first phone system: AI agents answer first, humans close. This skill reads recent conversations and turns them into open loops, meaning things still owed to a customer, each with who should close it. Goal: a short list a manager can clear in one sitting. Every loop points to the conversation it came from. Explicit user instructions always win over this skill. It reads first. Nothing is sent, tagged or changed while the list is built, and afterwards only the loops the user picks (step 6). ## Two kinds of input | | What you do | Covers | |---|---|---| | **Judgment** | Decide it yourself, without asking. | What counts as a loop, its urgency, who should close it, how to word it | | **Ground truth** | Read it from CloudTalk, or ask. Never invent it. | Who called, when, what was said or promised, which AI Voice Agents exist | A loop you infer is labelled as inferred. A next step nobody promised is labelled "Suggested". ## 1. Pick the period - Use the user's dates when they give them. Otherwise use the last 7 days, from midnight 7 days ago to now. - For "what's new since last time", start where the previous list ended, and say so. - Don't stretch the period on your own. Name it at the top in the user's timezone if you know it, plus the UTC times you queried (`YYYY-MM-DD HH:MM:SS`). > **✓ Gate:** one period, named with its exact start and end · no longer than the user asked for. ## 2. Look in three places 1. **Missed calls.** Call `cloudtalk_search_calls` with `status: "missed"`, `direction: "incoming"`, the period and `limit: 100`. Page with `page` while `pagination.next_page` is set, at most 6 pages; `pagination.items_count` comes on page 1 only, so keep that figure. Group the rows by caller (`external_number`, compared digit for digit). - A caller who tried more than once, or a known customer, may be a loop. Take at most 5, repeat callers first, and check each is still waiting. - A caller is **reached**, and not a loop, when an answered call with the same number, inbound or outbound, started after their latest miss and has a person on it (an `agent` on the row). Look in point 2's search with no filter first, never in the AI Voice Agent searches, whose `agent` is the AI. If those rows don't reach back to the miss, make one `cloudtalk_search_calls` with `public_external` set to their number, `status: "answered"`, `date_from` set to their latest miss and `limit: 5`. A row with a person on it means reached. A later answered call with no person on it, or our callback under 30 seconds of talk, keeps them as a possible loop: "answered without a person, may still be waiting" or "we tried to call back". A missed row with talk time (`talking_time` above 0) is usually a caller who spoke with an AI Voice Agent before a handoff nobody picked up: its summary often holds the loop. - For a known customer still waiting, call `cloudtalk_get_contact_interactions_summary` with `phone` set to their number in E.164, `max_calls: 20` and `sample_size: 2`, at most 3 per run. - Count the other missed callers under "Not covered", and offer `missed-call-follow-up` for them. 2. **Answered calls, by people and by AI Voice Agents.** Two searches over the period: `cloudtalk_search_calls` with `status: "answered"` and `limit:
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 1 — file references are metadata, not package contents.
get-started23.8 KB
---
name: get-started
description: Set up CloudTalk in this chat and show what it can do. Use right after CloudTalk is installed or connected, when the user asks what CloudTalk can do or how to start, or when a CloudTalk tool fails or returns nothing and the user doesn't know why. Checks the connection, finds what the account has (AI Voice Agents, call insights, texting, campaigns), and offers up to three first tasks that work on this account.
---
# Get started with CloudTalk
CloudTalk is the agent-first phone system: AI agents answer first, humans close. One place to run every call.
Goal: take the user from "connected" to a first useful answer in one or two turns. Done means the user has run one real task on their own account and knows which skill to use next. Explicit user instructions always win over this skill.
## Two kinds of input
| | What you do | Covers |
|---|---|---|
| **Judgment** | Decide it yourself, without asking. | Which three tasks to offer, how to word a summary, how to rank callers or calls |
| **Ground truth** | Read it from CloudTalk, or ask. Never invent it, default it, or copy it from an example. | Who the user is, what the account has, names, numbers, dates, what was said on a call |
People don't know their account's internal ids. Never show a company id, user id or tool name in what the user reads.
## 1. Check the connection
**No CloudTalk tools in this chat** (`cloudtalk_health_check` isn't available): CloudTalk isn't connected yet. This is normal right after install. Say so in one line, give the step for this app, and stop:
- Claude app: open Customize, then Plugins, open CloudTalk, go to its Connectors tab and choose Connect.
- Claude Code: run `/mcp`, pick the CloudTalk entry (`plugin:cloudtalk:cloudtalk`) and choose Authenticate.
- ChatGPT: open CloudTalk in ChatGPT's app settings and connect it.
- Grok: open CloudTalk in Grok's plugin settings and sign in.
Then add: "Sign in with CloudTalk as an Admin. CloudTalk's AI connection needs the Essential plan or higher." End with: "Say done once you've signed in, and I'll pick up from here." If CloudTalk still fails to connect after sign-in, the reasons are the ones under "It fails" below.
Otherwise call `cloudtalk_health_check`.
- **It succeeds:** find out who is signed in. If its `user_id` is above 0, call `cloudtalk_list_agents` with `id` set to it and greet the user by name and email in one line: "You're connected to CloudTalk as Jana Novak (jana@acme.com)." If the lookup finds nobody, say only "You're connected to CloudTalk." A `user_id` of 0, or none, means CloudTalk is connected with a company API key and no person is signed in: skip the lookup, say only "You're connected to CloudTalk.", and offer nothing that needs a signed-in person ("my last call").
- **It fails:** explain the cause in plain words, from the error, and stop. Retry at most once.
- Not signed in, or the sign-in expired: reconnect CloudTalk in the app's connector settings and sign in as a CloudTalk Admin.
- The error says the plan needs public API access (Essential or above): "CloudTalk's AI connection needs the Essential plan or higher. An Admin can change the plan in CloudTalk."
- The error says the account is not active: "This CloudTalk account isn't active right now. An Admin can check the account and billing in CloudTalk."
- The error says the account could not be verified: "CloudTalk couldn't confirm your account just now. Try again in a few minutes, and contact CloudTalk support if it keeps happening."
Never ask the user to paste a CloudTalk API key, password or sign-in code into the chat. Connecting always happens in the app's settings.
> **✓ Gate:** the connection works, or the user knows the one step to fix it · the greeting names a person and an email, or no one · no id appears in the reply · no API key, password or code was asked for.
## 2. Find what this account has
These are reads, so they run without asking. Make them in parallel when the appPreview of the first 4,000 characters. Read full instructions →
Referenced files: 1 — file references are metadata, not package contents.
missed-call-follow-up37.1 KB
--- name: missed-call-follow-up description: Make sure no missed caller or unanswered text waits. Finds today's missed CloudTalk calls (or those since the last run) and inbound texts nobody answered, drops anyone the team has reached since, and puts first callers an AI Voice Agent left waiting for a person and anyone past the user's response time. Names an owner for each and drafts a short text back from their history. Sends only what the user approves, rings the user's phone to call back now, or hands routine callbacks to an AI Voice Agent. Can run on a schedule, keeping the list in the app; for delivery to Slack or email, use missed-call-digest where it is available. Use when the user asks who called and didn't get through, who is waiting for a call back or a reply, to text back missed calls, or for a daily missed-call or inbound-lead digest kept in the app. For everything still owed after answered calls, use conversation-insights. Sending needs a number with SMS enabled; callbacks need AI Voice Agents; summaries need Conversation Intelligence. --- # Missed call follow-up CloudTalk is the agent-first phone system: AI agents answer first, humans close. A missed call is a customer left waiting, and so is a caller the AI Voice Agent promised a person. This skill closes that gap the same day. Goal: every caller missed in the period, every caller an AI Voice Agent left waiting for a person, and every inbound text nobody answered ends up in one of these places, and the user can see which: reached already, texted, called back by the user, queued for an AI Voice Agent callback, held until business hours, skipped on the user's say, or counted as likely noise. Explicit user instructions always win over this skill. This is same-day action on missed calls and unanswered texts. If the user wants the week's open loops from answered calls too, hand over to `conversation-insights`. ## Saved settings Every setting is optional; without them the skill covers the whole account, today. Collect them only when the user asks for a scheduled digest or names a scope (step 8), and save them into the scheduled task so a run never needs to ask again. Show them back in one line at the top of each list. | Setting | What it changes | Default | |---|---|---| | **Lines or teams** | Only missed calls to these groups (`group_id` from `cloudtalk_list_groups`, at most 5) or numbers (from `cloudtalk_list_numbers`) count, for example the sales lines. With a scope saved, the AI Voice Agent check in step 3 covers only the agents the user names as answering those lines | every line | | **Texting agents** | Whose SMS inbox counts for "already texted", opt-outs and unanswered texts (step 3), from `cloudtalk_list_agents`, at most 8. With a scope saved, pick the people on those teams | the signed-in user; none when signed in with a company key (`user_id` 0) | | **Reply line for texts** | The company line that answers unanswered texts on scheduled runs, which can't ask (step 5). Must have `sms_supported: true` | none: a scheduled run drafts the reply and leaves the line to pick when sending | | **Response time** | When a caller or text becomes overdue: a duration the user types (1 hour, 4 business hours, 1 business day) | none: no overdue marking | | **Schedule** | When scheduled runs happen | none | Never default a response time. A scope by number costs one `cloudtalk_get_call` per caller (the call log can't filter by the line called): prefer groups, and with numbers read at most 30 callers per run, oldest first, saying how many were left unread; the next scheduled run picks them up (step 1). ## Two kinds of input, treated oppositely | | What you do | Covers | |---|---|---| | **Judgment** | Decide it yourself. Don't ask. | the ranking, the wording of each draft, which reply suits each caller (a text, a call now, an AI Voice Agent, or a person later), the language when the evidence shows it | | **Ground truth** | Read it from CloudTalk, or ask, all in one messag
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 1 — file references are metadata, not package contents.
voice-agent-builder30.3 KB
--- name: voice-agent-builder description: >- Build, fix, or check a CloudTalk AI Voice Agent: its v2 "Expert Mode" configuration. Connected to CloudTalk, it creates, reads and saves the agent directly against your real account (numbers, knowledge bases, tools, transfer targets; every save needs your approval, and a change to an existing agent can be undone); offline, it returns the JSON you paste into the dashboard's Advanced/code tab. Use whenever the user wants to create or edit ANY inbound or outbound AI voice/phone agent for CloudTalk, for any use case or industry (reception, qualification, support, booking, surveys, reminders, notifications, lead capture and more; these are just examples, not the limit), or asks for an AI Voice Agent config, a goalPrompt/greeting/scenarios/skills, or pastes an existing config to review, edit, or reuse. Produces a behaviorally-sound, save-ready config that reuses the agent's existing setup, and runs a structural + behavioral validator first. license: Apache-2.0 --- # Build an AI Voice Agent (v2 Expert Mode) Turn a use case — plus a few facts only the user can supply — into a **save-ready AI Voice Agent v2** JSON config. **Two modes, one contract.** If the CloudTalk MCP tools (`cloudtalk_*`) are available, you are **connected**: read the agent with `cloudtalk_get_voice_agent` instead of asking for a paste, resolve account IDs with the `list_*` reads, and save through the write tools, each of which the app asks the user to approve (`mcp-tools.md`, `generator-contract.md` *Connected mode*). Otherwise you are **offline**: the user pastes their config, you return JSON for the dashboard's Advanced/code tab, and the save is an edit (`PUT`). Offline, the agent the user made in the UI is usually a **blank shell to unlock Expert Mode**: generate the config **fresh** for the use case and carry over **only** its environment/wiring (the outbound number + any real IDs) — never its prompt, skills, or behavior. The same holds connected when you rebuild an agent that exists. The output must be **behaviorally sound, not just schema-valid**. **Goal:** an AI Voice Agent that does the job the user described, saved after their approval or ready to paste, with nothing invented. **Done** means the configuration passes the validator (or the by-hand check), every save was approved, and the user knows the one next step. Explicit user instructions always win over these defaults. **Needs:** AI Voice Agents on the account and a CloudTalk Admin sign-in when connected; nothing offline. **Budget:** a build or fix is a handful of reads and one save, far under the account's 60 requests a minute, shared with colleagues. On a rate-limit error, wait a minute if the app can, then continue where you stopped; if it can't, stop and ask the user to say "continue". Never retry in a loop. **Connected, and no agent exists for this job yet** (the list has none that fits, or the user asks for a new one): **create it for them** with `cloudtalk_create_voice_agent`, after one plain-words summary of what it will do and the app's approval. Never send the user to the dashboard to make a blank agent first; that path is for offline use only. A create is a full document: every required field (`mcp-tools.md` *Write safety*) and the outbound number completed (step 1). ## Two kinds of input — treat them oppositely | | What you do | Covers | |---|---|---| | **Design** | **Author it.** Don't interrogate; a complete request needs no interview. | tone, task flow, guardrails, scenarios, the `extractData` proposal, numeric/voice tuning, provider/LLM | | **Ground truth** | **Obtain it — never invent, default, or copy from an example.** Connected: **fetch it** (numbers, transfer targets, KBs, tools, the agent's own document). Offline: ask. | the business's **real name** (spoken in `greeting`, always asked, never fetched), **real IDs** for any referenced feature explicitly requested (transfer target, KB, calendar, …), and an **o
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 24 — file references are metadata, not package contents.
voice-agent-checkup19.8 KB
---
name: voice-agent-checkup
description: >-
Check whether a CloudTalk AI Voice Agent is ready to go live, and what to fix first. Reads the agent's
setup, its knowledge bases, custom tools and phone numbers, then checks the greeting, the instructions,
handoffs to people, knowledge, numbers, languages, how calls end, the call length cap and what the
platform itself flags. Returns a verdict (Ready, Needs work or Don't go live), each finding with one
concrete fix, the tests to run and a go-live checklist. Use when the user asks "is my AI agent ready",
"can we go live", "check, review or audit my voice agent", "pre-launch check", "what's wrong with my
agent's setup", or right after building or changing an agent. Changes nothing (a test call goes only to your own phone, when you ask): fixes go to the
voice-agent-builder skill. Needs AI Voice Agents on the plan and a CloudTalk Admin sign-in.
---
# AI Voice Agent checkup
CloudTalk is the agent-first phone system: AI agents answer first, humans close. Before an AI Voice Agent
takes real calls, check it the way a careful manager would.
Goal: one verdict, the one fix to make first, and the tests that prove the agent works. Done means the user
knows what blocks launch, what to change, and what stays a dashboard step. Explicit user instructions always
win over this skill. It only reads; the one write is a test call the user asks for, to their own phone.
## Two kinds of input, treated oppositely
| | What you do | Covers |
|---|---|---|
| **Judgment** | Decide it. Don't ask. | which areas pass, each finding's severity, the order of fixes, the wording of each fix, which tests fit |
| **Ground truth** | Read it from CloudTalk, or ask in one batch. Never invent, default or copy it from an example. | which agent; its setup and every id in it; whether each knowledge base, tool, number and transfer target exists; what the agent is for (from its instructions); whether it runs inside a Call Flow (ask only when it hands off to one); the number for a test call (the user's own, never picked from a list) |
A finding you can't tie to a setting you read is a guess: leave it out. A fix that needs a value you don't
have (a group's extension, a calendar) says where the user gets it, never makes one up.
## References: load on demand
They ship beside this skill in `../voice-agent-builder/`. Read the section a check names; don't recite it.
| File | Read it for |
|---|---|
| `behavioral-guidance.md` | What performs: instructions (§2), transfers (§3.4), hangups and call length (§4), direction rules (§6), knowledge (§7), model and speech (§7a-bis to §7c), the §8 self-check. |
| `schema.md` | Field meanings and dependency rules (§2, §3), languages per provider (§4.3), provider, model and `optimizedSettings` (§5), skills (§6), scenarios (§7). |
| `referenced-resources.md` | What each knowledge base, tool, transfer target, number and SMS sender needs to work, and where the user fixes it. |
| `mcp-tools.md` | The two AI Voice Agent ids, paged lists, what has no tool. |
| `variables.md` | Any `{{variable}}` in the greeting, instructions or an SMS. |
| `practice-call.md` | The practice call in chat (step 6): how to play the agent, the plain-words score, and the label it carries. |
## Workflow
### 1 · Pick the agent
- **No CloudTalk tools in this chat:** ask the user to paste the agent's config from the dashboard's Expert
Mode (the Advanced/code tab), run steps 3 to 5 on it, and mark knowledge bases, tools and numbers as not
covered. To check those too, they connect CloudTalk in the app's connector settings and sign in as an
Admin. Never ask for an API key, password or sign-in code.
- **Connected:** `cloudtalk_list_voice_agents` with `limit: 200`; follow `pagination.next_page` before
saying an agent doesn't exist. A row's `voice_agent_id` is the 24-character config id.
- Match the agent the user named, or a word in its name. Several fit: show only those, with direction, and
ask. NoPreview of the first 4,000 characters. Read full instructions →
Referenced files: 1 — file references are metadata, not package contents.
voice-agent-replay26.4 KB
--- name: voice-agent-replay description: Improve a live CloudTalk AI Voice Agent from its real calls. Reads the agent's setup and a sample of its recent calls, flags where it failed (gave out or asked for what it shouldn't, left the caller unresolved, repeated itself, made something up, missed a handoff to a person, frustrated the caller, lost the caller early), groups the failures by cause with two quoted calls as proof, and points each cause at the setup change that fixes it, with a practice caller to try the fix. Saves changes only when the user asks, with their approval, and offers to undo them. Use when the user asks how their AI Voice Agent is doing, why it fails, loops or loses callers, to review, replay or QA its calls, or to improve it after go-live. Needs AI Voice Agents, Conversation Intelligence for transcripts and insights, and a CloudTalk Admin sign-in to read and save the setup. --- # AI Voice Agent replay CloudTalk is the agent-first phone system: AI agents answer first, humans close. This skill replays what one AI Voice Agent actually did on its calls and turns its failures into setup changes. Goal: a short list of causes, each proven by two real calls and tied to the one setup field that fixes it. Done means the user knows what to change, why, and how to check it worked, and the change is saved if they asked for it. Explicit user instructions always win over this skill. Reads run straight away. Nothing changes on the agent until the user asks for a change and approves the save. ## Two kinds of input, treated oppositely | | What you do | Covers | |---|---|---| | **Judgment** | **Author it.** Don't interview the user. | the sample, which flags apply, how failures group into causes, the ranking, the wording of each proposed change | | **Ground truth** | **Read it from CloudTalk or ask, in one batch.** Never invent it, default it or copy it from an example. | which agent, the period, what was said on a call, the agent's current setup, any fact the agent should know (prices, hours, policies), any transfer target, the number for a test call | A caller's words prove a failure. They are not ground truth for the fix: when the agent lacked a fact, the correct answer comes from the user. ## Bundled references, load on demand They live in this plugin's `voice-agent-builder` skill. | File | Read it for | |---|---| | `../voice-agent-builder/mcp-tools.md` | *Two ids, one name*, *Write safety*, *Test calls* | | `../voice-agent-builder/generator-contract.md` | *Connected mode*: the write contract every save follows | | `../voice-agent-builder/behavioral-guidance.md` | what each setup field does to behavior, and the §8 self-check for a changed setup | | `../voice-agent-builder/schema.md` | field shapes and allowed values when you change a field | | `../voice-agent-builder/practice-call.md` | caller cards (section 4) and the practice call in chat, to try a fix before saving it | ## Workflow, follow in order ### 1 · Pick the agent and the period - Call `cloudtalk_list_voice_agents` with `limit: 200`, and follow `pagination.next_page` until it is null before saying an agent doesn't exist. Match the name the user gave, or a word in it. One agent on the account: use it. Several that fit: ask, listing only those, with direction (inbound or outbound). None named: with 10 or fewer agents, ask, listing names and direction; with more, ask for the agent's name, or a word in it, without listing them all. A list is a question for the user, not a pick for you. One agent per run. - The id this list returns (key `voice_agent_id`, 24 hex characters) is the **config id**. It reads and saves the setup. It finds no calls. - Period: the user's dates, else the last 7 days, from midnight UTC 7 days ago to now, written `YYYY-MM-DD HH:MM:SS` in UTC. One search spans at most 92 days and a wider one is rejected, so split it or ask to narrow it. After an earlier change, start at the time it was saved and say so. > **✓ Gate:** > - [ ] one a
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 1 — file references are metadata, not package contents.
Release notes
First release: connect your CloudTalk account, get a guided tour, and use skills for missed calls, call insights, coaching and AI Voice Agents.
Declared in the saved package. Remote tools may change independently.
Package details
Publisher declarations from the archived package. These are separate from our research and the live service's terms.
- Package license
- Apache-2.0
- Package author
- CloudTalk
- Keywords
- See keywords
- Listing translations
- de-DE, es-ES, fr-FR, nl-NL, pt-PT
- Getting started skill
- ./skills/get-started/SKILL.md
- Commerce declaration
- Does not support commerceThis does not establish whether access is free or paid.
- Review scenarios
- 5 positive · 3 negativeScenario counts, not test results.
Declared capabilities
- Read
- Write
Package observed Nov 18, 2026.
Technical details
- First seen
- Nov 18, 2026 · 06:00 UTC
- Last seen
- Nov 18, 2026 · 06:00 UTC
- Collection status
- Collected
plugin_asdk_app_6afa18ff1c508191a265852ce504fb3f
Download plugin data (JSON)Plugin details: freshly prepared. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.