Skip to main content
When something goes wrong, the fastest route is a troubleshooting page rather than a person. The documentation quotes error strings verbatim so you can search for the exact text you saw, and the CLI can diagnose its own environment. This page routes you to the right place, then tells you plainly which parts of the interface look like help but are not. The Docs link at the bottom of the sidebar — which opens this documentation site — is the only escalation surface the interface wires up. There is no in-app support widget, ticket form, or live chat behind it.
Receipt does not ship a support address. No screen in the product opens a support channel, and the controls that look like they will are dead links. Who to contact, and how, is something your Receipt operator configures — ask them, rather than treating those controls as evidence that a channel exists.The Contact Us link in this documentation site’s header is the one address that does work, and it is a feedback address for these pages, not a product support queue. Use it to tell us a page is wrong; use your operator for a broken deployment.

​
Start with troubleshooting

Before looking for a person to ask, check whether the answer is already written down.
On a deployment you run yourself, gate on readiness rather than liveness: the runtime’s /readyz answers 503 while Postgres is unreachable, whereas /healthz returns 200 even then and reports readiness only inside the body. Health and observability lists every endpoint and what it returns.

​
Two dead ends to know about

Two places in the product look like they will connect you to someone. Neither does — every one of those buttons and links points at #:
  • The organization Analytics & Insights page has an Extraction Analytics card whose help text reads Contact support to enable., followed by a Contact us link. The page has no sidebar or menu entry, so an owner or admin reaches it by typing /organization/settings/analytics.
  • The pricing page’s Enterprise and On-Premise Deployment plans carry Contact Sales and Get in Touch buttons. The same Enterprise card, with the same button, sits below the plan grid on Organization settings → Billing.
If you click one of them expecting to reach a person, that is not a bug you are hitting — the destination simply is not built.

​
Not yet available

These surfaces exist in the interface but do nothing in this release. If you find one, you have not misconfigured anything.
The Policies page’s Guardrails tab describes the Guardrails page as “fully connected — unlike the modules alongside it here”. The second half is right; the first half is not, as far as enforcement goes. Treat Guardrails as an authoring and testing surface.

​
Reporting a security issue

Security reports should not go through public GitHub issues. Report them through your organization’s designated security contact channel instead, and include as much of the following as you can:
  • The issue type — for example, buffer overflow, SQL injection, or cross-site scripting
  • The full source paths involved
  • A tag, branch, commit, or direct URL that pins the version you are reporting against
  • Any special configuration needed to reproduce it
  • Step-by-step reproduction instructions
  • Proof-of-concept or exploit code, if you have it
  • The impact, including how an attacker might exploit it
That detail is what makes a report triageable quickly. If you do not get a response through the channel you used, follow up on the same private channel rather than escalating in public.

​
Before you report anything

Two checks save most round trips:
  • Confirm which host you are on. receipt doctor prints the endpoint the CLI resolved, whether that endpoint answers, and the state of your saved session, without opening a browser. A command that “does nothing” is often pointed at a different deployment than the one you are looking at in the browser.
  • Check whether the surface is one of the inert ones above. A disabled toggle or a button that goes nowhere is documented behaviour in this release, not a broken install.

What Kentron is

Start again from the beginning of the product tour.

Data handling and security

See how Receipt treats your data and your credentials.

Health and observability

Check whether a service you run is actually up.
Next step: return to the Kentron Core overview.