AiSensy

The current homepage positions AiSensy as an India-built WhatsApp engagement platform spanning Click-to-WhatsApp acquisition, broadcasts, retargeting, deterministic chatbots, AI agents, catalogs, payments, forms, multi-agent support and ecommerce/CRM integrations. These are WhatsApp-centered workflows; no current Instagram inbox, email, RCS or voice-agent product is documented.

AiSensy says it has a 100+ person team, is trusted by 210,000+ businesses across 68+ countries and is an official WhatsApp Business Solution Partner. The same page also displays older impact counters of 100,000+ businesses served, 1.5 billion+ messages and INR200 crore+ revenue generated for customers, without definitions or measurement methodology. It describes acquisition through Click-to-WhatsApp ads, forms, broadcasts, retargeting, catalogs, payments, live chat and chatbots.

The official LinkedIn page identifies AiSensy as a privately held software company founded in 2020, headquartered in Gurgaon, with a displayed 51-200 employee band. Current posts call Gautam Rajesh Shelley Founder and CEO; official/employee posts identify Mohit Dua as Co-Founder. The page is self-reported and does not provide audited headcount or ownership percentages.

The current terms name AiSensy Communications Private Limited, doing business as AiSensy, as the Indian contracting entity and describe the website, mobile application and related software/services. The registered-office text begins with Plot 22, Maison D Auraine Building, Gurugram. The terms do not disclose shareholders, funding, revenue or standard enterprise service levels.

The privacy notice names AiSensy Communications Private Limited, lists a Gurugram postal address and says Chargebee stores payment data. It describes account, contact, device, usage and marketing-source data, but does not publish a complete current subprocessor list, data-residency commitment, model-training policy for AI-agent conversation data or enterprise retention schedule.

The live India pricing implementation defines Free Forever; Basic at INR1,500/month; Pro at INR3,200/month; Premium at INR9,100/month; Unlimited at INR45,000/month; and Enterprise custom for 5 lakh+ messages/month. Quarterly saves 5% and yearly 10%; billing is prepaid. Meta pass-through charges are INR1.09 per delivered India marketing template and INR0.145 per utility/authentication template, while service-window replies are free. Extra seats cost INR750/month. Keyword Chatbot Flows cost INR2,500/month and the AI Agent add-on INR3,500/month, charged on top of a platform plan. Fair use caps 'unlimited' at 200 agents, 500 tags and 100 attributes. The FAQ still uses legacy 'conversation credits' wording even while explaining the current per-template model.

The current AI-agent page documents knowledge-base ingestion, long-term conversational context, AI routing, an instruction/orchestrator surface, no-code REST tool calling with GET/POST/PUT/PATCH/DELETE, product recommendations, lead qualification, appointments, order-status lookup, task completion and human handoff. The platform claims agents can trigger APIs and external actions, but connected systems and merchant-defined instructions determine authority. The page prices five agents at INR3,500/month with 3,500 AI messages, 500 test messages and three test numbers. A repeated comparison markets multilingual understanding, while its FAQ says responses are currently English-only and other-language questions can be understood only when context exists in the knowledge base; full multilingual responses are forthcoming.

The current help article explains that each intelligent response, tool call or Orchestrator reasoning step consumes an AI message. An add-on is required to go live; test flows receive 500 messages across up to three numbers; plans can bill monthly, quarterly or yearly; overages are billed and unused messages lapse. It documents smart routing from flows and human escalation, but does not publish model accuracy, hallucination tests, approval gates or a per-tool permission model.

The current release feed records live AI agents for sales, support and lead qualification, training on merchant data, bookings, lookups and follow-ups, human handoff, 500 test messages, Zoho synchronization, Template Message Journeys and the January 2026 per-message pricing transition. It is a useful current-versus-legacy surface but gives no independent production benchmarks.

