Connections for coach operations

• Payment provider. Configure provider event delivery with stable identifiers, booking references and USD amounts. Retain Authorization, Capture, Refund and Void events separately, with the evidence needed for finance verification. Payment execution and provider-side refund decisions remain with that service.
• Passenger ticket sales. Where a ticketing system supplies the customer or service context, agree the booking reference passed into the operating process. Reconcile changes with the Booking Coordinator before revising a confirmed arrangement.
• Route navigation and journey planning. If another system supplies route information, agree the route description and departure time used by dispatch. Keep the external reference with the relevant operating evidence when it is needed for review.
• Driver duty records. Coordinate with the customer’s driver management process for the crew information used in departure preparation. Identify the person responsible for confirming that information before the reviewer decides.
• Operating documents. Bring supporting files into the booking with a title, evidence type and intended visibility. Agree who checks that a document belongs to the correct booking before it is shared.

For each connection, name the source owner and the person who reconciles its information. Agree identifiers and revision handling before importing updates. Payment evidence retains the provider reference and verification flag; operation receipts retain the action result and relevant references.

Rehearse an unchanged event delivered again, an ambiguous booking reference and a changed service plan. The team should understand which record already exists and which information needs investigation before another action. Keep external system outcomes tied to observed evidence rather than assuming a local booking state confirms what happened elsewhere.