Waiting for a test result is one of the more difficult experiences in healthcare, and it produces a predictable pattern of contact. Two days after the test, people start asking. Four days after, they ask again. Every one of those messages is really asking something else: is everything all right.
A lab cannot answer that question, but it can remove most of the reason people ask.
The teardown: anxiety, not impatience
Nobody chases a result because they are annoyed about turnaround times. They chase because not knowing is worse than knowing, and because nobody told them when to expect anything. Silence turns a four-day wait into four days of escalating worry.
What patients ask
Patients usually ask when their results will be ready, how they will receive them, whether they will be contacted if something is wrong, whether no news means good news, whether they can get results directly, what happens if their doctor is away, whether results can be sent to another clinician and what the numbers on a report mean.
Publish turnaround per test
A page listing each test with its typical turnaround is the single most effective fix. Patients who know a particular test takes a week stop counting days after two. Delivery expectations work the same way in retail, as described in delivery date anxiety and how to answer it before checkout.
Explain who delivers results
Most patients do not understand that the lab reports to the requesting clinician. Saying so plainly, and explaining that the clinician will discuss the findings, redirects the question to the right place before it becomes a complaint.
Patient: My test was on Monday. Should I have heard by now? Assistant: The turnaround page shows the typical time for each test, and results are sent to the clinician who requested them, who will contact you to discuss them. If the expected time has passed, the team can check whether the report has been issued, so I can pass your details to them.
Never hint at findings
Confirming that a report has been issued is administrative. Anything beyond that, including tone, reassurance or urgency, risks conveying clinical information. The rule is absolute, as described in test results and prescription questions that need a person.
No news is not a policy
Patients frequently assume no contact means nothing was found. Publishing what actually happens, including how they will be told either way, prevents a dangerous assumption.
Delays happen
Samples get repeated, tests are added and specialist analysis takes longer. Explaining the common reasons for delay, without reference to any individual, reduces the assumption that silence means bad news.
Self-pay patients
People paying privately often expect direct access to results. Explaining your policy clearly, including whether results go to them or a clinician, avoids conflict at exactly the wrong moment.
Booking and preparation before
Everything upstream of the test is covered in test booking and preparation questions for diagnostic labs.
Publishing once, answered always
Repeated administrative questions are what published answers solve, as described in how financial advisors use chatbots to answer client questions.
Getting started
Publish turnaround by test, explain who delivers results and what happens either way, then answer at any hour. SpideyChat for healthcare organisations answers from your published pages. Try SpideyChat on your own site, or read about answers on the features page.