Start with one station and one service. Expand on measured results.
A first deployment is scoped to your systems, stations and providers. It produces the measures that justify the next station, and most of what it builds is reused when you add one.
The pathway
1. Scope
One product at one station. Agree the source of cases (console, file feed or integration), the providers, the service levels and who does what.
- Scope note
- Responsibility matrix
- Success measures
2. Set up
Tenant, branding, station rules and cut-offs, provider onboarding, passenger message templates, user roles. Typically weeks, not months.
- Configured tenancy
- Integrated providers
- Trained users
3. Run and measure
Live cases with weekly reviews against the agreed measures. Exceptions are the operating rhythm, not the surprise.
- Weekly scorecard
- Exception log
- Cost per case
4. Expand
Add the next station or product when the measures are met. Rules, providers, templates and reports carry over; local inputs are established per station.
- Expansion criteria met
- Next-station checklist
Success measures we agree up front
- Cost per resolved case
- Delivery performance against the promised window
- Proof completeness (custody and delivery evidence)
- Manual effort per case
- Passenger contacts per case
- Time to reunification
What is reused when you add a station
Reused as-is
Tenancy, workflows, message templates, provider integrations already live, reports, user roles, invoicing set-up.
Configured per station
Cut-offs, hand-over points, local providers and rates, airport rules.
Established per station
Collection location and release authority, hand-over arrangements with the local handler, screening route, local service costs, data-residency or regulatory steps where they differ.
Who does what, by operating model
| Model | Manages providers | Handles exceptions | Supports passengers | Owns the customer |
|---|---|---|---|---|
| Platform licence | You | You | You, with HalaBag templates and channels | You |
| Platform licence + per-case fee | You, with HalaBag's network available | You | You, with HalaBag templates and channels | You |
| Managed service (agreed scope) | HalaBag operations | HalaBag operations, escalations to you | HalaBag, under your brand | You |
Platform, usage and managed-service fees are agreed around the deployment scope. Fulfilment charges and partner commercial arrangements are defined separately.
Assess the problem and plan a first deployment
Tell us the stations, providers and source of cases. We come back within one business day with a scoped first deployment and the measures we would agree.