RIntelligence
BProof grade
6Metrics retained
2Evidence records
Ringg AIVendor

Reported outcomes

50 percent of callsL0 containmentThe measurement window was not disclosed. · Ringg AIBaseline: Prior automated containment was not disclosed. · Formula: The source reports the value directly but does not disclose underlying records, counting rules or calculation method.
35 percent of callsL1 qualification and transferThe measurement window was not disclosed. · Ringg AIBaseline: Prior qualification/transfer share was not disclosed. · Formula: The source reports the value directly but does not disclose underlying records, counting rules or calculation method.
90 secondsAverage handle timeThe averaging period was not disclosed. · Ringg AIBaseline: The before-state handle time was not disclosed; response time is a different measure. · Formula: The source reports the value directly but does not disclose underlying records, counting rules or calculation method.
30000 calls per monthMonthly call volumeCurrent monthly run rate reported in the 2026-06-01 case study · Ringg AIBaseline: Pre-deployment call volume was not disclosed. · Formula: The source reports the value directly but does not disclose underlying records, counting rules or calculation method.
2 minutesPre-deployment response timeBefore Ringg deployment · Ringg AIBaseline: This is itself the before-state; no earlier comparison was reported. · Formula: The source reports the value directly but does not disclose underlying records, counting rules or calculation method.
500 calls per dayPre-deployment human call capacityBefore Ringg deployment · Ringg AIBaseline: This is the stated before-state; staffing inputs were not disclosed. · Formula: The source reports the value directly but does not disclose underlying records, counting rules or calculation method.

Context and boundaries

Workflowcustomer_support_and_service–orders_inventory_and_marketplacesRingg describes Hindi/English pharmacy support grounded in medicine and order APIs, with deterministic sensitive-flow controls and contextual transfer to humans through Knowlarity.
Implementation?The case mixes pre-deployment context and a current monthly run rate without an overall deployment or common outcome window.
CaveatsThe case is vendor-hosted; no PlatinumRx-owned source was retained.–The published percentages do not explain the remaining 15% of calls or define denominator/exclusion rules.vendor_owned

Source trail

  1. Customer Case Studies | Ringg AI

    The current official case-study hub enumerates six dedicated customer stories: Ekart, PlatinumRx, Practo, PolicyBazaar, smallcase and PharmEasy.

    company · accessed 2026-07-13
  2. PlatinumRx Case Study | Ringg AI

    Ringg reports that PlatinumRx handles more than 30,000 Hindi/English calls per month with API retrieval of medicine and order data, deterministic controls for sensitive flows and contextual human transfers through Knowlarity. Reported outcomes are 50% L0 containment, 35% L1 qualification/transfer and 90-second average handle time; before deployment response time exceeded two minutes and human capacity was about 500 calls per day.

    company · accessed 2026-07-13
← Back to customer atlas