Typical build, installation, and channel wiring runs about one working week from the kickoff call, depending on how many channels you connect and whether WPML/multisite or custom order-schema work is involved. We confirm a firm timeline in writing after reviewing your site, WooCommerce version, and channel credentials. You are not buying a marketplace download — you are buying a plugin built and installed for your specific store.

Every build includes a post-launch support window for bug fixes and configuration adjustments. Because WhatsApp/Messenger run on Meta's Graph API and Telegram on the Bot API, those endpoints occasionally change; we offer a maintenance arrangement to keep webhooks, the WooCommerce REST sync, and HPOS compatibility working as WordPress, WooCommerce, and the messaging APIs update. Support terms are confirmed in your proposal.

Yes. The order-context panel is built to read from whichever order store your site uses — HPOS/custom order tables or the legacy post-meta storage. We verify your store's configuration during the build so order status, line items, and totals resolve correctly regardless of which storage WooCommerce is set to.

No. Conversations are stored as a custom post type inside your own WordPress database, and the plugin runs on your hosting. Inbound messages arrive through channel webhooks you control. The only external calls are to the messaging providers themselves (Meta and Telegram) to send and receive — there is no ECOSIRE-hosted middleman holding your chat history.

Yes. Assignment rules can route an incoming thread by channel, product category, or order value to a chosen agent or team. Agent access is governed by native WordPress roles and capabilities, internal notes stay staff-only, and supervisors can be given an oversight view across the whole queue. We configure these rules to match your team during the build.