Skip to main content
ImpelLabs is the layer between a business’s customers and the systems that answer them. It holds what a business knows, connects the channels its customers actually use, and runs the conversation. What it deliberately does not hold is your domain. Products, orders, appointments, patient records — those belong to the product that owns them. You expose what an assistant may do with them as tools, and the platform calls them.

Architecture

Why the platform stays domain-free, and where your product fits.

Quickstart

Stand up a tool server the platform will talk to.

Tool contract

Naming, schemas, and the subset every provider agrees on.

Security model

What the platform assumes about your server. Read before shipping.

​
What the platform gives you

WhatsApp today, with the website widget alongside it. A customer who starts in one and continues in another is one person — the platform resolves identity across channels and merges only on verified contact details.
A rolling summary plus a recent window, a context budget that drops memory before knowledge before history, and durable memory per customer. Your tools are called inside that, not instead of it.
Hybrid search — vector plus full-text, fused by reciprocal rank fusion — over uploads, crawled pages, FAQs and hand-written cards.
Credit metering per turn, idempotent tool execution, per-tenant isolation, and a 24-hour-window check before anything is sent on WhatsApp.

​
What you build

A tool server: an MCP server exposing your product’s capabilities. The platform discovers your tools, an operator reviews them, a customer switches them on, and the assistant calls them mid-conversation.
Shipping a new capability means adding a tool to your server and pressing re-discover. It does not require a platform release.

Start here

A working tool server in about ten minutes.