Interakt

Interakt presents a current full-stack WhatsApp growth platform for marketing, sales and support, with Instagram, RCS and voice surfaces. It reports 50,000+ businesses globally, 60+ integrations, a shared inbox, Sales CRM, campaigns, AI agents, WhatsApp commerce and real-time analytics.

Current terms identify Jio Haptik Technologies Limited (CIN U72900GJ2013PLC107560) as the Indian contracting company offering Interakt and list India, Singapore, Indonesia, Brazil, UAE, Philippines and Africa in the current footer.

The policy calls Interakt a product of Jio Haptik Technologies Limited and describes the company as providing a messaging SaaS platform that customers use to manage user communications. It describes collection, use, deletion/anonymisation and India-law safeguards but does not establish a complete current control or certification inventory.

The current pricing surface shows monthly, quarterly and annual packaging, Growth at USD 55/month, Advanced at USD 69/month, enterprise on request, an Instagram-only Starter tier, a Sales CRM plan at INR 2,499/month for five sales agents plus INR 499 per extra agent, WhatsApp AI-agent add-on/plan pricing, and separate message charges by template category and destination.

Interakt offers a 14-day free trial and says customers can start within minutes; its team provides setup help without extra support cost. Meta business verification is described as taking from three business days to four weeks and messaging is restricted while verification is pending.

Current AI-agent copy distinguishes fixed, rule-based automation from agents that interpret open-ended context and intent. It advertises FAQ, appointment booking, lead qualification, catalog-based product recommendation, and order management that tracks orders, updates delivery and handles returns; custom deployment across WhatsApp, web and voice is sales-assisted.

The Marketing Hub supports segmented WhatsApp and Instagram campaigns, broadcasts, automation, click tracking and campaign triggers for acquisition, conversion, retention and win-back.

The Support Hub centralizes WhatsApp and Instagram conversations in a shared inbox, supports assignment, automation and team handling, and is positioned for scaled customer support.

The WhatsApp-first Sales CRM captures leads from WhatsApp, workflows, APIs, Shopify and manual entry, assigns owners and statuses, and supports pipeline follow-up and team performance management.

Instagram Automation directly handles DMs, comments, mentions, price queries, giveaways, comment-to-DM replies and Instagram-to-WhatsApp lead capture. It combines Instagram and WhatsApp in one inbox and publicly lists INR 999/month plus tax for unlimited owner-role agents and Instagram conversations.

WhatsApp Commerce supports a WhatsApp store, catalog synchronization and browse-to-buy journeys. Current homepage and commerce copy identify Shopify, WooCommerce and Excel catalog sources and WhatsApp Pay for customer checkout.

Interakt automatically switches failed WhatsApp deliveries to RCS and supports rich, interactive messages in the SMS inbox. This is deterministic channel fallback, not an autonomous merchant decision.

The current official integration catalog covers ecommerce, CRM, support, payments and automation tools; the company advertises 60+ plug-and-play integrations.

The official Shopify integration connects store and customer events to catalogs, campaigns, abandoned-cart recovery, order notifications and support workflows.

The official WooCommerce integration supports abandoned-cart recovery and customer engagement on WhatsApp.

The official integration inventory contains a Return Prime connector, supporting a partner-mediated returns workflow; the retained surface does not establish Interakt as the system that authorizes refunds or disposition.

Interakt documents native WhatsApp Pay for eligible +91 WhatsApp Business API numbers, with UPI, cards and netbanking options so a customer can complete payment in the conversation.

The current product navigation includes WhatsApp Voice Calling as a live channel surface for business-customer calls.

MyCallGenie is positioned as an AI call receptionist within the current Interakt product suite. Public action, usage and pricing boundaries were not retained in enough detail to treat it as the same product surface as self-serve WhatsApp AI agents.

Interakt documents public APIs and webhooks for connecting business systems and triggering messaging workflows; downstream commerce execution remains dependent on connected-system permissions.

Interakt markets a drag-and-drop no-code chatbot builder for configured workflows, FAQs and handoff. The homepage says it can automate up to 80% of queries, but that aggregate marketing claim has no named case or disclosed calculation.

The official case sitemap enumerated 69 dedicated SMB, D2C and creator case URLs plus the case hub as of access. One dedicated CoverSure URL is effectively blank and the Happy Staff's URL currently renders a CoverSure story.

