Tabbly

The current homepage markets no-code voice agents for inbound, outbound and website use, 50+ languages/countries, local numbers, unlimited concurrency, bulk calls, live custom APIs, n8n/Make/Zapier workflows, recordings, transcription, sentiment, AI scoring and scheduling/data operations. It displays six named-person testimonials but no employer names. Current pricing statements conflict: the hero says within $0.03/minute, plan cards say $0.05 pay-as-you-go and $0.04 for committed enterprise volume, while the FAQ says $0.08; signup advertises $10 credits.

Tabbly says it was launched in 2025 by founders Manav Kulshrestha and Anushka Mishra. It positions the product for sales, lead follow-up, support and interviews, with Indian numbers, 50+ languages, multi-country telecom, call tracking, automated workflows and analytics.

The official LinkedIn page describes Tabbly as a partnership founded in 2021, headquartered in Bangalore, with a displayed company-size band of 2-10 employees. It shows Manav Kulshrestha, Shreyas Munge and Anushka Mishra as associated profiles; associated profiles are not audited headcount.

The live terms identify HypeSky Media and describe a different Tabbly product that transfers Facebook Lead Ads data to Google Sheets. They do not describe the current voice-agent service, creating a material operator/product-identity conflict.

The live privacy policy is dated 2023 and describes a HypeSky Media application connecting Facebook Lead Ads with Google Sheets. It does not specify current voice-call recording, transcription, model-provider, retention, residency or deletion practices.

The live page says subscriptions activate immediately, may be cancelled, and are non-refundable, but repeatedly describes unspecified writing tools rather than voice agents. It excludes third-party provider, API, model, infrastructure, telecom and customer-integration issues from refund eligibility.

The contact page uses Manav Kulshrestha's HypeSky Media email, an Indian mobile number, an Ahmedabad operating address for HypeSky Media and a separate Ahmedabad registered address. It conflicts with LinkedIn's Bangalore headquarters and does not identify a current incorporated Tabbly Labs entity.

The current API documentation supports programmatic creation and management of agents, phone-number purchase, outbound campaigns, contacts, inbound calling, call logs and webhooks through JSON HTTP endpoints authenticated with an organization ID and API key.

The API creates an active outbound campaign tied to an agent, with start/end schedules, time zone and greeting. It supports India Standard Time and documents direct campaign creation rather than a recommendation-only workflow.

The API adds one or many phone contacts to a campaign, optionally with per-contact greeting, instruction, identifier and SIP trunk. Added contacts are dialed; the documentation recommends a maximum batch size of 500.

The campaign API can update schedules and switch campaigns between active and paused status, demonstrating operator-controlled lifecycle state.

Completed-call logs expose transcript, summary, recording, sentiment, structured output, status, duration, cost, telco price and inbound/outbound direction with filters and pagination. Incomplete answered calls are excluded from this endpoint.

Post-call webhooks send answered or unanswered status plus transcript, summary, sentiment, QA pairs, recording, cost and output status. The page explicitly says failed webhook delivery is not retried, which is an execution reliability boundary.

The API creates an organization-owned phone voice agent with a greeting, speech-to-text language, voice, optional phone and operator-authored prompt. It is configured execution, not evidence of unconstrained agent planning.

The API updates agent name, greeting, prompt, voice, phone, speech language and status, or deletes the agent. These are operator/developer administration actions.

The API searches up to 20 purchasable E.164 telephone numbers across 33 documented countries, including India.

The API purchases a number for the organization. For +91 numbers it attempts automatic SIP-trunk activation; activation may fail after the number is purchased and then requires dashboard configuration.

The API enables inbound calls for an agent on its purchased telephone number.

The separate TTS product markets 14 languages, 100+ voices, SSML, MP3 output, streaming REST access and a 99.9% enterprise SLA. Its pricing is internally inconsistent: $0.009/minute, $15 per million characters for enterprise, $20 per million pay-as-you-go and an India display of INR1.2 per thousand characters all appear.

The current TTS documentation exposes an authenticated POST streaming endpoint returning 48kHz mono 16-bit LINEAR16 PCM/WAV audio. Rate limits are undisclosed and higher limits require support contact.

Tabbly founder Anushka Mishra demonstrates ecommerce COD confirmation at scale: the voice agent confirms a jewelry order, delivery address, INR3,000 COD amount and delivery availability, then the post says customer responses can be fed back to merchant systems through APIs. Emerald Jules is treated as a demonstration label, not a verified customer.

The retail guide markets Shopify/WooCommerce/POS sync, inventory lookup/reservation, SMS, payment, order status, returns/exchanges, promotions and loyalty. It also publishes four anonymous Tabbly-attributed result records: a UK fashion chain, Toronto boutique, US ecommerce store and Canadian cafe. These are marketing claims without named organizations or measurement methods. The page's $0.18/minute price conflicts with current homepage pricing.

