Review request timing and response volume research visual

Guest Feedback

Published

Review request timing and response volume

A measurement protocol for post-stay review requests, with send timing, channel ownership, stop rules, and the distance between requests sent and reviews received.

The useful measure is the share of checkout stays that receive exactly one review request, and the share of requests that lead to a review within the property's stated window.

Methodology

  1. The unit of analysis is one completed stay and the review request tied to it. A case enters the population when the reservation reaches checkout and the property sends at least one request through its own channel. A stay that ends in cancellation before arrival is excluded. Each case carries the property, the checkout date, the channel, and the person who owns the request.
  2. The observation window opens at checkout and closes at the end of the property's review window, such as fourteen or thirty days. A review that arrives after the window is recorded separately rather than counted as a response. The reviewer does not extend the window to capture a late review that followed a second request. This keeps the measure tied to the first ask.
  3. Request count is coded as zero, one, two, or more. A reminder is counted as a second request even when it uses the same template. The reviewer records the send time for each message and the channel used. A request sent by the platform and a request sent by the property are different fields. The property is not credited for a platform message it did not control.
  4. Timing is measured in hours from checkout to the first request. The reviewer records the checkout time from the reservation and the send time from the message log. A request sent before checkout is coded as premature. A request sent more than seven days after checkout is coded as late. The two codes are reported separately because they represent different failures.
  5. Channel ownership is coded as platform, email, text, or mixed. A mixed case is one where the property used more than one channel for the first ask. The reviewer notes whether the guest had opted out of a channel and whether the property respected the preference. A request sent after an unsubscribe is coded as a consent failure. The reviewer notes whether the guest had already opted out.
  6. The message is coded for content: a plain ask, an incentive offer, a rating instruction, or a complaint response. A plain ask requests an honest review without naming a score. A rating instruction suggests a star level or asks for a five-star result. An incentive offer ties a benefit to the review. The reviewer records the exact wording of any instruction.
  7. Response is coded as a review received, a private reply, a decline, or no response. A private reply includes a guest who answers the message without posting a review. A decline includes a guest who asks not to be contacted. The reviewer records the review score when it is visible and the date it was posted. The score is not used to judge the request's honesty.
  8. The complaint path is coded by whether the guest raised an issue before the request. A case with an open complaint is marked unresolved. The reviewer records whether the property closed the issue before asking for a review. A request sent while a complaint is open is coded as a sequencing failure even when the guest later posts a positive review.
  9. Stop behavior is coded as stopped after one send, stopped after a decline, continued after a decline, or no stop rule. The reviewer records the date of the last message and whether the guest replied. A sequence that continues after a clear no is coded as a consent failure. The field is intended to show whether the property can hear an answer that is not a review.
  10. Sampling takes every eligible stay when the portfolio produces fewer than thirty cases in the window. Above that volume, the frame uses a fixed interval across properties and weeks, stratified by channel and by stay length. The frame is frozen before coding, and replacements are allowed only for a missing record. Small cells are suppressed in the summary. The frame is stored with the case list.
  11. Two reviewers code the first ten cases independently for request count, timing, and stop behavior. Disagreements are resolved by the guest-contact lead, who writes the rule used for the case. Reliability is reported as the share of matching fields. The guest is not contacted to reconstruct the sequence because the review measures the property record and the message log. The rule is stored with the case file.
  12. Limitations are stated before any recommendation. The sample is a local record set, not an industry rate, and a review is not proof that a request was well timed. A guest may post a review weeks later without any request at all. The report names one proposed change with an owner and a review date, and no association is described as causation.
  13. A final field records whether the guest received a service recovery before the request. A recovery message, a credit, or a repair confirmation is coded as present only when it is dated before the review request. This separates a request sent after a resolved issue from one sent while the guest was still waiting. The recovery date is compared with the request date.
  14. The reviewer also notes whether the property tracked the review in the same record as the stay. A review that lives only in a platform dashboard is coded as a record gap. The export path is recorded so the comparison can be repeated. The field tests whether the team can compare requests with outcomes without exporting data from several tools by hand.

