Pickup Questions
Use FAQ for orientation, then intake when details are ready.
Request Pickup
FAQ SUPPORT
Find answers about pickup requests, STAT delivery, scheduled routes, service areas, lab and pharmacy courier support, portal visibility, proof records, documentation, and integrations.
Use FAQ for orientation, then intake when details are ready.
Urgent and recurring requests should use the right pickup or route path.
Location, lane, timing, and service-area fit should start with Service Areas.
Technical and documentation topics route to owner pages.
FAQ content is for quick clarification. Use categories to find the closest topic, then move to the proper pickup, service-area, documentation, portal, API, or contact path when the question becomes operational.
FAQ finder
Search by service topic or filter by category. Keep answers closed until needed so the page stays clear, scannable, and easier to use.
Use the STAT delivery form for urgent direct requests, the scheduled route form for recurring pickup programs, the general pickup form for one-time or quote requests, and the contact form for introductions or general questions.
Swiftline currently presents STAT Delivery as a California full-service capability. Other review or expansion areas may support non-STAT courier conversations by request, but STAT availability is not currently presented outside California.
A scheduled route is a recurring courier plan built around repeated pickup and delivery needs, such as daily office runs, pharmacy support, lab logistics, supply movement, or multi-stop business workflows.
Yes. If your area is not listed, Swiftline still welcomes the conversation. New service areas requests can be reviewed based on lane fit, service need, timing, operational readiness, and customer requirements.
The customer portal guidance path can support approved workflows such as order review, delivery visibility, proof-of-delivery records, and recurring route context when configured.
Chain of custody refers to a delivery record showing key custody events such as who released the package, pickup time and location, transfer or in-transit events, recipient confirmation, signature or proof of delivery, and reviewable history when available.
Swiftline can discuss API or integration workflows for customers who need authorized access to order details, delivery status, timestamps, route information, POD records, and approved workflow actions.
Yes. Temperature-sensitive workflows can be discussed by request. Swiftline can review handling instructions, logger report coordination, delivery record needs, and operational fit before presenting any specific capability.
Move from FAQ to an owner page when the question becomes operational: new delivery request, route planning, service-area review, documentation, portal access, API scope, or tracking support.
Use the closest pickup, service-area, documentation, portal, API, tracking, or contact path so Swiftline can review the details behind the question.