One stop ticketing solution for bus and coach operators

Bus Emergency Contact Policy: 5 Practical Decisions for Operators

notify-passengers-bus-delay-phone-on-bench

Written by

in

A bus emergency contact policy tells your staff who to call when a passenger falls ill, is injured or cannot be reached during a trip. For an operator it is a short set of rules about what you collect, who may see it and when it may be used.

This guide covers five decisions for a bus emergency contact policy. It gives no legal citations and no retention periods, because privacy rules depend on your market and on advice from your own legal counsel. It focuses on what the dispatcher and the driver can apply calmly.

The reader is the owner or operations manager. If a driver has ever stopped the coach for a sick passenger and nobody knew whom to call, the decisions below are written for you.

bus-emergency-contact-policy-phone-on-bench

Why a Bus Emergency Contact Policy Is Not the Same as a Breakdown Plan

A breakdown plan covers the vehicle. A bus emergency contact policy covers the person. Our guide to the bus breakdown response plan explains the mechanical side, while this policy answers a different question: whom do we call about this passenger?

The two meet in real life. A long delay at night can leave an elderly passenger without medication, and a stopped coach is also the moment when a family member calls the office. A bus emergency contact policy gives your team one place to look.

Without a bus emergency contact policy, every agent improvises. One writes a number on a paper slip, another asks the passenger to phone someone, and a third does nothing. When something serious happens, nobody can say which approach the company intended.

Decision 1: Decide Whether You Collect Emergency Contacts at All

The first decision in a bus emergency contact policy is whether to collect the data. Many operators collect none for adult passengers on short routes and ask only for the buyer’s phone number. That is a legitimate choice, but it should be a written one.

If you do collect emergency contacts, decide who must provide one. Common groups are unaccompanied minors, passengers who need assistance and passengers on long overnight departures. Our guide to the bus unaccompanied minor policy shows where a contact is almost always needed.

Keep the field optional for everyone else. A mandatory emergency contact on every booking adds a step to checkout, and a step in checkout costs sales. Test the effect on a single route before you make it a company-wide rule.

Decision 2: Decide What You Store and Who Can See It

An emergency contact is personal data about a person who never bought a ticket from you. Decide the minimum you need, which is usually a name and a phone number. Do not ask for an address or a relationship unless a staff member really uses it.

Decide which roles can see the contact. A driver may need it during the trip, a dispatcher during the shift and a manager afterwards. A counter agent selling tickets to the next customer does not need it. Ask your legal counsel to review the access rules and the retention period.

Connect the rule to your passenger list. Our guide to the bus passenger manifest shows what a driver sees at boarding. If the emergency contact sits on a different screen than the manifest, the driver will not find it when it counts.

bus-emergency-contact-policy-dispatch-desk

Decision 3: Decide When Staff May Use the Contact

The most important line in a bus emergency contact policy is the trigger. Write down the situations in which staff may call the contact, such as a medical event, a missing minor or a passenger who does not return to the coach at a stop. Write down also what staff must not do.

Do not leave the trigger to personal judgment. An agent who calls a family member about a ten minute delay creates a complaint, while an agent who waits too long in a medical case creates a much bigger problem. A short list of examples removes most of the doubt.

Decide who makes the call. In many companies the dispatcher calls, not the driver, because the driver is busy with the passengers and the road. Put the rule on the dispatcher card and in the driver briefing, and repeat it in the training sheet.

Decision 4: Decide What Staff Say and What They Record

A call to an emergency contact is a hard call to make. Write a short script that states who is calling, what happened and what the company is doing now. Keep it factual, and never guess about the passenger’s condition or the cause.

Record every use of an emergency contact. Note the date, the route, who called, who answered and what was agreed. The record protects the passenger and the staff, and it shows whether your bus emergency contact policy works in practice.

Review the record after each case. If staff could not reach the contact, ask whether the number was wrong or whether the data was missing. If the driver could not find the contact, the screen is the problem and not the person.

Decision 5: Decide How the System Supports the Policy

Software cannot write a bus emergency contact policy, but it can make it usable. UBT lists Point-of-Sale, Ticket Validation, Inventory Control and Real-time Reporting. It also lists automated SMS boarding reminders and real time fleet tracking for passengers and management.

Those capabilities matter because an emergency usually starts with a question about where the coach is and who is on it. Whatever platform you use, ask whether the passenger list and the trip status are visible to the dispatcher at the same moment.

Ask the vendor three practical questions. Can the booking collect an optional extra contact? Can a role limit who sees it? Can you export or delete the data when your policy requires it? If the answer is unclear, ask for a demonstration with your own routes.

Common Mistakes in a Bus Emergency Contact Policy

The first mistake is collecting the contact and never testing it. A number that nobody has ever called may contain a typo. Run a small check once a quarter on a sample of bookings and see whether the numbers connect.

The second mistake is keeping the data too long. A contact has a purpose for one trip, so decide when it is removed. Your legal counsel can tell you what the rule requires where you operate.

The third mistake is hiding the policy from the passenger. Say in the booking flow why you ask and who sees the answer. Our guide to the bus ticket terms and conditions is a good place to add that sentence.

The fourth mistake is a policy that lives in one manager’s head. Put the bus emergency contact policy on the dispatcher card, in the driver briefing and in the onboarding sheet for new agents, and review it after any serious incident.

Put Your Bus Emergency Contact Policy Into Practice

A clear bus emergency contact policy says whether you collect a contact, what you store, who can see it, when staff use it and how the call is recorded. Start with the one route where an emergency would be hardest to handle, and test the policy there.

To see POS, ticket validation, inventory control and real-time reporting in action, United Bus Tech provides Technology as a Service with no cost and no obligation if you do not like it. Request a free walkthrough from United Bus Tech and bring your own passenger data questions.