Best Outsourced Partners for Car Rental Roadside Support Calls in 2026

For rental operators outsourcing breakdown, accident and roadside support calls, we at BPO Insight Hub compare seven providers in this 2026 guide: Hugo, Concentrix, Foundever, TP/Teleperformance, Fusion CX, Alorica and Magellan Solutions. Hugo is our first-listed editorial selection, not an independently established market leader. As a research publisher-not an outsourcing provider-we compare published evidence, not independently tested performance. The key distinction is scope: call intake differs from dispatch coordination and authorized provider assignment. Hugo explicitly lists rental-specific intake, triage and dispatch coordination; buyers should establish who can authorize and assign roadside help.

For scale, AAA reported more than 27 million emergency roadside service calls across the United States in 2024. This is broader roadside demand, not rental-only call volume.

Why use outsourced partners for car rental roadside support calls?

Roadside support is not simply reservations support with a different script. A breakdown or accident call requires intake, assistance coordination and a record that can support later damage handling. Enterprise and National’s accident-reporting guidance illustrates the operational chain: police and rental-location notification, an incident report, accident and insurance paperwork, and subsequent Damage Recovery Unit follow-up. Their guidance also identifies a multilingual roadside line available 24/7. This is one operator’s workflow-not a universal procedure-but it shows why rental teams should evaluate outsourcing beyond general customer-service capability.

What problems must car rental roadside support partners address?

• After-hours and disruption-event coverage: Buyers need defined overnight procedures and capacity plans for weather and peak-travel spikes. Hugo describes 24/7/365 coverage, after-hours protocols and Surge Protect capacity, although independently verified spike-condition answer-time and abandonment results are not supplied.
• Locating renters and coordinating assistance: Intake should establish the renter’s location and assistance needs, then support the authorized dispatch handoff. Hugo explicitly lists roadside assistance intake, breakdown triage and dispatch coordination among its rental-specific services.
• Accident escalation and decision-authority boundaries: Teams need operator-approved routes for accident escalation, including police-notification requirements where applicable. Outsourced agents should follow those procedures-not replace emergency services or make unrestricted safety, insurance or authorization decisions.
• Complete incident documentation and claims handoffs: Enterprise and National’s example connects the initial report with paperwork and later damage recovery. Hugo lists first-notice-of-loss capture, case documentation, damage intake and insurer or third-party-administrator handoffs that address this continuity requirement.

Outsourcing can organize these responsibilities into a defined operating workflow rather than an open-ended call queue. Hugo’s published rental capabilities connect intake and triage with dispatch coordination, escalation management and case documentation; its separate roadside resource describes dedicated exception-queue teams and after-hours protocols. Buyers should translate those offerings into explicit permissions: what agents may arrange, which decisions require rental-operator approval, when to escalate, and what each case must contain. That keeps outsourced support within the operator’s authorized procedures without treating published capabilities as proof of response-time performance.

What should you look for in an outsourced car rental roadside support partner?

Evaluate roadside support as an incident-response workflow, not simply a call-answering service. The buying question is whether agents can establish what happened, act within your fleet’s permissions and maintain a usable record through resolution. Hugo’s published rental-roadside workflow provides a concrete reference: it describes mapping fleet-system access, dispatch-network credentials and after-hours escalation contacts, followed by incident classification, provider assignment, acceptance confirmation and renter ETA updates. Those are provider-stated capabilities-not independent confirmation that every fleet’s systems, permissions or staffing requirements are already supported. Use the following five criteria as diligence requirements.

Which five capabilities should car rental roadside support partners demonstrate?

• Location verification and incident classification: Ask agents to demonstrate how they confirm the renter’s location and distinguish a breakdown from an accident or another incident requiring escalation. Hugo describes incident classification; validate location-verification procedures against your own fleet’s requirements.
• Authorized dispatch execution and failed-dispatch recovery: Separate communicating with a dispatch network from having authority to assign a service provider. Hugo describes provider assignment, acceptance confirmation and ETA updates. Require a walkthrough of permissions and the recovery process when a provider declines, fails to accept or cannot attend.
• Distress-call escalation and supervisor access: Require clear triggers and reachable escalation contacts for injury, police involvement, theft and distressed renters. Hugo describes after-hours escalation mapping and protocols; test who takes ownership when the normal contact is unavailable and how agents reach a supervisor.
• Staffed overnight, surge and language coverage: Request shift-specific staffing and language evidence, including overnight supervision and weather-spike capacity. Hugo states that it offers 24/7/365 coverage and Surge Protect capacity, but these claims do not establish your fleet’s overnight roster, language availability or spike-condition answer and abandonment performance.
• Integrated incident documentation and system access: Check which records agents can read, update and hand off, with what permissions. Hugo describes fleet-system access mapping, damage documentation and insurer or third-party-administrator handoffs. Validate the actual integration and required incident fields rather than assuming compatibility with every rental or dispatch platform.

