01
Decode terminology
Look up what a test or abbreviation in a customer's message actually means.
Industry
Customer Support
What support people at health companies can do with Lunas today — starting with actually understanding the reports customers send them.
What Lunas supports
- Plain-language explanations of medical terminology
- File-aware reading of reports and documents
- A clear line between product help and clinical questions
The opportunity
Why this work needs medical context
A customer emails a lab's support desk: "my report says my eGFR is 58 — is your test broken?" The agent isn't a clinician, can't say "that's fine" or "see a doctor about that," and mostly needs to understand what the report even is before writing a careful reply.
That's a use an individual Lunas account covers today. The agent can ask Stethos what eGFR measures, how the report is structured, and how to explain the reference range without drifting into medical advice — then answer the product question accurately and route the clinical one to the team that owns it.
Team workspaces, approved response libraries, and support-platform integrations are on the roadmap; today the value is a sharper, better-informed human on the desk.
Where Lunas fits
Useful work before the final decision
Stethos helps explain, organize, and investigate. People and qualified professionals stay responsible for the decisions that follow.
02
Understand reports
Learn the structure of the document a customer is asking about.
03
Draft carefully
Explain product-relevant facts without slipping into medical advice.
04
Escalate cleanly
Recognize the clinical or safety question and hand it to its owner.
A practical workflow
From a question to human review
A repeatable path makes the model easier to supervise and the result easier to trust.
- 01
Read the question
Separate the product issue from the medical one.
- 02
Get the context
Ask Stethos about the terminology and report format involved.
- 03
Answer your part
Reply accurately on the product; stay out of clinical territory.
- 04
Route the rest
Send clinical, adverse-event, and urgent issues to the designated team.
Product path
Start with Lunas today. Grow into governed workflows.
Lunas.One is available to individuals today. Team & Enterprise workspaces and a governed Stethos API are in active development — the roadmap below is directional, not a promise of present availability, and larger deployments will require the right privacy, security, evaluation, and human-review controls.
Available in Lunas
- Individual accounts for support professionals
- File-aware medical conversations with Stethos 1.0
- Plain-language explanations of tests and terminology
Team, Enterprise & API direction
- Team support workspaces and role controls
- Approved response libraries and review queues
- A governed Stethos API for support platforms
Questions
What people usually want to know
Can Lunas answer my customers automatically?
No. There is no support-bot product or public API today; automation like that sits on the roadmap and would ship with review and escalation controls. What exists now is a tool that makes a human agent faster and more accurate.
Can support agents give medical advice through Lunas?
No. Lunas doesn't extend anyone's professional scope. It helps an agent understand and explain — the moment a question needs clinical judgment, it belongs with a qualified professional, and the agent's job is a clean handoff.
Which teams does this fit?
Anyone whose inbound tickets include medical documents or terminology: laboratories, health and wellness apps, device makers, benefits administrators. If your agents regularly search medical abbreviations mid-ticket, this is for them.
Try the product
Bring one real health question into context.
Use Lunas for information and organization, then involve a qualified professional whenever a health decision is needed.