The short of it
- Audience
- Online merchants and operators who need coverage without building their own CX org.
- Domain
- tenvur.com
The problem
Online operators need a way to field chat, callbacks, and routing — not a full contact-center platform. Tenvur runs chat-first launch with a dialer staged in, and routes work by agent progression rather than seat-count licensing.
What I built
- Public site: /, /product, /pilot, /faq
- Gated operator surfaces: /access, /merchant, /agent, /admin, /workspace/tasks/[taskId]
- Routing layer with approvals, certifications, and quality ranking
- Agent progression — digital resume / passport model for workforce
- Transcript-first work execution model
Stack
Next.js 14 App RouterPrisma + Postgres (demo-mode fallbacks where infra isn't wired)Telephony integration (staged)Workspace packages — @reise-tools/tenvur-core, tenvur-routing, tenvur-telephonyWorkflow packages — workflow-launch, workflow-oversight, workflow-control-planePreview-access + intake-review packages
What’s next
CRM/dialer layer — callback macros, queue rebalance, routing health controls. Then production hardening: real DATABASE_URL, real auth, telephony credentials, Resend setup, tenant compliance config.
Keep browsing
More from the studio
Every project on the showroom is live, in beta, or at client scale — no concept pages.