The official enterprise case sitemap enumerated 11 dedicated enterprise case URLs plus the enterprise case hub as of access.

A Jio Haptik document updated in 2022 describes Interakt as a Jio Haptik product on the official WhatsApp Business API and lists storefront, inbox, campaigns, order/shipping alerts, cart recovery and COD confirmation. This is retained as legacy lineage and capability context, not the sole basis for current shipping claims.

The current Haptik site markets Interakt by Haptik as a full-stack WhatsApp platform for enterprises, with campaigns, connectors, workflows, catalogs, analytics and click-to-WhatsApp ads.

An official certificate identifies Jio Haptik Technologies Limited and includes design, development and delivery of conversational-AI products and solutions including Interakt. Certification scope and current expiry should not be generalized beyond the certificate itself.

The official integration sitemap enumerates Shopify, WooCommerce, Zoho products, HubSpot, Freshdesk, Stripe, Salesforce, Zapier, Make, Razorpay, Instamojo, PayU, Pabbly, Facebook lead forms, Google Sheets, WebEngage and Return Prime. No Shiprocket-specific integration URL was present in this capped inventory.

Vendor-hosted named quantified case: WhatsApp support, abandoned-cart recovery, product launches and repeat-purchase engagement. 5 distinct reported metrics were normalized with source-level caveats.

Vendor-hosted named qualitative case: AI-agent lead qualification, catalog sharing, WhatsApp marketing and a Kylas CRM connection; no quantified outcome disclosed.

Vendor-hosted named quantified case: AI-supported WhatsApp commerce and retention; the URL and body alternate among Drink Delulu, iShots Life and Delulu. 5 distinct reported metrics were normalized with source-level caveats.

Vendor-hosted named quantified case: AI qualification and booking support for a homestay network. 7 distinct reported metrics were normalized with source-level caveats.

Vendor-hosted named quantified case: Automated customer communication and support for a business using WhatsApp. 3 distinct reported metrics were normalized with source-level caveats.

Vendor-hosted named qualitative case: Greetings, shared inbox, broadcasts and order updates; no quantified outcome disclosed.

Vendor-hosted named qualitative case: WhatsApp workflows and broadcasts for mental-health consultations; no quantified outcome disclosed.

Vendor-hosted named qualitative case: Product catalog, support, order updates and a configured 15-day sample follow-up; no quantified outcome disclosed.

Vendor-hosted named quantified case: WhatsApp cart recovery, retention, support and double COD confirmation. 4 distinct reported metrics were normalized with source-level caveats.

Vendor-hosted named quantified case: AI-agent support and price-on-request sales for an Indian art marketplace. 3 distinct reported metrics were normalized with source-level caveats.

Vendor-hosted named qualitative case: HubSpot-connected WhatsApp automation and proactive travel updates reduced calls qualitatively; no exact outcome disclosed.

Vendor-hosted named quantified case: Retail WhatsApp automation across a multi-branch sports chain. 4 distinct reported metrics were normalized with source-level caveats.

Vendor-hosted named quantified case: WhatsApp cart recovery, query conversion, support and call deflection for a fresh-flour brand. 6 distinct reported metrics were normalized with source-level caveats.

Vendor-hosted named qualitative case: Broadcasts, inbox, catalogs and order updates for an Ayurvedic brand; no quantified outcome disclosed.

Vendor-hosted named quantified case: Dealer communication and exhibition engagement on WhatsApp. 3 distinct reported metrics were normalized with source-level caveats.

Vendor-hosted named quantified case: WhatsApp conversion improvement for a tea brand. 3 distinct reported metrics were normalized with source-level caveats.

Vendor-hosted named quantified case: WhatsApp reactivation and cross-brand repeat-purchase campaigns. 4 distinct reported metrics were normalized with source-level caveats.

Vendor-hosted named quantified case: WhatsApp free-trial acquisition and conversion for a dessert chain. 4 distinct reported metrics were normalized with source-level caveats.

Vendor-hosted named quantified case: A WhatsApp restaurant-broadcast example with vendor-calculated revenue and ROI. 8 distinct reported metrics were normalized with source-level caveats.

Vendor-hosted named quantified case: Subscription renewal, reactivation and festive WhatsApp campaigns. 5 distinct reported metrics were normalized with source-level caveats.

Vendor-hosted logo-or-empty case: Dedicated official case URL is live but contains no usable case body or outcome.

