Kat · Pharmacy calls and requests
Phone ringing? Kat's got it.
Kat explains the intended pharmacy phone workflow: answer routine enquiries where configured, then preserve the context for staff when work needs their attention.
Kat owns configured pharmacy call handling, request records and the follow-through context that reaches staff.
The pharmacy problem
Every call needs a clear next step.
Routine questions, requests that need staff and questions that require a transfer all need their context to travel with the work.
What Kat covers
What Kat can handle.
Kat groups configured enquiry handling, structured request work and the record staff need for follow-through.
Routine phone enquiries
Configured routine questions can receive a consistent next step without losing the pharmacy context behind the call.
- Repeat requests and stock-related enquiries using permitted KSafe context
- Opening hours and public-holiday information
- KShop order status, bookings and general enquiries
Requests that become work
When a question cannot finish in the call, Kat can place the next action with the right person.
- Staff transfer when the caller needs a team member
- A structured ticket for unresolved follow-up
- Intake for a staff-reviewed information request
Records for follow-through
The call record keeps the relevant request context visible when staff continue the work.
- Configured call records, transcripts and summaries
- Assignment and follow-up context for the pharmacy team
Illustrative pilot workflow
Here’s what happens on a call.
This static sequence explains the intended path for a configured pharmacy enquiry; it does not simulate a phone system or patient record.
Answer and identify the request
Kat identifies whether the caller has a routine enquiry, a request needing work or a question for a staff member.
Use configured pharmacy, KSafe and KShop context
Configured context can guide the next step while the owning module retains its record and staff retain patient-specific access decisions.
Resolve, transfer or create a ticket
Configured routine enquiries receive their next step; otherwise the caller is transferred or unresolved work becomes a structured ticket.
Preserve the call record and follow-up
The request, its context and the staff follow-up remain visible together for the team responsible for the next action.
This is an illustrative pilot workflow, not a live product demonstration.
Staff control
Your team takes over when needed.
Kat supports the request path; it does not take over the pharmacy decisions that require authorised review.
Dispensing and clinical decisions
Kat does not make dispensing or clinical decisions; authorised pharmacy staff retain those decisions.
Patient-specific access and final follow-up
Staff control identity, authority, consent and pharmacy-review steps for patient-specific access, as well as the final follow-up.
Buyer value
Fewer interruptions. Better follow-up.
The value is a reliable handoff of context from a routine enquiry or unresolved request to the person responsible.
Pharmacy
A consistent next step for routine enquiries
Configured routine enquiries can receive the same clear next step each time they enter the pharmacy workflow.
Team
Context intact when staff take over
Unresolved work reaches the team with the call record and relevant context intact for follow-through.
KSuite connections
Where Kat gets its context.
Kat can use permitted connected-suite context while the relevant operational module remains accountable for its own record.
- KSafeStock-related enquiriesKSafe supplies permitted stock context for a Kat enquiry without transferring ownership of the inventory record.
- KShopOrder status questionsKShop remains the order owner while Kat can provide configured order-status information to a caller.
- KDashVisible follow-throughKDash can keep attention on unresolved Kat work without becoming the owner of the request record.
Illustrative example
A repeat and stock question.
Kat uses permitted pharmacy and KSafe context to identify the configured next step. If the question needs further review, the unresolved request reaches staff with the call record and context attached.
Pilot scope
Set the call rules together.
The described Kat workflow is intended pilot behaviour; public production availability is not asserted on this page.
- Routine enquiry handling, transfers and ticketing are configured with the participating pharmacy.
- Patient-specific access follows configured identity, authority, consent and pharmacy-review steps.
- Pharmacy staff retain dispensing, clinical and final follow-up decisions.
Buyer questions
Questions about Kat.
These answers keep the intended workflow, staff controls and connected records clear before a pilot conversation.
- Can Kat answer every pharmacy call?
- Kat describes configured routine enquiries. Other calls can be transferred or preserved as structured work for staff follow-through.
- Does Kat make clinical or dispensing decisions?
- No. Kat does not make dispensing or clinical decisions. Authorised pharmacy staff retain those decisions and final follow-up.
- How does Kat use KSafe and KShop?
- Kat can use permitted KSafe stock context and configured KShop order-status information while KSafe and KShop retain ownership of their records.