Zito Logistics Help Center

Search customer and corporate help by workflow. Start with the right article, then move into support only when the issue needs action.

Back to Zito Logistics loginOpen customer support

Login path

/login

Individual Customer and Corporate accounts use the Zito Logistics app.

Primary access

Phone OTP

Phone OTP is the first path. Email users verify OTP, then finish with password.

Core work

Book + Track

Bookings, payments, invoices, support, and account controls stay in one place.

Quick actions

Start from the right operational entry point before escalating to human support.

Login & OTP help

Troubleshoot phone OTP, email OTP, password continuation, and session recovery.

Open login

Create a booking

Open booking flow, review route rules, and confirm pricing inputs.

Open new booking

Track or raise support

Move from live tracking into customer support with booking context attached.

Open support

Review payments

Check wallet, invoice visibility, payment status, and finance questions.

Open payments

Service Roles

Role-by-role summary of who uses this app surface and what they should do here.

Individual Customer

Book direct deliveries, manage payments, raise tickets, and track trips.

  • Home, Book, Track, Payments, Support, and Account stay inside one service workspace.
  • Address, stop, and coordinate validation is required before booking confirmation.
  • Logout now stays inside Account.

Corporate

Manage contract-backed bookings, invoices, fleet, and commercial exposure.

  • Corporate users work inside Bookings, Contracts, Invoices, and Fleet.
  • Credit use and invoice exposure should be reviewed before placing more loads.
  • Corporate login remains person-based, not company-name based.

Help articles

Searchable workflow guidance, organized by article instead of one long static page.

Login and OTP flow

Current public auth flow for service users.

  • Open /login and choose Phone OTP or Email.
  • Phone login completes after OTP only.
  • Email login requires OTP first and password second.
  • If OTP is delayed, use the OTP screen resend control and wait for the cooldown countdown to finish.

Daily operating flow

What service users should do most often.

  • Create booking from the Book or New Booking flow.
  • Monitor live or historical bookings from Home and Track.
  • Use Payments to confirm settlement status and wallet activity.
  • Raise a ticket from Support when a booking-specific issue needs intervention.

Rules and controls

Important constraints aligned to the current product rules.

  • Only ACTIVE accounts can log in.
  • Bookings require valid coordinates; empty latitude/longitude is rejected.
  • Service users must not see internal-role registration paths.
  • Company names belong to registration, approval, contracts, and invoices, not login.

Need more help?

Escalate into human support when the article is not enough or the workflow needs action.

Need a human to act on this?

Open the customer support desk when the article is not enough, the booking is live, or money/document action is required.

Open customer support

Need live trip context first?

Go to tracking before opening a ticket when the issue is tied to one active delivery.

Open tracking