Findings

  • Review requests are often sent by whoever finishes the checkout task, not by a named owner. The result is a mix of platform prompts, email templates, and manual messages that no one can count. The protocol assigns one owner and one channel for the first ask. A single owner makes the request easier to time and easier to stop. A named owner also makes the stop rule enforceable.
  • Timing is the most visible difference between a request that feels courteous and one that feels automated. A message sent while the guest is still packing may be read as pressure. A message sent a few days later can arrive after the trip has faded. The reviewed records suggest that checkout plus a short travel buffer is a better default than an immediate send.
  • Duplicate asks are common when a property uses both a platform sequence and its own email. The guest receives two requests for the same stay and may ignore both. The protocol counts each message and records the channel. A property that cannot see the platform prompt should not assume the guest has not been asked. The guest should not have to answer the same request twice.
  • Rating instructions undermine the value of the review. A guest who is told to leave five stars is being coached, not asked. The reviewed cases show that plain requests produce reviews the property can learn from, including mixed ones. A request that names a score also creates a record the platform may treat as manipulation. The reviewer stores the exact instruction when one is present.
  • Incentives are a risky shortcut. A discount, a gift card, or a contest entry tied to a review changes the guest's reason for writing. The protocol codes any incentive as a separate message type. The property should ask for feedback because it wants the truth, not because it is buying a rating. The record should show who approved the incentive.
  • Open complaints should block the request. A guest who is still waiting for a repair or a credit is not in a position to review the stay fairly. The protocol marks the case unresolved until the issue has a written close. A request sent during that wait often turns a private complaint into a public one. The request is held until the resolution is written.
  • A clear no should end the sequence. A guest who asks not to be contacted has given an answer, even if it is not the one the property wanted. The reviewed records show that continued messages after a decline produce more unsubscribes and more complaints. The stop rule should be visible to whoever sends the next automated message. The preference is stored where the next sender can see it.
  • The review rate is a useful measure only when it is paired with the request count. A property that sends three messages per stay may have a high review count and a low trust level. The protocol reports requests and reviews side by side. A single request with a modest response is often a healthier pattern than a campaign with a high response.
  • Reviews that arrive without a request are worth recording. They show that the stay itself produced feedback, not the message. The reviewer should separate organic reviews from requested ones. That distinction helps the owner see whether the request is adding information or only adding volume. The reviewer records the date and the channel for each organic review, and links each review to its stay.
  • A lukewarm review is a service signal. The protocol routes a mixed review to the person who can fix the underlying issue before the property replies. A generic public response that thanks the guest without addressing the problem does not close the loop. The fix should be visible in the next stay, not only in the reply. A reply that ignores the issue is recorded as an open loop.
  • The arrival team and the review owner should share the same record. A greeter who hears a complaint at the door may not tell the person who sends the request. The reviewed cases suggest that a short handoff note reduces the chance of asking an unhappy guest for a rating. The note does not need to be long, only timely.
  • The limits of the measure are important. A review is a self-selected signal, and a request that produces no review may still have been welcome. The sample is local and the cells are small, so the findings are operating hypotheses. The next cycle should test one change, such as a single channel and a fixed send window, before treating the pattern as settled.

Research standards

Every review freezes its observation window before findings are calculated. Reviewers retain a row-level evidence ledger with the original artifact reference, timestamp, responsible role, status at cutoff, correction history, denominator, exclusions, and unresolved cases. Ambiguous records are coded independently before reconciliation, and both readings remain visible until an accountable adjudicator applies a documented rule. Missing information is treated as unknown rather than silently classified as success or failure. Sensitivity checks remove major record classes in turn so a pattern that depends on one owner, channel, event type, or reporting cycle is disclosed instead of presented as stable. Elapsed time is not translated into labor, an association is not described as causation, and local observations are not converted into external benchmarks.

Interpretation begins with counterexamples and the cases still open at the cutoff. A formally complete record may lack usable evidence, while an authorized alternative path may achieve the intended outcome without matching the expected workflow. The review therefore states the strongest alternative explanation, identifies the additional artifact that could distinguish it from the preferred reading, and records what would reverse or retire the resulting operating rule. Comparisons use the same field definitions and equivalent work classes; a material change in coverage, tooling, policy, or sample composition creates a new baseline rather than a trend. Follow-up records name the decision taken, responsible owner, anticipated signal, review date, exception path, and evidence required before a stronger intervention can be justified.

Governance checks keep only information necessary for the research question. Sensitive content is replaced with a controlled reference whenever an authorized reviewer can reproduce the classification without holding a copy. Access boundaries, retention expectations, correction ownership, disputed-interpretation routes, duplicate handling, spanning-record rules, and cutoff treatment are documented before release. Absolute counts appear beside percentages, small samples avoid false precision, and every external statement links to a listed source without implying that the publication measured the local record set. The proposed action must be proportionate, reversible, and reviewable. If the available evidence cannot support it, the gap becomes an explicit evidence request rather than an assumption.

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

This research note supports the STR Virtual Assistant topical map for vacation-rental guest communication, property readiness, issue routing, and evidence-based operational follow-through.

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

Sources

  1. Manage your financesU.S. Small Business AdministrationChecked 2026-11-19
  2. American Housing SurveyU.S. Census BureauChecked 2026-11-19
  3. Housing topicsU.S. Census BureauChecked 2026-11-19
  4. Fair housing guidanceU.S. Department of Housing and Urban DevelopmentChecked 2026-11-19
  5. Rental income and expensesInternal Revenue ServiceChecked 2026-11-19
  6. Wage and hour guidanceU.S. Department of LaborChecked 2026-11-19
  7. Cybersecurity FrameworkNational Institute of Standards and TechnologyChecked 2026-11-19
  8. Resources and toolsCybersecurity and Infrastructure Security AgencyChecked 2026-11-19
  9. Emergency planningReady.govChecked 2026-11-19
  10. Recordkeeping guidanceInternal Revenue ServiceChecked 2026-11-19
Review request timing and | STR Virtual Assistant