The current page documents opted-in contact import, approved templates, tags/attributes/behavior segmentation, campaigns, scheduling, carousel/button messages, delivery/read/click/reply analytics and retargeting based on prior interaction. These are deterministic operator-configured campaigns; the page does not establish independent pricing, budget or creative decisions by an AI agent.

AiSensy describes rule-based automation as trigger, predefined logic/flow and an outbound WhatsApp action. Documented ecommerce examples include abandoned-cart reminders, order and delivery updates; other verticals use bookings, reminders and transaction alerts. The direct action is messaging/workflow execution, not underlying fulfillment, inventory allocation or settlement.

The live-chat page documents a shared WhatsApp inbox, tags/attributes, agent rules, campaign/tag/attribute routing, conversation transfer, manager monitoring and explicit Active, Requesting, Intervened and History states. A user or unresolved bot can request intervention; an agent takes over with profile/history context and resolving the chat reactivates the chatbot. This is concrete bot-to-human handoff and deterministic routing, not multi-agent AI collaboration.

The current catalog page documents connecting a Meta/Shopify catalog, showing products, adding items to cart, placing orders and completing payments in WhatsApp. Keyword triggers are deterministic; the optional AI-agent trigger can interpret intent, answer catalog questions, recommend products and call APIs. Product records remain edited in Shopify/Meta, so AiSensy is a conversational catalog and cart layer rather than inventory or source-catalog authority.

AiSensy can send payment messages from broadcasts, live chat and chatbot flows; track pending/successful status; retarget incomplete payers; and display received payments in one dashboard. UPI, cards, net banking and gateways including Razorpay and PayU are supported. Payment authorization, processing, settlement and refunds remain with WhatsApp/native rails or external gateways rather than AiSensy.

The current INR2,500/month add-on provides five keyword/rule chatbots, a no-code flow builder, regex/keyword/template/CTWA triggers, lists, product cards, API calls, catalog/cart/payment actions, FAQ/order-status paths and live-agent escalation. Flows are merchant-authored deterministic orchestration; AI generation of a flow does not make runtime decisions autonomous.

The integrations page markets 2,000+ connections through direct APIs, Pabbly, Integrately and Zapier plus Shopify, WooCommerce, OpenCart, Razorpay, PayU, WebEngage, CleverTap, LeadSquared and Yuko Loyalty. It documents abandoned-cart/order/delivery messages, payment invoices/links, CRM-triggered broadcasts and loyalty-point/reward notifications. The 2,000+ count includes connector ecosystems and is not a list of 2,000 native AiSensy-built integrations.

The current Shopify integration directly triggers abandoned-cart, order-confirmation, shipping, delivery, COD-confirmation/RTO-reduction, feedback, reorder and promotion messages from store events. A one-click setup has a USD1 fee, with a manual path available. AiSensy sends and branches communications; Shopify/checkout systems remain the order and inventory systems of record.

The Razorpay integration maps payment-link-created, invoice-issued, subscription-halted and refund-processed events to approved WhatsApp campaigns using Razorpay and AiSensy parameters. It also supports broadcasts and chat. AiSensy executes notifications; Razorpay owns payment, refund and subscription state.

The WebEngage integration sends broadcasts and abandoned-cart reminders from WebEngage, syncs leads and connects WebEngage as a WhatsApp service provider through API key and webhook configuration. It supports US, India and Saudi WebEngage server endpoints, showing international integration coverage but not AiSensy data residency.

AiSensy publishes Project API and webhook documentation for programmatic messaging and inbound event integration. Pricing assigns Template Message APIs to Basic and broader Project APIs to Pro. Public APIs establish extension and external action surfaces, but no SDK, MCP server or universal agent-permission framework was found.

The current help article lists Shiprocket Checkout among selectable Shopify checkout platforms alongside Shopify, Razorpay, Breeze, GoSwift, ecom360, GoKwik and Simpl (upcoming). AiSensy supports checkout URL/event compatibility for WhatsApp cart/order messaging; the article does not establish a Shiprocket integration marketplace listing, reseller/bundle, shipment-data connection, joint price or customer outcome. Other checkout gateways may require paid custom development.

