Skip to content

Product2 publishers3 min readPublished Updated

Brian Chesky places Airbnb's next AI search somewhere between a chatbot and the version that just shipped

Airbnb CEO Brian Chesky calls this week's AI search a first version and says the next three to six months go to exploring interfaces groups can share. Any team putting AI into a shopping flow now faces the same unsettled interface question.

The Product Desk · Product desk

Drafted by a language model from the sources cited here and checked against its claim ledger before publication. How we use AISend a correction

Photograph accompanying Brian Chesky places Airbnb's next AI search somewhere between a chatbot and the version that just shipped
Photo: techcrunch.com

What happened

  • Chesky says chatbots handle browsing and shopping poorly because they show a few options at a time and make users take several turns to reach a result.
  • He expects apps to mix pre-designed screens with generative ones an AI builds on the fly, an approach startups Monogram and Wabi are testing.
  • For outside AI agents, Chesky says they will either hand users back to Airbnb or need a fuller SDK that brings Airbnb's features to them.
  • He says chatbots have proven good at lead generation, easing fears that AI tools would cut Airbnb out of the customer relationship.

Compiled by The Product DeskSomething wrong?How this is made

Why it matters

  • decision Airbnb's CEO calls what shipped a first version, so teams have no settled pattern to copy and should expect their own first AI interface to be replaced.
  • constraint Catalogues people browse for pleasure lose the most in a chat-only design, since it limits how much a shopper can see and compare in one turn.
  • exposure If outside agents only hand off, the customer relationship rests on each handoff reaching the company's app; an SDK puts more of the experience on the agent's screen.
  • constraint Teams citing Airbnb to justify skipping a chat window have a CEO's argument to point to, with no published booking or retention results behind it yet.

The chatbot shopper, as Brian Chesky describes him, says "Book me a flight, I don't want to look at it." [4] Chesky says Airbnb's guest is a different shopper. "With Airbnb, they enjoy looking at the product," he told TechCrunch [4]. He supports that with a claim about travel research. "Travel studies show that people actually derive more pleasure in planning and anticipating travel than they do traveling. So you don't want to take the inspiration and the browsing and the library experience of dreaming away," he said [5].

Here is what Chesky says users do: they browse because they like browsing, and they plan with family and friends [5][6]. Here is what a chat window assumes they do, by his description: one person works through a few options per turn until a result arrives [2][6]. The interview does not include usage, booking or retention figures for the new search, so the only evidence so far for Airbnb's design is Chesky's account of his own customers [15].

Chesky calls the current search unfinished. "I think what you're seeing today is also not the endgame for e-commerce or for travel or shopping," he said [3]. He declined to call the destination a midpoint, then put it between a chatbot and "what you see in the first version we shipped" [3]. He also rejects the opposite outcome, where every app ends up as a data feed for one general assistant. "I don't believe in a world where the apps become data layers of a universal simple UI," he said [14]. "Our interfaces should be adaptive to the utility and the function that we're doing," he added [13].

Chesky wants Airbnb to be more agent-friendly. He said that will take software infrastructure on Airbnb's end [9]. He listed what a guest who arrives through an outside agent might still want from Airbnb itself: good browsing, messaging the host, comparing, verifying identity, a map, and adding other items [11]. "We want to make our app more agentic, and we want to build a lot more user interface controls," he said [10].

His two objections to chat make a grid that any team can place a task on [1]. One axis asks whether the shopper wants to look or wants it done. The other asks whether one person decides or several. The flight booker sits in the solo, get-it-done corner, where chat or an agent fits [4]. Chesky puts Airbnb in the solo, looking corner. AI can run the search there, but the screen has to stay a place to browse [4][5]. The group trip is the looking-together corner, and Airbnb has put it on its own list to explore [7]. A group that wants it done needs an approval step, so several people can sign off on one booking before anyone is charged.

The second test covers agents. Sort the steps on Chesky's list into the ones an outside agent can finish and the ones that have to happen on the company's own screen [11]. Each step in the second group needs one of the two routes he named: a handoff back to the app, or an SDK that carries the feature into the agent [11].

What to watch

  • Whether Airbnb publishes booking or retention results for the new search, which would test Chesky's claim that guests want to browse.
  • Whether the group-planning interface Airbnb is exploring ships as a pre-designed screen or one an AI generates on the fly.
  • Whether agent companies build the SDKs Chesky describes or default to handing users back to apps like Airbnb's.
Loading claim ledger
Loading source directory links
Loading share composer
Loading topic controls
Loading related stories