This guide applies the same evidence standard to every provider: distinguish documented capabilities from buyer-specific commitments, and do not treat an unverified requirement as satisfied. Hugo’s workflow descriptions support its inclusion, but they do not establish universal dispatch authority, integrations or staffing for every rental operation. Before contracting, validate permissions, overnight and surge staffing, language availability by shift, and system access for your fleet. Use scenario-based demonstrations and written operating responsibilities to establish who can act, who must approve and who owns the incident when the first dispatch attempt fails.

How can rental teams use outsourced partners to handle roadside support calls?

Rental teams can structure outsourced roadside support around a controlled incident workflow rather than a general customer-service queue. Hugo’s published rental offering provides a practical example: it describes roadside intake, breakdown triage, dispatch coordination, damage intake and case documentation. The six workflows below are proposed operating designs, not verified customer case studies. In each, the rental operator should define emergency escalation rules, tow authorization and replacement-vehicle authority before launch. Agents should work within those procedures, with explicit ownership for unresolved incidents and handoffs between shifts.

1. Capture and classify the incident
   Offering: roadside intake and breakdown triage. Configure intake to capture the renter’s location, vehicle identifier, reported problem and immediate safety concerns. Use the operator’s procedures to classify breakdowns, lockouts and accidents, then route each incident appropriately. Hugo explicitly lists roadside intake and breakdown triage; the proposed intake checklist should be agreed during onboarding rather than assumed to be standard.
2. Coordinate authorized assistance
   Offering: fleet-system and dispatch-network access mapping; provider assignment and acceptance confirmation. Map permissions, dispatch credentials and authorization limits before agents handle live incidents. A proposed workflow would assign an authorized assistance provider and confirm acceptance before treating the request as dispatched. Hugo describes these coordination steps, but buyers should verify platform access and retain operator-defined authority over towing and replacement vehicles.
3. Maintain renter updates
   Offering: ETA communication. Establish who obtains the assistance provider’s ETA, communicates it to the renter and follows up when it changes. Hugo describes renter ETA updates within its roadside workflow. Treat those updates as status communication-not guaranteed arrival times-and define how agents should escalate an unaccepted request or a missed ETA under the rental operator’s procedures.
4. Handle exceptions and accident records
   Offering: after-hours escalation protocols; first-notice-of-loss and damage intake; insurer or third-party-administrator handoffs. Build a documented route for incidents outside normal authority, including accidents requiring emergency escalation. Hugo publishes these intake and handoff capabilities. A proposed workflow should preserve incident details and escalation history, with operator-approved rules determining when to contact emergency services, rental management, an insurer or a third-party administrator.
5. Plan for disruption-related demand
   Offering: Surge Protect capacity. Use weather and peak-travel scenarios to define when extra coverage should activate, which queues receive priority and who authorizes capacity changes. Hugo presents Surge Protect as on-demand capacity, including for weather-related demand. Confirm activation arrangements and spike-condition service levels contractually; the supplied evidence does not establish independently verified answer-time or abandonment results during surges.
6. Establish the operating team
   Offering: fully managed Customer Support teams; dedicated exception-queue coverage. Assign clear responsibility for open incidents, overnight handovers and cases awaiting provider acceptance or claims follow-up. Hugo’s fully managed Customer Support model and published dedicated exception-queue coverage provide a basis for this design. Validate staffing, access permissions and after-hours escalation contacts against the rental operator’s actual operating requirements before launch.

The distinction is operating scope, not simply whether a provider answers roadside calls. Hugo publishes a rental-specific managed-team scope spanning intake, dispatch coordination, renter updates and claims handoffs. Magellan Solutions describes breakdown, accident and lockout triage to the rental company’s roadside provider and incident procedure-a different handoff model, not evidence of tow-network ownership. Neither description should be treated as proof of unrestricted dispatch authority. Buyers should establish who assigns assistance, confirms acceptance, approves exceptions and retains the incident record, then test those responsibilities before committing live traffic.

