← Back to Guides

Set Up Your AI Receptionist with ChatGPT or a Compatible AI Assistant

Connect KestrelVoice to the AI assistant you already use — describe your business, review suggested settings, and approve every configuration change before it applies.

The model in one paragraph

Your AI assistant talks to KestrelVoice over a secure OAuth connection at https://kestrelvoice.com/api/mcp. It can read your status and prepare changes — but every change to your configuration produces an exact diff that only you can approve while signed in. Approval links expire, and the durable record of what was approved and applied lives in your dashboard under AI Approvals.

ChatGPT

App submitted — listing under review
  1. Open the Kestrel Voice app inside ChatGPT and choose Connect.
  2. ChatGPT sends you to KestrelVoice — sign in with Google OAuth using the account that owns your workspace.
  3. Grant the requested scopes (mcp:read to read status, mcp:write to prepare changes).
  4. Ask ChatGPT to read your configuration or prepare a change.
ChatGPT showing a live readback of the saved receptionist configuration — business name, agent name, greeting and status
ChatGPT reads back your real saved configuration — not a mock.
The KestrelVoice approval page showing an exact JSON diff of a proposed greeting change with Approve and apply and Approve only buttons
Every receptionist and workflow change stops on the approval page for human review of the exact diff — a preview record is saved, but no configuration changes.

Claude

Setup guidance — not yet verified end-to-end

KestrelVoice implements standard OAuth 2.1 discovery, dynamic client registration and PKCE, so standards-compliant remote MCP clients should connect. Claude's flow has not been verified end-to-end yet — follow these steps and report any issue.

Individual account

  1. Go to Customize → Connectors → Add custom connector.
  2. Name it “Kestrel Voice” and paste the remote MCP URL.
  3. Complete OAuth sign-in when prompted.

Team / Enterprise

  1. An organization owner adds the connector under Admin → Connectors.
  2. Each member still authorizes their own KestrelVoice account — access is per-user and per-workspace.

Other MCP clients

Any client supporting remote Streamable HTTP MCP with OAuth can connect using the same URL. Only the ChatGPT connection is verified today; Cursor, Claude Code and similar clients are unverified setup guidance.

Remote MCP server URL

https://kestrelvoice.com/api/mcp

Authentication: OAuth 2.1 + PKCE with dynamic client registration. Never paste a KestrelVoice API key or OAuth access token into a chat client.

What it can and can't do today

Supported

  • Read account, subscription, onboarding and readiness status
  • Read your saved receptionist configuration
  • Analyze your business website into a reviewable draft (extracted content is untrusted until you approve it)
  • Preview receptionist changes as an exact diff with an approval link
  • Preview and configure existing workflow templates
  • Check phone number, E911 and inbound-call readiness
  • Search available US numbers and save an area-code or exact-number preference before checkout
  • Retrieve your website-chat embed snippet

Not supported

  • Place or receive live phone calls from the assistant
  • Purchase phone numbers, start checkout, or charge your account
  • Access another customer’s workspace
  • Apply any configuration change without your explicit approval

Calls, leads, voice selection and usage tools are planned for v2 — the assistant will honestly decline them today.

The approval lifecycle

1

Preview

The assistant prepares an exact diff — current value vs proposed value — and a time-limited approval link. A durable preview record is saved for audit; no configuration changes.

2

Human approval

You open the link while signed in. Only the team member who made the request can approve it.

3

Apply

Approve & apply on the page, or return to the assistant to retry — either path requires the durable approval.

4

Verified record

The applied result is recorded against the action and visible in AI Approvals, alongside failed and expired requests.

Troubleshooting

The assistant says it can’t see my account▼
Sign out of both services and reconnect — expired OAuth sessions are the most common cause. Confirm you signed in with the account that owns the workspace.
My approval link expired▼
Links are time-limited for safety — including already-approved changes. Ask the assistant to prepare the change again, or find it under AI Approvals in your dashboard.
The assistant prepared a change but won’t apply it▼
That’s by design — a human must approve the exact diff first. Open the approval link or the AI Approvals page. Simpler writes like saving a number preference don’t need this step.
A change shows "needs review"▼
An apply timed out with an uncertain outcome. Compare the recorded diff against your live settings before requesting a new preview.

Every change needs a human

Your assistant drafts; you decide. See the workflow end-to-end in the demo.

Watch the demo Create an Account