tourkit is a volunteer-maintained open-source project rather than a company, so there is no sales contact, no support desk and no phone number. Everything happens in the open on GitHub, which means an answer is visible to the next person who hits the same problem.
Open an issue at github.com/yz174/tourkit/issues. A report is most useful with the package and version, the platform (web or React Native), the tour configuration that reproduces it, and what you expected instead. The troubleshooting page covers the failures that come up most often and is worth a look first, particularly for a step that skips itself or a target that never resolves.
Open an issue for anything that is not a defect too: how to model a particular onboarding flow, whether a pattern is supported, or which of the interaction modes fits a step. Label it as a question. Questions asked there often turn into documentation, which is how the recipes page grew.
Open an issue describing the onboarding problem you are trying to solve rather than the API you have in mind. Several existing features, including gates and fingerprint healing, came from a described problem rather than a proposed signature.
Use GitHub's private vulnerability reporting on the repository security tab rather than a public issue, so a fix can ship before the details are public. tourkit runs entirely inside your application and operates no servers, so the surface is the packages themselves and the local recorder server that tourkit record starts.
Pull requests are welcome on the repository. Packages are published to npm under the @tourkit scope. See About for the project's status and licence.