Short-Term Rental Operations

Key takeaways

  • Ask for the animal type, size, and stay dates in one structured request.
  • Route service and assistance animals through the fair-housing path, not the pet fee.
  • Show the owner the guest request, the property rule, and the cost before asking for a yes.
  • Record the approval scope so a later request cannot inherit it silently.
Talk through the executive workflow that needs clearer ownership.

Bring the recurring tasks, handoffs, and access boundaries you want dependable support to manage.

Talk with our team

Operating data

Primary workflowShort-Term Rental Operations
Reading time5 minutes
Internal next steps2 links
External citation1 source

Playbook

Why pet requests stall in the inbox

A pet request looks simple until the coordinator tries to answer it. The guest wants a yes today, the owner may be traveling, and the listing text rarely covers size, breed, or the number of animals. If the coordinator answers from memory, two guests with similar requests can receive different terms. A written exception path turns a scattered conversation into a decision the owner can review once and the team can apply consistently.

Begin by separating pets from service and assistance animals. A service animal is not a pet, and many fair-housing rules treat assistance animals differently from ordinary pet fees or restrictions. The coordinator should ask what the animal does for the guest only when the answer changes the process, and should not demand medical documentation on the spot. When the request falls into that category, route it to the property manager and the site's fair-housing guidance instead of quoting a pet fee.

Collect one complete request

Ask for the animal type, approximate size, number of animals, and the exact stay dates in a single structured message. Add the guest's proposed sleeping arrangement and whether the animal will be left alone in the unit. These details affect cleaning time, furniture protection, and the neighbor conversation more than the breed label does. A complete request also gives the owner something concrete to approve rather than a vague heads-up.

Attach the current property rule to the request before anyone evaluates it. The rule should state whether pets are allowed, any size or count limit, the fee, and the areas that are off limits. If the listing and the house manual disagree, pause the request and fix the source first. Quoting one document while the guest has read another creates a dispute that no amount of friendly wording can settle.

Give the owner a decision, not a debate

Prepare a short decision packet with the guest request, the property rule, the estimated cleaning impact, and the recommended answer. The owner should be able to approve, decline, or approve with conditions in one reply. Include the exact fee and the conditions that would change it, such as an additional animal or a longer stay. A packet that fits on one screen gets answered faster than a long thread with attachments.

Name a deputy before the owner becomes unavailable. The deputy can approve requests that fall inside the published rule and must escalate anything that changes the fee, the occupancy, or the property's insurance position. Record the deputy's authority and its expiry so a temporary arrangement does not become permanent by accident. When nobody has authority, the honest answer to the guest is a short delay, not a guess.

Talk through the executive workflow that needs clearer ownership.

Bring the recurring tasks, handoffs, and access boundaries you want dependable support to manage.

Talk with our team

Use a script that keeps the boundary visible

A useful reply thanks the guest, repeats the request in one sentence, and states what happens next with a time. It should not promise approval before the owner has decided, and it should not imply that a pet fee guarantees acceptance. If the answer is yes with conditions, list the conditions in the same message the guest will keep. If the answer is no, give the rule that applied and one alternative if the property has one.

Keep the same script for declines and approvals so the team does not drift into persuasive language under pressure. The goal is a clear record, not a debate the coordinator cannot win. A guest who understands the rule is less likely to argue at check-in, and the owner sees a consistent process rather than a series of special favors. Review the script quarterly against actual requests and tighten any phrase that caused confusion.

Work through a typical request

A guest booking a three-night stay asks to bring a fifteen-pound dog and offers to pay the listed fee. The coordinator confirms the property allows one dog under twenty pounds, attaches the rule, and notes that the cleaner needs an extra thirty minutes. The owner approves with the standard fee and a condition that the dog is not left alone during the first night. The coordinator sends one message with the fee, the condition, and the checkout reminder.

Two days later the guest asks to add a second dog. The coordinator does not extend the first approval, because the property rule covers one animal and the cleaning window was built around one. The request goes back to the owner with the new detail and a revised estimate. The guest may still receive a yes, but the record shows a fresh decision instead of a quiet expansion of the original terms.

Review the exception path

Pull five pet requests each month and check whether the rule, the owner decision, and the guest message agree. Include at least one decline, because approvals alone do not show whether the boundary works. Look for requests that were answered verbally, fees that were waived without authority, and animals that appeared at check-in without a record. Assign one fix and a retest date, then leave the note beside the property file for the next coordinator.

Related services

- Guest communication - Contact us

Sources

- HUD assistance animals guidance

Talk through the executive workflow that needs clearer ownership.

Bring the recurring tasks, handoffs, and access boundaries you want dependable support to manage.

Talk with our team

FAQ

When should a leader delegate this workflow?

Delegate it when repeated coordination, routing, or follow-up is taking time away from decisions that only the leader can make.

What should the assistant own first?

Start with intake rules, status visibility, and escalation timing so the assistant can act consistently before the workflow expands.