Greyhound · Safety & Response
On July 16, 2026, a Greyhound bus stopped near Gallup, New Mexico. The driver intervened. Police responded. Greyhound was notified. September 16 correspondence identifies a claims examiner and documents responses about records and seating. The owner and findings of a separate company safety review remain unresolved.
Records and correspondence through September 16, 2026 · Reviewed September 21
Greyhound reference GH034799
Customer Service management
Examiner identified; safety review still unresolved
The roadside response
The MCSO investigative report records that the bus driver pulled over, contacted police, and made Shubham leave the bus. It also records that Greyhound was informed and that report GH034799 was generated.
The bodycam record and the passenger’s correspondence describe the driver’s intervention and objection to having him returned to her bus.
Sources: MCSO report, page 2 · bodycam record · September 8 passenger email.
The company response
On September 8, Raelonda Robinson-Howard replied that she was escalating the correspondence to Customer Service management. Her response did not identify the manager, provide a direct contact, or set a specific response date.
On September 9 and 14, the passenger asked for the person responsible for GH034799. The September 16 replies identify Drake’s claims role; the operational safety-review owner remains a separate question.
Sources: company response · September 9 follow-up · September 14 follow-up.
Record update · September 21, 2026
Jeanine Drake identifies herself as a liability claims examiner. Her email signature identifies Gallagher Bassett Services, Inc. as third-party administrator for Flixbus/Bus Risk Retention Group. On September 16 she described investigating and evaluating the claim on the client’s behalf.
Drake declined the requested internal records and declined to comment on client or third-party records’ existence, contents, preservation status or production. This is a received response; it does not establish that the requested evidence has been preserved or delivered.
Please note that Gallagher Bassett's role is to investigate and evaluate the claim on behalf of our client.
As such, we are unable to disclose privileged, confidential, proprietary, personnel, claim handling, investigative, or other non-public information belonging to our client, nor can we provide internal records, claim notes, communications, incident reports, operational records, or other documents you requested through your correspondence.
Additionally, while we will review any information and evidence you choose to provide, we are not in a position to comment on the existence, contents, preservation status, or production of records maintained by our client or third parties during the course of our investigation.
A later September 16 reply says the review includes the incident, the response afterward and the passenger’s concerns about seating, privacy, rebooking and identity. Those are topics accepted for evaluation, not completed findings.
The investigation includes a review of the facts surrounding the incident, the response after the incident was reported, and any information relevant to the allegations being asserted.
We have also noted your concerns regarding post-incident seating arrangements, privacy during the reporting process, the rebooking and seat reassignment history, the passenger identity issue you referenced, and whether there was any prior indication of behavior that would have put company personnel on notice. These matters will be evaluated as part of the ongoing investigation.
Drake also reported one unsuccessful telephone attempt to reach a witness. An attempted call is not a completed interview, and claims outreach is separate from MCSO’s investigation. The reviewed emails do not identify the owner or conclusions of a separate company operational safety review.
Safety-review ownership → · Evidence custody and preservation →
Record update · September 21, 2026
In her later September 16 response, Drake acknowledged that another passenger suggested the alternative seating arrangement and said the claim file would reflect that. The female passenger’s concerns about the response remain matters for review.
I have reviewed my notes from our recorded statement, which indicate that the suggestion for an alternative seating arrangement came from another passenger and not from the driver.
To the extent my prior correspondence suggested that the driver personally offered to relocate you, I appreciate your clarification and will ensure the claim file accurately reflects the source of the proposed seating arrangement.
This records an acknowledgment and a commitment to reflect the correction. It does not establish that the complete claim file was corrected or that the safety review reached findings.
July 15, 2026 · Travel notices
Greyhound emailed an “unknown delay” notice and a separate notice that part of the trip had changed for operational reasons. In her September 14 escalation, the passenger described an approximately 15-hour delay that changed her travel circumstances and placed her on the later bus involved in the incident.
Sources: July 15 notices · passenger’s September 14 escalation.
July 16, 2026 · Incident reported
The MCSO report records the driver’s intervention, company notification, and Greyhound report GH034799. The underlying Greyhound incident report is among the records the passenger later sought.
Sources: MCSO report · passenger’s records request.
September 8, 2026 · Operational review requested
Her email describes repeated attempts to reach Safety, Legal, Risk Management, or an investigator through telephone, AI-assisted chat, and customer-service channels. She asks for a named person, preservation of the incident file and ticket photograph, review of the reported ticket-name discrepancy, and information about any later rebooking or transportation.
Raelonda Robinson-Howard replies that the correspondence is being escalated to Customer Service management.
Sources: passenger’s request · company’s reply.
September 9, 2026 · A name and direct contact requested
The passenger asks who issued the earlier responses Greyhound reportedly said it sent, who currently owns GH034799, and how to contact that person directly.
Source: September 9 follow-up.
September 14, 2026 · Management follow-up and executive escalation
She notifies Raelonda of the September 10 criminal filing and again asks who is assigned to GH034799, when it was assigned, whether the ticket photograph and related records have been preserved, and whether Greyhound subsequently rebooked or transported Shubham. She also sends an escalation to Flix leadership describing the reporting process and asking for one accountable person.
Sources: management follow-up · executive escalation · criminal filing.
September 8, 2026 · The company’s written reply
Thank you for reaching out to FlixBus. I am escalating your correspondence to the management team within our Customer Service Department. I see that you have included a reference number, which will assist with the review process. I will ask the appropriate team member to review your case and get back to you as expeditiously as possible.
Raelonda Robinson-Howard · Flix
Signed “Raelonda Howard”
Email subject: “RE: Operational Review Requested | Greyhound Incident GH034799 | Passenger Safety Failure.” Selected body text.
These are the questions raised in the passenger’s September correspondence.
Drake is identified for the claim. Identify who separately owns the company’s operational safety review, their title, assignment date and direct contact.
Explain what was investigated, what evidence was considered, and what Greyhound concluded or changed.
Account for the complete GH034799 file, the driver’s original photograph and related metadata, and the relevant reservation, ticketing, and boarding records.
Determine what name appeared in the travel records, what identification was checked, and how any discrepancy was handled.
Establish whether Greyhound rebooked or transported Shubham after his removal, and whether the incident informed that decision.
The passenger reports being told that Greyhound sent two responses she could not locate. Produce the messages and their sending and delivery information.
Selected email excerpts and source descriptions.
The Greyhound page reproduces selected email body text from July 15 and September 8–14, 2026 and summarizes the associated requests. Line wrapping is normalized. Private passenger and driver identities, booking details, personal contact information, signatures, quoted message history, and tracking links are omitted. The company’s September 8 response is distinguished from the passenger’s descriptions and follow-ups. Statements about missing contact, the earlier July 21 and August 18 replies, the reported name discrepancy, and later transportation are attributed to the correspondence that raises them. The approximately 15-hour delay is the passenger’s account; the July 15 notices confirm a disruption without establishing its complete duration.
September 8 · Female passenger to Raelonda Robinson-Howard
“I am asking for your help getting a serious Greyhound passenger-safety complaint to someone with authority to review it and respond directly.”
The email requests identification of the responsible reviewer; preservation of the incident file, driver’s ticket photographs, and related travel records; review of the reported ticket-name discrepancy; and information about subsequent transportation.
It also describes unsuccessful attempts to reach a responsible safety representative through telephone and AI-assisted chat, and asks for copies and delivery information for the July 21 and August 18 responses Greyhound reportedly said it sent.
September 9 · Female passenger to Raelonda Robinson-Howard
“Referring me to “the management team” still leaves me without a name, direct contact, or a date when someone will speak with me. Given Greyhound’s claim that it has already responded twice, I should not still be trying to establish who is handling this matter.”
Email subject: “Re: Operational Review Requested | Greyhound Incident GH034799 | Passenger Safety Failure.”
September 14 · Female passenger to Raelonda Robinson-Howard
“It is now September 14, and I still have not been contacted by the manager or other person responsible for reviewing the incident.”
The message asks for the assigned person and referral status, the missing earlier responses, confirmation of evidence preservation, and any subsequent rebooking or transportation decision.
Email subject: “Re: Operational Review Requested | Greyhound Incident GH034799 | Passenger Safety Failure.”
September 14 · Female passenger to André Schwämmlein at Flix
“My original Greyhound trip was delayed by approximately 15 hours.”
“One named, accountable person with authority to review this matter, answer these questions, preserve the evidence, and communicate directly with me.”
The escalation describes the passenger’s approximately 15-hour travel disruption and her attempts to obtain an accountable safety contact. It requests preservation of the incident, communications, customer-service, driver, ticketing, and subsequent-travel records.
Email subject: “CEO ESCALATION: Passenger Assault, 15-Hour Greyhound Disruption, Criminal Filing, and Two Months Without an Accountable Safety Contact | GH034799.”
July 15 · Greyhound travel notices
“Unknown delay on your journey” advises that the journey is experiencing an unknown delay and promises a further update. “Part of your trip has changed” says part of the itinerary was changed for operational reasons.
These notices document a disruption. The approximately 15-hour duration is the passenger’s account in her September 14 escalation.
September 8 · Female passenger to Greyhound Customer Service
The passenger says social-media support told her that Greyhound sent responses on July 21 and August 18. She reports searching her inbox, spam, trash, and archived mail without finding either response, and asks for complete copies, recipient addresses, dates, times, subjects, case references, and delivery information.
“Please also resend both responses to this email address now.”