stage 011 person
Solo founder
One workspace, one queue. The founder answers every message themselves. The assistant handles the routine asks and drafts the rest.
1 channel active · assistant drafts
An about page · the approach
We built the tool
we wished we had.
BootDesk is one workspace for customer operations. The channels, the conversations, the files, the assistant, and the team all live in the same place. No switching windows to finish one ticket.
For the team of one and the team of five hundred. Same workspace. Same habits. Same thread.
BOOTDESKcolophon
vol. 01On the record
A statement of purpose · not a contract
BootDesk is an omnichannel workspace for customer operations. It threads every channel into one ticket history.
The assistant reads the full thread before it writes a reply. The team answers, decides, and ships from one window. The customer never has to repeat themselves.
- principle · inboundall channelsEvery channel becomes inbound to the same queue.
- assistant · reads firstfull historyIt does not skim the last message and guess.
- team · one roominternal + customerDecisions live next to the conversation that produced them.
Drafted by the operators behind BootDesk.in draft
A colophon, not a hero screenshot. The product is on the homepage.
§ 02: the sprawl
The problem
Five tools open at once,
and the customer in none of them.
A customer operations team runs on a stack it never chose. The inbox, the chat app, the help desk, the voice provider, the social scheduler, the spreadsheet that tracks what the others miss. Each tool is fine. The space between them is where customers get lost.
What dies between tools
- The full thread
- What was decided
- What the new agent needs
i.
The assistant that was supposed to help reads only the last message.
Context dies between shifts. New agents start cold. The customer types “as I mentioned earlier” into their fourth tool of the morning.
The team is not lazy and the tools are not broken. The shape of the stack is the problem. Five inboxes were never going to behave like one.
A Monday morning · composite
illustrative- 09:04
Agent opens WhatsApp Web. Three messages waiting. Reads the first.
tab 1 - 09:07
§ 03: the answer
The approach
One workspace for
every channel, every conversation, every decision.
BootDesk takes a different shape. The customer’s voice arrives from anywhere. The team’s response leaves from one window. The assistant reads the whole history before it acts.
i.
Unified queue · this morning
5 channels · 1 inbox- WhatsApp
Maria B. · order #8830 · 3 messages
12:04 - Email
Same thread · forwarded by assistant
12:11 - Slack
@logistics reroute confirmed
12:14 - SMS
Outbound · replacement shipped
12:19 - Voice
Inbound · recording attached to ticket
12:31
one queue · one thread · ticket #4471
Every channel becomes inbound to the same queue.
Scale
From one founder
to a 500-person team, the same workspace.
§ 04: the span
The tenant model scales. Channels activate as needed. The assistant handles more as trust grows. Nothing about the workflow changes between stage one and stage four. The same workspace, the same habits, the same thread.
stage 025 agents
Small team
Five agents share the queue. Channels activate as customers arrive on new ones. The assistant drafts replies for review before they ship.
3 channels · internal chat on
stage 0350 agents
Multiple teams
Internal channels per team. The assistant routes, summarizes, and resolves inside the permissions an admin set. Handoffs stay clean across shifts.
8 channels · assistant acts
§ 05: the principles
A few things we will not compromise on.
Honest about what exists and what is planned. No per-seat tax. Security treated as engineering, not as a marketing page.
Ledger · six principles
in order · not negotiable01
proof
The product is the proof.
No logo walls, no vanity metrics, no testimonial theater. A real ticket thread is worth more than five polished customer quotes.
02
roadmap
The roadmap is visible.
Channels only get marked shipped when they ship. Status tags carry real meaning: shipped, in flight, on roadmap. The teams we serve plan their operations around it.
03
pricing
Consumption, not per-seat.
The tool scales with the work it does, not against the team you build. Adding an agent should not renegotiate the contract.
04
security
§ 06: the workbench
Who is behind it
Built by people who have
answered the phone at 2am.
i.
Ledger · what the team has done
no portraitsOwned SLAs at consumer brands when the SLA broke.
Trained new agents through their first week on the queue.
Written the macros the team actually used, and deleted the ones they did not.
Answered tickets on the holiday shift and the 2am page.
Built the internal tools that got replaced, and the ones that did not.
Shipped the migration that nobody on the team wanted to do again.
no vanity bios · the work is the bio
The principle matters more than the portraits.
We are not going to fabricate a founders row with polished headshots. The people building BootDesk have run customer support. They have written macros at 3am, trained new agents on Monday mornings, owned the SLA when it broke, and built internal tools the team hated using.
See the platform before you read another word.
Read the homepage. Read the security page. Then start free and put it in front of your team. The defaults are the ones an operator would pick. Change them when you disagree.
the BootDesk field guide · each section is a chapter being written