Search the guides or send us the symptom, session ID and a reply address. Keep keys and private workspace contents out of the message.
Recommended guides
Chosen by us, not ranked by traffic. This site runs no analytics, so there is no reading count to publish.
Nothing documented matches that.
That is worth knowing on its own. Open a ticket below and it will be triaged as a documentation gap as well as a question.
The docs, first
The evidence-bench document is extracted and run mechanically by gate 7 on a machine that never built KeepState, and reference pages are synced from the binary. If a synced page fails for you, that is our defect rather than your mistake.
answers now · 15 documented symptoms
A finding, not a ticket
If our own documentation or a published number was wrong, send it to findings and it goes to the front. We publish the correction; your name appears on it only if you ask us to add it.
findings@keepstate.ai · reply within two business days
Open a ticket
Tickets go to one queue and are answered out of it in order, apart from findings. There is no first-line script to get past, because there is no first line. Who reads that queue is stated once, next to the form, and it is not a support tier.
one queue · reply within two business days
Symptom, then the evidence you already collected, then what you think is happening. The third part is optional; the second saves a day.
Support is read by the team. findings@keepstate.ai is read daily, and a finding jumps whatever queue exists.
Every ticket gets a reply within two business days. That is a commitment, not a measured median; a measured number appears here when there is a measurement behind it.
Something is down right now
Check the status page first. If an incident is open we are already working on it and a ticket will not make it faster.
Status and incident history →For dated public service information, read the service status and incident summaries. Internal form-test records are not published.
We received your message.
Reference:
We could not confirm your message.
Check the request status before sending it again. Your reference is shown below.
Reference: unavailableUnavailable until the status check finds the request. If it never reached us there is no reference, and nothing was sent.