One Inbox for 2–10 Listings: Who Answers Which Thread

Thomas Garner
Aug 18
12 min read

Updated: 6 days ago

White bedroom with a gray headboard and black-framed doors to trees

The 24-hour clock does not care that you have three listings. Airbnb scores the first reply on a thread, not on a brand, and a new inquiry on listing two does not wait because you were finishing a checkout note on listing one. A 2-10 book is a system of stays. Each stay starts a thread with its own clock. If nobody can say who is awake for that house, the thread dies at hour twenty-five and the listing keeps the miss. One inbox is a filing cabinet. It is not a watch.

This page is not a time-zone lecture and it is not a software stack. The clocks already exist. Listing response rate looks back thirty days at new inquiries and reservation requests answered inside twenty-four hours. Superhost uses a different twelve-month first-reply tape on homes you own. Stay issues run on three days, twelve hours, or one hour of local daytime, per stay. A small portfolio system should name who answers which thread this week. It should not add a second inbox that still has no owner.

A composite later in this essay is already common: three listings, one night watch, and a phone that lights up without saying which porch. That setup can work if the watch is named and the saved reply names the house. It fails when one person is the brand, the lock, and the after-hours answerer for every door. Write the watch the way you write roles on a small book. A name, a listing, a local hour. If you cannot say those three things, you do not have an inbox. You have a pile.

Clocks are per thread

A new inquiry is a new clock. So is a new reservation request. Follow-ups in a thread you already opened do not move listing response rate or response time. The first reply is the only reply that scores. That is true when you own one house. It is still true when you own eight. Airbnb does not average your brand. It asks whether this guest, on this listing, got a response inside twenty-four hours. Three listings can start three clocks before lunch. One inbox that treats them as one conversation will miss one of them.

Listing response rate is a thirty-day tape. It is the share of new inquiries and reservation requests you answered inside twenty-four hours on that listing. A decline counts. Letting a request expire does not. Superhost is a different tape: twelve months of first replies, plus accept or decline inside twenty-four hours, scored on the home listings you own. Do not mix them. A clean week can repair the thirty-day number. A clean week cannot repair a quarter you already spent quiet. Time-zone clocks already taught the windows. This page is who holds them when the inbox holds more than one house.

The stay clocks are stricter once a guest is close. If check-in is more than five days away, you have three days. Inside five days, ordinary stay issues run on twelve hours of local daytime. A time-sensitive access problem runs on one hour of local daytime. Those windows attach to the stay, not to the brand. A dead keypad on listing two does not wait because listing one is having a quiet week. Write the thread as a stay. Name the house in the first line. Then answer the clock that stay is actually on, not the clock you wish the brand had.

Who is awake for which listing

Name a person per listing for local daytime. Local daytime belongs to the pin, not to the city on your license. If two houses sit in one town, one watch can cover both porches. If the houses sit in two towns, you may have two mornings. Do not assume the owner is awake for every pin. Write the hours on a card the phone can see: this person takes listing A from seven to three on the pin, that person takes listing B, and nobody leaves a reservation request to die overnight. A decline still counts. Silence does not.

The cleaner is not the default answerer. Neither is the marketer. Answering is a job with a clock. Owner, cleaner, co-host, marketer are four jobs even when one body holds two of them. If the cleaner also answers, say which threads they may touch and which they escalate. If a co-host answers on a house they do not own, their replies can save your thirty-day rate on that listing. Those same co-host stays do not buy them Superhost. The badge still sits on the owner of the home listing. Write that on the watch so nobody is padding the wrong tape.

Two towns is two files for copy. It can still be one inbox if the watch is honest. Same-town versus two-market tells you whether the guest is comparing both tiles. The inbox question is whether the same person can hit both local daytimes. If they cannot, split the watch before you split the brand. Hiring the inbox is a clock hire when threads die, not a reason to buy a dashboard. Name who is awake. Then name who is the backup when that person is in a car. A listing with no backup is already late at hour twenty.

Saved replies that name the house

A saved reply that says the house is how a guest on listing two gets the code for listing one. Name the listing in the first sentence of every first reply. Name the town if you hold two markets. Name the access method that listing actually uses. Do not let a brand voice erase the noun. Guests do not book a portfolio. They book a porch. If the reply could be pasted onto any of your doors, it is not ready. Rewrite it until a tired night-watch person cannot send the wrong driveway.

