Swiftline request intake and courier coordination visual

REQUEST PICKUP

Request a pickupor choose the right courier pathwithout hunting for the form.

Start with the general pickup form, or choose STAT, scheduled route, documentation, API, or temperature-sensitive workflow when your request needs a more specific path.

Start Pickup Request Request STAT Delivery

Pickup Form First

Use the main form for one-time, same-day, healthcare-aware, or business courier requests.

STAT Requests

Use urgent intake when timing, pickup readiness, and direct delivery need fast dispatch review.

Scheduled Routes

Plan recurring stops, windows, cadence, facility deliveries, and repeat courier lanes.

Special Handling

Use focused paths for documentation, API, temperature-sensitive notes, or service-area questions.

The pickup form is the main path. Specialized paths help route complex requests faster.

Swiftline collects practical details such as pickup area, delivery area, timing, package type, contact information, facility notes, and handling needs. Service area, availability, timing, and final delivery details are confirmed after intake.

Use Start Pickup Request for most one-time, same-day, medical, pharmacy, lab, or business courier needs.
Use STAT when timing is urgent and pickup readiness needs fast review.
Use Scheduled Routes when stops repeat across facilities, homes, offices, labs, pharmacies, or clinics.
Use Service Areas only to understand where Swiftline can support delivery activity.

Main request form

General Pickup Request

Best for one-time pickup, same-day delivery, healthcare-aware courier, pharmacy, lab, business courier, or quote requests.

Start pickup request

Urgent timing path

STAT Delivery Request

Use for time-sensitive deliveries that need pickup readiness, route fit, driver availability, and communication review.

Request STAT delivery

Recurring route path

Scheduled Route Planning

For repeat stops, facility routes, pharmacy deliveries, lab routes, office routes, route windows, and operating cadence.

Plan a route

Where Swiftline delivers

Service Areas

Use this page to understand service-area direction, delivery regions, and whether a location or lane may fit Swiftline operations.

View service areas

POD, custody, or records path

Documentation / Proof Review

For proof of delivery, custody-style handoff expectations, documentation notes, or procurement review conversations.

Request documentation

Connected workflow path

API / Portal Coordination

For order creation, status updates, proof records, notification events, permissions, and approved workflow actions.

Request API coordination

Handling notes and exception planning

Temperature-Sensitive Workflow

For handling instructions, timing windows, packaging notes, logger-report coordination, and exception communication.

Discuss temperature workflow

Choose by urgency first, then by workflow.

Most customers should start with the pickup form. Choose STAT for urgent timing, scheduled routes for repeat work, documentation or API when records or systems are the main question, and Service Areas only when the delivery region is unclear.

Start Pickup Request: best default for most customers.
STAT Delivery: use when the clock matters and dispatch needs urgent context.
Scheduled Routes: use for recurring pharmacy, lab, facility, medical, or business stops.
Documentation/API/Temperature: use when the workflow needs a focused operational conversation.

Ready to send details?

The main pickup form is the fastest starting point for most requests. Swiftline can redirect the conversation after reviewing pickup, delivery, timing, service type, and handling details.

Start Pickup Request View Service Areas