Frequently asked questions.

Which channels are actually live today?

Voice (outbound + inbound, Twilio + Exotel) is live and tested end-to-end. The platform is voice-first by design — that is the focus.

Can I clone my own voice?

Post-launch (Pro tier). It's an ElevenLabs integration with a recorded-consent + KYC gate. Until then, pick from 6 English personas + 1 Hindi (Bulbul).

What languages are supported?

English (US/UK accents, 6 personas) and Hindi (Bulbul). Deepgram handles transcription in dozens of languages, so the model side scales; the bottleneck is voice synthesis. Add a language request via hello@callfunnel.ai — Cartesia ships new voices monthly.

Does the AI sound robotic?

Cartesia Sonic-2 is among the best real-time TTS on the market — most listeners think Skylar or Jacqueline is a human until the third turn. Pre-rendered objections (we have 65 cached MP3s) sound especially natural because they're not synthesised in real time. Listen to the demos on the homepage.

What does the ₹9 / $0.10 per-minute rate include?

The telephony leg (Twilio or Exotel), the LLM tokens (Claude Haiku turns + retrieval prompt), the STT seconds (Deepgram), and the TTS characters (Cartesia). One flat rate, rounded up to the nearest minute. No surcharge for inbound vs outbound, personas, or KB retrieval.

What happens when my wallet hits zero?

New outbound dials and messages block. The in-flight call finishes (we never hang up mid-sentence). You get a wallet-low email earlier, a wallet-exhausted email when it hits zero. Top up to resume.

Can I get a refund on my wallet?

Yes — unused bundled wallet balance is refundable minus payment-gateway fees (~2–3%), back to your original payment method, in 7–10 business days. Trial credit isn't refundable. Email billing@callfunnel.ai.

Can I switch between Bundled and BYOK?

Yes, any time. Your workflows, knowledge bank, and timeline stay; only the keys the orchestrator uses change. Saved BYOK keys go dormant on the bundled tier; reactivate by flipping back.

Are you DPDP / GDPR compliant?

Scaffolding is in place from day one: consent records per contact per scope, DSR export + erase in under 30 seconds, audit logs per tenant, data residency. Final terms of service review by counsel before general availability; until then, sign up with this in mind. Detailed model in security & DSR docs.

Where does my data live?

India tenants → Mumbai. US tenants → us-east. EU tenants → eu-west (post-launch). Picked at tenant creation; we don't move silently. Each tenant gets a dedicated Postgres schema, Mongo database, Qdrant collection, and Vault path — no shared rows.

Will the AI ever lie about being an AI?

No. The rule book validator rejects any workflow that instructs the AI to claim it's a human. If a customer asks "are you a real person?" the AI says no, names CallFunnel, and continues with the conversation. Honesty is enforced at the validator layer, not left to per-workflow discipline.

Can the AI invent discounts or refunds?

No. Below the concession threshold, the AI can only offer values the rule book explicitly authorises. Above it, the decision drops into Slack with the transcript and waits for a human. There's no path where the AI invents a number you didn't sanction.

When does the REST API launch?

Auth, onboarding, billing, numbers, DSR endpoints are live today. Workflow + campaign endpoints exist but are partly stubbed (dial loop wires up Phase 8). Full public REST API + outbound webhooks ship at launch (Pro tier). MCP endpoint ships post-launch.

Can I drive CallFunnel from Claude.ai?

Yes, via the hosted MCP endpoint (post-launch). Connectors → Add custom MCP, paste the URL + your tenant token, and Claude can place calls, send messages, read timelines, approve concessions. MCP docs.

Do you have a Zapier / Make.com integration?

Post-launch. Outbound webhooks land first (Pro tier), then the no-code connectors. If you have a specific Zap in mind, email us so we prioritise the right triggers + actions.

My test dial didn't connect.

Check: (1) wallet has budget (Dashboard → Billing), (2) outbound webhook configured at provider, (3) Twilio "Geographic Permissions" enables the destination region, (4) the number is verified as the From caller. Most failed dials map to one of these four.

BYOK key validation fails.

Read the error message in Dashboard → Onboarding — we surface the provider's actual response. Common: Anthropic key revoked at console, Twilio SID/auth-token mismatch, Cartesia key on the wrong account. Regenerate at the provider and re-paste.

Webhook isn't reaching my server.

Dashboard → Webhooks → Failures lists the last 50 attempts with response body. Common causes: signature verification mismatch (compute on raw body, not parsed), TLS cert issue, ngrok URL stale. We don't retry past 6 attempts over 38 hours; replay manually from the dashboard.