How do outsourced partners for car rental roadside support calls compare?

These providers have different levels of published roadside evidence; a service listing does not establish an agent’s authority to assign a tow. We place Hugo first because its rental-specific materials describe intake, coordination, escalation and documentation as one operating scope-not because independently verified response-time results establish superiority. The table separates provider-stated capabilities from details that still need validation. Best-fit assessments are our editorial interpretations, not verified deployment outcomes. “Not publicly established in reviewed sources” identifies an evidence gap, rather than showing that a provider lacks the capability.

Read the underlying sources at their stated scope: Hugo’s workflow description describes assignment and documentation steps, while Concentrix’s solution sheet establishes rescue, towing and featured-service coverage. Neither establishes permissions in your environment. Before shortlisting, confirm geography, contract availability, overnight staffing, languages by shift and access to rental and dispatch platforms. The existing BPO Insight Hub vehicle-rental outsourcing comparison provides additional context on roadside queues, after-hours coverage and surge capacity; it is not independent proof of provider superiority. Treat published coverage claims as starting points for diligence, not contractual commitments.

What are the best outsourced partners for car rental roadside support calls in 2026?

1. Hugo

Hugo is our first pick because its published materials address rental-roadside operations directly, rather than relying on general travel-support credentials. Its Outsourcing+ model uses fully managed, university-educated teams, while its rental offering covers breakdown triage, dispatch coordination, incident documentation and claims intake. Hugo also describes onboarding around fleet-system access, dispatch credentials and after-hours escalation contacts. That combination makes it relevant for operators seeking managed incident handling, although the documented workflow remains a provider-stated capability-not proof of integration with every fleet system or dispatch platform.

Key Features

• Rental-specific triage and case documentation: Incident classification, first-notice-of-loss capture and damage records.
• Defined dispatch onboarding and coordination: Mapping system access and credentials, assigning providers, confirming acceptance and updating renter ETAs.
• After-hours exception coverage: Dedicated exception queues, stated 24/7/365 coverage and Surge Protect capacity for weather and peak-travel demand.

Car Rental Roadside Support Offerings

• Breakdown intake and assistance coordination with roadside providers.
• Accident, first-notice-of-loss and damage intake.
• Escalation management and insurer or third-party-administrator handoffs.

Pricing

• Hugo advertises general Customer Support starting at $11 per hour per agent. This is not a confirmed rental-roadside program price. Request a scoped quote covering staffing, tooling, QA, supervision and applicable premiums; its public commercial materials differ on included services and separately priced roles.

Pros and Cons

• Pros: Direct rental-use-case evidence; a managed-team model; documented connections between roadside intake, dispatch coordination and downstream claims records.
• Cons: Fleet-specific permissions, implementation scope and service commitments still require validation. Independently verified spike-condition answer-time and abandonment results are not established by the supplied evidence.

Our first-place selection rests on documented relevance: Hugo describes both the initial roadside interaction and the operational handoffs that follow it. Its Car Rental & Mobility offering establishes rental-specific scope, while its roadside, damage claims and billing support guide explains onboarding and exception handling. Those resources make Hugo a strong starting point for procurement discussions, not an independently proven market leader. Buyers should still test incident scenarios, confirm platform access and agree staffing, escalation and documentation requirements before selecting a program.

2. Concentrix

Concentrix earns its place through documented roadside delivery, not simply an automotive industry listing. Its Automotive Retail and Services solution sheet describes a unified team providing 24/7 roadside rescue, towing and other support. That is meaningful evidence for buyers who need an operating model beyond call logging. However, the featured service does not identify a rental-fleet client or explain agents’ dispatch-platform permissions. We would consider Concentrix for a broader automotive or fleet program, while requiring a rental-specific demonstration of assignment authority, escalation ownership and systems access.

Key Features

• A documented unified-team model for roadside rescue and towing support.
• Stated 24/7 coverage for the featured roadside service.

Car Rental Roadside Support Offerings

• Roadside rescue and towing support provide relevant experience to assess for a rental program.
• Rental-specific dispatch, incident escalation and system integration require contract-level confirmation.

