IVRy

Name: IVRy
Brand: IVRy

株式会社IVRyは「最高の技術をすべての人と企業に届ける」をミッションに、対話型音声AI SaaS「IVRy」を開発・運営している会社です。

Est 2019|Valuation $170.6M|Raised $58M

LinkedIn 900|Website|Web traffic 872K|FTEs 25|HQ Minato-Ku, Tokyo Metropolis, JP

MarketsInteractive Voice Response (IVR)

Published Oct 8, 2026

01Common complaints

If you require a full enterprise omnichannel contact center suite
- Alternatives such as Genesys Cloud CX may be more appropriate when you need mature omnichannel routing, workforce engagement management, and governance across a large agent base.
If you need maximum platform composability and already have AWS expertise
- Amazon Connect may be more appropriate for teams that prefer to build highly tailored experiences and integrate deeply into AWS-native data pipelines.
If your security policy requires SOC 2 Type II or specific ISO certifications not publicly documented
- Vendor materials emphasize ISO/IEC 27001 and some enterprise controls, but do not publicly document SOC 2 Type II or ISO 27017/27018 in the retrieved sources.
If predictable, flat-rate billing is a strict requirement
- Variable telephony usage costs and usage-based AI dialogue charging can make costs less predictable; organizations needing flat-rate cost models should model high-usage scenarios.
Current limitations acknowledged by the vendor or evident in this run
- The retrieved sources do not include a vendor-published limitations list; procurement teams should request an up-to-date product limitations and roadmap document.
Features on the roadmap (not yet available)
- Roadmap details were not reliably identified in the captured materials; request the current roadmap from the vendor.
Scale limitations
- No public documentation of hard scale limits was identified; enterprise prospects should request references and performance data for comparable call volumes.
Security or compliance gaps
- SOC 2 and ISO 27017/27018 are not publicly documented in the retrieved sources.
- Data residency and explicit hosting-region documentation were not found in the surfaced pages.
API limitations or integration constraints
- Not evidenced in the retrieved sources; request API documentation and integration references when evaluating.

- If you require a full enterprise omnichannel contact center suite - Alternatives such as Genesys Cloud CX may be more appropriate when you need mature omnichannel routing, workforce engagement management, and governance across a large agent base. - If you need maximum platform composability and already have AWS expertise - Amazon Connect may be more appropriate for teams that prefer to build highly tailored experiences and integrate deeply into AWS-native data pipelines. - If your security policy requires SOC 2 Type II or specific ISO certifications not publicly documented - Vendor materials emphasize ISO/IEC 27001 and some enterprise controls, but do not publicly document SOC 2 Type II or ISO 27017/27018 in the retrieved sources. - If predictable, flat-rate billing is a strict requirement - Variable telephony usage costs and usage-based AI dialogue charging can make costs less predictable; organizations needing flat-rate cost models should model high-usage scenarios. - Current limitations acknowledged by the vendor or evident in this run - The retrieved sources do not include a vendor-published limitations list; procurement teams should request an up-to-date product limitations and roadmap document. - Features on the roadmap (not yet available) - Roadmap details were not reliably identified in the captured materials; request the current roadmap from the vendor. - Scale limitations - No public documentation of hard scale limits was identified; enterprise prospects should request references and performance data for comparable call volumes. - Security or compliance gaps - SOC 2 and ISO 27017/27018 are not publicly documented in the retrieved sources. - Data residency and explicit hosting-region documentation were not found in the surfaced pages. - API limitations or integration constraints - Not evidenced in the retrieved sources; request API documentation and integration references when evaluating.

Deal disqualifiers: what makes a POOR fit

Requirements for global, multi-language omnichannel deployments
Needs for very deep customization that exceed packaged workflows
Security gates that require a specific publicly documented security certification or explicit regional hosting guarantees that the vendor has not publicly documented

02Why they buy