Keep the library short enough that someone will open the right card. First reply to an inquiry. First reply to a reservation request. A decline that still answers the question. A same-day access fail. A checkout reminder that names this house's trash rule. That is enough for a 2-10 book. Do not build a novel. Do not store staff notes in a reply a guest will see. Guest-experience language belongs in the stay the thread is about. The other listings can stay out of the paragraph unless the guest asked about a second house you actually have in that town.

The host profile is allowed to be one voice. The thread is not allowed to be vague. Host profile work still has to match the person who will type inside twenty-four hours. A saved reply signed by a brand the guest cannot find on the listing is another kind of mash. Use the house name the title already uses. Use the access sentence the listing already published. If those two objects disagree, fix the listing before you polish the macro. A clever reply cannot save a thread that sends the wrong lockbox.

What not to automate

Do not auto-send check-in details for the wrong house. Do not auto-decline a reservation request because the inbox is loud. A decline counts as a response. An expire does not. Instant Book can cut the number of requests you have to accept by hand. It does not retire new messages, and it does not write the one-hour reply at the door. Automation is allowed to draft. A person still has to send anything that names a code, a gate, a parking pad, or a neighbor. Those nouns belong to one stay.

Do not automate Superhost. The badge looks at twelve months of first replies and at accept or decline inside twenty-four hours on homes you own. A bot that answers hello and then goes quiet still leaves you the stay clocks. A bot that accepts a request you cannot host still leaves you the cancel math. When the book outgrows DIY is a job question. It is not a prompt to wire every thread to a script. If a person cannot name the house, the script cannot either. Keep the human on first replies that change the stay.

Leave the one-hour access window in a human hand. Local daytime still means the listing's day. A keypad that fails at four on the pin is not a ticket for tomorrow morning on your phone. The night watch can hold a named backup, a spare lockbox sentence, and a number they are allowed to call. They should not hold a generic we will look into it. If you cannot staff that hour, do not publish an access method that needs it. Write a slower method you can actually keep, then tell the truth on the listing. A fake one-hour promise is worse than a lockbox with a named walker.

Composite: three listings, one night watch

A composite: two lake cabins in one county and one in-town apartment, one owner, one phone on the night stand. The cabins share a local daytime. The apartment may share the town or it may not. The night watch is one person who can answer a thread and cannot drive to three doors at once. That can work. Write what they may send: the named-house first reply, a decline, a hold-on-access sentence that names the local walker. Write what they may not send: a new code they invented, a refund, a promise that someone is ten minutes away when nobody is.

Give that person a card, not a vibe. Listing A, lockbox, walker Maya. Listing B, keypad, same walker. Listing C, in-town unit, downstairs neighbor on a paid text. If the night message is a new inquiry, the twenty-four hour clock is the one that matters and a named reply before bed will do. If the night message is a guest already on a porch, the one-hour local-daytime clock may already be running, or it will start at local morning. The watch should know which case they are in before they type. A Tuesday dashboard that cannot show which listing the thread belongs to is decoration.

The composite fails when the owner treats all three stays as one brand after dark. Saved replies that say our cabin go out to the apartment. The walker gets a text with no address. The thirty-day tape on listing C drops while listing A looks fine, and nobody notices until a quarter later. Split the watch on paper even if one body still holds the phone. Name the house in every send. Name the backup for the hour you will sleep. Three listings is still a system of stays. The night watch is how that system survives the hours you are not a brand.

430 vs 829 vs 2895 on a book

Article 430 is the thirty-day listing tape. Response rate is the percent of new inquiries and reservation requests answered inside twenty-four hours in the past thirty days. Response time is the average time to those new messages. Follow-ups in an existing thread do not move either number. On a 2-10 book you have one of these tapes per listing. A quiet listing can hide a loud miss on the house you launched last month. Read them apart. Each listing's numbers stay on their own line. A blended brand score hides a miss.

Article 829 is Superhost. It sits on the listing owner of a home listing, account in good standing. You need ten reservations, or three reservations totaling at least one hundred nights. You need a response to ninety percent of new messages, and to accept or decline new reservation requests, inside twenty-four hours. Cancellation rate has to stay under one percent except for published valid reasons and Major Disruptive Events. Overall rating has to sit at 4.8 or higher, counting when both sides review or when the fourteen-day window ends. Evaluation is every three months on the prior twelve months: January 1, April 1, July 1, October 1. All owned home listings on the account feed that one tape. Co-host stays on a listing you do not own do not.

