Skip to navigation

Owner verification, unpaid number release, and Connectors (experimental)

  • Account: to buy a phone number, create an API key or invite a teammate, the account owner now needs a verified email and a verified phone number. Signing in with Google or Apple counts as a verified email. You need a verified email before you can verify a phone number.
  • Account: sign-up, sign-in, password reset and verification-code requests now include a Cloudflare Turnstile check.
  • Account: the dashboard no longer shows a cookie banner. Whether Talkif may report your sign-up, first call, phone number or payments to the ad platform that brought you is a setting of its own, under User menu → Preferences → Privacy → Ad measurement. It is off unless you turn it on. From November 15, 2026 it stays opt-in in the EU/EEA, the UK, Switzerland and Turkey and is on by default elsewhere; a choice you made always wins. See Privacy Policy §14.4.
  • Telephony: a number whose rental stays unpaid is suspended and, after 14 days of suspension, released back to the carrier — you lose the number. You get a notice 3 days before the release. A top-up that covers the rental before then reactivates it. See Buy a number.
  • Telephony: accounts younger than 30 days can hold at most 2 rented numbers. (Later replaced by limits based on payments — see the November 2, 2026 entry.)
  • Builder: the assistant can save changes to a flow from any page, not only the flow canvas. It never overwrites edits made after it last read the flow. See Assistant.
  • Builder: from chat, the assistant can create, pause, resume and delete alert rules for people in your account, and contact support for you. See Assistant.
  • Builder (experimental): Connectors let a voice agent reach tools you link to your account during a call — your coding-assistant sessions, knowledge sources or other agents — to ask them questions, look things up or give them tasks. An owner or admin turns Connectors on under Developer → Integrations after reading and accepting its terms; then add a Connectors node to a flow.
  • API: an API key must have at least one scope. A create request without scopes is refused instead of creating a key with full access. Existing keys are unchanged. See Authentication.
  • API: API keys can call only the endpoints in the public API definition. Dashboard-only endpoints answer an API key with 403 api_key_not_allowed. The browser-call endpoints the WebRTC SDK uses (/calls/webrtc/…) are part of the public definition. See Error codes.