Three days, when a human is involved
The assistant answers first. If the ticket needs a person, we reply inside three business days. Right for teams testing the surface or running light volumes.
window · business hours, EU
Per-seat pricing charges you for the agent on holiday, the channel you haven't wired yet, the inbox sitting empty. BootDesk charges for the resources you actually consume, with a floor that matches your commitment.
At a 40-agent team on the Growth tier, a typical month bills around €160 against a €100 floor. The busy month of November billed €320. The quiet week of August still billed the floor. (Composite illustration.)
Growth tier · floor €100 · billed in arrears
words the assistant read and wrote this month
pictures produced for replies and campaigns
channels with at least one conversation this month
teammates who signed in to the workspace
A real-looking statement. Every line is a resource you used, not a seat you rented.
Every tier ships the same product: all twelve channels, the assistant, tickets, forms, files, voice, internal chat. The difference is the floor you commit to, the per-unit rate you pay, and how fast we pick up the phone.
Legend
Compare
Features down the left, tiers across the top.
Tier 01
€10 / month floor
pay for what you use
Tier 02
€100 / month floor
priority rates and queue
Tier 03
€500 / month floor
identity, audit, dedicated onboarding
Three months · Growth tier · €100 floor
illustrativeA floor is the amount you commit to spend each month. It is not a ceiling. If you use more than the floor, you pay the difference. If you use less, you pay the floor.
The chart beside this paragraph reads three months of a Growth team. June was quiet, the floor held. July crept over. August was the busy month and the bill tracked it honestly.
Pick a tier, set your usage, read the math. The floor is the minimum you pay. Defaults reflect a small team.
We do not gate the product. There is no “starter tier without voice” or “growth tier without the assistant”. The floor moves, the per-unit rate moves, the response time moves. The product does not.
WhatsApp, Messenger, Instagram, Threema, Matrix, Slack, Teams, Discord, email, SMS, voice, and RCS. Connect any live channel on Starter.
The assistant is the same model on every tier. It reads the full thread, reaches for connectors, drafts replies, and hands off with a summary. The rate you pay per token is the only difference.
A ticket collects every message, file, call, and internal note into one history. No plan splits the thread. No plan hides the past.
Lead forms, support forms, intake forms. Each one creates a ticket, routes by intent, and hands the assistant the context to answer.
The assistant handles the first answer on every tier. The response time below is the ceiling for when a human has to be involved, from the moment the ticket is routed to a person to the moment they reply.
The assistant answers first. If the ticket needs a person, we reply inside three business days. Right for teams testing the surface or running light volumes.
window · business hours, EU
A human replies inside twenty-four hours, seven days a week. The assistant runs in the priority queue, so the first answer lands faster too.
window · 7 days, priority queue
A human replies inside twelve hours. Onboarding is dedicated, the account has a named contact, and the queue is staffed for the teams who cannot afford to wait.
Enterprise adds the controls a security, compliance, or procurement team will ask for before they sign. Nothing here is decorative. Each capability answers a question we have been asked by an administrator.
BootDesk speaks OIDC as a provider and as a consumer. Sign in to other applications with your BootDesk identity, or let your corporate identity provider sign you in to BootDesk.
Group claims, scoped tokens, refresh rotation. Works with the identity provider your security team already runs.
provider · consumer
group claims · scoped tokens
Every action, every actor, every timestamp, exportable as an immutable log.
If your question is not here, write to us. A human replies on the SLA of the tier you pick.
A note on the dot. A middle dot marks a chosen boundary. The capability lives in a higher tier.
The words the assistant reads and writes. Priced per million tokens. Long threads cost more than short ones.
Pictures the assistant produces for replies, campaigns, and forms. Priced per image, scaled by resolution.
A channel counts as active when it carries at least one conversation in the month. Idle connectors do not bill.
Teammates who signed in to the workspace this month. The agent on holiday does not bill. The one who answered does.
Files attach to the ticket, get scanned on arrival, and open for editing without leaving the workspace. Storage bills by what you keep, not by a seat allowance.
Inbound and outbound voice, agent-to-agent calls, video for when a conversation needs a face. Recordings land on the ticket.
Internal chat ships in the workspace too. It replaces the external chat your team uses today, when you are ready.
shippedwindow · 7 days, named contact
A note on the assistant. The assistant replies in seconds on every tier, including Starter. The SLA above is the human ceiling, not the first-answer clock.
Scheduled exports of tickets, threads, and files to your own storage.
Per-record retention windows set by policy. A ticket can live ninety days, a call recording seven years, a file forever.
A named contact runs the rollout, wires the first channels, and trains the first shift.
We build the connector to your internal API, your store, your warehouse system. Maintained as the spec changes.