Help desk for agencies

A help desk that lives with the work

Agencies don't have a support department — the people answering client requests are the people delivering the projects. Pinboard puts tickets, chat, and delivery in one workspace.

Client requests arrive by email, Slack screenshot, and 'quick call.' Somebody pastes them into the project tool, somebody else forgets, and the client asks for a status update you don't have. A real help desk fixes the intake problem — but a separate help desk product creates a new one: support now lives in a different system than the work it generates. Pinboard's service desk is an app inside the workspace, so the ticket, the task that resolves it, and the hours it took are one connected record.

Overheard

Sound familiar?

Did anyone see Dana's email?
Requests arrive by email, chat, and hallway — no queue, no owner, no SLA. Something slips, and the client notices first.
I thought you replied to that.
A standalone help desk means retyping tickets as tasks, syncing status by hand, and answering "is this done?" twice.
Is this covered by the retainer?
The hours spent on "small asks" never reach a timesheet, so scope creep stays invisible until the retainer's gone.

Intake

Every request becomes a ticket with an owner and a clock

Public intake forms give each client a place to file requests. Tickets carry priorities, categories, SLA targets, and assignment groups — so the queue is the single source of truth.

Public intake forms
A branded form per project or client — no login required to file a request.
SLAs and priority queues
Response targets that are visible, tracked, and impossible to quietly miss.
Assignment groups
Route design requests to designers and billing questions to the PM automatically.
Tickets · Service Desk
MC
Total 9Open 3Resolved 4
#
Title
Status
Updated
#36
Portal: live order-status visibilityDrafted by AI
New
just now
#35
Invoice PDF shows old logo
Open
2 days ago
#34
Add teammate to portal access
Pending
4 days ago
SLA: first response 4h · resolution 3 business days

Live chat

Chat that answers first, escalates gracefully

An embeddable chat widget starts with an AI agent grounded in your knowledge base and hands off to a human with the full transcript when it should.

Live Chat · Agent console
MC
WAITING2
Jordan · Lakeline
waiting 0:42
Claim
Guest · pricing page
waiting 1:15
Claim
You're on duty
Hi — can I get an update on our March invoice?
AI answered · visitor asked for a human
Taking over from the bot — one sec, pulling it up. You won't need to repeat anything.
Reply…

AI-first response

Common questions get answered from your KB before anyone is interrupted.

Human takeover

One click brings a person into the conversation with complete context.

Timesheet · This week
MC
Mon
Tue
Wed
Thu
Fri
ACME onboarding
ImplementationBILLABLE
2
1.5
2
1
Support triage
SupportBILLABLE
1
2
0.5
1.5
Sprint planningSuggested
Internal
1
0.5
Week total13.0h · 11.5h billable

Connected

From ticket to task to timesheet without retyping

A ticket links to the task that fixes it and the time logged resolving it — because they're the same workspace, the same client, the same records.

Tickets next to projects
The request and the delivery work share one client context.
Hours land on the timesheet
Time spent on requests is tracked like any other work, so it can be billed like any other work.

See it run

48 minutes, start to smarter

Follow one support request through the desk — AI first, human when it matters, and a knowledge base that learns from the save.

2:14 PM

A customer hits a snag

They open the chat widget on your site — no account, no form maze.

Our invoices page is showing a 404?
2:14 PM · 4 seconds later

The AI agent answers first

Instant response, grounded in your knowledge base — with its source attached.

Invoices moved under Billing → Documents last week. Here's the direct link.
Source: "Where did invoices go?" · KB
2:16 PM

A human takes over in one click

The link 404s for this account — the agent sees it's out of its depth and hands off. Dana claims the chat from the live queue.

That link 404s too…
D
Hi, this is Dana — I can see the error on our side. Fixing it now.
2:17 PM

It becomes a ticket with an SLA

One click turns the conversation into a tracked ticket — transcript attached, priority set, clock running.

ACME-T147Invoices 404 for Meridian accountsHighSLA 3h 58m
3:02 PM

Resolved — and the KB gets smarter

Dana ships the fix and the assistant drafts a KB article from the resolution, so next time the bot handles it alone.

Resolved in 48 minutes · SLA met
KB draft: "Invoices 404 after Billing move" — ready for review

Pricing

What it costs

The planned Service Desk add-on is +$10 per seat per month on top of Pro ($10 per editor) — one line item, not a second product. Planned pricing — the whole platform is free while in early access, and early-access teams get notice before anything is ever charged.

Questions

FAQ

Whatever channel suits them: a public intake form (no account needed), the chat widget on your site, or email. Your team works the queue inside Pinboard; clients get updates without needing to learn your tooling.

No — the service desk is an app in the same workspace as projects, docs, and timesheets. The person answering the ticket is one click from the project it belongs to.

Nothing right now — approved workspaces get the full platform free during early access. Planned pricing is Pro at $10 per editor per month, with Service Desk (+$10), CRM (+$15), and AI (+$12) as optional per-seat add-ons, so you only pay for the apps you switch on.

Yes. Pinboard ships an MCP server with 56 tools, so the assistant you already use — Claude, or any MCP-compatible assistant — can create tasks, log time, file tickets, and query boards directly. There's also an open REST API with token auth.

Early access

Run it all in one workspace

Request early access — every app, no credit card, free while in alpha.

Free plan available · No credit card · Free while in early access