The guide markets ecommerce order tracking, returns, COD confirmation, cart recovery, payment/order APIs, human handoff and Hindi/Hinglish use. It describes Starter, Growth and Enterprise minute bands but does not reconcile those blog packages with the live homepage's pay-per-minute cards.

Tabbly markets Indian accents and languages, ecommerce order tracking, returns and product inquiries, plus configured CRM, payment and custom-API integrations and hybrid AI-human operations. The page is product marketing, not implementation documentation.

The guide claims APIs and iOS, Android and JavaScript SDKs for web, mobile and customer-service integrations. A live REST API is separately documented, but no retained public SDK reference establishes current SDK completeness, so SDK claims remain partial.

The page markets 50+ languages, major Indian languages, Hinglish/Tanglish/Kanglish code-mixing, real-time switching and intent recognition. No public language benchmark, word-error rate or per-language production status is disclosed.

The 20-page live blog archive exposed 230 distinct post slugs at access time and labels its content as how-to guides, case studies and articles. The archive and all pages containing explicit Tabbly-attributed deployments, testimonials or result blocks were inventoried; generic industry examples and competitor claims were excluded from normalized cases.

The page reports five anonymous India deployments explicitly using Tabbly: Delhi ecommerce number provisioning, Mumbai insurance calling, Bengaluru fintech collections, Hyderabad rural insurance and Pune edtech scaling. It also claims connectors/compliance controls not present in the retained API docs, so those product statements remain marketing evidence only.

The article explicitly says an anonymous regional mortgage company with 15 loan officers implemented Tabbly for lead response and qualification, reporting results after 90 days. Two additional mortgage examples do not explicitly attribute their deployment to Tabbly and are excluded from the normalized Tabbly case universe.

The page provides three anonymous case blocks with explicit Tabbly implementations: a Mumbai luxury developer, Pune affordable-housing project and pan-Maharashtra aggregator. It also markets 24-hour implementation, CRM/calendar/property-system connections and contextual human routing, but named integration documentation is absent.

The page explicitly attributes one anonymous competitive-exam platform's implementation to the Tabbly Hindi TTS API and publishes four metrics. Two other education examples do not name Tabbly and are excluded from the normalized Tabbly case universe.

The guide markets Tabbly integrations with Salesforce, HubSpot and Zendesk and describes read/write actions such as lead/deal/ticket creation, status updates, call logging, follow-ups and escalation. It also contains generic examples that do not explicitly say Tabbly and therefore are not normalized as Tabbly cases. No official marketplace listing was found for the claimed native HubSpot integration.

The page publishes an anonymous aggregate for organizations using Tabbly: contact rates, outbound-cost reduction, conversion improvement, compliance and outreach capacity. It also promises white-glove project management, compliance guidance, script development and ongoing optimization; these are managed services, not autonomous product actions.

An explicit anonymous Tabbly case says a 50-employee SaaS company replaced tier-one work from a three-person support team with one senior specialist, reducing annual support cost from $180,000 to $55,000 and describing the reduction as 70%. Other industry examples on the page do not explicitly name Tabbly and are excluded.

The guide explicitly attributes anonymous Tabbly deployments for retail WISMO, dental scheduling, UK gym bookings and clinic support. It reports call volume, savings, no-show, time-saved and wait-time claims without organizations, methodology or customer-owned corroboration.

The page explicitly attributes a 15-location restaurant deployment and a financial-services analytics deployment to Tabbly. Other healthcare and software examples are not explicitly Tabbly-attributed and are excluded. The page also reports blind testing with 200+ customers, but does not disclose protocol or sample ownership.

The pricing article reports anonymous customer aggregates for missed calls, lead response, support savings, AOV and break-even, and one anonymous real-estate agency committed-plan result. Its $0.08/minute entry price conflicts with the live homepage's $0.03, $0.04, $0.05 and $0.08 statements.

The article says 'we deployed Tabbly' for anonymous insurance claims and retail orders and separately claims 200+ deployments, 500-user surveys, a 4.9/5 rating, 60% workload reduction and 35% engagement lift. Customers, denominators and measurement methods are not named.

The page labels an anonymous logistics record as a case study and says Tabbly supplied shipment updates, delay alerts and ETA responses before escalating exceptions. It reports reduced escalation and increased satisfaction without methodology or customer identity.

The page explicitly says an anonymous European staffing firm used Tabbly for multilingual technology hiring and reports faster screening and more diverse candidates. Broader benchmark ranges on the page are not normalized as that customer's results.

The page says an anonymous major lending institution implemented Tabbly voice agents and reports faster recovery, higher debtor response and fewer delinquent-account rollovers. Claims that Tabbly personalizes repayment options are blog marketing; no current payment-plan write API or underwriting action is documented.

The page says an anonymous mid-sized agency using Tabbly reduced its complaint backlog while the system handled routine issues and escalated legal threats to humans. It explicitly frames complex and emotional cases as human responsibilities.