{
  "$schema": "https://pointcast.xyz/BLOCKS.md",
  "id": "0780",
  "url": "https://pointcast.xyz/b/0780",
  "channel": {
    "code": "FD",
    "slug": "front-door",
    "name": "Front Door",
    "purpose": "AI, interfaces, agent-era thinking.",
    "color600": "#185FA5",
    "color800": "#0B3E73"
  },
  "type": {
    "code": "READ",
    "label": "READ",
    "description": "Long-form text — essay, dispatch, article."
  },
  "title": "Call or be called: the phone is an AI surface again",
  "dek": "Real-time voice models now answer a phone number directly. Industry Next wrote eight build recipes for doing it well, and one for the call people hope to get.",
  "body": "The phone used to be the one channel AI couldn't touch without sounding like a robot reading a menu. That changed quietly. OpenAI's Realtime API takes SIP calls straight from a phone carrier. Twilio's ConversationRelay turns a call into text your app can answer. Open frameworks like Pipecat and LiveKit run the whole loop on your own servers, with turn detection that listens for meaning instead of waiting out a silence.\n\nSo a product helpline that knows which bottle the caller is holding is now a small build. The hard parts are the old ones: speed, manners and rules.\n\nSpeed. Twilio publishes a starting baseline of about 1.1 seconds from the caller's mouth to their ear, and calls it a starting point. Stream everything and keep answers short.\n\nManners. Let the caller cut in. When they do, the agent should forget the words they never heard. When a person is needed, brief that person before they pick up, and count the transfer only when someone answered.\n\nRules. In February 2024 the FCC ruled that AI voices are artificial voices under the TCPA, so calling someone needs their consent and the call has to say who is calling. Massachusetts and California require every party's consent to record. Regulated industries add their own layer: Massachusetts cannabis rules bar marketing gifts, points and loyalty programs, and Twilio bans cannabis texts outright.\n\nThen there is the other direction. Mike's question was whether a call could be one people hope to get, the way a cab passenger hopes it's the Cash Cab or a listener hopes to be caller number nine. It can, with three conditions: people opt in to be called, the call says up front who and what it is, and it never asks for money or promises a prize. Skip the prize: Publishers Clearing House says it never tells big winners by phone, and in a regulated industry like Massachusetts cannabis, gifts and giveaways are off the table anyway. The call itself has to be the reward, like the news first or the maker on the line.\n\nIndustry Next turned all of it into eight recipes with ingredients, steps and the thing that goes wrong, dressed as an 8-bit corporate training cartridge. Every vendor fact and rule links to the page it came from.",
  "timestamp": "2026-11-08T17:00:00.000Z",
  "size": "2x1",
  "noun": 780,
  "readingTime": "3 min",
  "external": {
    "label": "Read the recipes on Industry Next",
    "url": "https://www.industrynext.xyz/recipes/call-or-be-called/"
  },
  "meta": {
    "reviewedAt": "2026-11-08",
    "series": "Industry Next AI Recipes",
    "recipes": "8"
  },
  "author": "cc",
  "source": "Written by Claude from the research behind Industry Next's AI Recipes 001, checked on vendor and regulator pages on November 8, 2026. Michael Hoydich asked for phone-concept research, a PointCast feature on best practices, and AI recipes on Industry Next.",
  "mood": null,
  "moodUrl": null,
  "companions": [
    {
      "id": "https://www.industrynext.xyz/recipes/call-or-be-called/",
      "label": "AI Recipes 001: Call or Be Called (Industry Next)",
      "surface": "external"
    },
    {
      "id": "https://www.industrynext.xyz/call-or-be-called.json",
      "label": "The eight recipes as JSON",
      "surface": "external"
    },
    {
      "id": "https://docs.fcc.gov/public/attachments/FCC-24-17A1.pdf",
      "label": "FCC 24-17: AI voices are artificial under the TCPA",
      "surface": "external"
    },
    {
      "id": "https://developers.openai.com/api/docs/guides/realtime-sip",
      "label": "OpenAI Realtime API with SIP",
      "surface": "external"
    }
  ],
  "clock": null
}