The live hub links 30 dedicated customer pages. The sitemap adds one public case (BankSathi) and two paths that now render login shells (SoftwareSuggest and Trias Infotech), yielding 31 usable public cases. Hub-level claims of 71% higher engagement, 25-60% revenue growth, 98% opens, 45-60% clicks and 7% engagement have no cohort, baseline, period or formula, so they are not treated as grade-A or case-specific proof.

Automation Lite is an India SMB/retail offer shown at INR899/month with an INR500 promotional price plus GST, 25 templates, three automations, two members, unlimited contacts and a QR kit. It quotes the same INR1.09 marketing and INR0.145 utility message rates. This is a lower-end mobile/QR-led package distinct from the main pricing cards; the duration and relationship of the promotional price to the standard offer are not fully defined.

AiSensy's shop markets an offline/retail QR acquisition package at INR699 monthly or INR1,999 quarterly with three broadcasts, three flows, 25 templates, one owner plus one agent, an AI template/ad-creative generator and a physical QR kit. This supports small-store onboarding but creates packaging fragmentation versus Automation Lite and the main platform tiers.

The current Google Play listing identifies AiSensy Communications Private Limited as developer, shows 10,000+ downloads and a June/July 2026 update stream, and describes mobile WhatsApp account application, broadcasts, no-code chatbots, analytics and multi-agent chat. Developer-declared disclosures say the app may collect and share personal, financial and other data, encrypts data in transit and supports deletion requests. Download count is not paid-customer evidence.

Dream Green Capital's official portfolio links directly to aisensy.com and describes it as enabling businesses to broadcast and manage reach with a CRM. This supports a portfolio/investor relationship, but the investor does not disclose round date, instrument, amount, ownership or whether the holding remains current.

AiSensy lets merchants create/manage Meta ads that open WhatsApp, capture the resulting contact, tag/segment leads and launch chatbot or follow-up journeys. The main pricing code says its Ads Manager can create Click-to-WhatsApp, lead-form, website-traffic and sales ads. Public evidence supports campaign execution, but not autonomous bid/budget optimization or independently verified CAC lift.

WhatsApp Forms collect structured lead, booking, preference, feedback and survey data inside a WhatsApp journey and can pass the captured data into segmentation or follow-up workflows. Forms execute data collection, not independent lead-scoring accuracy or a complete CRM system of record.

The Lite tutorial says WhatsApp API setup is usually live within ten minutes, display-name approval can take three to four hours, KYC requires GST or MSME/Udyam, the promotional plan is INR500/month plus GST with no lock-in and QR kits arrive in four to seven business days. It documents QR-scan, ad-click and keyword-triggered drip automations. QR-kit delivery is tracked through an aisensy.shiprocket.co page, showing AiSensy uses Shiprocket as a fulfillment provider for its own kit; this is not a merchant-facing software bundle.

AiSensy's official LinkedIn post says the company began in Haldwani with seven people and grew from 5-10 businesses to 10,000+ WhatsApp Business API businesses before receiving Meta's Emerging Partner of the Year 2023 award. These historical scale claims are lower than current website counters and are retained as dated rather than conflicting current totals.

The current tutorial says INR3,500/month unlocks five chatbots and 7,000 AI messages, with 7,000/15,000/30,000/50,000/100,000-message packs, billed overages and no carry-forward. This conflicts with the live pricing implementation and AI-agent card, which currently show 3,500 included AI messages at the same INR3,500/month. The tutorial also says each knowledge-base answer, tool call or Orchestrator reply consumes a message and testing supports up to three numbers with 500 messages.

Vendor-hosted named case: Adani Realty used Click-to-WhatsApp ads, automated qualification for project, budget, location and site-visit intent, follow-ups and centralized lead handling. AiSensy reports 30% lower cost per lead, 25% lower cost per qualified lead and 30% growth in sales-qualified leads; no dates, counts, endpoint values or attribution method are disclosed.