Article 2895 is the stay map, and it is the one guests feel in the driveway. Three days when check-in is more than five days out. Twelve hours of local daytime for other stay issues inside five days or during the stay. One hour of local daytime when access is time-sensitive. Those windows apply per stay, not per brand. A book of three listings can be inside all three windows on the same afternoon. Superhost across owned listings is the badge math. 430 is the current watch. 2895 is the porch. Keep all three named. If your Tuesday list cannot tell them apart, you will fix the wrong clock and miss the thread that actually expires tonight.

Frequently Asked Questions

How should independents staff one inbox across 2-10 listings?

Name a person, a listing, and a local hour. Local daytime belongs to the pin, not to the city on your license. One watch can cover two houses in the same town. Two towns may need two mornings. Write a backup for the hour you will sleep. The cleaner is not the default answerer unless you put that job on paper. A first reply must name the house. If you cannot say who is awake for a thread, you do not have an inbox. You have a pile that will miss the twenty-four hour clock.

What do generic answers get wrong about multi-listing inboxes?

They treat the inbox as a brand and the clocks as one number. Airbnb scores threads, not companies. Listing response rate is a thirty-day tape per listing. Superhost is a twelve-month tape on homes you own. Stay issues run on three days, twelve hours, or one hour of local daytime per stay. Generic posts also sell software before a named watch. A second login will not decide who answers listing two at local 9 a.m. Then pick a tool that shows which house the thread is about.

When should I ignore a new inbox app and fix the watch first?

Ignore the app if nobody is named for local daytime, saved replies still say the house, and reservation requests expire because two people each thought the other had it. Software cannot invent a night backup or a sentence that names the right driveway. Write the watch card, the named-house first replies, and the escalate rules. Then choose a tool that keeps those objects in one place the answerer can open. A new login on top of a pile is just a prettier pile. The twenty-four hour clock will not care about the logo.

What is the difference between 430, Superhost, and the stay clocks?

Article 430 is listing response rate and time over the past thirty days on new inquiries and reservation requests. Follow-ups in an existing thread do not move it. Superhost uses a different twelve-month first-reply tape, plus accept or decline inside twenty-four hours, on home listings you own. Article 2895 is the stay map: three days, twelve hours, or one hour of local daytime, attached to the stay rather than the brand. A 2-10 book runs all three at once. Keep the three tapes on separate lines. An average is not the inbox.

Who should answer after dark on a three-listing book?

Name one night watch and write what they may send. A named-house first reply and a decline are safe. A new code they invented, a refund, and a claim that someone is ten minutes away are not. If the message is a new inquiry, the twenty-four hour clock is the one that matters. If a guest is already on a porch, the one-hour local-daytime window may be running or will start at local morning. Give them a card with each listing's access method and the local walker they are allowed to call.

Should saved replies mention every listing I own?

The thread is about one stay. Name that house, that town if you hold two markets, and the access method that listing already published. The host profile can be the one place both towns appear. A saved reply that could be pasted onto any door will send the wrong driveway. Keep the library short: inquiry, request, decline, access fail, checkout reminder. Do not store staff notes in a guest reply. If the guest asks about a second house you actually have in that town, answer that question. Do not advertise the rest of the book.

Do co-host replies protect Superhost on listings I do not own?

Co-host performance on a listing they do not own does not count toward Superhost for the co-host. If someone answers on your owned home, those replies can protect your thirty-day rate and your Superhost tape, because the badge sits on the listing owner. If you only co-host a friend's condo, those stays do not feed your badge. Write the watch so nobody is padding the wrong tape. Answering is still a clock job. Superhost is still an owner tape. Keep those facts on the same card.

What is optional versus mandatory on a multi-listing inbox?

Mandatory: a named answerer per listing for local daytime, a backup for the hours you sleep, first replies that name the house, and a human on anything that sends a code or an access promise. Mandatory also means you accept or decline requests inside twenty-four hours instead of letting them expire. Optional: Instant Book, extra macros, a second app, and a brand voice in the signature. Do not automate the one-hour access window. Do not auto-decline because the inbox is loud.

Work with Crest & Cove Creative

Stop letting one Inbox for 2–10 Listings stay vague on the live listing.

Bring the current listing and the page that is supposed to do this job. We will rewrite one Inbox for 2–10 Listings so it matches what is actually true on the tile. Reach out at crestcove.co or (256) 998-7502.