Answers for the fulfillment rail.
Guides and answers for NeoLife — the fastest compliant way to route a telehealth order to a compounding pharmacy. We are writing this help center out article by article; in the meantime, browse the topics below or reach the team directly.
Browse the knowledge base
Six areas cover the whole rail — from connecting your first clinic to the API and the security posture behind it. Each opens to the questions it will answer.
Getting started
Connect a clinic, add a pharmacy, and route your first telehealth order end to end.
Orders & fulfillment
How orders flow to the pharmacy, status updates, and handling exceptions.
Billing & plans
Metered order pricing, invoices, plan changes, and what counts as a billable order.
Integrations & API
API keys, webhooks, the SDK, and the CLI. Full reference lives on the docs site.
Compliance & security
HIPAA posture, data handling, subprocessors, and where PHI does and does not flow.
Account & access
Sign-in, roles and permissions, team members, and recovering access.
Talk to a human.
We answer support requests during US business hours. Email us with your clinic or pharmacy name and, where relevant, an order reference. To keep the channel outside the PHI boundary, never include patient health information in a support message.