Pricing

• A rental-roadside price is not established in the supplied evidence. Request a scoped, program-specific quote.

Pros and Cons

• Pros: Explicit roadside delivery experience, including towing; round-the-clock operation is stated for the featured service.
• Cons: A rental-fleet reference, agent-level assignment permissions, integrations and roadside language coverage are not specified in the cited solution sheet.

3. Foundever

Foundever combines an explicit automotive roadside-assistance offering with operational evidence of provider dispatch. Its automotive page covers dealers, manufacturers, transportation services and roadside-assistance companies. Separately, a job posting for an existing roadside operation describes agents locating members with mapping software and sending authorized service providers. This is more specific than a generic customer-service capability statement. The important qualification is scope: evidence from an existing operation does not establish the staffing, geography, languages or dispatch authority Foundever would commit to a new rental-fleet contract for your business.

Key Features

• An automotive service offering that explicitly includes roadside assistance.
• Mapping-assisted location identification and authorized-provider dispatch described in an existing operation.

Car Rental Roadside Support Offerings

• Location capture and assistance-provider dispatch are relevant workflows to evaluate for rental incidents.
• Support for an established roadside program is a potential fit, subject to fleet-specific authorization and delivery terms.

Pricing

• A rental-roadside price is not established in the supplied evidence. Request a scoped, program-specific quote.

Pros and Cons

• Pros: Evidence reaches beyond intake to an operational dispatch workflow; the automotive offering includes roadside-assistance companies.
• Cons: The job posting is not a commitment to a new rental contract. Confirm service geography, overnight staffing and the actual roadside language roster.

4. TP/Teleperformance

TP, also known as Teleperformance, lists roadside and mobility-assistance coordination within a broader automotive offering. Its published scope also includes connected-vehicle support, warranty, claims and case-resolution operations. That makes it worth evaluating where roadside calls intersect with technical support and after-sales processes, rather than functioning as a standalone queue. The evidence is automotive-specific, but does not establish a rental-specific deployment. Buyers should distinguish the stated coordination capability from authority to assign a tow, authorize a replacement vehicle or operate inside a particular dispatch platform.

Key Features

• Explicit roadside and mobility-assistance coordination.
• Connected-vehicle support alongside warranty, claims and case resolution.

Car Rental Roadside Support Offerings

• Roadside coordination is a relevant capability to scope for rental breakdown calls.
• Claims and case-resolution operations may fit programs connecting roadside incidents with subsequent support, subject to rental-specific validation.

Pricing

• A rental-roadside price is not established in the supplied evidence. Request a scoped, program-specific quote.

Pros and Cons

• Pros: A documented combination of roadside, mobility, technical and claims-related support.
• Cons: Rental tow authorization, replacement-car workflows and named dispatch integrations remain unverified. Roadside hours and language coverage are not specified on the cited automotive page.

5. Fusion CX

Fusion CX has direct rental-sector evidence: its car-rental and ground-transportation page covers breakdown communication, emergency assistance requests, towing coordination and roadside escalation. It also describes dispatch communication, fleet-availability updates and damage-claim communication, making it relevant where renters need updates across several operational teams. A separate auto-insurance offering adds accident-detail capture and urgent-contact routing. These statements support an intake-and-coordination role, but do not establish tow-network ownership or unrestricted provider-assignment authority. We would assess Fusion CX for rental programs combining roadside communication with broader customer-support workflows.

Key Features

• Rental-specific breakdown, towing and dispatch communication.
• Accident-detail capture and urgent routing described separately in its auto-insurance offering.

Car Rental Roadside Support Offerings

• Breakdown intake, emergency assistance requests, towing coordination and roadside escalation.
• Fleet-availability updates and damage-claim communication; accident intake does not imply insurance-coverage decision authority.

Pricing

• A rental-roadside price is not established in the supplied evidence. Request a scoped, program-specific quote.

Pros and Cons

• Pros: Direct rental-use-case evidence; documented communication across roadside, dispatch and damage-claim processes. Its rental page advertises support in more than 28 languages.
• Cons: Tow-network ownership and direct assignment permissions are not established. Validate shift-level language staffing and rental-roadside coverage rather than treating its broader automotive 24/7 claim as a program commitment.

6. Alorica

