Self Service for Ferry Operators
Self Service focuses on letting customers complete suitable booking and travel tasks without staff intervention. The page covers the complete workflow, records, exceptions, integrations and decision criteria.
One source of truth for passenger self-service
This detailed workflow is a solution-design requirement, not an assertion that every step is available in every Ferry Software configuration. It must be confirmed during project scoping; the documented platform foundation is central booking, fares and payments, communication, reporting, mobile control and API integration. The workflow must create one reliable operational view for customers, booking agents, terminal staff, finance users and system administrators.
Authenticate the booking to send updated documents
A complete passenger self-service follows a deliberate sequence: authenticate the booking, show permitted actions, validate the fare conditions, recalculate price or capacity, request payment when needed, confirm the change and send updated documents. Each transition needs a visible status, an owner and a defined next action. The system should not silently assume success after an interruption. If a step changes price, capacity, entitlement or departure readiness, the dependent records must be recalculated before confirmation. Staff also need to distinguish a temporary hold from a completed transaction.
Booking reference, customer verification and permitted action
The workflow relies on connected data objects rather than one undifferentiated customer record. The important records are booking reference, customer verification, permitted action, fare condition, change amount, payment and reissued ticket. Each object needs a stable identifier and a clear source of truth. Validation should happen when the data is captured, but authorized staff must be able to correct genuine operational differences without deleting the original history. Changes that affect capacity, price, payment or boarding should create a traceable event.
Customer verified and action permitted
Configuration determines which transactions are permitted and which require review. Roles should separate day-to-day sales from tariff configuration, sensitive overrides and financial corrections. A decision is made against customer verified, action permitted, capacity available, amount settled and new state confirmed. The outcome should be reproducible: two trained users given the same facts should reach the same result. Where local policy allows discretion, the user records a reason and the approving role. This protects customers from inconsistent treatment and helps management improve rules that regularly cause exceptions.
Handling name change not permitted or vehicle change needs manual review
Real ferry operations do not follow a perfect happy path. The design must explicitly cover situations such as name change not permitted, vehicle change needs manual review, departure already closed, additional payment fails and customer opens two sessions. For each case the operator defines whether the transaction is blocked, recalculated, transferred to another role or allowed with an override. The user must see what changed and which downstream records are now stale. A correction is only complete when affected capacity, price, documents, payment and operational lists agree again.
Customer website to email delivery
The relevant hand-offs include customer website, booking platform, payment provider and email delivery. Integration is useful only when identifiers, timing and failure behaviour are agreed. A request may time out after the central system has already accepted it, so retries must not create a second booking, charge or capacity reservation. Interfaces should authenticate callers, validate codes and report actionable errors. Monitoring should show both technical delivery and business reconciliation. Ferry Software documents an open API and synchronization with websites, partner platforms and external systems; the exact endpoints and connected products are confirmed for each implementation.
Three passenger self-service scenarios
A customer-facing example starts with the task “authenticate the booking”, continues with “show permitted actions” and must finish with a state that staff can see without re-entering the transaction. An operational example examines this exception: name change not permitted. the team needs a controlled decision, a reason and a traceable result rather than an informal workaround. A connected-channel example sends the same authoritative record through customer website and booking platform, while preventing duplicate capacity or payment effects.
Confirming customer verified, action permitted and capacity available
Before confirming a transaction, the responsible role checks customer verified, action permitted, capacity available, amount settled and new state confirmed. The relative importance of these checks depends on the page: an operational control may prioritize departure and entitlement, while a commercial workflow also considers price and payment. Operators define cut-off times, override permissions, escalation paths and evidence requirements.
Piloting Self Service
Implementation should begin with one representative route and a small set of trained roles. Map the current process, remove duplicate entry, configure the authoritative data and rehearse both normal and disrupted sailings. Confirm that existing editorial pages, customer communications and operating procedures remain intact. During rollout, measure completion time, unresolved exceptions, reconciliation differences and staff feedback. Expand only after the pilot can be supported reliably.
Frequently asked questions
What operational problem does Self Service for Ferry Operators address?
Self Service focuses on letting customers complete suitable booking and travel tasks without staff intervention. The page covers the complete workflow, records, exceptions, integrations and decision criteria. It connects the customer or staff action with capacity, commercial and departure records instead of leaving separate teams to reconcile them manually.
Which steps belong to the passenger self-service?
The core sequence is: authenticate the booking, show permitted actions, validate the fare conditions, recalculate price or capacity, request payment when needed, confirm the change and send updated documents. The exact rules and user responsibilities are configured for the operator’s routes, vessels, channels and working procedures.
Which records must remain consistent?
The primary objects are booking reference, customer verification, permitted action, fare condition, change amount, payment and reissued ticket. Stable identifiers and status history are required so changes can be traced across booking, operational and financial views.
How should exceptions be handled?
The implementation defines explicit actions for cases such as name change not permitted, vehicle change needs manual review and departure already closed. Each resolution needs an authorized role, a reason and updates to every affected downstream record.
Can this workflow connect with other systems?
Relevant connections include customer website, booking platform, payment provider and email delivery. The documented Ferry Software API supports integration, while authentication, available endpoints, retry behaviour and reconciliation are agreed for the specific project.
Is every described capability included by default?
No. This page describes the required business workflow. Availability and project scope must be confirmed before it is presented as an enabled Ferry Software capability.