Does every listing need its own AI co-host?

No. One AI co-host covers a portfolio the same way one good assistant does: a single mailbox hears about every house, and the sorting happens on arrival. We run exactly this shape on a live operator mailbox — several listings, one mail rule, one place to approve replies — so the answer below is a description, not a plan. The parts that must stay separate, stay separate: every house keeps its own fact sheet, and a guest asking about house A is never answered from house B's facts. What multiplies when you add a door is the facts, not the setup.

One mailbox, every house

Guest-message notifications from all of your listings already land in one inbox — yours. The AI taps that stream with a single mail rule, the same one-minute rule setup uses for a single house: any mail from the booking platform is redirected to the service's ingest address. Nothing about that rule names a listing, so the tenth house costs the same mailbox work as the first — none. The work moves to the question that actually matters at portfolio scale: which house is this message about?

Sorting is done with evidence, not vibes

Each arriving message is matched to a house using only evidence in the mail itself: the listing id, a thread the system has matched before, a confirmation code, or the exact title of a listing it knows. Thread ids and confirmation codes are remembered only after a message has been positively placed — never learned from a guess. When evidence conflicts, or a title matches two houses, the message is held and written up instead of routed to the likelier one, because at portfolio scale a confidently wrong answer — the right gate code for the wrong house — is the expensive failure. Mail that matches nothing is set aside with a note to you, unanswered.

The facts never blend

Each registered house gets its own fact sheet, built from that listing's public page, and a reply about a house draws on that house's sheet alone. There is no portfolio-wide pile of facts for an answer to fish from. That is also why the per-house cost of adding a door is the same two-minute job it is for a single host: read the new house's sheet once, confirm the check-in time and the quirks are right, done.

You can leave a house out

A portfolio is rarely uniform — one house is being renovated, one owner wants hands-on handling, one is your own place. Exclusion is a first-class setting, not a workaround: a listing can be registered as excluded, its messages are ignored on purpose, and the exclusion is sticky — it stays until you explicitly lift it, so a later bulk change can't quietly opt the house back in. The first portfolio mailbox we wired had exactly this shape: one of the listings was registered excluded from day one, and the system has dropped its mail ever since.

What stays singular

Approvals don't multiply either. Held drafts from every house arrive in the same inbox, and the same one sender — you, from your account's address — approves each one with a word. Ten houses do not mean ten dashboards or ten logins; they mean more drafts through one door you already watch. If you manage doors for owners rather than for yourself, the portfolio side of this — policies per owner, per-door pricing — is laid out on the property-managers page.

If you want to see the per-house part before wiring anything, paste one listing into the demo at /try — it builds that house's fact sheet and answers from it alone, which is the whole trick, repeated once per door.