Bloka is a modular B2B workspace built for teams that hate one-size software. You pick the modules. You wire the automations. You set the permissions. The product is powerful, and the surface area is wide.
Pricing tiers, API behaviour, SSO enforcement, plan changes, workspace roles, every customer question lives in a long tail of "how exactly does this work for our setup." The support team is small on purpose. The promise to customers has always been: an answer in seconds, on the same page they are already on, without filing a ticket.
Holding that promise as the user base crossed five figures meant rebuilding the front line around a single knowledge base and an agent that could read it faster than any human.
8,200 inquiries this year, mapped to the KB.
Categories sized by inbound volume. Each bar is a chunk of the support day the team no longer has to ride.
Three answers, lifted straight from the KB.
How do I move from Starter to Team without losing my modules?
Plan changes preserve all modules, automations, and shared boards. Upgrade is prorated, downgrade applies at the end of the cycle. Settings → Workspace → Plan.
Can I scope an API key to a single workspace?
Yes. Keys can be scoped per workspace or per module. Owner role required. Settings → Developer → Keys → Scope.
Where do I enforce SSO on a Team plan?
SSO is enforced under Settings → Security → SSO. SAML 2.0 with Okta, Azure AD, and Google Workspace, JIT provisioning supported.
The shape of our support day used to be a wall of pricing questions and a thinner column of edge cases. Today the pricing wall is gone and the edge cases are the whole day. That is a better job.
Docs are written once. The agent reads them on every inbound.
When a new module ships or pricing changes, the doc gets updated in one place. The agent picks the change up on the next inbound. No re-training the support team. No outdated macros. No "let me check with engineering" rounds. The KB is the source of truth and the answer engine at once.
For Bloka, that means the support pod stays small as the product grows, and the release cycle does not have to wait for a wave of support training. Engineering ships, the docs catch up the same day, and the agent serves the new answer to the very next customer who asks.
A support pod that runs lean, reads fast, and answers in eight seconds.
97% of common questions answered without a human.
Pricing, plans, API behaviour, workspace permissions, billing, integrations, and SSO. The agent reads the question, surfaces the right KB article, and answers in the Bloka voice on the same line. 97% of inbound common questions never reach a person.
Under 8 seconds to first reply, all day, every day.
A founder in São Paulo at 2am gets the same first reply as a CTO in London at 11am. Median time to first reply is under 8 seconds, with zero coverage gap on weekends or public holidays. Every inquiry, every timezone, same speed.
76% reduction in support tickets the team has to touch.
Before the agent, the Bloka inbox carried the full weight of every billing question, every "where do I click" message, every plan-change query. Today the team only sees the gnarly edge cases, the enterprise SSO requirements, the partnership questions. Every ticket that lands is worth a real reply.
The team writes the docs once and the agent does the rest.
When a new module ships or pricing changes, the doc gets updated in one place. The agent picks the change up on the next inbound. No re-training the support team. No outdated macros. No "let me check with engineering" rounds.
A support pod sized for the work that needs a human.
Bloka did not need to grow the support pod as the user base crossed five figures. It needed the pod to stop answering the same hundred questions and start answering the harder ten. The KB is the answer engine. The agent is the front line. The team is the second line, on the conversations that genuinely benefit from one.
Want this for your support pod?
A 20-minute walkthrough on your KB, your product surface, and the support shape you want next quarter. No slide deck.