Vendor-hosted named case: ADNEC Group automated event notifications/reminders and FAQ/survey chatbots and routed complex questions to live agents. AiSensy reports a 45% increase in 'user experience,' 4x revenue growth versus the previous year and 10x growth in Google reviews. Revenue attribution, currency, review counts and the user-experience measure are not disclosed.

Vendor-hosted named case: Ajmera Tyres deployed WhatsApp Pay across 13 retail locations plus rule chatbots and live support. The page reports a 23% increase in payment collection/collection efficiency; it does not provide baseline collections, payment count, value, period or formula.

Sitemap-only public vendor case: BankSathi used behavior-branching WhatsApp flows and Hinglish audio to re-engage advisors inactive for three to six months. AiSensy reports 10% reactivation, 4.5x ROI and 92% delivery; no spend/revenue inputs, message count, denominator or campaign dates are disclosed. A named BankSathi digital-marketing manager testimonial is included, but it is hosted only by AiSensy.

Vendor-hosted named case: Choice Connect used delivery/performance analytics, automatic failed-message retries, action-triggered follow-ups, CTWA tagging, button journeys, routing and chatbots. AiSensy reports 20% higher lead acquisition, 45% lower lead churn and 2x operational efficiency; definitions, endpoints, counts and measurement window are absent.

Vendor-hosted named case: Cosco replaced email/WhatsApp-app broadcasts, automated order and delivery updates, used live chat/chatbots and obtained verification. Results say 3x better reach, 2x engagement and 98% open rate, described as 5x email/SMS. A named executive testimonial says reach moved from around 30-35% to around 90%, while the challenge text says 35%; 90/35 is about 2.57x and 90/30 is 3x, so the headline depends on which baseline is used. No dates or message counts are shown.

Vendor-hosted named government-operator case: DTC's Hindi/English bot, PeLocal-built webview, native UPI flow and QR ticket execute bus-ticket selection and purchase in WhatsApp. AiSensy reports 14 lakh+ tickets sold since launch and 2x user satisfaction; the launch date, user-satisfaction instrument, baseline and transaction denominator are not given. PeLocal, not AiSensy, built the station-selection webview.

Vendor-hosted named case with named sales-support lead testimonial: FlexiFunnels used verified WhatsApp broadcasts and automated onboarding, webinar, launch, payment and renewal communications. AiSensy reports 38% higher CSAT, 2x overall user experience and 30% of webinar registrations via WhatsApp; survey method, baseline, registration counts and period are absent.

Vendor-hosted named case: FliQi used CTWA targeting for ages 21-45 in rural Rajasthan, live support and follow-up notifications. AiSensy reports 85% conversion of qualified leads during a campaign, 70-80% quarter-over-quarter revenue growth, 60% of business from CTWA and 80% of clients from remote Rajasthan. Counts, quarter dates, revenue values, attribution and exact 'business' denominator are absent.

Vendor-hosted named case: Give used a qualifying donation/payment chatbot, fundraiser broadcasts and an Instagram WhatsApp button. AiSensy reports 90% payment success, 15x ROI on the first WhatsApp broadcast and 1,000+ organic leads from Instagram. The body also says '100s' of leads, a looser quantity than the results panel; transaction counts, spend, revenue, period and attribution are absent.

Vendor-hosted named case: GroMo used flows for sales attribution, a bot that creates dispute tickets from uploaded documents, WhatsApp Pay/Google Sheets for trainer enrollment/payment visibility and Zoho CRM logging. AiSensy reports 70% higher support/service resolution efficiency and real-time tracking, with no baseline, ticket count, time measure or period. The ticket creation is a direct configured action; payment and CRM state depend on external systems.

