Read a reply-time promise as a defined service window, not as evidence about who is typing. Check the starting event, time zone, working days, message types, and exceptions before treating a phrase such as “within a day” as a precise commitment.
Speed alone does not establish whether a reply came from the creator, a team member, or an automated process.
Define the clock
A useful response window needs a beginning and an end. Consider these different hypothetical descriptions:
Scroll across the table on smaller screens.
| Wording | What remains unclear |
|---|---|
| Usually quick replies | No measurable window is given |
| Replies within 24 hours | Whether every message type is covered |
| Replies on weekdays | Which time zone and what happens on holidays |
| Replies after a booked session | What event starts the response period |
Do not fill those gaps with the interpretation most convenient to you. If timing is central to a purchase, ask for the missing condition first.
Keep ordinary delays separate from authorship
A delayed reply could have several explanations. A quick reply could also have several explanations. Neither observation identifies the person or tool behind it.
A March 2026 Hacker News comment described receiving a message during a live event while remaining uncertain about its author. That is one person's anecdote, not a test of the account or evidence about the whole platform.
The online-status and reply-times guide covers why an activity indicator cannot answer the authorship question.
Make a fair private timeline
If you need to follow up on a specific offer, record only the relevant facts: the published window, when the covered request was sent, any stated absence, and when a reply arrived.
For example, a fictional promise covering weekday support should not be evaluated as though it promised continuous weekend conversation. Equally, an undefined “soon” should not be rewritten as a precise deadline after the fact.
Keep that timeline private. You generally do not need to repost message content or another person's identifying information to describe a delay.
Choose a proportionate next step
Use the established support route for a clear question about the published window. Repeated messages can make a conversation harder to follow and do not create stronger evidence.
If a refund or payment dispute is involved, consult the current official-terms guide. This article does not establish entitlement to a refund or interpret a contract for your jurisdiction.
When writing a review, separate the actual promise from your own preferred response speed. OnlyDetect's editorial policy calls for the same distinction between observation and interpretation.