General information
Answer hours, location, delivery, transfer process, vaccination availability, and store policy from approved documents.
Collect refill requests, answer general store questions, and escalate patient-specific or clinical questions instead of letting AI guess.
Refill request intake, phone overload reduction, backend eligibility checks, and staff escalation.
Each client gets its own source documents, allowed actions, escalation rules, integrations, staff access, and reporting.
Answer hours, location, delivery, transfer process, vaccination availability, and store policy from approved documents.
Collect the minimum details staff need to review a refill request without making unapproved clinical claims.
When integrated, query permitted refill or account data through the client's approved system boundary.
Create staff tasks when identity, medical judgment, coverage, or patient-specific information is required.
Sensitive questions become tasks for staff rather than AI guesses.
Answers come from client documents, web sources, and authorized systems.
Calls, notes, outcomes, and staff actions remain visible.
Only if the pharmacy connects an approved backend system and defines the exact response rules. Without that source, the agent should collect the request and escalate.
Those should be routed to staff. The value is reducing repetitive intake while keeping patient-specific or clinical decisions inside the pharmacy team.
The first pilot should focus on the call types that create obvious value: missed revenue, repetitive phone load, urgent routing, or staff follow-up.