Vendor-hosted named case with HomeLane VP Product testimonial: a bot qualifies leads, suggests appointment slots, pushes confirmed details to CRM and provides a store locator. AiSensy reports 900+ new qualified leads/month, 2.8% WhatsApp lead-to-order conversion versus 1.3% on other channels, a 2x headline and 300+ monthly design consultations. The exact relative lift from the stated endpoints is 115.38%, not exactly 100%; cohort comparability and dates are absent.

Vendor-hosted named case with Hummingbird Head of IT testimonial: guests book/manage/cancel hotels in WhatsApp with OTP, payment links, webviews, bots and human support. AiSensy reports 70% lower response time, 55% higher engagement and 65% more WhatsApp bookings; endpoint values, booking counts, revenue effect and period are not given.

Vendor-hosted named case: IndiaMART replaced repetitive buyer-verification calls with WhatsApp messages/forms and automated order/shipping/delivery notifications. Baseline context is 50 lakh enquiries/month, 2 crore calls/month, eight call centers and four calls per enquiry. The results panel says 50 lakh WhatsApp enquiries and 10 lakh approved, 33% more buyer conversion, 60% fewer complaints and 3x engagement. The page does not reconcile 10/50=20% with the 33% lift or provide the prior approval rate, dates or complaint counts.

Vendor-hosted named case with a named operations-manager testimonial: Jaipuria Schools automated parent/alumni/event/admission, HR and franchise-sales communications. AiSensy reports 2.5x communication efficiency, faster hiring and more engaged franchise prospects; only the efficiency claim is quantified, with no task counts, time baseline, formula or period.

Vendor-hosted named ecommerce case: Keeros used broadcasts, order/payment/delivery and cart reminders, live support/chatbots and CTWA. The page reports 20-40% cart recovery (body says up to 40%), 40% business/sales growth, 3x engagement, 98% read/open rate and 45-60% click-throughs, against a 25% email/SMS open-rate baseline. Counts, revenue values, campaign dates and attribution are absent.

Vendor-hosted named qualitative case with LearnTube co-founder testimonial: AiSensy automated personalized onboarding, course updates, certificate dispatch and admissions-chatbot nudges, leaving counselors to handle exceptions. The page says the team saved hours and reduced admissions cycle time but reports no outcome quantity, baseline, timeframe or formula; the 5 million+ learner figure is customer context, not an AiSensy outcome.

Vendor-hosted named case with founder testimonial: LiveLong Wealth used broadcasts, live support and verification. AiSensy reports 98% open rate, 5x email/SMS open rates and 3x engagement; no message count, exact channel baseline, period or engagement definition is disclosed.

Vendor-hosted named case: visitors scan a QR code and purchase zoo tickets through an automated WhatsApp flow. AiSensy reports cash counters falling from 11 to one, a 90.91% analyst-derived reduction, while staff focus and visitor experience improved qualitatively. No dates, ticket volume, staffing count or counter-comparability details are given.

Vendor-hosted named case: NMIMS used application-dropoff reminders, webinar/event broadcasts, student notifications, chatbots and live support. The challenge says 40% filled applications only midway, while the solution says the prior dropoff rate was 60%; no reconciliation is provided. AiSensy reports 45-60% recovery of dropped applications, 83% of repetitive support queries automated, 3x support engagement, 5x lead generation with 45,000+ qualified leads and 3x event/webinar signups. Dates, counts behind most ratios and attribution are absent.

Vendor-hosted named case: The 1% Club replaced ad-to-landing-page steps with CTWA, forms, WhatsApp payment and behavior-segmented broadcasts. The case states a roughly 20% ad-to-landing-page lead dropoff baseline, then reports 5x leads at the same budget and 3x conversions. Lead counts, conversion rates, spend, period and causal controls are not disclosed.

Vendor-hosted named case with a named digital-marketing manager testimonial: People Matters used opt-in/lead-magnet campaigns, intent buttons, event-specific flows, 24-hour reminders, confirmations/e-tickets, polls and feedback branching. AiSensy reports 25% higher lead conversion, 2x email-relative engagement and 35% lower manual operations; endpoints, audience counts, work-hour baseline and dates are absent.