Product differentiators supported by available evidence
- Vendor messaging indicates short onboarding and low initial subscription costs for starter tiers, including a free allowance for a limited number of calls.
- Enterprise security controls are described in vendor materials (role-based access, audit logs, IP restrictions, MFA, and PII masking in transcripts).
- Japan-market focus and domestic customer logos/case examples are prominent in vendor materials.
Claims needing careful validation
- Vendor statements about market leadership or ranking should be validated by reviewing survey methodology and category definitions before relying on them for procurement decisions.

- Product differentiators supported by available evidence - Vendor messaging indicates short onboarding and low initial subscription costs for starter tiers, including a free allowance for a limited number of calls. - Enterprise security controls are described in vendor materials (role-based access, audit logs, IP restrictions, MFA, and PII masking in transcripts). - Japan-market focus and domestic customer logos/case examples are prominent in vendor materials. - Claims needing careful validation - Vendor statements about market leadership or ranking should be validated by reviewing survey methodology and category definitions before relying on them for procurement decisions.

03Field reports

Note on name collisions: "IVRy" also matches unrelated products/terms online (e.g., "iVRy" VR headset streaming app). This report focuses on ivry.jp (Japanese phone/voice AI SaaS). Some review results for "iVRy" were excluded from product sentiment because they refer to a different product.

Review platforms (accessible in this research)

ITreview
- The product listing shows a generally positive overall rating with a small number of reviews for 「アイブリー」. Example positive sentiment on the page includes recommendations from some reviewers.
- Limitation: deeper extraction of individual low-rating reviews was not performed in this run; additional review sampling would be needed for a balanced quantitative view.
TrustRadius
- The surfaced page provided a pricing catalog entry but did not return authentic user-review quotes in the captured excerpts for IVRy; it was therefore not used as substantive review evidence in this run.
Gartner Peer Insights
- Searches did not surface an IVRy-specific listing in the accessible results; Gartner Peer Insights often requires access and is category-driven.

- ITreview - The product listing shows a generally positive overall rating with a small number of reviews for 「アイブリー」. Example positive sentiment on the page includes recommendations from some reviewers. - Limitation: deeper extraction of individual low-rating reviews was not performed in this run; additional review sampling would be needed for a balanced quantitative view. - TrustRadius - The surfaced page provided a pricing catalog entry but did not return authentic user-review quotes in the captured excerpts for IVRy; it was therefore not used as substantive review evidence in this run. - Gartner Peer Insights - Searches did not surface an IVRy-specific listing in the accessible results; Gartner Peer Insights often requires access and is category-driven.

Community / social sentiment

English-language community searches are confounded by the name collision with an unrelated VR app. Vendor social channels post growth metrics but are not independent customer reviews.

Vendor / partner case studies (not independent reviews)

A vendor press release about an Autobacs franchise partner attributes measurable outcomes after IVRy introduction (automation of a share of peak-season phone responses, an improvement in answer rates, increased app reservations, and reported staff experience improvements). These are vendor-published claims and should be treated as such unless independently validated.
A third-party vendor partner blog narrates a successful implementation but provides limited quantitative metrics in the captured excerpt; it serves as a qualitative adoption signal rather than independent ROI verification.

- A vendor press release about an Autobacs franchise partner attributes measurable outcomes after IVRy introduction (automation of a share of peak-season phone responses, an improvement in answer rates, increased app reservations, and reported staff experience improvements). These are vendor-published claims and should be treated as such unless independently validated. - A third-party vendor partner blog narrates a successful implementation but provides limited quantitative metrics in the captured excerpt; it serves as a qualitative adoption signal rather than independent ROI verification.

Autobacs franchise partner (株式会社アイエー)

Reported outcomes (vendor press release)
- Automation of a substantial portion of peak-period phone responses
- Answer rate improved substantially
- Mobile app reservations reportedly increased several-fold
Critical evaluation
- The source is vendor-distributed press material; methodology, baseline definitions, time windows, and attribution (what operational changes accompanied the IVRy deployment) are not disclosed in the captured excerpts. Use these figures as directional outcomes rather than independently validated ROI.

- Reported outcomes (vendor press release) - Automation of a substantial portion of peak-period phone responses - Answer rate improved substantially - Mobile app reservations reportedly increased several-fold - Critical evaluation - The source is vendor-distributed press material; methodology, baseline definitions, time windows, and attribution (what operational changes accompanied the IVRy deployment) are not disclosed in the captured excerpts. Use these figures as directional outcomes rather than independently validated ROI.

