Give your clients a support portal in five minutes
If you run projects for clients, this is the fastest upgrade to how you handle their problems — and it costs you no extra seats.
Agencies and consultancies live with a specific version of the intake problem: every client has their own idea of how to report a bug, and all of them are wrong. One emails the account manager, one messages a developer directly, one saves problems up for the weekly call.
Here's how to replace all of that with one link, in about five minutes.
Step 1 — Open the project's Requests tab
In VectorKan, each project has its own request portal. Open the project you want clients reporting into and switch to Requests.
Step 2 — Turn the public form on
Flip the Public request form switch. A shareable link appears immediately,
in the form vectorkan.com/request/your-project-id. That's the whole setup.
Step 3 — Share it where clients already are
Wherever they currently email you, put the link instead:
- In your email signature, and in the kickoff email for new clients.
- As a "Report a problem" button in the product or client dashboard you've built for them.
- Pinned in the shared Slack or Teams channel.
- On your website's support page.
Expect to redirect people for a couple of weeks — "could you pop that in the form?" — and then it sticks, because the form is genuinely less effort than composing an email.
Step 4 — Triage what arrives
Submissions land in a queue rather than straight on your board, which is the important design decision. Not every report is a ticket: some are duplicates, some are questions, some are feature requests wearing a bug costume.
For each one you either convert it to a tracked ticket — one click, with the reporter's words and contact details carried onto the issue — or close it with a reply. Both are good outcomes. What you avoid is a board full of items nobody triaged.
What this costs you
Nothing per client. The portal is a public link, so the person filing a request needs no account and consumes no seat, and they see nothing but the form — never your board, your other clients, or your internal comments.
That's the part that makes this practical for agencies. Giving twenty clients tracker logins is expensive and awkward; giving twenty clients a link is neither.
If you'd rather use your own form
Some teams want the form inside their own product, styled to match. The REST API covers that — post to the issues endpoint from your backend and skip the hosted form entirely. Same destination, your interface.
Frequently asked questions
How do I set up a client support portal?
In VectorKan, open the project, go to the Requests tab, and switch on the public request form. A shareable link appears straight away — share it by email, from your website, or inside a product you've built for the client.
Do clients need an account to submit a request?
No. The portal is a public link, so clients file requests without signing up and without consuming a paid seat. They see only the form, never your board or other clients' information.
Do customer requests go straight onto the board?
No, they land in a triage queue first. You convert genuine ones into tracked tickets with a single click, which carries the reporter's description and contact details onto the issue, and close the rest with a reply.
Can I use my own form instead of the hosted one?
Yes. VectorKan's REST API lets you create tickets from your own website or product, so you can build the form to match your branding and still have everything arrive in the same place.