Docs

Get Help: Opening a Support Case

Raise a support case with Zippykind from inside the dispatch software, pick the right category and priority, and follow the reply.

Published

Get Help is how you reach Zippykind support from inside the dispatch software. Find it at Get Help in the left menu (/app/get-help). It keeps every case you have opened in one list, with its status, so a question does not disappear into somebody's inbox.

Opening a case

Press New Case at the top right and fill in the form.

  • Category — Billing / Payments, Driver App, Dispatch Software, Integration (Epic, etc), Feature Request, Get Dedicated Phone Number, Request Account Deletion, or Other.
  • Priority — Low, Normal (the default), High or Urgent.
  • Subject — a short summary of what is wrong or what you need. Required.
  • Description — as much detail as you can give: steps to reproduce, the exact error message, what you expected instead. Required.
  • Related Ticket ID — optional. You can search by ticket id, customer name or address, and attaching the ticket saves a round trip when the problem is about one delivery.
  • Attachment — optional. JPEG, PNG or WEBP, up to 5MB. A screenshot of the error is usually worth more than a paragraph describing it.

Two categories that are really requests, not problems

  • Get Dedicated Phone Number — this is how you rent a virtual phone number for your account. You need one before Zippykind can send SMS to your customers or connect calls between customers and drivers without exposing real numbers.
  • Request Account Deletion — the route for asking that your account be closed. Use it deliberately.

Some places in the software link straight into this form with the category pre-selected — the import row limit notice does it, for example. That is the same form, just filled in for you.

Following a case

Your cases are listed with case number, status, priority, subject, category and when they were last updated. Zippykind replies by email, and you can reply to an open case from this page, so the whole conversation stays attached to the case.

Writing a case that gets fixed quickly

  • Give one specific example: a ticket id, a driver name, a time. "Notifications are not working" is far slower to solve than "ticket 84213 at 2:15pm sent no SMS".
  • Say what you expected as well as what happened.
  • Set the priority honestly. If everything is urgent, nothing is.
  • Check the support docs first for settings-shaped problems — a surprising number of "it stopped working" cases are a switch on the Settings page, and the article will get you an answer in two minutes instead of two hours.