Product roadmap

Build the operating layer around customer conversations

Think Reply is being built in layers: first the shared customer workspace, then production provider activation, then deeper revenue and commerce workflows. Priorities may move when provider requirements, reliability work or customer feedback changes.

Start free Read the docs

ShippedCore workspace and growth foundation

NextProvider activation and production readiness

LaterDeeper commerce and revenue workflows

ShippedAvailable in the product foundation

Core customer workspace

The first layer gives teams a practical operating workspace instead of another isolated chatbot dashboard.

Unified Inbox with assignment, notes, tags and saved replies Native Telegram and Website Chat message flow Contacts, lead pipeline and reusable audience lists Campaign drafts, scheduling and delivery records AI Assistant plus business Knowledge Base Email outreach sequences and suppression controls Automation triggers, conditions and actions Team, billing, audit logging and plan enforcement

ShippedGrowth and operations layer

WhatsApp, commerce and business tools foundation

The second layer connects customer conversations to the work that happens around them.

WhatsApp approved-template sync foundation Scheduled WhatsApp campaign path with workspace timezone Meta catalog connection, product sync and product cards WooCommerce verification and signed webhooks Shopify OAuth and webhook architecture Bookings and public booking flow Invoices with public invoice links and status tracking Voice activity and social planning records

NextProduction activation

Turn provider foundations into live customer connections

These items depend on production credentials, platform verification or provider approval rather than only application code.

Meta app review and live WhatsApp / Messenger / Instagram authorization Google OAuth production verification for Gmail Shopify production app credentials and compliance webhooks Live UddoktaPay account activation Social publishing permissions for connected networks Voice provider selection and click-to-call path

ExpandingDeeper revenue workflows

More automation around customer value

After core providers are live and stable, the next depth comes from connecting commerce, messaging and follow-up more tightly.

Abandoned-cart follow-up Order-status messaging workflows Catalog segmentation and product recommendations Public booking availability rules Online invoice payment Advanced campaign attribution and analytics More business and productivity integrations Deeper multi-step customer journey automation

How to read this roadmap

“Shipped” means the application workflow exists in Think Reply. “Next” can still depend on third-party credentials, reviews or provider activation before every customer can use it in production. “Expanding” describes intended product depth, not a guaranteed delivery date.