Omnify

Omnify is a B2B platform where a business connects its own messengers and gets an assistant that answers customers, keeps the lead moving through a built-in CRM, and hands the conversation to a person when it should. Telegram and WhatsApp work; Instagram has an adapter but the connect endpoint returns 501 until Meta approves the permission, which felt more honest than pretending.

FastAPI over Postgres with pgvector, and a Next.js cabinet. Every channel funnels into one inbound handler that dedupes by external id and debounces, then a queue worker runs the agent — five tools, no more: search the knowledge base, create or update a lead, hand off to a human, save a contact fact, check availability. Tenant isolation is enforced in the database with row-level security rather than in application code, because application code is where that kind of thing eventually leaks.

The feature I had to rebuild is the one that tells an owner which questions their bot couldn't answer. The obvious version flags a gap when retrieval finds nothing — and measured against a real knowledge base it caught zero of five real gaps, because the reranker will happily float almost any chunk from the right domain above the threshold. Finding something and answering something are not the same event. The signal that works is structural: the agent itself calling handoff with a reason of missing information.

It's a working MVP on a test stand, not a launched product. No billing yet, and WhatsApp goes through an unofficial gateway that Meta could close.