Vendor-hosted named qualitative case: The Happy Staff's URL currently renders a qualitative CoverSure insurance story about broadcasts, inbox and automation.

Vendor-hosted named quantified case: Click-to-WhatsApp advertising and lead conversion for a go-karting venue. 6 distinct reported metrics were normalized with source-level caveats.

Vendor-hosted named quantified case: WhatsApp follow-up and sales automation for a timber business. 2 distinct reported metrics were normalized with source-level caveats.

Vendor-hosted named quantified case: Automated customer updates for a home-construction business. 2 distinct reported metrics were normalized with source-level caveats.

Vendor-hosted named quantified case: Shopify-connected WhatsApp notifications, cart recovery, support and COD-to-prepaid nudges. 4 distinct reported metrics were normalized with source-level caveats.

Vendor-hosted named quantified case: WhatsApp support and resolution automation. 2 distinct reported metrics were normalized with source-level caveats.

Vendor-hosted named quantified case: Indonesian WhatsApp and Instagram automation story with inconsistent acquisition/conversion labels. 5 distinct reported metrics were normalized with source-level caveats.

Vendor-hosted named quantified case: WhatsApp reminder automation. 2 distinct reported metrics were normalized with source-level caveats.

Vendor-hosted named quantified case: Instagram automation and WhatsApp sales conversion for a menswear brand. 8 distinct reported metrics were normalized with source-level caveats.

Vendor-hosted named quantified case: Instagram comment and DM automation for a creator. 5 distinct reported metrics were normalized with source-level caveats.

Vendor-hosted named quantified case: Indonesian conversational automation case. 6 distinct reported metrics were normalized with source-level caveats.

Vendor-hosted named quantified case: Instagram automation for a creator account. 6 distinct reported metrics were normalized with source-level caveats.

Vendor-hosted named quantified case: WhatsApp cart recovery and customer service. 5 distinct reported metrics were normalized with source-level caveats.

Vendor-hosted named quantified case: Shopify-connected catalogs, support, COD confirmation and WISMO. 1 distinct reported metric was normalized with source-level caveats.

Vendor-hosted named quantified case: WhatsApp customer communication for a toy brand. 1 distinct reported metric was normalized with source-level caveats.

Vendor-hosted named quantified case: WhatsApp product inquiry and order confirmation. 4 distinct reported metrics were normalized with source-level caveats.

Vendor-hosted named quantified case: WhatsApp engagement and commerce for a home-decor brand. 1 distinct reported metric was normalized with source-level caveats.

Vendor-hosted named quantified case: Abandoned-cart recovery on WhatsApp. 1 distinct reported metric was normalized with source-level caveats.

Vendor-hosted named quantified case: WhatsApp customer engagement and support. 3 distinct reported metrics were normalized with source-level caveats.

Vendor-hosted named quantified case: Abandoned-cart recovery and feedback collection for an oral-care brand. 2 distinct reported metrics were normalized with source-level caveats.

Vendor-hosted named quantified case: Support bot and Diwali commerce campaigns. 3 distinct reported metrics were normalized with source-level caveats.

Vendor-hosted named quantified case: WhatsApp chatbot engagement campaign. 2 distinct reported metrics were normalized with source-level caveats.

Vendor-hosted named quantified case: WhatsApp engagement and international student-market expansion. 8 distinct reported metrics were normalized with source-level caveats.

Vendor-hosted named quantified case: WhatsApp commerce and support for a fashion brand; page contains copied healthcare wording. 4 distinct reported metrics were normalized with source-level caveats.

Vendor-hosted named quantified case: Healthcare WhatsApp engagement and support. 4 distinct reported metrics were normalized with source-level caveats.

Vendor-hosted named quantified case: WhatsApp support automation for a jewelry brand. 3 distinct reported metrics were normalized with source-level caveats.

Vendor-hosted named quantified case: WhatsApp event invitation and attendee conversion. 5 distinct reported metrics were normalized with source-level caveats.

Vendor-hosted named quantified case: Cart recovery, faster support and repeat purchases. 4 distinct reported metrics were normalized with source-level caveats.

Vendor-hosted named quantified case: WhatsApp cart recovery, support and sales for an artisan brand. 4 distinct reported metrics were normalized with source-level caveats.

Vendor-hosted named quantified case: WhatsApp lead response and online revenue growth for a jewelry brand. 2 distinct reported metrics were normalized with source-level caveats.

