All projects

SnobBots · Ecommerce / Customer support

Multi-tenant AI chatbot platform.

Private deployment, client project

Category

AI

Year

2023-2024

Capabilities

AI, Cloud & Automation

Industry

Ecommerce / Customer support

SnobBots on a laptop
SnobBots on a phone

The problem

Resellers wanted to offer AI support agents to their own customers, but every deployment was bespoke, so onboarding a new shop took days of manual setup.

Our approach

We built a multi-tenant MERN architecture where each shop runs an independent, context-aware agent, and layered automated provisioning on top so resellers could stand up bots in bulk rather than one at a time.

Inside the product

More than one screen.

3 more screens from SnobBots, captured at device size.

SnobBots: Handover inbox on a laptop

Handover inbox

Conversations the bot could not close, with the order and customer beside them.

SnobBots: Knowledge base on a laptop

Knowledge base

The catalogue, orders API and policies each bot is allowed to answer from.

SnobBots: Shop widget on a laptop

Shop widget

The customer-facing chat as it appears on a client’s storefront.

On the phone

SnobBots: Home on a phone

Home

SnobBots: Handover inbox on a phone

Handover inbox

SnobBots: Knowledge base on a phone

Knowledge base

SnobBots: Shop widget on a phone

Shop widget

How it is built

Architecture

MERN: React, an Express and Node.js API, and MongoDB for tenant and conversation data. Pinecone holds per-tenant embeddings so retrieval is scoped to one shop’s knowledge base, and provisioning runs without manual setup.

Key features

Multi-tenant architecture with isolated agents
RAG for context-aware, business-specific answers
Automated bulk bot provisioning
Reseller management dashboard
Embeddable support widget

Challenges & solutions

Where it got hard.

Challenge

Retrieval across a shared vector index surfaced one shop’s content in another shop’s answers.

Solution

Partitioned embeddings per tenant in Pinecone so retrieval can only ever reach the requesting shop’s namespace.

Challenge

Manual per-shop setup made reseller onboarding the bottleneck on growth.

Solution

Automated provisioning end to end, turning a multi-day manual process into a bulk operation.

Results

What shipping it changed.

60%faster deployment through automated orchestration.
1namespace per tenant, so no shop can read another’s content.

Stack

  • Frontend

    • React
  • Backend

    • Node.js
    • Express
  • Database

    • MongoDB
    • Pinecone
  • AI

    • RAG
    • LLM

Let's talk

We can usually tell within one call whether the approach above transfers to your problem, and what would need to change.