Contact

Philadelphia Metro Authority publishes this contact reference to help riders, researchers, and community members direct inquiries to the correct channel. The sections below cover available contact methods, the geographic scope of service this office addresses, and what information to prepare before reaching out. Matching the right contact path to the right inquiry type reduces resolution time significantly — a message sent to the wrong channel may wait 5 to 7 business days before being rerouted.

Additional contact options

Beyond a standard message submission, the Philadelphia Metro system maintains distinct channels for distinct inquiry categories. Using the correct channel is the single most reliable way to accelerate a response.

Phone contact is best suited for time-sensitive matters: service disruptions in progress, safety concerns, or lost property reported within 24 hours of loss. The Philadelphia Metro Lost and Found reference lists retrieval procedures that apply once an item has been logged.

Written correspondence — submitted through postal mail or a formal contact form — is appropriate for accessibility accommodation requests, complaints and formal feedback, and matters related to paratransit eligibility. Written channels create a timestamped record, which matters when a response or acknowledgment is required within a regulatory timeframe.

Public meeting participation is the appropriate channel for policy input, budget commentary, and capital project feedback. Scheduled dates and participation procedures are listed on the Philadelphia Metro Public Meetings page.

Transit Police handles on-system safety and security incidents. Reports involving criminal activity or a threat to rider safety should be directed to the Philadelphia Metro Police Transit Unit, not the general contact form.

How to reach this office

Philadelphia Metro Authority operates as the administrative reference body for system-wide information. Contact routing follows a structured triage model:

1. General rider inquiries — service questions, fare information, and schedule clarification — are addressed through the main inquiry form or by consulting the relevant reference pages, including fares and passes and hours of operation.
2. Accessibility and accommodation requests — covered under the Americans with Disabilities Act Title II framework — require written submission and carry a response obligation under federal guidelines. Supporting detail is available on the Philadelphia Metro Accessibility page.
3. Media and research inquiries — including data requests related to ridership statistics or funding and budget — are directed to the public affairs and governance channel.
4. Employer and benefits program inquiries — covering commuter benefits or employer transit programs — are handled by a dedicated business liaison function, not the general rider support queue.
5. Capital project and environmental review comments — relevant to active capital improvement projects or environmental impact assessments — are submitted in writing and entered into the public record.

Response timelines differ by channel. General rider inquiries targeting publicly documented information typically resolve within 2 business days. Formal complaints, accommodation requests, and public records inquiries follow statutory timelines established under Pennsylvania's Right-to-Know Law (65 P.S. §§ 67.101–67.3104), which sets a 5-business-day acknowledgment requirement and a 30-calendar-day response window for most requests.

Service area covered

This office addresses inquiries related to the Philadelphia metropolitan transit footprint. The Philadelphia Metro Service Area page defines the full geographic boundary, but the core coverage encompasses Philadelphia County and the transit corridors extending into Bucks, Chester, Delaware, and Montgomery counties — the 5-county Southeastern Pennsylvania region served by the SEPTA network.

Inquiries involving transit connections to New Jersey Transit (NJ Transit) or Amtrak services fall partially outside this office's direct scope. The Philadelphia Metro Transit Connections reference identifies the boundary between system-specific and interagency matters. For Park and Ride facilities and feeder routes at the edge of the service zone, the Philadelphia Metro Park and Ride page identifies which locations fall within addressable jurisdiction.

What to include in your message

A well-structured message reduces back-and-forth by as much as 60 percent compared to incomplete submissions, based on standard public agency triage benchmarks. Including the following elements at the time of first contact increases the likelihood of a single-contact resolution:

• Inquiry category — identify whether the message concerns a fare issue, an accessibility matter, a complaint, a public records request, or a service disruption
• Station or line reference — specify the station name or line designation; the Philadelphia Metro Stations and Philadelphia Metro Lines pages provide standardized naming
• Date and time — include the specific date and approximate time of the incident or observation being reported
• SEPTA Key Card number — required for fare disputes and account-related inquiries; card management details appear on the Philadelphia Metro SEPTA Key Card page
• Prior reference number — if following up on an existing inquiry, include the original submission reference number to prevent duplicate routing

Messages lacking a station or line reference, a date, or an inquiry category are the 3 most common reasons for delayed responses in public transit contact systems. Omitting any of these elements shifts the message into a secondary clarification queue before substantive handling can begin.

Privacy Policy