Use case
Flocci Chat for agencies and web studios
Short answer
For an agency, Flocci Chat is a service line: one script tag adds a grounded, self-learning support assistant to any client site you ship — each client in an isolated workspace with their own branding, knowledge base and ticket inbox. Setup is an afternoon; the knowledge base maintains itself as the site changes.
The easiest recurring deliverable you'll ever ship
You already build and maintain client websites. Flocci Chat turns each of those sites into its own support assistant with one script tag — no content project, because the knowledge base fills itself from the site you just built (crawl + passive learning, JS-rendered stacks included). Client changes their services page? The assistant re-learns it on the next visit. The deliverable maintains itself, which is what makes it viable at agency margins.
Isolation and branding, per client
Each client is a separate workspace: their own widget key, their own knowledge base (isolated with PostgreSQL Row-Level Security), their own assistant name, greeting, colors and tone, their own ticket inbox. Escalations reach the client's team — replies land in-chat and by email — so you're not in the support loop unless you want to be the operator. Nothing leaks between clients by construction, not by policy.
The commercial shape
Credit pricing keeps packaging simple: 1 credit = 1 answered visitor message, 500 free credits per new workspace to prove value in the pitch, rupee-denominated packs after. Typical small-business sites answer a few hundred messages monthly — price your managed-support retainer accordingly and the margin is yours. The dashboard's analytics (top questions, unanswered intents) also hand you a content-improvement upsell every month, backed by data.
Frequently asked questions
Can I manage multiple client chatbots?
Each client site runs its own isolated workspace with separate keys, knowledge base, branding and tickets. Set up each in minutes; the self-filling knowledge base removes the ongoing content maintenance that kills agency margins.
Can the client handle their own escalations?
Yes — tickets land in their workspace inbox and their team replies from the dashboard, reaching the visitor in-chat and by email. You can stay out of the day-to-day loop entirely.
How do I demo it in a pitch?
Embed the widget on the client's staging or live site, browse their key pages for five minutes (each page is learned on the spot), then let the client ask it their own FAQ questions live — the 500 free credits cover the whole pitch cycle.
Does it work on the no-code builders we use?
Yes — passive learning reads rendered pages, so Webflow, Framer, Wix and WordPress builds are covered the same as custom React work.
Try it on your own website
One script tag. 500 free credits — roughly 500 answered visitor messages. Every feature on, no card. The widget in the corner of this page is the product, running on its own site.
Create your workspace — free