Summarize with AI
A guest sends a lockbox question at 8:10 p.m. You spend six minutes responding, wait while they try the code, then spend four minutes arranging another way in. The issue ends at 9 p.m. Your elapsed response window was 50 minutes; your described work was 10 minutes.
That distinction makes communication records easier to understand. Being reachable throughout an evening does not establish that you worked throughout it.
Record active work and leave waiting visible
Participation concerns work performed in an activity. Treasury Regulation 1.469-5T(f) supplies the participation and proof rules. A work log should describe the actual tasks rather than convert availability into service hours.
For a guest incident, note what you read, investigated, wrote, or coordinated. Pause a timer during unrelated activities. If you were actively troubleshooting while waiting for a reply, describe that work separately from idle waiting.
The final tax treatment still depends on your activity and circumstances. A well-described message is evidence of a task, not an automatic qualification decision.
A daily summary can remain specific
You do not need a separate paragraph for every short message. An illustrative daily entry could read: “12 minutes total: answered two arrival questions for reservation R14 and contacted the cleaner about a missing key.”
Use the actual total you tracked or a supportable approximation, identifying an estimate when relevant. Do not apply an automatic 15-minute minimum to every reply. Message timestamps show when messages were sent; they do not measure all the time spent composing or investigating them.
Where available, retain the relevant thread or a reference that lets you retrieve it. Prefer reservation identifiers over copying guests’ personal details into widely shared reports.
Separate setup work from automated delivery
Writing a new check-in sequence or testing an access instruction can take active work. Record the setup session and what changed. Messages sent automatically afterward do not create new owner work each time the software sends them.
The same distinction applies to templates: record time you spent revising one, and any later individual response you personally handled. Do not multiply the setup time by the number of bookings that received the template.
Review overlapping records
Before totaling the day, compare communication entries with repairs, travel, and other tasks. If a repair entry already includes the call that arranged access, do not count that call again in the messaging summary.
Keep the duration and explanation together. When the source only establishes that a conversation occurred, leave the exact duration unresolved rather than deriving minutes from the time between the first and last message.
See why calendar time is not necessarily work time for the same issue in scheduled events. In HostHours, review captured notes against what you did before using them in a professional handoff.
Clear answers
Frequently asked questions
Can I record an entire evening spent available to guests?
Availability alone does not show work performed. Record the time spent handling tasks and distinguish it from waiting, personal activities, and time spent at another job.
Can I combine short guest messages into a daily record?
Yes. Keep a factual task summary and a supportable total duration, with references to the conversations when helpful. Avoid automatic minimums for each message.
Do automatically sent messages create owner work hours?
The time you spend preparing and testing a workflow can be recorded for review. The software sending each later message does not itself create additional owner work.
Can message timestamps prove how long I worked?
They establish sending times, not the whole duration of composing or troubleshooting. Preserve them as context without treating the full conversation window as active work.
