2026-11-20 · ← News
Gemini gets a phone line as Duplex handles calls, but Europe is left waiting
Google has integrated Duplex into Tasks in Gemini, letting the agent call businesses, wait on hold, and arrange appointments. The free rollout covers six countries outside Europe, and the real test will be the experience of the people answering those calls.
The image could not be loaded.
Google has integrated its nearly decade-old Duplex technology into Tasks in Gemini. A user can ask the agent to call businesses, compare available times, and add the result to a calendar. The free rollout covers the United States, Japan, Korea, Canada, Australia, and India, but not the European Union.
Duplex has moved from fixed bookings to free-form Gemini tasks
The original Duplex from 2018 handled narrow scenarios such as restaurant reservations. Google later deployed LaMDA and a hybrid architecture that paired generative language with deterministic state management. The current system uses Gemini for understanding, planning, and conducting a call from a free-text instruction.
Google gives an example in which Gemini calls two car dealerships in parallel, waits on hold, finds a conflict-free calendar slot, and records the booking. Each call opens with a disclosure that an automated Google system is calling. Businesses can opt out in their Google Business Profile or ask the system to stop calling during a conversation.
The phone extends agents to businesses without APIs
Many local services still accept requests only by phone. Duplex turns the telephone into an integration layer for a restaurant, repair shop, or salon that does not need to install software or change its workflow. For the user, Gemini crosses the boundary between recommending an action and completing it.
Google has an unusual advantage here: Search and Maps know the businesses, Calendar knows the user's availability, and Gemini can connect the request with personal context. Google says information gathered through Duplex calls had appeared in Search and Maps more than one trillion times by 2023. That is not a call count, but it indicates the scale of the infrastructure behind the feature.
User convenience can become another queue for staff
Google tunes for sub-second latency, noisy phone lines, and natural turn-taking. Technical fluency does not settle the operational problem. A receptionist may have to negotiate with several agents at once, repeat conditions to a machine, or repair an error while the customer is absent. Automation costs can shift from the user to the business.
Google itself acknowledges that Tasks can fail or miss the mark. Availability is another limit: the base rollout covers six countries, while some advanced features begin only in the United States. Users in the Czech Republic and the rest of the EU cannot enable Gemini calling yet.
Declined calls and repaired bookings will decide the outcome
A count of completed tasks is insufficient. Google should disclose how often businesses decline calls, how many bookings require correction, and how frequently a human must take over. Opt-out rates will matter too, because they show whether the feature saves businesses more time than it consumes.
The next signal will be expansion beyond the first six countries and reliable operation across languages and legal regimes. Until evidence extends beyond Google's own examples, Duplex is impressive telephone infrastructure. It becomes a trusted personal assistant only when the receptionist on the other end is not paying for the user's convenience.
Lilith's verdict
The user sends Gemini on a phone errand and walks away. Google wins only if the receptionist, after the third agent call, is not hunting for a switch that disconnects the whole building.