KiloDrive
Menú
Support and Disputes

From report to resolution: how a KiloDrive support case should work

A plain-language guide to opening a structured KiloDrive case, attaching relevant evidence, following status changes and knowing when outside help may apply.

Caribbean customer discusses a structured support case with a KiloDrive specialist.

Short answer: A KiloDrive support case should connect the problem to the relevant trip, payment, document or account event, give the user a case number, preserve a private conversation and evidence trail, and show a truthful status: Received, Reviewing, Waiting for information or Resolved. It should never leave a person guessing whether a tap created a case.

A structured case is more useful than a vague message because the service team can see the correct context without asking the user to post sensitive information in ordinary chat. The user can follow the next action, reply securely and retain a history of what was decided. Urgent safety events still belong in the Safety workflow or local emergency channel; an ordinary support queue is not an emergency dispatch service.

What this means Choose the record and topic that best match the problem, describe the outcome you need, attach only relevant evidence, and keep the case number. The status should tell you who needs to act next.

Begin with the thing that went wrong

KiloDrive's support contract allows a case to be associated with a trip, payment, document or a general account matter. That reference is valuable: a fare concern can point to the exact trip and receipt, while a document review concern can point to the relevant document without exposing its private storage path. The topic and issue type should be selected from the supported choices rather than typed as a hidden code.

A useful description answers four questions: what happened, when did it happen, what did the app show and what reasonable outcome is requested? Include a local date and time and the visible trace or case reference. Do not paste an access token, password, OTP, full bank account, payment card or unredacted identity document into a message. If the workflow offers a private evidence upload, use that controlled path.

After submission, the app should display the case number prominently. A successful request with no cases is an empty state; a service failure is an error with retry. The interface must not turn a rate-limit or validation response into a blank screen or claim that a case exists when the server did not accept it.

Read the status as a next-action signal

Received means KiloDrive recorded the case. Reviewing means an authorized support worker is assessing it. Waiting for information means the team needs a reply or evidence from a party. Resolved means the recorded support work has reached a conclusion. These labels should appear consistently in the API, mobile app and Portal, even if older records used Open, Answered or Closed.

Resolved does not mean the user agreed with every finding, and it does not erase the conversation. The KiloDrive contract provides a 14-day reopen window for an eligible resolved case. The detail view should explain the current reopen or escalation option instead of presenting a generic close icon. Closing a case should require a clear action and reason; dismissing a dialog should simply say Cancel.

Support response times can depend on priority, complexity, staffing and country policy. KiloDrive should show an SLA only when a live, owned policy supplies it. This article makes no response-time guarantee. A safety case, payment reconciliation issue and spelling correction do not necessarily belong in the same queue or have the same urgency.

Evidence should clarify, not create another privacy problem

Useful evidence can include a receipt, relevant screenshot, photograph, correspondence or a precise description of an event. More data is not automatically better. Jamaica's Office of the Information Commissioner describes data minimisation as limiting collection to what is adequate and relevant for the purpose. The same regulator recommends logging requests and complaints, verifying authenticity, assigning responsibility, communicating extensions and providing a reference number and review path.

Restricted identity and compliance documents require an authenticated in-app viewer and audited access. They should not become public links or ordinary email attachments. Support staff should see only the material their capability and country workspace permit, while users should be able to understand what evidence is attached and whether more information is requested.

When an outside complaint path may apply

Start by giving KiloDrive enough information to investigate. In Jamaica, the Consumer Affairs Commission offers a complaint process for unresolved consumer matters and asks for details such as the service, payment, receipt number and supporting document. The Office of the Information Commissioner accepts complaints concerning personal-data handling. A bank or payment provider may have its own dispute process.

Those channels have different legal authority and scopes; a KiloDrive ticket does not replace them or extend a statutory deadline. Preserve your receipt and correspondence, check the relevant authority's current requirements and seek independent advice when necessary. The Legal Centre, Privacy Policy and Terms and Conditions explain the current KiloDrive framework.

A practical case checklist

  1. Select the affected trip, payment, document or account topic.
  2. State the facts, local date and desired outcome concisely.
  3. Attach only necessary evidence through the protected control.
  4. Record the case number and check who owns the next action.
  5. Reply in the case conversation, not through rider-driver chat.
  6. Read the resolution and any reopen or external escalation guidance before the deadline.

What is still uncertain

Issue types, priorities, SLA targets, external escalation bodies and evidence-retention periods can vary by country and case class. A displayed case status does not decide legal liability, payment-provider rights or insurance coverage. KiloDrive must confirm that every live queue has an owner and current policy before publishing response-time claims. Users should consult the competent regulator or professional adviser for their circumstances.

Frequently asked questions

How do I know KiloDrive received my support case?

A successful submission should open a durable case detail with a visible case number and Received status. Keep that number for follow-up.

What does Waiting for information mean?

It means the case cannot progress without a requested reply or evidence. Open the conversation and provide only the specific information requested.

Can I attach an identity document to any message?

No. Restricted documents should use the dedicated private evidence or document workflow, not ordinary chat, email or a public link.

Can I reopen a resolved KiloDrive case?

The current support contract allows eligible cases to be reopened within 14 days. The detail screen should show whether that action remains available.

Does opening a KiloDrive case replace a regulator or bank dispute?

No. External complaint and payment-dispute rights have their own scope and deadlines. Preserve your evidence and check the relevant authority's current process.

Sources

Explora temas relacionados