Vendor-hosted named case: PhysicsWallah used CTWA-to-chatbot segmentation, promotional broadcasts, live chat, reminders and FAQ bots. AiSensy reports 3x leads, 4x webinar attendance and 5x course sales. The legacy email baseline is 20% opens and 2-5% click-through, but the case does not provide WhatsApp endpoint rates, counts, revenue, period or attribution method.

Vendor-hosted named case: Refrens automated reseller onboarding and enabled freelancers to send invoices through WhatsApp. The page reports 98% onboarding-message opens, 5x email/SMS open rates, 50,000+ paid users/subscriptions and 3x engagement. The baseline says up to 80% of emails were unopened, implying at least 20% opened; 98/20=4.9x, consistent with the rounded 5x headline. The portion of paid subscriptions attributable to AiSensy, dates and counting method are not disclosed.

Vendor-hosted named ecommerce case: AiSensy connected Skullcandy's store to trigger abandoned-cart reminders 15-20 minutes after abandonment, broadcasts and order/delivery updates. The page reports 150x ROI, 25-40% cart recovery and 3x message engagement. Spend, attributed revenue, cart counts, denominator, dates and ROI convention are absent.

Vendor-hosted named ecommerce case: The Hatke used 15-20 minute cart reminders, broadcasts, order/delivery updates, live support and verification. AiSensy reports 21x ROI, up to 40% cart recovery and 3x engagement; body text also says real-time support produced 2x engagement, creating an unexplained 2x versus 3x difference across scopes. The prior email/SMS baseline is 20% opens and 2-5% clicks; no counts, dates, spend or revenue are disclosed.

Vendor-hosted named case: Thyrocare's BookMyTest used a unified multi-agent inbox, CTWA, broadcasts, carousel/buttons and chatbots for package discovery and bookings. AiSensy reports 40% higher booking conversion, 5x engagement, daily conversations rising from 30-40 to 200-300 and 2x operational efficiency without team growth. Endpoint conversion rates, exact conversation ratio (which ranges 5x-10x), team size and dates are absent.

Vendor-hosted named agency case: Tule used opted-in broadcasts, webinar/ticket/order/cart notifications and live support, and onboarded ecommerce clients to the platform. AiSensy reports 3x business growth and 98% open rate. A '360 Business Transformation' result is qualitative wording, not a defined 360-degree or numeric measure. Counts, revenue values and period are absent.

Vendor-hosted named qualitative case: Weatherseal used instant enquiry acknowledgement, timed follow-ups, multi-step WhatsApp journeys, missed-call callback triggers, CTWA lead capture/organization and business verification. The case reports faster response, higher agent productivity and stronger credibility but no quantified attributable outcome, baseline, period or formula.

Vendor-hosted named case: Yakult India used an information/support chatbot, promotional flows and WhatsApp surveys. The page says a June 2024 survey reached 9,000+ users; stronger two-way communication, faster feedback and support improvement are qualitative. It provides no response count/rate, comparison, formula or downstream business outcome.

Vendor-hosted named agency case with co-founder testimonial: YDS used broadcasts, payment/reminder notifications, live chat, a 24/7 chatbot and retargeting. AiSensy reports 3x business growth/sales and 98% open rate, while the testimonial says 2-3x growth. The baseline is 20% email/SMS opens and 2-5% clicks. Revenue, message count, period and attribution are absent.

The URL remains in AiSensy's sitemap but currently returns a generic page titled 'Login' with no public case body, customer workflow or metric. It is inventoried but excluded from normalized cases because there is no usable public evidence.

The URL remains in AiSensy's sitemap but currently returns a generic page titled 'Login' with no public case body, customer workflow or metric. It is inventoried but excluded from normalized cases because there is no usable public evidence.