We're doing our best to answer your questions as quickly as we can. There are a couple of things, though, you can do to get your problem solved faster. Here they are.
Look around before you submit your request. In many cases, you can get your question answered instantly—without submitting any request! Most of the common questions have already been answered and we keep adding new articles. Please browse our Help Center before leaving a ticket—you’ll save your time and help us reply to other requests faster. Win-win :)
Provide detailed information about your problem. Describe your problem in detail, so our support personnel can identify your problem and solve it right away instead of going back and forth to get all the necessary data. So please tell us:
- what exactly are you trying to achieve with beacons?
- at what stage do you encounter a problem?
- what tools are you using?
- what beacons are affected (please provide their Unique IDs)?
- are you able to reproduce this bug on other beacons?
- to what account are those beacons assigned to?
- any other information that you think may help us find a solution for you.
Grant us an access to your Kontakt.io Proximity Web Panel account. Diagnosing some problems is much faster if we can access your account to make changes directly. We don’t need your password, just a clearly expressed consent to modify some settings if needed.
Visit our GitHub account. If you are a developer, and you have a problem with our Proximity SDKs, please raise an issue on our GitHub account. Our developers are monitoring them and can help you if there is something wrong with the SDKs. Please be aware, though, that we don’t provide support in writing applications. We assume that you have a proper knowledge and experience to write mobile applications on your own.
Contact our Sales team if you are interested in beacons. They are better qualified to help you choose the right solution for your needs, discuss pricing, partnerships, or any non-standard requests regarding our products.