Prepare a direct-booking refund request evidence packet

Reservation intake

Key takeaways

• Record the source and time for every material reservation intake fact.
• Keep operator decisions separate from assistant coordination.
• Close only after linked guest, vendor, access, and property records agree.

Operating data

Playbook

a guest requests a full refund after an interrupted stay and several messages describe the incident differently. This is the sort of ordinary STR problem that becomes expensive when one person answers from memory and everyone else acts on a different record. STRVirtualAssistant should open one case, keep the uncertainty visible, and give the operator a short decision path. The aim is not to make the assistant the property manager. It is to make the facts usable before the available window closes. For this reservation intake case, the working record centers on reservation, contract version, payment references, requested amount, guest reason, original reports, response timeline, vendor findings, prior promises, decision owner, accounting route, and reply deadline.

Start with the request exactly as it arrived. Record reservation, contract version, payment references, requested amount, guest reason, original reports, response timeline, vendor findings, prior promises, decision owner, accounting route, and reply deadline. Keep screenshots, photos, or platform messages in their approved system and link to them rather than scattering copies through chat. A useful case record shows where each field came from and when someone last checked it. If a field is unknown, write unknown. A blank cell is too easy to misread as a quiet confirmation. For this reservation intake case, the working record centers on reservation, contract version, payment references, requested amount, guest reason, original reports, response timeline, vendor findings, prior promises, decision owner, accounting route, and reply deadline.

The first working check is simple: quote the request accurately and build a timeline from source records without deciding fault or entitlement. That sentence should appear near the top of the case because it tells the next coordinator what to verify first. It also prevents a familiar-looking event from being processed as if it were last week's event. Property rules, occupancy, vendor availability, and platform records can change between otherwise similar requests. For this reservation intake case, the working record centers on reservation, contract version, payment references, requested amount, guest reason, original reports, response timeline, vendor findings, prior promises, decision owner, accounting route, and reply deadline.

Use property-local dates and times throughout the record. Add the source time when a platform or vendor reports in another zone. An arrival at 3:00 can mean three different things if the message, calendar, and onsite team are reading different clocks. The coordinator should resolve that basic ambiguity before sending reminders or changing access. This small discipline also makes the later timeline much easier to audit. For this reservation intake case, the working record centers on reservation, contract version, payment references, requested amount, guest reason, original reports, response timeline, vendor findings, prior promises, decision owner, accounting route, and reply deadline.

Next, separate observations from decisions. A guest message, a cleaner check-in, a device screen, and a vendor note are observations from different positions. None automatically authorizes a promise. the manager decides refunds, credits, contract interpretation, dispute posture, and the final message. The assistant can prepare options and explain their downstream effects, but the selected option needs a named owner and a timestamp. If the operator has a standing rule, cite the rule and its current version. For this reservation intake case, the working record centers on reservation, contract version, payment references, requested amount, guest reason, original reports, response timeline, vendor findings, prior promises, decision owner, accounting route, and reply deadline.

Write the guest or vendor update in plain language. State what has been confirmed, what remains open, who is checking it, and when the next update will arrive. Avoid technical guesses and soft promises such as "it should be fine." Those phrases feel helpful in the moment but create a new commitment that may not match the underlying work. A short, accurate holding message is more useful than an optimistic answer that another teammate must unwind. For this reservation intake case, the working record centers on reservation, contract version, payment references, requested amount, guest reason, original reports, response timeline, vendor findings, prior promises, decision owner, accounting route, and reply deadline.

The case needs a visible exception lane. Escalate when a payment dispute is open, legal language appears, personal injury is alleged, records conflict, or a prior message may contain an unauthorized promise. The assistant should not bury one of these facts inside a routine checklist. Put it at the top, use the operator's urgent contact path, and note who acknowledged it. If immediate danger is reported, the safety process takes priority over administrative completeness. The record can be finished after the right people have responded. For this reservation intake case, the working record centers on reservation, contract version, payment references, requested amount, guest reason, original reports, response timeline, vendor findings, prior promises, decision owner, accounting route, and reply deadline.

Access deserves its own check even when access is not the original complaint. Ask whether a guest, cleaner, vendor, or building representative must enter a controlled area. Confirm identity through an approved route and issue only the narrow permission the manager authorized. Do not paste permanent codes into a broad thread. When temporary access expires, record the retirement event instead of assuming the system removed it. For this reservation intake case, the working record centers on reservation, contract version, payment references, requested amount, guest reason, original reports, response timeline, vendor findings, prior promises, decision owner, accounting route, and reply deadline.

Cost and guest remedy decisions stay outside the assistant's implied authority. The case can show a quoted price, cancellation term, service window, or prior message. It should also flag the practical consequence of waiting. That still does not turn the coordinator into the person who approves spend, waives a term, admits fault, or promises compensation. A clean boundary protects the guest as much as it protects the operator because the final answer comes from someone who can honor it. For this reservation intake case, the working record centers on reservation, contract version, payment references, requested amount, guest reason, original reports, response timeline, vendor findings, prior promises, decision owner, accounting route, and reply deadline.

Handoffs should be brief enough to read on a phone. Put the property and reservation first, followed by the current state, immediate deadline, verified facts, conflicts, requested decision, and next owner. Link the source artifacts underneath. Do not paste a diary of every routine click. The point is to let a manager understand the live choice without reopening five systems, while leaving enough provenance for another coordinator to reproduce the summary. For this reservation intake case, the working record centers on reservation, contract version, payment references, requested amount, guest reason, original reports, response timeline, vendor findings, prior promises, decision owner, accounting route, and reply deadline.

Before marking the case complete, check every dependent record. A guest message may require a calendar note. A vendor visit may affect access, turnover, inventory, or an inspection. A corrected listing detail may need a scheduled publication check. The assistant should update only the systems covered by the approved procedure and should record any system that remains out of sync. Silent partial completion is one of the common ways a closed task returns during the next stay. For this reservation intake case, the working record centers on reservation, contract version, payment references, requested amount, guest reason, original reports, response timeline, vendor findings, prior promises, decision owner, accounting route, and reply deadline.

Closure has a concrete test: the decision cites the approved basis, payment action has a traceable reference, and the guest receives the authorized response. Add the closer's name and the time of the final check. If part of the issue remains unresolved, close the immediate action only and create a separate owned follow-up. That is better than leaving a vague open case in the daily queue. It also gives the operations lead a realistic view of recurring defects instead of a pile of tasks that never quite end. For this reservation intake case, the working record centers on reservation, contract version, payment references, requested amount, guest reason, original reports, response timeline, vendor findings, prior promises, decision owner, accounting route, and reply deadline.

Review a sample of these cases each month. Look for missing source links, late escalations, repeated manager questions, promises made before approval, credentials left active, and follow-ups that reopened. The review is not a score of individual effort. It is a way to find where the written routine does not match the property operation. Change one rule at a time, name the owner, and record the next date for checking whether the revision worked. For this reservation intake case, the working record centers on reservation, contract version, payment references, requested amount, guest reason, original reports, response timeline, vendor findings, prior promises, decision owner, accounting route, and reply deadline.

STRVirtualAssistant can maintain this routine as part of the relevant service workflow. A nearby example is the related STR operations guide. For the outside boundary used in this article, consult FTC consumer review and business guidance. The public source supplies context, not a property-specific decision. The operator still needs to approve the local rule and keep it current. For this reservation intake case, the working record centers on reservation, contract version, payment references, requested amount, guest reason, original reports, response timeline, vendor findings, prior promises, decision owner, accounting route, and reply deadline.