Express courier. Direct.
Also overnight.
x25pronto Switzerland takes goods direct to the destination. Small loads go by car. Larger loads go by van or Van XL. Direct, express and overnight trips run Monday to Sunday when a slot is free. Free times are shown in the booking calendar. This keeps the plan clear.
Standardised exception definitions and escalation levels for branch logistics
Clear exception definitions and tiered escalation speed up decisions across branch networks. This practical framework helps Swiss businesses act consistently.
Quick answer
Define exceptions in clear categories (e.g. damaged parcel, missing documents, wrong delivery), standardise reporting channels and set three to four escalation levels. This reduces resolution time in Zurich, Geneva or Lugano and gives consistent decision rules.
Why standardised exceptions matter
Vague terms cause delays and inconsistent fixes. Branches in different cantons often use their own wording. A single taxonomy creates comparability. Teams in Basel, Lausanne or St. Gallen can decide faster and restore operations.
Core categories for exceptions
Use a short, clear list. Recommended categories: 1) Damaged parcel, 2) Missing or wrong delivery, 3) Missing/incorrect documents, 4) Address issue/return, 5) Time-critical delay. Add short definitions and examples so staff classify incidents correctly.
Three to four escalation levels — structure and roles
Level 1: Branch handles and documents; simple fixes without approval. Level 2: Regional supervisor reviews and decides (e.g. replacement delivery, damage claim). Level 3: Central operations or customer service makes decisions with financial or legal impact. Optional Level 4: Management escalation for reputation or compliance risks. Each level has a maximum response time and a set of allowed actions.
Communication and reporting channels
Use consistent reporting channels: mobile app, web form and phone hotline. Each ticket gets an ID and required fields (category, photos, signature optional). Automatic routing and status updates by e‑mail or push reduce follow-ups. Consider integrations to your TMS or ERP for smoother workflows.
KPIs and continuous improvement
Track resolution time per escalation level, repeat incidents per branch and first-contact resolution rate. Monthly reports reveal trends. Use data for targeted training or process changes.
Practical checklist to roll out a new exception rule
1) Category name and definition, 2) real-world examples, 3) mandatory ticket fields, 4) responsible party per escalation level, 5) maximum response times, 6) permitted actions per level, 7) communication channels, 8) reporting fields. The checklist helps scale consistency across sites.
Frequently asked questions
How detailed should exception categories be?
As detailed as needed but as short as possible. Too many categories confuse users. Five to seven main categories usually suffice and allow for notes.
What response times are realistic?
Branch actions (Level 1) should happen within 30–60 minutes. Regional responses (Level 2) within 2–4 hours. Central decisions (Level 3) within one business day. Adjust times to your service level and capacity.
How to train staff quickly and consistently?
Use short e‑learning modules, case studies and a one‑page reference card at the branch. Quarterly refreshers and review of incident reports keep rules current.
Do we need IT changes for the reporting channels?
Not immediately. Many teams start with standard forms and a shared inbox. Longer term, integrate with your TMS for automation and better reporting.