Contact support

Send us a message

Everything you send here reaches the Pishik team directly. There's no phone line or live chat during the beta — this form is the way in, and replies come to the email address you give us.

Pick the topic that fits

The topic just routes your message to the right place — you can always add detail in the message itself.

What to include (and what to leave out)

A good support message is specific but safe. The goal is to tell us exactly what you were doing and what went wrong — without handing over anything sensitive. Pishik is built so that we never hold your documents; please keep it that way when you write in.

Include these — they help us help you fast

• Your workspace name (the company name shown in the app sidebar).
• The contract title the issue is about — the name, not a link.
• What you expected to happen, and what happened instead.
• The exact on-screen message or error text, typed out or described.
• Where you were: the screen or path, using the app's own labels — for example Board, Sent, Repository, or Settings → Data & export.
• When it happened, roughly, and whether it's still happening.

Never paste these

Here's why it matters: your files live in your own storage, and Pishik only ever holds the share links and workflow state — never the documents themselves. A share link is access to the document. Pasting one into a support ticket would hand us the very thing our design deliberately keeps out of our hands. A plain description of the problem is always enough for us to help. For the full picture of what Pishik does and doesn't store, see Where your data lives.

A common mistake

You don't need to send a screenshot of the document, and you shouldn't send the document itself. If a screenshot genuinely helps, capture only the Pishik screen — the board, the flow map, the error — and crop out any contract text or share URLs first.

What to expect when you contact us

We read every message and we do genuinely want to help. Here's an honest picture of what support looks like during the beta, so there are no surprises.

Best-effort support, no SLA

Pishik is in private, invite-only beta. We answer questions and help beta participants on a best-effort basis — but there is no service-level agreement, no guaranteed response time, and no uptime commitment while the beta runs. That's set out plainly in Section 3 of the Beta Program Agreement: the beta is provided as-is, and we're not contractually obligated to meet any response time. In practice, we aim to get back to you as quickly as we reasonably can.

How we reply

• We reply by email, to the address you entered — so double-check it before you send, and keep an eye on your spam folder.
• There's no phone line, live chat, or priority queue during the beta. Email is the single channel, and every topic reaches the same team.
• We use your details only to reply to you — nothing more. See the Privacy Policy.

If the form won't send

To keep out spam, the form accepts only a handful of messages from the same place in a short window. If you send several in quick succession and see an error, wait a few minutes and try once more. Persistent send failures usually point to a network or rate-limit issue — 'Try again later': rate limits explained covers what's happening and what to do.