Platform overview
A product layer for businesses that treat WhatsApp as real inbound infrastructure.
The goal is not just to add another chatbot widget. It is to give a business a controllable AI operating layer for customer conversations, bookings, lead intake, and owner visibility.
WhatsApp-first conversations
The product starts where customer demand already appears. Instead of inventing a new inbox, Traject treats WhatsApp as the primary operational channel.
Intent-driven workflow routing
A conversation does not have to stay inside one script. FAQ, booking, and lead capture can coexist inside the same business interaction.
Controlled outcomes
Business actions should be validated, logged, and visible. The MVP is designed around safe handling rather than unbounded assistant improvisation.
Marketplace-ready expansion
The near-term product is focused, but the platform is being shaped so more agent capabilities can be added through subscriptions later.
Live in MVP
- WhatsApp-first FAQ handling
- Booking flow with business-aware validation
- Lead capture and owner visibility
- Transcript and notification workflows
Next layers
- Google sign-in and structured onboarding
- Marketplace subscriptions by agent
- Richer use-case pages and onboarding flows
- Voice and multi-agent expansion
Next action
Move into the sign-in shell and prepare for onboarding.
This phase keeps the public experience product-led while preparing the next auth and onboarding layer.
Continue with Google