How does Scripts support and customer service work?
Scripts provides customer service primarily through email at support@scripts.co, the support channel listed on its public materials as of June 2026. Scripts does not publish a support phone number, live chat, or a self-service ticketing portal, so clinic teams should plan around email-based help when an order or account issue comes up.
If your operations team handles pharmacy issues over email today, Scripts's model will feel familiar. Here is what is publicly known about Scripts support and how a platform with in-app support tied to each order compares.
Proudly Partnered With
The verifiable ways to reach Scripts support.
Scripts's public materials list one direct support channel. When a path is not documented, confirm it during onboarding rather than assume it exists.
Email — support@scripts.co
Email is the support channel Scripts lists publicly as of June 2026. Send order questions, account changes, and issue reports here, and keep your own copy of the thread since replies live in your inbox rather than alongside the order.
Your account or onboarding contact
Clinics that sign with Scripts are typically assigned an onboarding or account contact during setup. Confirm who that person is, their response window, and whether they cover ongoing support or only the initial rollout.
Phone, chat, or ticketing — not published
Scripts does not publish a support phone number, live chat widget, or self-service ticket portal on its public site as of June 2026. If your team needs same-day phone escalation, ask Scripts to confirm in writing before you sign.
If support stalls
Document the order and the ask
Because email threads sit outside the order record, include the patient reference, the medication, and the order date in every message so support can act without a second round-trip.
Set a follow-up clock
Agree on a response window during onboarding and follow up if it passes. Without a published SLA, a clear internal follow-up rule keeps a stalled refill from sitting unanswered.
Is email support enough — or do you want support tied to the order?
Scripts
Your team is comfortable handling pharmacy issues over email.
- Email at support@scripts.co matches how your operations staff already work through order problems.
- You do not need a published phone line or live chat for same-day escalation.
- An assigned account contact during onboarding covers your support expectations.
Fizy Health
You want every support thread attached to the order and patient.
- You want support tickets that open from inside the order, so context travels with the question.
- You want threaded replies your whole team can see — not a message trapped in one person's inbox.
- You want order status and support to live in the same place your team already works.
What support looks like when it lives in the app.
Support is the moment a clinic feels a platform's quality. These are the outcomes when help is tied to the order instead of an email inbox.
Support tied to the order — not lost in email
Open a support ticket from inside the order so the patient, medication, and status are already attached, with threaded replies your team can follow.
See order status before you even ask
Per-line tracking shows where each order is across compounders, so many where-is-my-order questions answer themselves.
Get told when something changes
Notifications fire on status changes and exceptions, so your team learns about a held order from the app instead of a patient phone call.
Fewer support tickets caused by rejections
Cart validation catches invalid SIGs, licensure mismatches, and stock gaps before payment, so fewer issues become support threads after the fact.
What clinics ask about Scripts support.
- Support
How do I contact Scripts support?
Scripts lists email support at support@scripts.co on its public materials as of June 2026. That is the documented support channel; Scripts does not publish a support phone number or live chat.
- Channels
Does Scripts have a customer service phone number?
Scripts does not publish a customer service phone number on its public site as of June 2026. If phone support matters to your clinic, ask Scripts to confirm phone availability and hours in writing before signing.
- Channels
Does Scripts offer live chat or a ticketing portal?
Scripts does not publicly list a live chat widget or self-service ticketing portal as of June 2026. Email and any assigned account contact are the documented paths to support.
- Expectation
What response time should I expect from Scripts support?
Scripts does not publish a support response-time commitment publicly. Confirm an expected response window during onboarding and set an internal follow-up rule so a stalled order does not sit unanswered.
- Comparison
How is Fizy Health support different from Scripts?
Fizy Health provides in-app support tickets that open from inside an order, with threaded replies tied to the patient and medication. Scripts support runs through email, where context lives in an inbox rather than alongside the order.
- Audience
Is Scripts support for clinics or for patients?
Scripts is a clinic-facing fulfillment portal, so its support serves clinic staff and prescribers rather than patients directly. Patient questions about a shipment route through the clinic.
Sources reviewed June 2026
- Scripts public website and FAQ (scripts.co), reviewed June 2026.
- Fizy Health platform capabilities reflect the live product.
See support that lives where you work.
Fizy Health keeps support, order status, and notifications in one place tied to each order and patient. Free to start.