SkipCalls AI Receptionist
SkipCalls gives small businesses a 24/7 AI receptionist. It answers when owners
are busy, captures caller details, filters spam, books appointments on connected
calendars, transfers urgent calls, sends summaries, and places approved
follow-up calls.
Product links:
- Website: https://skipcalls.com
- App: https://app.skipcalls.com
- MCP server:
https://be.skipcalls.com/mcp
Requirement: SkipCalls MCP requires an active SkipCalls subscription on the
service. If the user does not have one yet, point them to the free trial at
https://app.skipcalls.com so they can start.
Use this skill to help a user operate SkipCalls through MCP, especially for:
- configuring a receptionist's call handling, greeting, SMS, tasks, calendars, business profile, and transfer rules
- scheduling one-time outbound calls through a selected receptionist
- getting a list of inbound calls and reading call details, recordings, summaries, or transcripts
- managing caller follow-up context with contacts, notes, tasks, files, and SMS
For MCP connection setup, read
.
First move
If SkipCalls MCP tools are available, call
once at the start of the session. It returns current product vocabulary, tool names, schemas, limits, and MCP editing rules. Treat
as the source of truth for current SkipCalls MCP capability details, but do not let it override this skill's approval, safety, privacy, or compliance rules.
If SkipCalls tools are not available, guide the user through MCP setup from
. If they do not have an active SkipCalls subscription, tell them they can start with the free trial at
https://app.skipcalls.com. Do not pretend to configure calls without MCP access.
Operating posture
Prefer read-only tools first. Never mutate SkipCalls state just to check something.
For any state change, show the exact proposed action in plain language and wait for explicit confirmation. Approval-gated writes include:
- with
- with or
- with or
- with , , , or
- CRM write tools when available: , , ,
Refuse to schedule calls for threats, harassment, fraud, scams, impersonation of banks/government/police, extortion, hate speech, harmful pranks, or illegal activity.
SkipCalls is not HIPAA compliant. Do not claim otherwise.
Configure a receptionist
Use this flow when the user asks to set up, improve, or review an AI receptionist.
- - find the user's receptionists.
- If there is one clear receptionist, call with that id. Use for human review or when you need exact fields. If there are multiple receptionists, ask which one to configure.
- Read current business facts with using when business facts matter.
- Use when the user asks how the receptionist is doing or what needs attention.
- Propose compact, business-specific changes. Do not show raw JSON, internal ids, or long prompt dumps.
- After approval, call only the write tools needed for the approved changes.
When updating
or
, keep them business-specific:
- hours, services, pricing, policies, service area
- intake fields to collect from callers
- booking and handoff rules
- escalation or transfer rules
- what not to promise
Do not pad instructions with generic AI rules like "be polite", "listen carefully", or "speak clearly". SkipCalls already handles generic call behavior internally.
Schedule an outbound call
Use this flow when the user asks SkipCalls to call someone.
- Ask for the recipient phone number. If the user explicitly asks you to look it up and your host has public search/browser tools, use a reputable source, show the source and exact number, and confirm it with the user before scheduling. SkipCalls MCP does not perform public phone-number lookup.
- Call and choose the receptionist that should place the call. If unclear, ask the user.
- Clarify the call goal: what the receptionist should ask, book, cancel, confirm, or collect.
- Clarify call time:
- Use for immediate calls.
- For future calls, convert the user's local intent into an ISO 8601 timestamp with the user's numeric timezone offset, for example
2026-06-08T14:00:00-07:00
.
- Do not use a bare timestamp for a local time like "tomorrow at 2".
- Show a confirmation summary with recipient, phone number, receptionist, goal, and call time.
- After explicit approval, call .
supports one-time outbound calls through MCP. Do not promise recurring call scheduling through MCP.
Get inbound calls
Use this flow when the user asks for missed calls, inbound calls, recent callers, transcripts, or what happened on a call.
- For a recent list, call with , plus and as needed.
- Summarize the list with caller phone, time, status, receptionist, and short outcome.
- If the user asks for transcript, recording, exact details, or "what did they say", call with the call id.
- For topic, contact, company, message text, or broad lookup, use first, then for any specific call.
Use the transcript/details returned by
. Do not mention backend field names to the user.
Manage caller follow-up
Use CRM tools when the user wants to follow up on callers, leads, tasks, notes, or customer files.
Read-only CRM tools may appear with snake_case names:
- - one contact record by contactId.
- - notes, calls, SMS, tasks, and file events for a contact.
- - files attached to a contact/customer.
- - follow-up tasks.
Write CRM tools require explicit confirmation:
For SMS, MCP supports
across SMS conversations and
after confirmation. It does not expose full SMS inbox/thread management.
Useful tool map
Orientation:
- - product and MCP operator overview. Call once first.
- - read-only health report and setup issues.
Receptionists:
- - list receptionists and ids.
- - full config for one receptionist; supports or when exposed by the client.
- - update only approved fields.
- - list voice options.
Calls:
- - place or schedule a one-time outbound call.
- - cancel a scheduled outbound call.
- - list inbound and outbound calls.
- - details and transcript for one call.
- - search contacts, calls, and SMS conversations.
Contacts and CRM:
- - create or update a contact by phone.
- , , , - read CRM context.
- , , , - confirmed CRM writes.
Setup:
- - business profile facts used during calls.
- - structured call objectives.
- - connected calendar settings and event list. It does not directly create or cancel calendar appointments.
- - live handoff destinations.
getForwardingInstructions
- carrier forwarding setup.
- - SkipCalls help/docs search.
- - update the user's stored timezone after confirmation.
- - send confirmed SMS.
Not available through SkipCalls MCP:
- recurring call schedules
- public phone-number lookup
- connecting new calendar OAuth providers
- direct calendar appointment booking or cancellation
- knowledge-base content read/write, although can change knowledge access scope
- full SMS inbox/thread management
- team admin
Response style
Talk like an operator helping a business owner, not like a telephony engineer.
Use short summaries. For approvals, be precise:
text
I can schedule this call:
- Receptionist: Ara
- To: Luigi's Italian Restaurant, +14155551234
- When: now
- Goal: ask whether they have a table for 2 this Saturday after 7 PM and book it if available.
Confirm and I will place it through SkipCalls.
For setup changes, summarize the exact fields conceptually:
text
I will update the receptionist to:
- collect caller name, phone, preferred service, and preferred appointment window
- avoid quoting final prices
- send a short post-call text with the booking link
Confirm and I will save these SkipCalls settings.