Chibagin Computer Service (ちばぎんコンピューターサービス) blog

The partner blog reports a successful migration to IVRy and describes operational outcomes in narrative form without quantified metrics in the captured excerpt; treat as qualitative adoption evidence.

Google Cloud ecosystem case compilation (Gemini migration)

A case compilation indicates IVRy migrated operational infrastructure to a model referred to as Gemini to improve recognition accuracy and response speed and introduced multi-turn dialogue features.
Critical evaluation
- This is an ecosystem/partner case narrative that provides technical directionality but does not constitute an independent business ROI audit. It is relevant for technical due diligence on model and infrastructure choices and potential vendor ecosystem dependencies.

- A case compilation indicates IVRy migrated operational infrastructure to a model referred to as Gemini to improve recognition accuracy and response speed and introduced multi-turn dialogue features. - Critical evaluation - This is an ecosystem/partner case narrative that provides technical directionality but does not constitute an independent business ROI audit. It is relevant for technical due diligence on model and infrastructure choices and potential vendor ecosystem dependencies.

04Best fit

Company sizes

Best-fit profiles are likely:
- Small to mid-market organizations where inbound calls materially impact frontline operations
- Multi-location businesses (retail and service chains) where standardizing phone handling across sites is useful
- Enterprise and public sector use is plausible based on vendor messaging and case examples, but should be validated through security reviews, integration capability checks, and SLA confirmation

Industries and verticals where adoption is strongest (with customer examples)

Retail/service chains (autobacs franchise partner example)
Financial services, public sector, and facilities services are visible in vendor case lists, but detailed case pages were not opened in this research run

Roles and personas

Operations and administration leaders responsible for phone handling
Customer support and call center managers
IT and digital transformation leaders in Japan focused on operational automation

Pain points and challenges the product addresses

Missed calls and low answer rates during peak periods
High time cost of repetitive inquiries and call routing
Staffing constraints and operational consistency across locations

Qualification criteria: what makes a GOOD fit

High volume of repetitive inbound inquiries that can be standardized
Desire for incremental automation and rapid initial deployment
Japan-based operations requiring Japanese-language voice recognition and dialogue

05The pitch

What the product does (core value proposition in objective terms)

IVRy (brand/service name commonly shown as 「アイブリー」) is a Japanese cloud service for automating and standardizing inbound phone handling using IVR and conversational/voice AI, together with call logging, analysis, and related workflow automation. Vendor product site.
Typical vendor-described use cases include reducing time spent answering calls, handling routine inquiries outside business hours, routing calls, transcribing and summarizing conversations, and providing metrics via analytics dashboards.

- IVRy (brand/service name commonly shown as 「アイブリー」) is a Japanese cloud service for automating and standardizing inbound phone handling using IVR and conversational/voice AI, together with call logging, analysis, and related workflow automation. Vendor product site. - Typical vendor-described use cases include reducing time spent answering calls, handling routine inquiries outside business hours, routing calls, transcribing and summarizing conversations, and providing metrics via analytics dashboards.

Target market and market positioning

Primary market appears to be Japan-based small and mid-sized organizations with meaningful inbound call volumes (stores, clinics, hospitality, local services), with vendor materials indicating expansion into larger enterprise and public-sector workflows. The vendor describes security and support offerings intended for enterprise customers.
Vendor materials emphasize short onboarding and low initial pricing (including a zero-cost entry point and a free allowance for a small number of calls) intended to reduce adoption friction.

- Primary market appears to be Japan-based small and mid-sized organizations with meaningful inbound call volumes (stores, clinics, hospitality, local services), with vendor materials indicating expansion into larger enterprise and public-sector workflows. The vendor describes security and support offerings intended for enterprise customers. - Vendor materials emphasize short onboarding and low initial pricing (including a zero-cost entry point and a free allowance for a small number of calls) intended to reduce adoption friction.

Get a comprehensive analysis of IVRy including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →