Zallo

The challenge

Appointment businesses lose bookings when phones go unanswered; operators also need modular back-office SKUs instead of a single legacy monolith release train. Without a coherent multi-product enterprise suite foundation, Zallo stakeholders faced fragmented tools, slow handoffs, and limited visibility—classic failure modes Tekvers designs against.

The solution

Zallo: Gateway-led suite—production multi-tenant AI receptionist (zallo.ai) plus NestJS/Next ERP-style SKUs (CRM, POS, finance, HRM, inventory, CMS) with shared portal UI. End-to-end receptionist loop: answer → book → SMS follow-up. Tekvers delivered a maintainable multi-product enterprise suite system for Zallo using NestJS, Next.js, TypeScript, Supabase Postgres + RLS (REC), with phased rollout, operator workflows, and documentation suited to long-term ownership.

Approach

Deliverables

• ▸AI receptionist product surface (voice, portals, APIs, SMS, Stripe hooks, marketing)
• ▸Platform gateway for auth, entitlements, and suite home
• ▸Modular product APIs/portals across CRM, POS, finance, HRM, inventory, manufacturing, projects, reports, CMS
• ▸Shared TypeScript contracts and `@zallo/portal-ui`
• ▸Docker Compose / Caddy-oriented deploy path for REC
• ▸Vertical presets path for med spa → adjacent appointment verticals

Outcomes

• ▸End-to-end receptionist loop: answer → book → SMS follow-up
• ▸Independent module delivery with shared identity patterns
• ▸Clearer commercial packaging per Zallo product SKU
• ▸Modern Nest/Next path off a legacy .NET ERP domain split

Impact

Zallo behaves like a product family—clinics get a production AI front desk; operators entitle ERP siblings as needed; identity and entitlements stay centralized without forcing one release train.

Tech stack