Vendor-hosted named qualitative case: Shared inbox, Shopify browsing and payment, and order notifications; no quantified outcome disclosed.

Vendor-hosted named quantified case: WhatsApp support and conversion for a consumer brand. 5 distinct reported metrics were normalized with source-level caveats.

Vendor-hosted named quantified case: WhatsApp merchant onboarding and support for restaurant software. 7 distinct reported metrics were normalized with source-level caveats.

Vendor-hosted named quantified case: WhatsApp support scale, cart recovery and revenue contribution. 5 distinct reported metrics were normalized with source-level caveats.

Vendor-hosted named quantified case: WhatsApp commerce, COD confirmation and customer service for an apparel brand. 3 distinct reported metrics were normalized with source-level caveats.

Vendor-hosted named quantified case: WhatsApp delivery and open-rate improvement for a D2C brand. 2 distinct reported metrics were normalized with source-level caveats.

Vendor-hosted named qualitative case: Qualitative WhatsApp engagement story; only a 2–5% email-open baseline is disclosed, not a quantified Interakt outcome.

Vendor-hosted named qualitative case: Bulk campaigns to thousands and 24/7 support are described without a quantified business outcome.

Vendor-hosted named quantified case: WhatsApp automation for scaled customer handling. 1 distinct reported metric was normalized with source-level caveats.

Vendor-hosted named quantified case: WhatsApp communication and support for an education company. 6 distinct reported metrics were normalized with source-level caveats.

Vendor-hosted named quantified case: WhatsApp inquiry response and lead handling for religious services. 3 distinct reported metrics were normalized with source-level caveats.

Vendor-hosted named quantified case: WhatsApp customer engagement for a technology provider. 1 distinct reported metric was normalized with source-level caveats.

Vendor-hosted named qualitative case: Qualitative WhatsApp commerce story; 70–80% online-order share describes the customer's channel mix, not a quantified Interakt outcome.

Vendor-hosted named quantified case: WhatsApp lead-to-trial funnel for a cooking-robot company. 4 distinct reported metrics were normalized with source-level caveats.

Vendor-hosted named quantified case: WhatsApp student support with contradictory volume claims. 4 distinct reported metrics were normalized with source-level caveats.

Vendor-hosted named qualitative case: WhatsApp support setup in three to four days; the case states a prior one-to-two-day wait but no quantified post-Interakt outcome.

Vendor-hosted named quantified case: WhatsApp engagement for insurance advisory. 3 distinct reported metrics were normalized with source-level caveats.

Vendor-hosted named quantified case: WhatsApp travel sales and support during the pandemic. 3 distinct reported metrics were normalized with source-level caveats.

Vendor-hosted named quantified case: Enterprise WhatsApp notifications and lead generation. 4 distinct reported metrics were normalized with source-level caveats.

Vendor-hosted named quantified case: High-scale WhatsApp lifecycle automation for Jio. 4 distinct reported metrics were normalized with source-level caveats.

Vendor-hosted named quantified case: WhatsApp store-to-door ordering and customer engagement. 3 distinct reported metrics were normalized with source-level caveats.

Vendor-hosted named quantified case: WhatsApp lead capture and routing for an electric-vehicle brand. 2 distinct reported metrics were normalized with source-level caveats.

Vendor-hosted named quantified case: WhatsApp investment journeys and customer support. 2 distinct reported metrics were normalized with source-level caveats.

Vendor-hosted named qualitative case: 24/7 WhatsApp support during a surge in purifier enquiries; no exact outcome metric disclosed.

Vendor-hosted named qualitative case: Authenticated WhatsApp credit-disbursal journey for CASHe; the title anonymizes the customer while the body names CASHe. No quantified outcome disclosed.

Vendor-hosted named quantified case: Omnichannel support and WhatsApp automation for a Singapore telecom. 6 distinct reported metrics were normalized with source-level caveats.

Vendor-hosted named quantified case: WhatsApp food ordering for train passengers. 2 distinct reported metrics were normalized with source-level caveats.

Vendor-hosted named quantified case: Custom WhatsApp chatbot for lead generation. 2 distinct reported metrics were normalized with source-level caveats.

Vendor-hosted named qualitative case: WhatsApp customer-care integration for concurrent conversations, agent productivity and call deflection; the case reports only a qualitative reduction in calls.