Skip to main content
GullySystem
Logistics

Ticket Management for Courier companies

Keep courier enquiries and disputes linked to their shipment evidence and responsible customer or carrier action.

Helpdesk

Does this function belong in your operation?

Use where the counter or account desk follows cases across customers, collectors and external carriers.

A customer reports a missed collection, disputed shipment outcome, return issue or service-charge concern.

A shipment enquiry needs the booking and carrier reference, latest sourced status and the customer’s actual concern. Keep missing-pickup cases separate from disputed delivery, packaging or billing questions so the responsible person can act. Record carrier case numbers and outstanding customer information without promising an external response. Closure should explain the evidenced outcome; a delivered status, submitted claim or promised refund alone does not settle every part of the customer’s issue.

Bring the records the workflow depends on.

  • Customer concern and actual booking or carrier reference
  • Latest sourced tracking or handover evidence
  • Customer-provided observations and relevant permissions
  • Named owner, external case reference and closure criteria

Outputs to check

  • Shipment-linked enquiry register
  • Customer and carrier action history
  • Evidenced resolution and reopening record

Follow the ticket management workflow.

Use this sequence to compare your current process with the proposed module. Agree the owner, permission and exception at each step.

  1. 1. Record the actual concern

    Retain the customer’s report and affected shipment. Distinguish missed pickup, recipient dispute, return request and billing issues.

  2. 2. Review available evidence

    Compare actual handover records and sourced status information without overwriting conflicting customer evidence.

  3. 3. Assign the next action

    Identify the responsible internal person and any customer or carrier dependency. Record the external case reference where one actually exists.

  4. 4. Review the response

    Retain the carrier’s findings and customer response. A claim submission is not a claim decision or completed reimbursement.

  5. 5. Close or reopen with reasons

    Explain what evidence supports closure and what separate financial or custody action remains. Preserve earlier history when new evidence reopens the case.

Who uses the module, and who approves?

Keep responsibilities distinct even when one person holds more than one role.

Support owner

Maintains the case evidence, customer communication and next action.

Custody or pickup coordinator

Supplies actual collection and handover information for investigation.

Accounts reviewer

Owns the decision and evidence for disputed charges, credits or refunds.

Decide how exceptions are handled.

These business rules belong in configuration and testing. A normal transaction alone does not demonstrate that the workflow is ready.

Carrier says delivered but recipient disagrees

Retain both records and request the relevant delivery evidence without treating either statement as automatic resolution.

Several messages concern the same parcel

Link them to the case while preserving each new observation.

Carrier investigation remains pending

Show the dependency and named follow-up owner without promising its decision or response date.

Can this work independently?

The desk needs authorised access to relevant booking and carrier evidence. The carrier, insurer or authority owns its actual investigation and decisions. A ticket coordinates follow-up; it does not make those external services available or establish a financial settlement.

Systems and records it connects with

  • Orders and tasks: Accepted booking, actual pickup and custody outcomes.
  • Carrier evidence: Dated status and available delivery or return records.
  • Accounts: Approved charge corrections and separately executed refunds.

Configure, test and introduce the workflow.

  • Review a missed pickup and a disputed delivery from actual support records.
  • Agree evidence access, external dependency ownership and closure reasons.
  • Test a delivered-status complaint and an approved-but-unpaid refund while keeping each outstanding action visible.

Check the result before rollout.

Apply these checks to a sample from the agreed workflow, then repeat with an exception. Keep the expected result beside the test record.

  • Cases identify the affected shipment and real customer concern.
  • External responses preserve source and case reference.
  • Claim acceptance, refund approval and actual settlement are distinct.
  • Reopened cases retain earlier decisions and evidence.
Courier companies

How the business operates.

A courier company’s counter or account desk receives a document or parcel request, checks the information needed for an actual carrier service and coordinates collection or counter handover. A booking reference is different from physical acceptance by the carrier. This proposed software scope covers counter bookings and recurring office or seller pickups, with shipment follow-up and service billing. It accommodates an operator’s own collection team or a confirmed carrier collection without assuming an owned transport network. International enquiries require the actual carrier’s current acceptance and document review; recording a sender’s declaration does not verify the contents or provide customs clearance.

Booking and acceptance review

Identify sender, recipient, billing account, parcel pieces and declared contents. Refer unresolved item or destination questions to the actual carrier before treating the requested service as accepted.

Collection and counter custody

Record the pickup request or actual counter receipt. Track labels, piece counts and handover evidence, including parcels still awaiting carrier acknowledgement.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Sender, recipient and actual service-buyer references
  • Declared contents, piece count and measured or supplied package information with source
  • Requested carrier service and acceptance or document-review references
  • Pickup request, counter receipt and actual carrier handover evidence

Operational bottlenecks to check

A label exists but the parcel is still at the counter

Booking data and physical custody have different milestones. The desk needs to identify parcels lacking a carrier handover acknowledgement.

International answers differ between staff

Retain the actual carrier response for the declared item and destination. Do not turn an earlier acceptance for another shipment into a universal permission.

How work flows across this business

This module sits within a wider operating process. Use the sequence to identify the other teams and records affected by a change.

  1. 1. Record the shipping request

    Capture the sender’s information and the service requested. Distinguish documents from goods as directed by the actual carrier, keeping unresolved content questions visible.

  2. 2. Confirm the service basis

    Retain the reviewed carrier option, accepted charge basis and required next actions. A rate indication or printed label does not establish physical acceptance.

  3. 3. Coordinate collection and handover

    Assign the actual pickup work or confirm the external collection request. Reconcile received pieces with the handover acknowledgement and retain any mismatch.

  4. 4. Follow the shipment evidence

    Record the carrier’s status with its source and time. Obtain the available delivery evidence or route a reported problem to a named case owner.

  5. 5. Reconcile and close responsibilities

    Bill approved service charges and allocate verified receipts. Keep a carrier investigation, returned parcel or financial adjustment open until its own outcome is supported.

Industry reports to connect with

  • Bookings awaiting content, carrier or document clarification
  • Pickup requests by assignment and evidenced outcome
  • Counter parcels awaiting acknowledged carrier handover
  • Shipment enquiries awaiting customer or carrier action

Questions before implementation.

When should courier companies consider ticket management?

Use where the counter or account desk follows cases across customers, collectors and external carriers. A customer reports a missed collection, disputed shipment outcome, return issue or service-charge concern.

What should we bring to the requirements discussion?

Bring anonymised examples of Customer concern and actual booking or carrier reference; Latest sourced tracking or handover evidence; Customer-provided observations and relevant permissions; Named owner, external case reference and closure criteria. Show who creates, checks and changes each record. Use only records from an activity that meets the suitability conditions above.

Does this replace our existing business software?

The starting point is your current system and the gap you need to close. Keep courier enquiries and disputes linked to their shipment evidence and responsible customer or carrier action. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

Closing a support case does not establish delivery, resolve legal liability or execute reimbursement.

How are scope, price and rollout decided?

The proposal follows a review of your records, user roles, branches and existing software. Data migration, connections, training and support are scoped separately where needed. Cases identify the affected shipment and real customer concern. Use this check when reviewing the first working version.

Talk to us

Discuss ticket management for your business.

Tell us which workflow needs attention and which systems your team uses. The next step is a requirements discussion and a written scope.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements