Roadmap
Chota roadmap: what we started in April 2026 and do not yet call finished
In April 2026 we opened several product tracks. This single decision log separates work in progress from functionality available to customers.
Four tracks and their honest status
We began exploring voice workflows on April 15, review collection and analysis on April 17, and a native CRM track on April 21. In parallel, we discussed potential partnerships for integrations and go-to-market work.
These dates indicate the start of work, not a public release. Until a feature has been tested and appears in the available product, we label it as a development track.
- Voice agents: research into calls, consent, cost, and operator handoff.
- Reviews: consolidating signals and recurring themes without promising automatic management decisions.
- Chota CRM: a separate product track; current CRM integrations do not mean a native CRM is released.
- Partnerships: discussions are not agreements until there is a confirmed public outcome.
How we decide what becomes a product feature
Every track needs an observable customer process, an owner of the outcome, and a safe fallback. We test whether the feature solves a recurring problem better than an existing integration or a scoped service project.
If a task is unique to one company, it may remain a custom project. Only a repeatable workflow that can be supported without hidden manual work belongs in the product.
Where to check the current status
The product page lists currently available capabilities. This article preserves decision context and dates, but it does not replace the Chota interface or the commercial description at the time of connection.
Related posts
How we launched the Chota knowledge base and where its limits are
A first-hand look at Chota's document workflow: how business materials become agent context, what must be tested, and why a knowledge base does not replace process ownership.
How we select and route models in Chota
Instead of an unverified list of names, we explain the durable process Chota uses to balance task quality, latency, context, and model cost.