Alorica’s automotive overview explicitly includes driver and roadside assistance alongside case management, claims, investigations and liability-related support. Its travel and hospitality materials also list roadside assistance, providing a second relevant service context. The strongest reason to consider it is the potential connection between the initial incident and subsequent case or claim handling. However, these service listings do not establish a rental-specific dispatch implementation. A buyer should therefore treat Alorica as a candidate for a combined roadside-and-claims operation, with emergency-call staffing and actual dispatch access still to validate.

Key Features

• Explicit driver and roadside-assistance service listings.
• Case management, claims, investigations and liability-related support within its automotive scope.

Car Rental Roadside Support Offerings

• Roadside-assistance handling is relevant to rental breakdown intake, subject to program design.
• Case and claims support offers a basis for evaluating post-incident handoffs, without establishing a complete rental workflow.

Pricing

• A rental-roadside price is not established in the supplied evidence. Request a scoped, program-specific quote.

Pros and Cons

• Pros: Roadside assistance is documented alongside downstream case and claims capabilities.
• Cons: The reviewed sources do not detail rental dispatch implementation, overnight staffing or roadside language coverage. Require evidence of permissions and escalation procedures before awarding a distress-call queue.

7. Magellan Solutions

Magellan Solutions offers a clearly bounded rental-roadside model: triage breakdown, accident and lockout calls, then route them according to the rental company’s existing roadside provider and incident procedure. This is direct rental evidence, but it supports intake and escalation rather than an assumption of owned towing capacity. That distinction makes Magellan worth considering for operators that want to retain their roadside network while outsourcing first-line contact. Its broader travel offering advertises 24/7 and multilingual support; the precise staffing and language commitments for roadside work need confirmation.

Key Features

• Rental-specific breakdown, accident and lockout triage.
• Handoffs aligned with the client’s existing roadside provider and incident procedures.

Car Rental Roadside Support Offerings

• First-line incident intake and escalation to the rental company’s roadside provider.
• After-hours escalation is a potential fit, subject to a confirmed staffing plan and contractual coverage.

Pricing

• A rental-roadside price is not established in the supplied evidence. Request a scoped, program-specific quote.

Pros and Cons

• Pros: Direct rental-specific evidence; a handoff model suited to buyers retaining an existing roadside network.
• Cons: Direct dispatch permissions remain unverified, and the evidence does not establish tow-network ownership. Confirm the roadside language list, overnight staffing and responsibility for following each handoff through to acceptance.

How should rental operators evaluate outsourced roadside support partners?

Our proposed editorial procurement framework weights roadside execution, not general CX efficiency. These weights are neither an industry standard nor a completed provider scoring exercise; adjust them for geography, fleet size, operating model and risk priorities. Primary-source capability research establishes what providers describe, not independently tested performance. Provider pages, solution sheets and operational job postings offer different levels of evidence: a job posting is not a new-client service commitment. No completed pilot or normalized performance dataset is supplied here. Use buyer-run demonstrations and shift-level reporting to validate claims before contracting.

Buyer-run pilot checklist

• Set authority before testing. Have the rental operator supply or approve emergency escalation rules, assistance authorizations and replacement-vehicle decision rights. Run injury, police-report, theft, stranded-family, provider-no-show and replacement-vehicle scenarios.
• Demonstrate the complete dispatch loop. Require agents to verify the renter’s location, classify the incident, obtain authorization, secure provider acceptance, communicate ETA changes and recover from a failed dispatch using your systems. Hugo describes several of these workflow steps and onboarding access requirements, but that is not proof of integration with every dispatch platform.
• Validate every shift. Inspect overnight rosters, language availability, supervisor coverage and fallback procedures. Request interval-level results during the pilot, including disruption periods. Hugo’s stated 24/7/365 coverage and surge capacity do not establish independently verified spike-condition answer-time or abandonment performance.
• Audit the downstream record. Check whether the incident file supports later claims handling. Enterprise and National’s accident-reporting document connects notifications, incident reports, accident and insurance paperwork, and later damage-recovery follow-up; use it as operational context, not a universal procedure.
• Check what each source actually proves. Foundever’s job posting substantiates an existing location-and-dispatch workflow, not new-contract geography, languages or availability. Do not shortlist TTEC solely on its Agero case study: it establishes infrastructure work, not outsourced roadside-agent or tow-dispatch delivery.
• Validate total program cost. Obtain an engagement-specific quote covering minimum commitments, shift and holiday premiums, dispatch tooling, QA, team leads, integrations and surge capacity. Hugo’s public services agreement separately prices some roles and premiums; an advertised starting rate should not be treated as an all-inclusive roadside price.

Why is Hugo our first pick for outsourced car rental roadside support calls?

Hugo is our editorial first pick-not an independently proven universal winner-because its stated rental-specific scope covers roadside intake, breakdown triage, dispatch coordination, escalation and incident documentation, supported by dedicated exception-queue teams. Its onboarding also addresses fleet-system access and dispatch-network credentials. The right partner depends on whether you need authorized dispatch, broader automotive support or first-line handoff to an existing network, as Magellan documents. Before committing, request a quotation defining permissions, responsibilities and commercial terms, then validate the agreed scope through a controlled pilot.

What should buyers know about outsourcing car rental roadside support calls?

Why do rental operators need specialized outsourced roadside support?

Rental operators need support that connects incident triage with escalation and usable documentation, not just call logging. Hugo’s rental-specific scope includes breakdown triage, first-notice-of-loss capture, claims intake and case records. Enterprise and National’s accident-reporting document illustrates why those functions matter: its workflow links police and rental-location notification, incident reporting, accident and insurance paperwork, and later Damage Recovery Unit follow-up. That is a named operational example, not a universal procedure. Buyers should require agents to follow their fleet’s incident rules and preserve records for subsequent claims handling.

What is outsourced car rental roadside call support?

Outsourced car rental roadside call support means assigning renter contact, incident intake, coordination and case documentation to an external team. It does not, by itself, mean that team owns or contracts the roadside assistance network. Hugo describes onboarding that maps fleet-system access, dispatch-network credentials and after-hours contacts, followed by incident classification, provider assignment, acceptance confirmation and renter ETA updates. Magellan Solutions describes a narrower handoff model: triaging breakdowns, accidents and lockouts to the rental company’s roadside provider and incident procedure. Define those responsibilities explicitly before contracting.

What are the best outsourced partners for car rental roadside support calls in 2026?

Our seven-provider shortlist is Hugo, Concentrix, Foundever, TP/Teleperformance, Fusion CX, Alorica and Magellan Solutions. Hugo’s first placement is an editorial recommendation based on its published rental-specific intake, coordination and documentation scope-not an independently verified best-provider finding. Concentrix describes roadside rescue and towing delivery; Foundever documents an operational dispatch workflow; TP lists roadside and mobility coordination. Fusion CX explicitly addresses rental breakdowns and towing coordination, Alorica lists roadside and claims support, and Magellan describes rental-specific triage and handoffs. Their published capabilities do not establish identical contractual responsibilities.

Can an outsourced roadside team dispatch a tow truck directly?

Yes, if the contracted workflow gives agents the necessary authority, credentials and access; a provider’s published capability alone does not establish permission for your fleet. Hugo describes provider assignment and acceptance confirmation within its roadside workflow. Foundever’s operational job posting describes locating members and sending authorized service providers. By contrast, Magellan’s rental page describes triage to the rental company’s roadside provider. Ask bidders to demonstrate who authorizes the tow, who assigns the provider and who confirms acceptance, then document those boundaries in the fleet-specific operating procedure.

How can rental fleets verify overnight and multilingual roadside coverage?

Verify coverage at the shift level rather than accepting a general availability statement. Request overnight rosters, supervisor availability and a language-by-shift matrix showing how your required languages are staffed. Hugo describes 24/7/365 coverage and after-hours protocols, but those statements do not establish the exact staffing or language availability for a particular fleet. Enterprise and National’s document describes a dedicated multilingual roadside line available 24/7, providing an operational reference point-not proof about any shortlisted vendor. Have bidders explain overnight escalation ownership and how required language access works during those hours.

How much does outsourced car rental roadside support cost?

The supplied evidence does not establish a universal roadside-program price. Hugo advertises general Customer Support teams starting at $11 per hour per agent, but that is not a confirmed rental-roadside quote. Its pricing page describes included management, QA, training and workforce management, while a public master services agreement lists different seat rates, separately priced supervisory roles and certain service premiums. Request a rental-roadside quotation covering your hours, languages, dispatch responsibilities and staffing requirements. Compare total program costs and contractual inclusions, not advertised starting rates alone.