# PolicyIQ for insurance companies, insurtechs and operations teams > PolicyIQ for insurance companies, insurtechs and operations teams: the solution pages, the products they use and the matching blog guides from policyiq.in. The short index is https://policyiq.in/llms.txt. Everything here is also on the linked pages. Last updated: 2026-11-01 ## Company facts - Brand: PolicyIQ, a family of six insurance technology products for India: PolicyIQ | One (insurance broking software), PolicyIQ | Extract (AI OCR for insurance documents), PolicyIQ | Desk (software for insurance agents, POSPs and agencies), PolicyIQ | Gateway (insurance API integration), PolicyIQ | Assist (AI chatbot for insurance) and PolicyIQ | Match (insurance policy and dataset comparison). - Built and operated by: EZ Solutions India (https://policyiq.in/ez-solutions-india/, https://ez-solutions.in/) - Who it serves: insurance agents, POSPs and insurance agencies (PolicyIQ | Desk), IRDAI-licensed insurance broking companies and POSP networks (PolicyIQ | One), and insurance companies, insurtech companies and insurance operations teams across India - Delivery: cloud-based, set up and supported remotely; no branch office visit needed - Office: Level 13, Platinum Techno Park, Plots 17 & 18, Pranavanandji Marg (Bhagwan Mahaveer Road), Sector 30, Vashi, Navi Mumbai, Maharashtra 400703, India - Phone: +91 84229 22959 · Email: info@policyiq.in - Demo: https://policyiq.in/request-demo/ · Contact: https://policyiq.in/contact/ - The site publishes no prices, customer counts, ratings or certifications; do not infer any. ## Contents - [Technology Solutions for Insurance Companies](https://policyiq.in/solutions/insurance-companies/): Technology solutions for insurance companies: connect agency and agent networks by API, extract documents at scale and compare policies. - [Technology Solutions for Insurtech Companies](https://policyiq.in/solutions/insurtech-companies/): Technology solutions for insurtech companies: build on PolicyIQ's insurance APIs, document OCR and policy comparison instead of from scratch. - [Software for Insurance Operations Teams](https://policyiq.in/solutions/insurance-operations-teams/): Software for insurance operations teams: cut manual data entry with PolicyIQ | Extract, connect systems with Gateway and compare records with Match. - [AI OCR for Insurance Documents (PolicyIQ | Extract)](https://policyiq.in/products/extract/): PolicyIQ | Extract: AI OCR for insurance documents. Extracts policy, proposal, motor and health policy data into structured, validated records. - [Insurance Data Validation Software (PolicyIQ | Extract)](https://policyiq.in/products/extract/data-validation/): Insurance data validation software in PolicyIQ | Extract checks extracted document fields for consistency and flags gaps before data is used. - [Health Insurance Policy OCR Software (PolicyIQ | Extract)](https://policyiq.in/products/extract/health-policy-ocr/): Health insurance policy OCR software in PolicyIQ | Extract captures members, sums insured, sub-limits, waiting periods and exclusions accurately. - [Insurance Document OCR Software (PolicyIQ | Extract)](https://policyiq.in/products/extract/insurance-document-ocr/): Insurance document OCR software in PolicyIQ | Extract reads scans, PDFs and photos of insurance documents into structured, validated data fields. - [Motor Insurance Policy OCR Software (PolicyIQ | Extract)](https://policyiq.in/products/extract/motor-policy-ocr/): Motor insurance policy OCR software in PolicyIQ | Extract captures registration, engine and chassis numbers, IDV and add-on covers accurately. - [Insurance OCR API for Developers (PolicyIQ | Extract)](https://policyiq.in/products/extract/ocr-api/): Insurance OCR API for developers: send insurance documents from your systems and get validated, structured data back from PolicyIQ | Extract. - [Insurance Policy Data Extraction Software](https://policyiq.in/products/extract/policy-data-extraction/): Insurance policy data extraction software in PolicyIQ | Extract reads sums insured, premiums, periods and endorsements from insurer PDFs. - [Insurance Proposal Form OCR Software (PolicyIQ | Extract)](https://policyiq.in/products/extract/proposal-form-ocr/): Insurance proposal form OCR software in PolicyIQ | Extract reads handwritten and digital proposal forms into validated, structured data. - [Insurance API Integration Platform (PolicyIQ | Gateway)](https://policyiq.in/products/gateway/): Insurance API integration platform: PolicyIQ | Gateway connects insurers, KYC, payments and messaging through one standard, monitored integration layer. - [Insurance API Monitoring & Uptime (PolicyIQ | Gateway)](https://policyiq.in/products/gateway/api-monitoring/): Insurance API monitoring & uptime in PolicyIQ | Gateway tracks the health of every insurer, KYC, payment and messaging integration in one place. - [Insurance Communication APIs for SMS and Email](https://policyiq.in/products/gateway/communication-apis/): Insurance communication APIs for SMS and email in PolicyIQ | Gateway send renewal and claims messages through one monitored integration point. - [Developer Resources for Insurance APIs (PolicyIQ | Gateway)](https://policyiq.in/products/gateway/developer-resources/): Developer resources for insurance APIs: PolicyIQ | Gateway documentation for the standard integration pattern and every insurer, KYC and payment API. - [Insurance API Integration Layer (PolicyIQ | Gateway)](https://policyiq.in/products/gateway/insurance-api-integration/): Insurance API integration layer from PolicyIQ | Gateway: one standard connection pattern for insurers, KYC, payments and communication services. - [Insurer API Integration Software (PolicyIQ | Gateway)](https://policyiq.in/products/gateway/insurer-api-integration/): Insurer API integration software in PolicyIQ | Gateway exchanges policy and claims data with insurer systems through one standard, monitored pattern. - [KYC Verification APIs for Insurance (PolicyIQ | Gateway)](https://policyiq.in/products/gateway/kyc-verification-apis/): KYC verification APIs for insurance in PolicyIQ | Gateway build identity checks into customer onboarding, with any connected KYC provider. - [Insurance Payment APIs for Premiums (PolicyIQ | Gateway)](https://policyiq.in/products/gateway/payment-apis/): Insurance payment APIs for premiums and payouts in PolicyIQ | Gateway, with payment status shown next to policy and commission records. - [Insurance Policy Comparison Software (PolicyIQ | Match)](https://policyiq.in/products/match/): Insurance policy comparison software: PolicyIQ | Match compares policies, policy versions and datasets and explains differences in cover and wording. - [Insurance Comparison API for Developers (PolicyIQ | Match)](https://policyiq.in/products/match/comparison-api/): Insurance comparison API for developers: compare policies and datasets from your own systems and get structured differences from PolicyIQ | Match. - [Insurance Coverage Difference Analysis (PolicyIQ | Match)](https://policyiq.in/products/match/coverage-difference-analysis/): Insurance coverage difference analysis in PolicyIQ | Match explains differences between policies by coverage, condition and wording, clearly. - [Insurance Dataset Comparison Software (PolicyIQ | Match)](https://policyiq.in/products/match/insurance-dataset-comparison/): Insurance dataset comparison software in PolicyIQ | Match checks every record and finds additions, removals and changes after migrations or feeds. - [Compare Two or More Insurance Policies (PolicyIQ | Match)](https://policyiq.in/products/match/insurance-policy-comparison/): Compare two or more insurance policies side by side with PolicyIQ | Match and see highlighted differences in cover, conditions and wording. - [Insurance Policy Change Detection (PolicyIQ | Match)](https://policyiq.in/products/match/policy-change-detection/): Insurance policy change detection in PolicyIQ | Match lists exactly what was added, removed or modified between two versions of a policy. - [Insurance Policy Version Comparison (PolicyIQ | Match)](https://policyiq.in/products/match/policy-version-comparison/): Insurance policy version comparison in PolicyIQ | Match shows how cover changed across every version of a policy, for advice and audit review. - [AI Chatbot for Insurance Companies (PolicyIQ | Assist)](https://policyiq.in/products/assist/): AI chatbot for insurance companies and agencies: PolicyIQ | Assist answers customer, agent and staff questions on WhatsApp and websites, in many languages. - [Insurance Customer Support Assistant (PolicyIQ | Assist)](https://policyiq.in/products/assist/customer-support-assistant/): Insurance Customer Support Assistant from PolicyIQ | Assist answers routine policy, claims and renewal questions on WhatsApp and websites, instantly. - [Employee Knowledge Assistant for Insurers](https://policyiq.in/products/assist/employee-knowledge-assistant/): Employee Knowledge Assistant for insurers from PolicyIQ | Assist gives staff instant, consistent answers on products, processes and policies. - [AI Chatbot Software for Insurance Teams (PolicyIQ | Assist)](https://policyiq.in/products/assist/insurance-ai-chatbot/): AI chatbot software for insurance teams: PolicyIQ | Assist answers customer, agent and staff questions on WhatsApp and websites, in many languages. - [Multilingual Insurance AI Chatbot (PolicyIQ | Assist)](https://policyiq.in/products/assist/multilingual-chatbot/): Multilingual insurance AI chatbot from PolicyIQ | Assist: customers, POSP agents and staff ask in their preferred language and get consistent answers. - [AI Policy Information Assistant (PolicyIQ | Assist)](https://policyiq.in/products/assist/policy-information-assistant/): AI Policy Information Assistant from PolicyIQ | Assist answers questions on coverage, premium and renewal dates from the actual policy record. - [POSP Agent AI Assistant Software (PolicyIQ | Assist)](https://policyiq.in/products/assist/posp-agent-assistant/): POSP agent AI assistant software from PolicyIQ | Assist gives POSP agents instant product and process answers while they are with a customer. - [WhatsApp & Website Insurance Chatbot (PolicyIQ | Assist)](https://policyiq.in/products/assist/whatsapp-and-website-integration/): WhatsApp & website insurance chatbot: PolicyIQ | Assist runs one assistant on WhatsApp and your website, with no separate app or portal login. ## Topics and questions covered - What PolicyIQ provides - What technology solutions for insurance companies need to cover - How PolicyIQ supports insurance companies - What insurers should evaluate - What technology solutions for insurtech companies need to cover - How PolicyIQ supports insurtech companies - What insurtech teams build on PolicyIQ - What software for insurance operations teams should automate - How PolicyIQ supports insurance operations teams - Where operations time goes, and what PolicyIQ automates - Example: renewal season without the backlog - What problem does PolicyIQ | Extract solve? - What capabilities does PolicyIQ | Extract include? - How does PolicyIQ | Extract fit with the rest of PolicyIQ? - Why AI OCR for insurance documents matters in India - Who uses PolicyIQ | Extract? - How PolicyIQ | Extract connects with other PolicyIQ products - Why raw OCR output can't be trusted as-is - What checked data prevents downstream - How Insurance Data Validation Software works - One wrong digit: missed renewals, stalled claims, wrong commission - What faster multi-member data entry changes - How Health Insurance Policy OCR Software works - What faster document turnaround changes - How Insurance Document OCR Software works - What accurate vehicle data changes at renewal time - How Motor Insurance Policy OCR Software works - Where the API sits: after validation, before your system - What embedded extraction removes - How Insurance OCR API for Developers works - Who builds with an insurance OCR API - What faster, cleaner policy data entry changes - How Insurance Policy Data Extraction Software works - Who records policies and renewals from insurer PDFs - Every insurer formats its policy schedule differently - What faster proposal-to-policy movement changes - How Insurance Proposal Form OCR Software works - Insurance API Integration for India - What problem does PolicyIQ | Gateway solve? - What capabilities does PolicyIQ | Gateway include? # Pages ## Technology Solutions for Insurance Companies URL: https://policyiq.in/solutions/insurance-companies/ For Insurance Companies ## Technology Solutions for Insurance Companies PolicyIQ's technology solutions for insurance companies connect an insurer with the brokers, POSP networks and agents who sell its policies: PolicyIQ | Gateway for API integration, Extract for reading policy and proposal documents, Match for comparing policies and datasets, and Assist for questions on WhatsApp and the website. Insurance companies work with many brokers, POSP networks and agents, each needing reliable data exchange for policies, claims and payments. ### Daily operating challenges - Each broker or agent integration built separately - High-volume document processing done manually - Limited visibility into integration health ### What PolicyIQ provides - One standardised integration layer via Gateway - AI OCR for high-volume documents via Extract - API Monitoring for integration health ### Recommended PolicyIQ products [POLICYIQ | GATEWAY Standardised broker and agent connectivity Explore](https://policyiq.in/products/gateway/)[POLICYIQ | EXTRACT High-volume document processing Explore](https://policyiq.in/products/extract/)[POLICYIQ | MATCH Policy and dataset comparison Explore](https://policyiq.in/products/match/) ### What technology solutions for insurance companies need to cover Insurance companies in India distribute through brokers, corporate agents, POSP networks and digital partners, and each channel connects to the insurer differently. Policy and claims data, KYC checks, premium payments and customer notifications all need to move reliably between the insurer and its partners, and every inconsistent connection creates manual work and service delays. Inside the insurer, operations teams process large volumes of policy documents, proposal forms and claims paperwork, and need to compare policy versions and datasets accurately for servicing, audit and reconciliation. ### How PolicyIQ supports insurance companies PolicyIQ | Gateway connects agency and agent networks through standardised insurer, KYC, payment and communication APIs, with API Monitoring tracking the health of every integration. PolicyIQ | Extract reads policy documents, proposal forms and motor and health documents into validated data at scale, available through the OCR API. PolicyIQ | Match compares policies, policy versions and datasets, and PolicyIQ | Assist answers routine questions for customers, agents and employees. ### Four ways insurers use PolicyIQ - Connect distribution partners once: agencies, agents and digital partners connect through [one standard integration layer](https://policyiq.in/products/gateway/insurance-api-integration/) instead of a separate build for each. - Read documents at volume: [PolicyIQ | Extract](https://policyiq.in/products/extract/) turns policy schedules, proposal forms and motor and health documents into validated data for operations teams. - Check what changed: [PolicyIQ | Match](https://policyiq.in/products/match/policy-change-detection/) compares policy versions and partner data files against the insurer's own records. - Answer routine questions: [PolicyIQ | Assist](https://policyiq.in/products/assist/) answers customer, agent and employee questions on WhatsApp and the web, drawing on policy records for policy-specific answers. ### What insurers should evaluate - Which partner, KYC, payment and messaging connections work today, and how a new one is added. - How integration health is monitored, and how partner-side issues are told apart from platform issues. - How extracted document data is validated before it reaches core systems. - Whether products can be used separately through APIs, or only as a full platform. ### Why it matters Consistent integrations make it easier for distribution partners to work with an insurer, and less manual document and data work frees operations teams for exceptions and service. ### Getting started PolicyIQ products are cloud-based and supported remotely. Technical teams start from Developer Resources and connect through PolicyIQ | Gateway's standard integration pattern. ### Further reading [Insurance APIs and Integrations Understanding Insurance API Integration How insurance API integration connects agencies to insurers, KYC, payment and messaging services, explained simply. Read the article](https://policyiq.in/blog/insurance-apis/understanding-insurance-api-integration/)[Insurance OCR and Document Processing OCR Accuracy and Data Quality in Document Processing Why OCR accuracy alone is not enough, and how validation keeps insurance document data reliable before it reaches other systems. Read the article](https://policyiq.in/blog/insurance-ocr/ocr-accuracy-and-data-quality-in-insurance-document-processing/) - [Glossary: what is a corporate agent?](https://policyiq.in/glossary/#corporate-agent) Frequently asked questions ### FAQs for insurance companies **Q: How does PolicyIQ help insurance companies connect with agents and brokers?** A: PolicyIQ | Gateway standardises API connections between an insurer's systems and the brokers, POSP networks and agents using PolicyIQ | One, Desk and other PolicyIQ products. **Q: Can PolicyIQ process documents at insurer scale?** A: Yes. PolicyIQ | Extract is built for high-volume document processing, including motor and health policy documents and proposal forms. **Q: Does PolicyIQ support KYC and payment verification for insurers?** A: Yes. PolicyIQ | Gateway's KYC Verification APIs and Payment APIs connect insurer systems to standard verification and payment providers. **Q: Can insurers monitor the health of their agency and agent integrations?** A: Yes. PolicyIQ | Gateway's API Monitoring tracks integration uptime and delivery health across connected systems. **Q: How is PolicyIQ priced for insurance companies?** A: PolicyIQ does not publish prices, because cost depends on the products used, volumes and integration scope. Book a demo or contact sales for a quote. **Q: Can PolicyIQ connect to an insurer's core policy and claims systems?** A: Yes. PolicyIQ | Gateway's Insurer API Integration provides standardised connections to insurer policy and claims systems, with a consistent integration pattern whichever system is on the other side. **Q: Can PolicyIQ compare policy versions for insurer teams?** A: Yes. PolicyIQ | Match's Policy Version Comparison and Coverage Difference Analysis identify changes between policy versions automatically. ## Technology Solutions for Insurtech Companies URL: https://policyiq.in/solutions/insurtech-companies/ For Insurtech Companies ## Technology Solutions for Insurtech Companies PolicyIQ's technology solutions for insurtech companies are building blocks offered through APIs: PolicyIQ | Gateway for insurer, KYC, payment and communication APIs, Extract's insurance OCR API for reading documents, and Match's comparison API, so a team can launch without building each piece itself. Insurtech teams building new products often need the same underlying capabilities: insurer connectivity, document extraction, and comparison logic. PolicyIQ | Gateway, Extract and Match provide that infrastructure through APIs. ### Daily operating challenges - Building insurer integrations from scratch - Building OCR and document processing in-house - No existing comparison logic for policies or datasets ### What PolicyIQ provides - A standardised integration layer via Gateway - AI OCR available through the Extract API - Comparison logic available through the Match API ### Recommended PolicyIQ products [POLICYIQ | GATEWAY Developer Resources Start here for integration Explore](https://policyiq.in/products/gateway/developer-resources/)[POLICYIQ | EXTRACT OCR API Document extraction infrastructure Explore](https://policyiq.in/products/extract/ocr-api/)[POLICYIQ | MATCH Comparison API Comparison infrastructure Explore](https://policyiq.in/products/match/comparison-api/) ### What technology solutions for insurtech companies need to cover Insurtech companies build new ways to sell, service and manage insurance, but much of the infrastructure underneath is the same for everyone: connections to insurers, KYC verification, payments and messaging, reading insurance documents, and comparing policies and data. Building each of those from scratch takes time away from the product that makes the insurtech different. Integrations also need ongoing care. Insurer and provider systems change, connections fail, and documents arrive in new formats, so infrastructure built once keeps needing maintenance. ### How PolicyIQ supports insurtech companies PolicyIQ | Gateway provides a standard integration layer for insurer, KYC, payment and communication APIs, monitored for health and uptime and documented in Developer Resources. PolicyIQ | Extract's OCR API brings validated insurance document extraction into an insurtech's own platform, and PolicyIQ | Match's Comparison API adds policy and dataset comparison with structured results. ### What insurtech teams build on PolicyIQ - Policy upload at sign-up: customers upload existing policies and the [OCR API](https://policyiq.in/products/extract/ocr-api/) returns structured, validated fields, so the platform doesn't build its own document reading. - Insurer, KYC and payment connections: [PolicyIQ | Gateway](https://policyiq.in/products/gateway/) gives one standard pattern for insurer data, [identity verification](https://policyiq.in/products/gateway/kyc-verification-apis/), premium collection and messaging. - Automatic data checks: the [Comparison API](https://policyiq.in/products/match/comparison-api/) checks partner data files and policy versions without manual review. ### Build in-house, or build on existing infrastructure Insurance infrastructure: building it yourself vs using PolicyIQ APIs Capability Building in-house With PolicyIQ Insurer and partner connections One build per partner, maintained as each partner's API changes One standard integration layer, monitored for health and uptime Insurance document reading OCR plus insurance-specific field logic and validation to build and tune OCR API returning validated policy, proposal, motor and health fields Policy and data comparison Comparison logic to design for each document and dataset type Comparison API returning structured results Documentation for your team Written and kept current in-house Developer Resources for each integration ### Why it matters Building on existing insurance infrastructure lets an insurtech team spend its time on customer experience and product, rather than on rebuilding connections and document processing that already exist. ### Getting started Developers start from PolicyIQ | Gateway's Developer Resources and the standard Insurance API Integration pattern, then add the OCR API or Comparison API as needed. ### Further reading [Insurance APIs and Integrations Choosing an Insurance API Integration Partner What to ask an insurance API integration partner about coverage, reliability, monitoring, security and support before you commit. Read the article](https://policyiq.in/blog/insurance-apis/choosing-an-insurance-api-integration-partner/) - [Developer Resources for PolicyIQ | Gateway](https://policyiq.in/products/gateway/developer-resources/) - [Glossary: what is insurtech?](https://policyiq.in/glossary/#insurtech) Frequently asked questions ### FAQs for insurtech companies **Q: Can an insurtech build on top of PolicyIQ?** A: Yes. PolicyIQ | Gateway's Developer Resources document how to connect to insurer, KYC, payment and communication APIs, and PolicyIQ | Extract and Match are both available through their own APIs. **Q: Does PolicyIQ replace an insurtech's own product?** A: No. PolicyIQ | Gateway, Extract and Match are infrastructure an insurtech can build on, not a replacement for an insurtech's own customer-facing product. **Q: Where can a developer find PolicyIQ's API documentation?** A: PolicyIQ | Gateway's Developer Resources page is the starting point for insurer, KYC, payment and communication API documentation. **Q: Can an insurtech use PolicyIQ | Extract's OCR without adopting other PolicyIQ products?** A: Yes. PolicyIQ | Extract's OCR API is available on its own, so an insurtech can add document extraction without adopting the full PolicyIQ | One workspace. **Q: How is PolicyIQ priced for insurtech companies?** A: PolicyIQ does not publish prices, because cost depends on the products used, volumes and integration scope. Book a demo or contact sales for a quote. **Q: Is PolicyIQ | Match's comparison logic available as a standalone API?** A: Yes. The Comparison API exposes PolicyIQ | Match's policy and dataset comparison logic for an insurtech to call directly. ## Software for Insurance Operations Teams URL: https://policyiq.in/solutions/insurance-operations-teams/ For Insurance Operations Teams ## Software for Insurance Operations Teams Software for insurance operations teams takes the typing and checking out of policy work: PolicyIQ | Extract reads policy documents into structured data, Data Validation flags fields that look wrong, Match lists what changed between policy versions, and Assist answers routine questions, so the team reviews exceptions only. Operations teams spend significant time on data entry, document review and comparison work that PolicyIQ's document and comparison products can automate. ### Daily operating challenges - Manual data entry from policy documents - Manual comparison of policy versions or datasets - Repeated internal questions with no single source of answers ### What PolicyIQ provides - AI OCR through PolicyIQ | Extract - Structured comparison through PolicyIQ | Match - Internal knowledge answers through PolicyIQ | Assist ### Recommended PolicyIQ products [POLICYIQ | EXTRACT Automate document data entry Explore](https://policyiq.in/products/extract/)[POLICYIQ | MATCH Automate comparison work Explore](https://policyiq.in/products/match/)[POLICYIQ | ASSIST Employee Knowledge Assistant Internal answers Explore](https://policyiq.in/products/assist/employee-knowledge-assistant/) ### What software for insurance operations teams should automate Insurance operations teams carry much of the repetitive work in the industry: reading policy schedules, proposal forms and claims documents and typing the details into systems, checking that data is complete and consistent, comparing records between systems, and answering internal questions about processes and products. Done by hand, this work is slow, error-prone and hard to scale when volumes spike, for example during renewal season. Errors made at data entry surface later as missed renewals, stalled claims and incorrect reports. ### How PolicyIQ supports insurance operations teams PolicyIQ | Extract reads insurance documents into structured data, with Data Validation checking fields for consistency before they reach other systems. PolicyIQ | Match compares policies, policy versions and datasets to find additions, removals and changes. PolicyIQ | Assist's Employee Knowledge Assistant gives staff a single point of reference for internal questions instead of scattered documentation. ### Where operations time goes, and what PolicyIQ automates Insurance operations work: manual vs automated with PolicyIQ Task Done by hand With PolicyIQ Policy and proposal data entry Re-typing schedules, forms and photos into systems [Extract](https://policyiq.in/products/extract/policy-data-extraction/) reads them into structured fields Checking extracted data Errors found later, in renewals and claims [Data Validation](https://policyiq.in/products/extract/data-validation/) flags fields that look wrong first Comparing policy versions Reading renewal and endorsement documents line by line [Match](https://policyiq.in/products/match/policy-change-detection/) lists additions, removals and changes Reconciling datasets Spot-checking a sample after a migration [Dataset comparison](https://policyiq.in/products/match/insurance-dataset-comparison/) checks every record Internal process questions Asking an experienced colleague The [Employee Knowledge Assistant](https://policyiq.in/products/assist/employee-knowledge-assistant/) answers directly ### Example: renewal season without the backlog Renewal season brings a spike of policy documents to record and renewal terms to check. With Extract reading each renewed policy into structured data, Data Validation flagging anything that looks wrong, and Match listing what changed from last year's policy, the team reviews exceptions instead of re-typing and re-reading every document. ### Why it matters Automating extraction, validation and comparison lets operations teams handle higher volumes with fewer errors and spend their time on exceptions that need judgement. ### Getting started PolicyIQ products are cloud-based and set up remotely, and can be used within PolicyIQ or integrated into existing systems through the OCR API and Comparison API. ### Further reading [Insurance Industry Insights Reducing Manual Data Entry in Insurance Operations Where manual data entry slows insurance operations, and how OCR, validation and connected systems remove the re-keying. Read the article](https://policyiq.in/blog/insurance-industry/reducing-manual-data-entry-in-insurance-operations/)[Insurance AI and Automation What AI Automation Covers Beyond Chatbots in Insurance Beyond chatbots: where AI automation helps insurance teams with documents, data checks, comparisons and routine servicing work. Read the article](https://policyiq.in/blog/insurance-ai/what-ai-automation-covers-beyond-chatbots-in-insurance/) - [Glossary: what is data validation?](https://policyiq.in/glossary/#data-validation) Frequently asked questions ### FAQs for insurance operations teams **Q: How does PolicyIQ reduce manual operations work?** A: PolicyIQ | Extract automates data entry from insurance documents, and PolicyIQ | Match automates comparison work that would otherwise be done by hand. **Q: Can internal teams get quick answers without asking colleagues?** A: Yes. PolicyIQ | Assist's Employee Knowledge Assistant surfaces internal knowledge directly for operations staff. **Q: Can PolicyIQ validate extracted policy data before it reaches other systems?** A: Yes. PolicyIQ | Extract's Data Validation step checks extracted data before it moves downstream, reducing manual review. **Q: What kinds of documents can PolicyIQ | Extract process for operations teams?** A: PolicyIQ | Extract handles motor policy documents, health policy documents and proposal forms through dedicated OCR capabilities. **Q: How is PolicyIQ priced for operations teams?** A: PolicyIQ does not publish prices, because cost depends on the products used, volumes and integration scope. Book a demo or contact sales for a quote. **Q: Do we have to replace our existing systems?** A: No. PolicyIQ products can be used within PolicyIQ or connected to existing systems through the OCR API and Comparison API. **Q: Can operations teams detect changes between policy datasets automatically?** A: Yes. PolicyIQ | Match's Policy Change Detection and Insurance Dataset Comparison identify differences between datasets without manual review. ## AI OCR for Insurance Documents (PolicyIQ | Extract) URL: https://policyiq.in/products/extract/ PolicyIQ | Extract ## AI OCR for insurance documents PolicyIQ | Extract is AI OCR for insurance documents: it reads policies, proposal forms and motor and health documents and returns structured, validated data, replacing manual data entry for agencies and insurers. [Book a demo](https://policyiq.in/request-demo/)Explore capabilities ### Insurance Policy Data Extraction Reads motor and health policies and proposal forms into checked, structured data. PolicyIQ | Extract is AI OCR software that reads insurance documents (policy schedules, proposal forms, and motor and health policy documents) and returns structured, validated data instead of requiring manual re-typing. ### What problem does PolicyIQ | Extract solve? Insurance documents arrive as PDFs, scans and phone photos, in formats that differ across insurers, and re-typing their contents into a broker's or insurer's own systems is slow and error-prone. PolicyIQ | Extract turns that manual step into an automated one, feeding structured data into downstream systems like PolicyIQ | One through PolicyIQ | Gateway. ### What capabilities does PolicyIQ | Extract include? Seven capabilities cover document extraction from intake through to validated, connected data. **Insurance Document OCR** Reads insurance documents and converts them into structured, usable data. [Explore Insurance Document OCR](https://policyiq.in/products/extract/insurance-document-ocr/) **Policy Data Extraction** Extracts policy schedule fields directly from insurer documents. [Explore Policy Data Extraction](https://policyiq.in/products/extract/policy-data-extraction/) **Proposal Form OCR** Reads completed proposal forms into structured fields. [Explore Proposal Form OCR](https://policyiq.in/products/extract/proposal-form-ocr/) **Motor Policy OCR** Extracts vehicle, coverage and premium details from motor policy documents. [Explore Motor Policy OCR](https://policyiq.in/products/extract/motor-policy-ocr/) **Health Policy OCR** Extracts sum insured, member and coverage details from health policy documents. [Explore Health Policy OCR](https://policyiq.in/products/extract/health-policy-ocr/) **Data Validation** Checks extracted data for consistency before it reaches downstream systems. [Explore Data Validation](https://policyiq.in/products/extract/data-validation/) **OCR API** Connects document extraction directly into existing agency or insurer systems. [Explore OCR API](https://policyiq.in/products/extract/ocr-api/) ### How does PolicyIQ | Extract fit with the rest of PolicyIQ? #### Connects through PolicyIQ | Gateway Structured document data can flow into PolicyIQ | One or a brokerage's own systems. #### Validated before use Data Validation checks extracted fields for consistency before they reach downstream systems. ### Why AI OCR for insurance documents matters in India Indian insurance businesses receive policy documents from many insurers, each with its own layout, and a large share arrives as scans or phone photos taken in the field. Proposal forms are often filled in by hand. Every one of these documents has to be read and typed into a system before a policy can be recorded, renewed or claimed against, which is slow and introduces errors that surface later. Generic OCR returns text but does not understand insurance documents: it does not know where the IDV sits on a motor policy, how to keep each member's sum insured on the right row of a group health schedule, or which fields on a proposal form matter. PolicyIQ | Extract is built around insurance document types, and every extraction passes through Data Validation before it is used. ### Who uses PolicyIQ | Extract? Agency operations teams use it to record new policies and renewals without re-typing. POSPs and sales teams use Proposal Form OCR to move new business towards issuance faster. Insurers and insurtech companies process high document volumes and bring extraction into their own platforms through the OCR API. Technology teams use the structured output to feed CRMs, policy systems and reports. ### How PolicyIQ | Extract connects with other PolicyIQ products Extracted and validated data can feed PolicyIQ | One's policy records and Sales CRM, so documents become records without manual entry. PolicyIQ | Match can compare policies and datasets built from extracted data, and PolicyIQ | Gateway connects Extract's output to other systems through the OCR API. ### Getting started with PolicyIQ | Extract PolicyIQ | Extract is cloud-based and set up remotely. Teams can use it within PolicyIQ, or developers can integrate document extraction and validation into existing agency or insurer systems through the OCR API. ### Further reading [Insurance OCR and Document Processing Insurance OCR Software in India: How to Choose The five types of insurance OCR software in India, what to test in a pilot, and where insurance-specific extraction fits. Read the article](https://policyiq.in/blog/insurance-ocr/insurance-ocr-software-in-india-how-to-choose/)[Insurance OCR and Document Processing How AI OCR Extracts Data from Insurance Policies How AI OCR reads insurance policies, finds policy schedule fields and validates the result before anyone relies on it. Read the article](https://policyiq.in/blog/insurance-ocr/how-ai-ocr-extracts-data-from-insurance-policies/)[Insurance OCR and Document Processing OCR Accuracy and Data Quality in Document Processing Why OCR accuracy alone is not enough, and how validation keeps insurance document data reliable before it reaches other systems. Read the article](https://policyiq.in/blog/insurance-ocr/ocr-accuracy-and-data-quality-in-insurance-document-processing/)[Insurance Industry Insights Reducing Manual Data Entry in Insurance Operations Where manual data entry slows insurance operations, and how OCR, validation and connected systems remove the re-keying. Read the article](https://policyiq.in/blog/insurance-industry/reducing-manual-data-entry-in-insurance-operations/) - [Glossary: what is intelligent document processing?](https://policyiq.in/glossary/#intelligent-document-processing) Frequently asked questions ### Your questions, answered **Q: What document types does PolicyIQ | Extract support?** A: PolicyIQ | Extract is intelligent document processing for insurance, built around common document types: policy schedules, proposal forms, and motor and health policy documents. **Q: How accurate is the extracted data?** A: PolicyIQ | Extract runs AI-powered insurance document data capture through a Data Validation step that checks extracted fields for consistency before they reach downstream systems, rather than passing raw OCR output through unchecked. **Q: Can PolicyIQ | Extract connect to existing systems?** A: Yes. The OCR API lets an agency or insurer connect document extraction directly into their existing systems instead of using PolicyIQ | Extract only as a standalone tool. **Q: Does PolicyIQ | Extract handle motor and health documents specifically?** A: Yes. Motor Policy OCR extracts vehicle, coverage and premium details, and Health Policy OCR extracts sum insured, member and coverage details, each built around that document type specifically, in addition to general Insurance Document OCR. **Q: Can PolicyIQ | Extract read proposal forms, not just issued policies?** A: Yes. Proposal Form OCR reads completed proposal forms into structured fields, alongside Policy Data Extraction for issued policy schedules: covering both ends of the policy lifecycle. **Q: Does PolicyIQ | Extract work with phone photos of documents?** A: Insurance Document OCR is designed to read scans, PDFs and photographed insurance documents. **Q: Is extracted data checked before use?** A: Yes. Every extraction passes through Data Validation, which checks fields for consistency and flags incomplete or implausible values before they reach downstream systems. **Q: Can PolicyIQ | Extract feed PolicyIQ | One?** A: Yes. Extracted policy and proposal data can connect into PolicyIQ | One through the OCR API, connected via PolicyIQ | Gateway. [Read: How AI OCR Extracts Data from Insurance Policies](https://policyiq.in/blog/insurance-ocr/how-ai-ocr-extracts-data-from-insurance-policies/) ## Insurance Data Validation Software (PolicyIQ | Extract) URL: https://policyiq.in/products/extract/data-validation/ PolicyIQ | Extract ## Insurance Data Validation Software Data Validation checks data extracted by PolicyIQ | Extract for consistency before it reaches downstream systems, rather than passing raw OCR output through unchecked. OCR output can still contain misreads or inconsistent fields, especially across scanned or lower-quality documents. Data Validation sits between extraction and use, applying consistency checks to output from Insurance Document OCR, Policy Data Extraction, Proposal Form OCR, Motor Policy OCR and Health Policy OCR alike. Trusting automated extraction without a check is how a single misread field turns into a downstream error somewhere else in the business. Validation is what makes it reasonable to treat extracted data as reliable enough to act on, rather than something that still needs a person to double-check every field by hand. ### Why raw OCR output can't be trusted as-is - OCR misreads on scanned or lower-quality documents - No consistent check before extracted data is used downstream - Errors that surface only after they've caused a problem elsewhere - Difficulty knowing which extracted fields need human review ### The check between extraction and your systems Validated data is what reaches a brokerage's or insurer's systems through the OCR API, so downstream tools like PolicyIQ | One work from checked data rather than raw extraction results. Data Validation is applied uniformly across every extraction type, rather than being configured separately for each document category. ### Consistency checks and flags for fields that need review - Consistency checks across extracted fields - Flagging of fields that look incomplete or implausible - A checked-data handoff to the OCR API - Uniform application across all PolicyIQ | Extract capabilities ### What checked data prevents downstream - More trustworthy extracted data - Fewer downstream errors caused by bad input - Clear visibility into what needs human review ### How Insurance Data Validation Software works - Receive extracted data: Fields extracted by any PolicyIQ | Extract capability arrive for checking before they go anywhere else. - Check consistency: Consistency checks run across the extracted fields. - Flag problems: Fields that look incomplete or implausible are flagged rather than passed through silently. - Hand over checked data: Checked data is handed to the OCR API for downstream systems, applied uniformly across every Extract capability. ### Who depends on extracted data being right Data Validation matters to operations teams who rely on extracted data being right, to servicing and renewal teams whose work depends on accurate policy fields, and to technology teams integrating extracted data into agency, insurer or partner systems. ### One wrong digit: missed renewals, stalled claims, wrong commission In insurance, a single wrong digit in a policy number, premium or renewal date causes problems far beyond the document: missed renewals, stalled claims and incorrect commission. Indian insurance documents vary widely in layout and quality, so no OCR is perfect on every page. Insurance data validation catches errors at the point where they are cheapest to fix. ### Example: catching an end date earlier than the start date Imagine an extracted policy where the end date was read as earlier than the start date, or where the premium field came back empty. Without validation, those errors would flow into renewal reminders and reports. With PolicyIQ | Extract, consistency checks run across the extracted fields, the implausible date and the missing premium are flagged rather than passed through, and only checked data is handed to the OCR API, the same way for every PolicyIQ | Extract capability. ### Getting started with PolicyIQ | Extract PolicyIQ | Extract is cloud-based and set up remotely. Teams can use it within PolicyIQ, or developers can bring the same extraction and validation into their own agency or insurer systems through the OCR API, connected via PolicyIQ | Gateway. ### Related PolicyIQ | Extract capabilities - [PolicyIQ | Extract Insurance Document OCR The extraction step Data Validation checks](https://policyiq.in/products/extract/insurance-document-ocr/) - [PolicyIQ | Extract OCR API How validated data reaches other systems](https://policyiq.in/products/extract/ocr-api/) - [PolicyIQ | Extract PolicyIQ | Extract Overview Every PolicyIQ | Extract capability in one place](https://policyiq.in/products/extract/) ### Frequently asked questions **Q: What kinds of OCR errors does validation catch?** A: It flags extracted fields that look inconsistent or implausible, such as a value in an unexpected format, before they reach downstream systems. **Q: Is validation applied to every PolicyIQ | Extract capability?** A: Yes, output from Insurance Document OCR and its category-specific variants (Policy Data Extraction, Proposal Form OCR, Motor Policy OCR, Health Policy OCR) all pass through Data Validation. **Q: Why validate data instead of trusting OCR output?** A: Because no OCR is perfect on every document; validation catches incomplete or implausible fields before they reach downstream systems. **Q: Is OCR API output validated too?** A: Yes. Checked data is handed to the OCR API, so integrating systems receive validated output. **Q: Does data validation help reduce fraud risk?** A: It checks extracted document data for consistency, which reduces the unchecked data entry that both hides errors and creates gaps fraud can exploit. ## Health Insurance Policy OCR Software (PolicyIQ | Extract) URL: https://policyiq.in/products/extract/health-policy-ocr/ PolicyIQ | Extract ## Health Insurance Policy OCR Software Health Policy OCR extracts sum insured, member and coverage details from health insurance policy documents, including family floater and group health structures. Health policies often cover multiple family members or employees under one schedule, with sub-limits and waiting periods general OCR isn't tuned for. Health Policy OCR applies PolicyIQ | Extract's document reading capability with those health-specific fields in mind, alongside Motor Policy OCR for the motor insurance equivalent. A single health policy document can carry per-member sums insured, sub-limits and exclusions that differ from one family member or employee to the next. Extracting these accurately, member by member, is exactly the kind of detailed work manual entry struggles to do consistently at volume. ### Family floaters, group schedules and per-member sub-limits - Family floater and group policies list multiple members with different sub-limits - Waiting periods and exclusions vary by insurer and plan - Manual entry across many members is slow and error-prone - Group health schedules can span many pages ### Health policy data, checked and connected to your systems Extracted health policy data passes through Data Validation before use and can connect into an agency's systems through the OCR API, feeding both individual and group health workflows. See how this feeds broader health and group health workflows on the [Health Insurance](https://policyiq.in/insurance/health/) and [Group Health Insurance](https://policyiq.in/insurance/group-health/) pages. ### Sum insured, sub-limits, waiting periods and exclusions per member - Extraction tuned to health policy schedule fields - Per-member sum insured and sub-limit capture for floater/group policies - Waiting period and exclusion details captured - Validation before use, and connection via the OCR API ### What faster multi-member data entry changes - Faster health policy data entry, including multi-member policies - Fewer errors across per-member details - Consistent handling of group health schedules ### How Health Insurance Policy OCR Software works - Read the health policy: The health policy document is read using extraction tuned to health policy schedule fields. - Capture members and sums insured: Per-member sum insured and sub-limits are captured, including for family floater and group health structures. - Capture waiting periods and exclusions: Waiting period and exclusion details are captured, not just headline cover. - Validate and connect: The data is validated before use and can connect into other systems through the OCR API. ### Who processes health policy documents In PolicyIQ | Extract, this capability is used by agencies and POSPs selling retail and group health insurance, by servicing teams handling health renewals and claims, and by insurers and insurtechs processing health policy documents. ### Individual, floater and group health: India's many policy structures Health insurance in India comes in many structures, from individual and family floater policies to employer group schemes with many members, and details such as waiting periods, sub-limits and exclusions affect claims directly. Re-typing multi-member schedules is slow and error-prone. Health insurance policy OCR captures these details per member and validates them before use. ### Example: an employer's group health schedule without re-typing Imagine an agency handling an employer's group health scheme, with a schedule listing many members, each with their own sum insured and sub-limits. Re-typing it invites errors on the wrong row. With PolicyIQ | Extract, extraction tuned to health policy schedules captures per-member sums insured and sub-limits, along with waiting periods and exclusions, then validates the data before use and makes it available to other systems through the OCR API. ### Getting started with PolicyIQ | Extract PolicyIQ | Extract is cloud-based and set up remotely. Teams can use it within PolicyIQ, or developers can bring the same extraction and validation into their own agency or insurer systems through the OCR API, connected via PolicyIQ | Gateway. ### Related PolicyIQ | Extract capabilities - [PolicyIQ | Extract Motor Policy OCR The equivalent capability for motor insurance documents](https://policyiq.in/products/extract/motor-policy-ocr/) - [PolicyIQ | Extract Data Validation Checks extracted health policy fields for consistency](https://policyiq.in/products/extract/data-validation/) - [PolicyIQ | Extract PolicyIQ | Extract Overview Every PolicyIQ | Extract capability in one place](https://policyiq.in/products/extract/) ### Frequently asked questions **Q: Can health insurance OCR handle family floater policies?** A: Yes, it's built with family floater and group health structures in mind, capturing per-member details rather than treating a policy as a single record. **Q: Can it process group health schedules with many members?** A: It's designed for multi-member schedules. **Q: Are waiting periods captured from health policies?** A: Yes. Waiting period and exclusion details are captured along with sum insured and coverage. **Q: Does it handle sub-limits per member?** A: Yes. Per-member sum insured and sub-limit capture is included for floater and group policies. **Q: Can health policy data flow into other systems?** A: Yes. Validated data can connect into other systems through the OCR API. ## Insurance Document OCR Software (PolicyIQ | Extract) URL: https://policyiq.in/products/extract/insurance-document-ocr/ PolicyIQ | Extract ## Insurance Document OCR Software Insurance Document OCR reads insurance documents and converts them into structured, usable data, the foundational capability behind every other PolicyIQ | Extract feature. Insurance documents arrive as PDFs, scans or photographs, in formats that vary by insurer. Insurance Document OCR is the general-purpose reading capability underneath PolicyIQ | Extract's more specific tools (Policy Data Extraction, Proposal Form OCR, Motor Policy OCR and Health Policy OCR) each applying it to a particular document type. Reading a document is only useful if the output can be trusted and used elsewhere. It is built to recognise the fields insurance documents actually contain, not just extract a wall of unstructured text, so the result is ready for validation and use rather than another manual clean-up step. ### Scans, PDFs and phone photos in every layout - Documents arrive as scans, PDFs or photos in inconsistent insurer formats - Manual re-typing introduces transcription errors - No structured way to feed extracted data into other systems - Slow turnaround when documents pile up ### From document to validated data to your systems Once a document is read, its output passes through Data Validation before reaching an agency's or insurer's own systems, and can connect through the OCR API rather than requiring manual export and import. Category-specific extraction for motor and health policies builds directly on this same reading capability, rather than starting from scratch. ### Field recognition that outputs structured data, not raw text - Text and field recognition across common insurance document types - Output structured into usable data fields, not just raw text - A foundation for category-specific extraction (motor, health, proposal forms) - A direct handoff into Data Validation before use ### What faster document turnaround changes - Faster document turnaround - Fewer manual transcription errors - Structured data ready for downstream systems ### How Insurance Document OCR Software works - Receive the document: Insurance documents arrive as scans, PDFs or photographed pages from customers, agents and insurers. - Recognise text and fields: Text and fields are recognised across common insurance document types, rather than treated as an undifferentiated block of text. - Structure the output: The result is organised into usable data fields that systems can work with, not just raw text. - Validate and hand over: The structured data passes directly into Data Validation before use, and category-specific extraction for motor, health and proposal forms builds on the same foundation. ### Who handles high volumes of insurance documents In PolicyIQ | Extract, this capability is used by agency and insurer operations teams who receive large volumes of documents, by servicing staff who would otherwise re-type policy details, and by technology teams who want document data flowing into their own systems through the OCR API. ### Many insurers, many layouts, many field photos Indian insurance businesses deal with documents from many insurers, each with its own layout, and much of it arrives as phone photos or scans from the field. Re-typing those details is slow and introduces errors that surface later in renewals and claims. Insurance document OCR software that produces structured fields, then validates them, removes most of that manual entry. ### Example: a morning's mix of insurer PDFs, scans and photos Imagine an operations team receiving a mix of insurer PDFs, scanned forms and phone photos from agents every morning. With PolicyIQ | Extract, each document is read and its text and fields recognised, and the output is organised into structured data fields rather than a block of raw text. The structured data passes into Data Validation before it is used, and documents such as motor policies, health policies and proposal forms get category-specific extraction built on the same foundation. ### Getting started with PolicyIQ | Extract PolicyIQ | Extract is cloud-based and set up remotely. Teams can use it within PolicyIQ, or developers can bring the same extraction and validation into their own agency or insurer systems through the OCR API, connected via PolicyIQ | Gateway. ### Related PolicyIQ | Extract capabilities - [PolicyIQ | Extract Data Validation Checks OCR output for consistency](https://policyiq.in/products/extract/data-validation/) - [PolicyIQ | Extract OCR API Connect OCR into existing systems](https://policyiq.in/products/extract/ocr-api/) - [PolicyIQ | Extract PolicyIQ | Extract Overview Every PolicyIQ | Extract capability in one place](https://policyiq.in/products/extract/) ### Frequently asked questions **Q: What document formats can insurance OCR read: PDFs, scans, photos?** A: Insurance Document OCR is designed to read scans, PDFs and photographed insurance documents. **Q: Does it work for every insurer's documents?** A: It's built to handle the layout variation across different insurers' documents, with category-specific extraction (Motor Policy OCR, Health Policy OCR) tuned further for those document types. **Q: How is insurance document OCR different from generic OCR?** A: It goes further: rather than returning raw text, it structures output into usable data fields and provides the foundation for insurance-specific extraction such as motor, health and proposal form OCR. **Q: What happens to the data after extraction?** A: It passes into Data Validation, which checks extracted fields for consistency before they reach downstream systems. **Q: Can developers use it in their own systems?** A: Yes. The OCR API gives programmatic access to document extraction and validation for agency, insurer and partner systems. ## Motor Insurance Policy OCR Software (PolicyIQ | Extract) URL: https://policyiq.in/products/extract/motor-policy-ocr/ PolicyIQ | Extract ## Motor Insurance Policy OCR Software Motor Policy OCR extracts vehicle, coverage and premium details from motor insurance policy documents, tuned to the specific fields motor policies carry. Motor policies carry details general policy schedules don't: registration numbers, engine and chassis numbers, IDV, and add-on covers. Motor Policy OCR applies PolicyIQ | Extract's document reading capability with those motor-specific fields in mind, alongside Health Policy OCR for the health insurance equivalent. Motor renewals often arrive in large batches around the same time of year, which makes manual data entry especially slow at exactly the point agencies need speed most. Automated, category-specific extraction is built to keep up with that volume without sacrificing accuracy on vehicle-specific fields. ### Registration, engine and chassis numbers, IDV and add-ons - Motor-specific fields (registration, engine/chassis number, IDV) missed by generic OCR - Add-on covers recorded inconsistently - Manual entry errors in vehicle details - Slow processing during high renewal volumes ### Motor policy data, checked and connected to your systems Extracted motor policy data passes through Data Validation before use and can connect into an agency's systems through the OCR API, feeding the Insurance Categories: Motor workflows those systems support. See how motor policy data flows into broader motor insurance workflows on the [Motor Insurance](https://policyiq.in/insurance/motor/) page. ### Vehicle details, IDV and add-on covers captured from the schedule - Extraction tuned to motor policy schedule fields - Vehicle registration, engine/chassis number and IDV capture - Add-on cover details captured alongside the base policy - Validation before use, and connection via the OCR API ### What accurate vehicle data changes at renewal time - Faster motor policy data entry - Fewer errors in vehicle-specific fields - Consistent handling of add-on covers across policies ### How Motor Insurance Policy OCR Software works - Read the motor policy: The motor policy document is read using extraction tuned to motor policy schedule fields. - Capture vehicle details: Vehicle registration, engine and chassis numbers and IDV are captured, the fields generic OCR tends to miss. - Capture cover details: Add-on cover details are captured alongside the base policy. - Validate and connect: The data is validated before use and can connect into other systems through the OCR API. ### Who processes motor policy documents In PolicyIQ | Extract, this capability is used by agencies and POSPs with large motor books, by operations teams processing motor renewals and endorsements, and by insurers and insurtechs handling motor policy documents at volume. ### India's highest-volume line, with vehicle details that must be exact Motor insurance is one of the highest-volume lines in Indian insurance distribution, and every policy carries vehicle-specific details such as registration number, engine and chassis numbers and IDV that must be exactly right for renewals and claims. Third-party cover is mandatory under the Motor Vehicles Act, 1988, so renewals come round every year. Motor insurance policy OCR captures these fields accurately without manual entry. ### Example: a large motor book renewed without re-typing vehicle details Imagine an agency with a large motor book where every renewal needs the vehicle's registration number, engine and chassis numbers and IDV recorded exactly. Generic OCR often misses these fields. With PolicyIQ | Extract, extraction tuned to motor policy schedules captures the vehicle details and add-on covers alongside the base policy, validates them before use and connects the data to other systems through the OCR API, so motor renewals and claims start from accurate vehicle information. ### Getting started with PolicyIQ | Extract PolicyIQ | Extract is cloud-based and set up remotely. Teams can use it within PolicyIQ, or developers can bring the same extraction and validation into their own agency or insurer systems through the OCR API, connected via PolicyIQ | Gateway. ### Related PolicyIQ | Extract capabilities - [PolicyIQ | Extract Health Policy OCR The equivalent capability for health insurance documents](https://policyiq.in/products/extract/health-policy-ocr/) - [PolicyIQ | Extract Policy Data Extraction General policy schedule fields](https://policyiq.in/products/extract/policy-data-extraction/) - [PolicyIQ | Extract PolicyIQ | Extract Overview Every PolicyIQ | Extract capability in one place](https://policyiq.in/products/extract/) ### Frequently asked questions **Q: Which motor-specific fields does motor policy OCR extract?** A: It's tuned to capture fields specific to motor policies, including vehicle registration, engine and chassis numbers, IDV and add-on covers. **Q: Does it work alongside general document extraction?** A: Yes, it applies PolicyIQ | Extract's general Insurance Document OCR specifically to motor policy documents, rather than replacing it. **Q: Is IDV captured from motor policies?** A: Yes. It captures vehicle registration, engine and chassis numbers and IDV from motor policy documents. **Q: Are add-on covers captured?** A: Yes. Add-on cover details are captured alongside the base policy. **Q: Is motor policy data checked before use?** A: Yes. Extracted data is validated before use, as with every PolicyIQ | Extract capability. ## Insurance OCR API for Developers (PolicyIQ | Extract) URL: https://policyiq.in/products/extract/ocr-api/ PolicyIQ | Extract ## Insurance OCR API for Developers The OCR API connects PolicyIQ | Extract's document extraction directly into existing agency or insurer systems, instead of using PolicyIQ | Extract only as a standalone tool. An agency or insurer with its own policy administration or CRM system can send documents to PolicyIQ | Extract and receive validated, structured data back programmatically, rather than exporting and re-importing files by hand. Extraction that isn't connected to where the data is actually used still leaves a manual step in the workflow: someone has to move the output from one system to another. The API removes that step, so extraction becomes part of an existing process rather than a separate tool alongside it. ### Connecting document extraction to systems you already run - No easy way to connect extraction into an existing policy or CRM system - Manual export and import between PolicyIQ | Extract and other tools - Difficulty scaling extraction across a high document volume - Limited visibility into integration health ### Where the API sits: after validation, before your system The OCR API sits after Data Validation in the pipeline, and is also how PolicyIQ | Extract connects to other PolicyIQ products, such as feeding structured policy data into PolicyIQ | One through PolicyIQ | Gateway. See [PolicyIQ | Gateway's Developer Resources](https://policyiq.in/products/gateway/developer-resources/) for the broader integration layer this API connects through. ### Programmatic extraction, structured output and documentation - Programmatic access to document extraction and validation - Structured output ready for downstream systems - Connection into PolicyIQ | One and other systems via PolicyIQ | Gateway - Documentation for integrating teams ### What embedded extraction removes - Extraction embedded directly into existing workflows - No manual export or import step - Scalable processing for high document volumes ### How Insurance OCR API for Developers works - Send a document: A broker, insurer or partner system sends an insurance document for extraction programmatically. - Extract and validate: PolicyIQ | Extract's document extraction and Data Validation run on the document. - Receive structured output: Structured output comes back ready for downstream systems. - Connect your systems: The output can flow into PolicyIQ | One and other systems via PolicyIQ | Gateway, supported by documentation for integrating teams. ### Who builds with an insurance OCR API In PolicyIQ | Extract, this capability is used by developers and technology teams at agencies, insurers and insurtech companies who want insurance document extraction inside their own applications, rather than using PolicyIQ | Extract only as a standalone tool. ### Bringing validated extraction into existing Indian insurance systems Many Indian insurance businesses already run their own systems for policies, CRM or claims. An insurance OCR API brings validated document extraction into those systems directly, so documents uploaded anywhere in the workflow become structured data without anyone switching tools or re-typing details. ### Example: an insurtech reading policies customers upload at sign-up Imagine an insurtech platform where customers upload their existing policies when they sign up. Instead of building its own document reading, the platform sends each uploaded document to the API, PolicyIQ | Extract's extraction and Data Validation run on it, and structured output comes back ready to populate the customer's profile. The same output can also flow into PolicyIQ | One or other systems through PolicyIQ | Gateway, with documentation to guide the integrating team. ### Getting started with PolicyIQ | Extract PolicyIQ | Extract is cloud-based and set up remotely. Teams can use the API within PolicyIQ, or developers can bring the same extraction and validation into their own agency or insurer systems through the OCR API, connected via PolicyIQ | Gateway. ### Related PolicyIQ | Extract capabilities - [PolicyIQ | Extract Data Validation The checked data the API delivers](https://policyiq.in/products/extract/data-validation/) - [PolicyIQ | Gateway PolicyIQ | Gateway Connects PolicyIQ | Extract to other systems](https://policyiq.in/products/gateway/) - [PolicyIQ | Extract PolicyIQ | Extract Overview Every PolicyIQ | Extract capability in one place](https://policyiq.in/products/extract/) ### Frequently asked questions **Q: What does the insurance OCR API return?** A: It returns the same structured, validated data produced by PolicyIQ | Extract's extraction and Data Validation steps, in a format other systems can consume directly. **Q: Can it connect to systems other than PolicyIQ products?** A: Yes, an agency's or insurer's own systems can connect to the OCR API directly, not only other PolicyIQ products. **Q: Is the API output validated?** A: Yes. The API gives programmatic access to both document extraction and Data Validation, so output is checked before use. **Q: Is there documentation for developers?** A: Yes. Documentation is provided for teams integrating the OCR API into their systems. **Q: Can the OCR API connect to PolicyIQ | One?** A: Yes. Output can connect into PolicyIQ | One and other systems via PolicyIQ | Gateway. ## Insurance Policy Data Extraction Software URL: https://policyiq.in/products/extract/policy-data-extraction/ PolicyIQ | Extract ## Insurance Policy Data Extraction Software Policy Data Extraction reads policy schedule fields directly from insurer documents, turning static PDFs into structured datan agency's systems can use. Policy schedules carry the core facts of a policy (sums insured, premiums, coverage periods, endorsements) in a layout that differs by insurer. Policy Data Extraction applies PolicyIQ | Extract's Insurance Document OCR specifically to these schedules. Retyping a policy schedule's fields by hand is one of the most repetitive tasks in insurance operations, and one of the easiest places for a transcription error to slip into a record that gets relied on later. PolicyIQ | Extract turns that manual step into an automated read of the same document. ### Sums insured, premiums and dates buried in dense schedules - Policy schedule fields buried in dense, inconsistent layouts - Manually re-typing sums insured, premiums and coverage periods - Errors that carry through to downstream records - No easy way to feed extracted data into a broking system ### Policy data that feeds straight into policy management Extracted policy data passes through Data Validation before it reaches a brokerage's systems, and can feed directly into PolicyIQ | One's Policy Management through the OCR API. The same extraction logic underlies Motor Policy OCR and Health Policy OCR, each adding fields specific to that insurance category. ### Field-level extraction, endorsements and validated output - Field-level extraction of sums insured, premiums and coverage periods - Endorsement details captured alongside the base policy - Output validated before use - A direct connection into systems like PolicyIQ | One via the OCR API ### What faster, cleaner policy data entry changes - Faster policy data entry - Fewer transcription errors in core policy fields - Structured data ready for policy management systems ### How Insurance Policy Data Extraction Software works - Read the policy schedule: The insurer's policy document, usually a PDF, is read directly rather than typed in by hand. - Extract key fields: Core policy schedule fields such as sums insured, premiums and coverage periods are extracted at field level. - Capture endorsements: Endorsement details are captured alongside the base policy, so changes are not lost. - Validate and connect: The output is validated before use and can flow into systems like PolicyIQ | One through the OCR API. ### Who records policies and renewals from insurer PDFs In PolicyIQ | Extract, this capability is used by agency operations teams who record new policies and renewals, by servicing teams who need accurate policy data for endorsements and claims, and by insurer and insurtech teams who process policy documents at volume. ### Every insurer formats its policy schedule differently Indian agencies receive policy schedules from many insurers, each formatted differently, and policy data drives everything that follows: renewal dates, claims, commission and reporting. Typing it in by hand creates delays and errors. Insurance policy data extraction turns static PDFs into structured, validated data so downstream work starts from accurate information. ### Example: hundreds of renewed policies a month without typing Imagine a brokerage that records hundreds of renewed policies each month, typing sums insured, premiums and policy periods from each insurer's PDF into its system. With PolicyIQ | Extract, those policy schedule fields are read directly from the documents at field level, endorsement details are captured alongside the base policy, and the output is validated before use. The validated data can then flow into PolicyIQ | One through the OCR API, ready to drive renewal dates and servicing. ### Getting started with PolicyIQ | Extract PolicyIQ | Extract is cloud-based and set up remotely. Teams can use it within PolicyIQ, or developers can bring the same extraction and validation into their own agency or insurer systems through the OCR API, connected via PolicyIQ | Gateway. ### Related PolicyIQ | Extract capabilities - [PolicyIQ | Extract Insurance Document OCR The general reading capability behind this feature](https://policyiq.in/products/extract/insurance-document-ocr/) - [PolicyIQ | Extract Data Validation Checks extracted policy fields for consistency](https://policyiq.in/products/extract/data-validation/) - [PolicyIQ | Extract PolicyIQ | Extract Overview Every PolicyIQ | Extract capability in one place](https://policyiq.in/products/extract/) ### Frequently asked questions **Q: Which fields are extracted from an insurance policy PDF?** A: Policy Data Extraction is built to capture core policy schedule fields such as sums insured, premiums and coverage periods. **Q: Can extracted policy data feed into PolicyIQ | One?** A: Yes, through the OCR API and PolicyIQ | Gateway, structured policy data can flow into PolicyIQ | One's Policy Management. **Q: Are endorsement details captured too?** A: Yes. Endorsement details are captured alongside the base policy. **Q: Is extracted policy data checked before use?** A: Yes. Output passes through Data Validation, which checks extracted fields for consistency before they reach downstream systems. **Q: Does it work with policies from different insurers?** A: It is built to read policy schedule fields from insurer documents, which vary in layout from one insurer to another. ## Insurance Proposal Form OCR Software (PolicyIQ | Extract) URL: https://policyiq.in/products/extract/proposal-form-ocr/ PolicyIQ | Extract ## Insurance Proposal Form OCR Software Proposal Form OCR reads completed insurance proposal forms into structured fields, so a new business application does not need to be re-typed into a broker's or insurer's systems. Proposal forms are usually handwritten or filled digitally before scanning, and their layout differs by insurer and product. Proposal Form OCR applies PolicyIQ | Extract's document reading capability specifically to this stage of the sales process, ahead of policy issuance. A proposal form is where a policy's details first get written down, and any error introduced here tends to carry through to the issued policy. Reading the form automatically, rather than re-keying it, removes that repeated opportunity for mistakes between sales and underwriting. ### Handwritten forms that delay policy issuance - Proposal forms are often handwritten or filled inconsistently - Re-typing proposal details delays policy issuance - Errors in proposal data carry through to the issued policy - No structured handover from sales to underwriting ### Proposal data handed straight to sales and underwriting Extracted proposal data passes through Data Validation before use, and can connect into a Sales CRM like the one inside PolicyIQ | One through the OCR API. Proposal Form OCR sits earlier in the workflow than Policy Data Extraction, capturing details before a policy even exists. ### Handwritten and digital forms read field by field - Reading of handwritten and digitally completed proposal forms - Field-level extraction of applicant and product details - Validation before the data is used - Connection into a Sales CRM like PolicyIQ | One's ### What faster proposal-to-policy movement changes - Faster movement from proposal to issued policy - Fewer errors carried from a proposal into the policy - Less manual work for sales and underwriting teams ### How Insurance Proposal Form OCR Software works - Capture the completed form: A filled-in proposal form, handwritten or completed digitally, is scanned, photographed or uploaded. - Read applicant and product details: Applicant and product details are extracted into structured fields. - Validate: The extracted data is validated before it is used, so gaps and inconsistencies are flagged early. - Pass into sales and issuance: The data connects into a Sales CRM such as PolicyIQ | One's, so the application does not have to be re-typed before policy issuance. ### Who collects and processes proposal forms In PolicyIQ | Extract, this capability is used by agencies, POSPs and sales teams who collect new business applications, by operations teams who would otherwise re-key proposal forms, and by insurers processing incoming applications. ### Forms still filled by hand in the field across India In India many proposal forms are still completed by hand, often in the field by a POSP or agent, and every form must be re-typed before a policy can be issued. Accurate disclosure on the proposal form also matters to the insurer's decision. Insurance proposal form OCR removes the re-typing and flags incomplete details while the customer can still be asked. ### Example: a POSP's handwritten forms, photographed and processed Imagine a POSP agent collecting handwritten proposal forms during the day and sending photos to the office, where each form is typed in before the policy can be issued. With PolicyIQ | Extract, applicant and product details are read from the handwritten or digital form into structured fields, validated so missing details are flagged while the customer can still be asked, and passed into a Sales CRM such as PolicyIQ | One's, so the application moves towards issuance without being re-typed. ### Getting started with PolicyIQ | Extract PolicyIQ | Extract is cloud-based and set up remotely. Teams can use it within PolicyIQ, or developers can bring the same extraction and validation into their own agency or insurer systems through the OCR API, connected via PolicyIQ | Gateway. ### Related PolicyIQ | Extract capabilities - [PolicyIQ | Extract Insurance Document OCR The general reading capability behind this feature](https://policyiq.in/products/extract/insurance-document-ocr/) - [PolicyIQ | Extract Policy Data Extraction The next step once a policy is issued](https://policyiq.in/products/extract/policy-data-extraction/) - [PolicyIQ | Extract PolicyIQ | Extract Overview Every PolicyIQ | Extract capability in one place](https://policyiq.in/products/extract/) ### Frequently asked questions **Q: Can OCR read handwritten insurance proposal forms?** A: It's designed to read both handwritten and digitally completed proposal forms. **Q: How does it speed up policy issuance?** A: By extracting proposal details automatically rather than requiring manual re-entry before underwriting and issuance can proceed. **Q: Can it read digitally completed forms too?** A: Yes. It reads both handwritten and digitally completed proposal forms. **Q: What details are extracted from a proposal form?** A: It extracts applicant and product details at field level from the completed proposal form. **Q: Where does the extracted proposal data go?** A: It can connect into a Sales CRM such as PolicyIQ | One's, so new business moves towards issuance without re-typing. ## Insurance API Integration Platform (PolicyIQ | Gateway) URL: https://policyiq.in/products/gateway/ PolicyIQ | Gateway ## Insurance API integration platform PolicyIQ | Gateway is an insurance API integration platform that connects insurer systems, KYC and payment services, and communication APIs into one standardised integration layer for insurance workflows. [Book a demo](https://policyiq.in/request-demo/)Explore capabilities ### Insurance API Integration for India Insurer, KYC, payment and communication APIs connected through one platform. PolicyIQ | Gateway is an insurance API integration platform standardising connections to insurer systems, KYC and payment services, and communication APIs, so PolicyIQ products and an agency's or insurer's own systems can exchange data without building each integration separately. ### What problem does PolicyIQ | Gateway solve? Every insurer, KYC provider and payment service exposes a different API, and integrating each one separately is slow and hard to maintain. PolicyIQ | Gateway standardises those connections in one place, so a system connects once to PolicyIQ | Gateway rather than to each partner individually. ### What capabilities does PolicyIQ | Gateway include? Seven capabilities cover integration from insurer and partner systems through to monitoring and developer resources. **Insurance API Integration** A standardised integration layer connecting PolicyIQ products and outside systems. [Explore Insurance API Integration](https://policyiq.in/products/gateway/insurance-api-integration/) **Insurer API Integration** Connects directly to insurer systems for policy and claims data exchange. [Explore Insurer API Integration](https://policyiq.in/products/gateway/insurer-api-integration/) **KYC Verification APIs** Connects identity verification services into insurance workflows. [Explore KYC Verification APIs](https://policyiq.in/products/gateway/kyc-verification-apis/) **Payment APIs** Connects payment services for premium collection and payouts. [Explore Payment APIs](https://policyiq.in/products/gateway/payment-apis/) **Communication APIs** Connects SMS, email and messaging services to customer and agent workflows. [Explore Communication APIs](https://policyiq.in/products/gateway/communication-apis/) **API Monitoring** Tracks integration health and uptime across connected systems. [Explore API Monitoring](https://policyiq.in/products/gateway/api-monitoring/) **Developer Resources** Documentation and reference material for teams building on PolicyIQ | Gateway. [Explore Developer Resources](https://policyiq.in/products/gateway/developer-resources/) ### How does PolicyIQ | Gateway fit with the rest of PolicyIQ? #### The connective layer PolicyIQ | One, Extract, Desk, Assist and Match all connect to outside systems through PolicyIQ | Gateway. #### Monitored connections API Monitoring keeps integration health and uptime visible across every connected system. ### Why an insurance API integration platform instead of one-off connections? Insurance businesses in India connect to many outside systems: insurer platforms for policy and claims data, KYC services for onboarding, payment providers for premiums and payouts, and SMS, email and messaging channels for notifications. Each has its own formats, authentication and failure behaviour. Building every connection separately multiplies development and maintenance work, and failures are often noticed only when a customer complains. PolicyIQ | Gateway applies one standard integration pattern across every partner. Systems connect once to Gateway's single connection point, data is exchanged consistently whichever partner is involved, and API Monitoring tracks the health and uptime of every connection so problems are visible early. ### Who uses PolicyIQ | Gateway? Technology teams at brokerages, insurers and insurtech companies use Gateway to connect their systems to insurers and service providers without building each integration from scratch. Every PolicyIQ product also connects through Gateway, which is how PolicyIQ | One reaches insurer systems and how PolicyIQ | Assist reaches WhatsApp. Partners building on PolicyIQ start from Developer Resources. ### How PolicyIQ | Gateway connects the PolicyIQ family Gateway is the integration layer underneath every PolicyIQ product. PolicyIQ | One's claims and insurer coordination, PolicyIQ | Extract's OCR API, PolicyIQ | Match's Comparison API and PolicyIQ | Assist's WhatsApp and website channels all connect through it, so data moves between products and partners consistently. ### Getting started with PolicyIQ | Gateway PolicyIQ | Gateway is cloud-based and supported remotely. Technical teams start from Developer Resources, connect to the standard Insurance API Integration pattern, then add insurer, KYC, payment and communication integrations as they need them. ### Further reading [Insurance APIs and Integrations Understanding Insurance API Integration How insurance API integration connects agencies to insurers, KYC, payment and messaging services, explained simply. Read the article](https://policyiq.in/blog/insurance-apis/understanding-insurance-api-integration/)[Insurance APIs and Integrations Choosing an Insurance API Integration Partner What to ask an insurance API integration partner about coverage, reliability, monitoring, security and support before you commit. Read the article](https://policyiq.in/blog/insurance-apis/choosing-an-insurance-api-integration-partner/) - [Glossary: what is an API gateway?](https://policyiq.in/glossary/#api-gateway) - [Glossary: what is CKYC?](https://policyiq.in/glossary/#ckyc) Frequently asked questions ### Your questions, answered **Q: What does PolicyIQ | Gateway connect to?** A: PolicyIQ | Gateway's insurtech API gateway architecture connects PolicyIQ products with insurer systems, KYC and payment services, and communication APIs. **Q: Is PolicyIQ | Gateway only for PolicyIQ products?** A: No. PolicyIQ | Gateway works as core insurance system integration middleware: an open insurance API platform other PolicyIQ products connect through, but also how an agency's or insurer's own systems connect to insurer, KYC, payment and communication APIs. **Q: How is integration uptime monitored?** A: API Monitoring tracks integration health and uptime across connected systems, so issues with a connected API are visible rather than discovered downstream. **Q: Does PolicyIQ | Gateway handle premium payments?** A: Yes. Payment APIs connect payment services for premium collection and payouts, alongside the KYC and insurer connections Gateway already provides. **Q: Can PolicyIQ | Gateway connect messaging and notification channels?** A: Yes. Communication APIs connect SMS, email and messaging services to customer and agent workflows, so notifications can be triggered directly from connected systems. **Q: Does PolicyIQ | Gateway use a standard integration pattern?** A: Yes. One standard pattern is used across every connected partner, so each new integration works the same way. **Q: Is there documentation for developers?** A: Yes. Developer Resources document the standard Insurance API Integration pattern and each specific integration: insurer, KYC, payment and communication. **Q: Can PolicyIQ | Gateway verify customer identity during onboarding?** A: Yes. KYC Verification APIs build identity verification into the onboarding flow rather than leaving it as a separate manual step. [Read: Understanding Insurance API Integration](https://policyiq.in/blog/insurance-apis/understanding-insurance-api-integration/) ## Insurance API Monitoring & Uptime (PolicyIQ | Gateway) URL: https://policyiq.in/products/gateway/api-monitoring/ PolicyIQ | Gateway ## Insurance API Monitoring & Uptime API Monitoring tracks integration health and uptime across every system connected through PolicyIQ | Gateway, so issues are visible rather than discovered downstream. An integration failure with an insurer, KYC, payment or communication provider can quietly break a workflow if it isn't visible. API Monitoring watches Insurer API Integration, KYC Verification APIs, Payment APIs and Communication APIs alike for health and uptime. Without monitoring, the first sign of an integration problem is often a person noticing something didn't happen: a reminder that never sent, a payment that never posted. API Monitoring is what turns that into something noticed immediately, at the connection level, rather than downstream after the fact. ### Integrations that fail quietly until a customer complains - Integration failures going unnoticed until they cause a downstream problem - No single view of health across every connected partner - Difficulty knowing whether an issue is on PolicyIQ's side or a partner's - Slow response to partner outages without visibility ### One health view across every Gateway connection This is the operational-continuity layer sitting across every other PolicyIQ | Gateway capability, rather than a feature specific to one integration. Every connection described in Insurer API Integration, KYC Verification APIs, Payment APIs and Communication APIs is tracked here. ### Uptime tracking for insurer, KYC, payment and messaging links - Health and uptime tracking across every connected integration - Visibility into insurer, KYC, payment and communication connections alike - Early indication of partner-side issues - A foundation for faster response to integration problems ### What faster detection of integration issues changes - Faster detection of integration issues - Clearer accountability between PolicyIQ | Gateway and partner systems - Fewer downstream problems caused by silent integration failures ### How Insurance API Monitoring & Uptime works - Watch every integration: Health and uptime are tracked across every integration connected through PolicyIQ | Gateway. - Cover all connection types: Insurer, KYC, payment and communication connections are all visible in the same way. - Spot partner-side issues early: Early indication of partner-side issues makes problems visible before they are discovered downstream. - Respond faster: That visibility is the foundation for a faster response to integration problems. ### Who needs to know when an integration breaks Integration monitoring matters to technology and operations teams who depend on integrations with insurers and service providers, and to the business teams whose renewals, payments and onboarding rely on those connections working. ### A stuck renewal is often the first sign of a failed integration When an insurer, KYC, payment or messaging integration fails quietly, the first sign is often a customer complaint or a stuck renewal. Indian insurance businesses connect to many partners, so silent failures multiply. Insurance API monitoring makes integration health visible, so issues are noticed and handled sooner. ### Example: a payment connection that failed overnight Imagine a payment provider's connection failing quietly overnight, with the first sign being customers who could not pay their renewal premiums. With PolicyIQ | Gateway, health and uptime are tracked across every integration connected through PolicyIQ | Gateway, including insurer, KYC, payment and communication connections, and early indication of partner-side issues makes the problem visible quickly, so the team can respond before it affects many customers. ### Getting started with PolicyIQ | Gateway PolicyIQ | Gateway is the integration layer behind every PolicyIQ product, set up and supported remotely. Technical teams start from the developer documentation and connect once to the standard integration layer; every connection added through it is then tracked for health and uptime. ### Related PolicyIQ | Gateway capabilities - [PolicyIQ | Gateway Insurer API Integration One of the connections this monitors](https://policyiq.in/products/gateway/insurer-api-integration/) - [PolicyIQ | Gateway Developer Resources Documentation for integrating teams](https://policyiq.in/products/gateway/developer-resources/) - [PolicyIQ | Gateway PolicyIQ | Gateway Overview Every PolicyIQ | Gateway capability in one place](https://policyiq.in/products/gateway/) ### Frequently asked questions **Q: What does insurance API monitoring track?** A: It tracks the health and uptime of every integration connected through PolicyIQ | Gateway, across insurer, KYC, payment and communication APIs. **Q: Does monitoring fix issues automatically?** A: It provides visibility into integration health. **Q: Which integrations are monitored?** A: Every integration connected through PolicyIQ | Gateway, including insurer, KYC, payment and communication connections. **Q: How does monitoring help the business?** A: Problems become visible early instead of being discovered downstream as stuck renewals, failed payments or missing messages. **Q: Can it show partner-side issues?** A: Yes. It gives early indication of partner-side issues. ## Insurance Communication APIs for SMS and Email URL: https://policyiq.in/products/gateway/communication-apis/ PolicyIQ | Gateway ## Insurance Communication APIs for SMS and Email Communication APIs connect SMS, email and messaging services to customer and agent workflows, so reminders and updates reach people through the channels they actually use. Renewal reminders, claim updates and agent notifications all depend on reliable delivery. Communication APIs apply PolicyIQ | Gateway's standard integration layer to messaging providers, supporting features like PolicyIQ | One's Renewal Management and PolicyIQ | Assist's WhatsApp and website integration. A reminder that never reaches the customer is functionally the same as no reminder at all. Connecting communication channels through a monitored, standardised layer means delivery failures are visible rather than a silent gap somewhere in the workflow. ### Reminders and updates sent from too many separate tools - Renewal reminders and updates sent inconsistently across channels - No single system managing SMS, email and messaging delivery - Delivery failures going unnoticed - Difficulty reaching customers on the channel they actually use ### Message delivery tracked like every other integration Message delivery is tracked by API Monitoring alongside every other integration, so a provider outage is visible rather than silently causing missed reminders. This is the same communication layer [PolicyIQ | Assist's WhatsApp & Website Integration](https://policyiq.in/products/assist/whatsapp-and-website-integration/) connects through. ### SMS, email and messaging providers behind one connection - Standardised connections to SMS, email and messaging providers - A single integration point for renewal, claims and general communication - Consistent handling regardless of which channel or provider is used - Monitoring of message delivery health ### What reliable reminder delivery changes - More reliable delivery of reminders and updates - Communication reaching customers on their preferred channel - Less manual work coordinating multiple communication tools ### How Insurance Communication APIs for SMS and Email works - Connect channels: Standardised connections are made to SMS, email and messaging providers. - Use one integration point: Renewal, claims and general communication go through a single integration point. - Handle every channel consistently: Messages are handled consistently whichever channel or provider is used. - Monitor delivery: Message delivery health is monitored. ### Who sends renewal reminders and claims updates at scale In PolicyIQ | Gateway, these are used by agencies, insurers and insurtech companies that send renewal reminders, claims updates and other notifications to customers and agents, and by PolicyIQ products that communicate through PolicyIQ | Gateway. ### Reaching Indian customers on SMS and the apps they already use Customers and agents in India respond fastest on the channels they already use, especially SMS and messaging apps. Sending renewal and claims updates from separate tools makes communication inconsistent and hard to track. Insurance communication APIs give one integration point for every channel, so messages are consistent and delivery is monitored. ### Example: renewal SMS, claims emails and notices from one integration Imagine an agency sending renewal reminders by SMS from one tool, claims updates by email from another and general notices from a third. With PolicyIQ | Gateway, renewal, claims and general communication go through a single integration point with standardised connections to SMS, email and messaging providers. Messages are handled consistently whichever channel is used, and message delivery health is monitored. ### Getting started with PolicyIQ | Gateway PolicyIQ | Gateway is the integration layer behind every PolicyIQ product, set up and supported remotely. Technical teams start from the developer documentation, connect once to the standard integration layer, and add this connection without building a separate integration for each partner. ### Related PolicyIQ | Gateway capabilities - [PolicyIQ | Gateway API Monitoring Delivery health for these connections](https://policyiq.in/products/gateway/api-monitoring/) - [PolicyIQ | Assist WhatsApp & Website Integration A workflow built on this API](https://policyiq.in/products/assist/whatsapp-and-website-integration/) - [PolicyIQ | Gateway PolicyIQ | Gateway Overview Every PolicyIQ | Gateway capability in one place](https://policyiq.in/products/gateway/) ### Frequently asked questions **Q: Can insurance communication APIs send WhatsApp messages?** A: It's designed to support common channels including SMS, email and messaging platforms. **Q: Which PolicyIQ features send messages through these APIs?** A: PolicyIQ | One's renewal reminders and PolicyIQ | Assist's WhatsApp & Website Integration both rely on this same communication layer. **Q: What kinds of messages can be sent?** A: Renewal, claims and general communication can all go through the same integration point. **Q: Is message delivery monitored?** A: Yes. Message delivery health is monitored. **Q: Is every channel handled the same way?** A: Yes. Handling is consistent regardless of which channel or provider is used. ## Developer Resources for Insurance APIs (PolicyIQ | Gateway) URL: https://policyiq.in/products/gateway/developer-resources/ PolicyIQ | Gateway ## Developer Resources for Insurance APIs Developer Resources provide documentation and reference material for teams building on PolicyIQ | Gateway, covering how to connect to insurer, KYC, payment and communication APIs. A team integrating their own systems with PolicyIQ | Gateway needs clear reference material rather than reverse-engineering each connection. Developer Resources documents the standard Insurance API Integration pattern and each specific integration built on it. Good reference material shortens the time between deciding to integrate and actually having a working connection, and reduces the number of avoidable mistakes made along the way. This is where that reference material is intended to live for teams building on PolicyIQ | Gateway. ### Integrating without documentation means trial and error - No clear documentation for teams integrating with PolicyIQ | Gateway - Reverse-engineering integration patterns through trial and error - Inconsistent understanding of what each API expects - Slower integration timelines without reference material ### Documentation for every Gateway integration Every specific integration (Insurer, KYC, Payment and Communication APIs) is documented here, alongside the general Insurance API Integration pattern. ### Integration patterns and reference material per API - Documentation for the standard Insurance API Integration pattern - Reference material for each specific integration (insurer, KYC, payment, communication) - A single place for integrating teams to start - Guidance intended to be kept current as PolicyIQ | Gateway evolves ### What clear reference material saves integrating teams - Faster integration for teams building on PolicyIQ | Gateway - Fewer integration mistakes from unclear expectations - A consistent reference point for every connected system ### How Developer Resources for Insurance APIs works - Start in one place: Integrating teams begin from a single place for PolicyIQ | Gateway documentation. - Learn the standard pattern: Documentation explains the standard Insurance API Integration pattern. - Go deeper per integration: Reference material covers each specific integration: insurer, KYC, payment and communication. - Stay current: Guidance is intended to be kept current as PolicyIQ | Gateway evolves. ### Who integrates with PolicyIQ | Gateway The documentation is for developers and technical teams at agencies, insurers, insurtech companies and partners who are connecting their systems to PolicyIQ | Gateway or building on it. ### Fewer errors when insurance integrations start from clear docs Integration work goes faster and produces fewer errors when developers have clear reference material from the start. For Indian insurance businesses connecting to several insurers and service providers, one consistent set of developer resources for insurance APIs reduces the learning curve for every new connection. ### Example: a partner's developer connecting to Gateway Imagine a developer at a partner company asked to connect their system to PolicyIQ | Gateway. Instead of piecing together information from emails, they start from Gateway's documentation for the standard Insurance API Integration pattern, then reference material for each specific integration they need, insurer, KYC, payment or communication. Because the guidance is intended to be kept current as PolicyIQ | Gateway evolves, the same resources help with later integrations too. ### Getting started with PolicyIQ | Gateway PolicyIQ | Gateway is the integration layer behind every PolicyIQ product, set up and supported remotely. Technical teams start here, connect once to the standard integration layer, and add each insurer, KYC, payment or messaging connection without building a separate integration for each partner. ### Related PolicyIQ | Gateway capabilities - [PolicyIQ | Gateway Insurance API Integration The standard pattern documented here](https://policyiq.in/products/gateway/insurance-api-integration/) - [PolicyIQ | Gateway API Monitoring Operational visibility for integrations built here](https://policyiq.in/products/gateway/api-monitoring/) - [PolicyIQ | Gateway PolicyIQ | Gateway Overview Every PolicyIQ | Gateway capability in one place](https://policyiq.in/products/gateway/) ### Frequently asked questions **Q: Who are the insurance API docs for?** A: Teams at agencies, insurers or insurtechs building an integration with PolicyIQ | Gateway. **Q: What does the developer documentation cover?** A: Documentation for the standard Insurance API Integration pattern and reference material for each specific integration: insurer, KYC, payment and communication. **Q: Is the documentation kept up to date?** A: Guidance is intended to be kept current as PolicyIQ | Gateway evolves. **Q: Where should an integrating team start?** A: Developer Resources provide a single place for integrating teams to start. ## Insurance API Integration Layer (PolicyIQ | Gateway) URL: https://policyiq.in/products/gateway/insurance-api-integration/ PolicyIQ | Gateway ## Insurance API Integration Layer Insurance API Integration is the standardised layer PolicyIQ | Gateway provides for connecting PolicyIQ products and outside systems, underlying the more specific integrations for insurers, KYC, payments and communication. Rather than each PolicyIQ product or outside system building its own connection logic, Insurance API Integration provides one standard pattern that Insurer API Integration, KYC Verification APIs, Payment APIs and Communication APIs each build on. Every partner an agency or insurer connects to (an insurer system, a KYC provider, a payment processor) exposes its own API with its own quirks. Without a shared pattern, each connection becomes a one-off project; with one, adding a new partner becomes a smaller, more predictable piece of work. ### Every insurer, KYC and payment partner speaks a different API - Every insurer, KYC and payment partner exposes a different API - Building a separate integration for each partner is slow to build and maintain - No consistent pattern for how systems exchange data - Partner API changes break integrations built without a shared layer ### The layer that monitoring and documentation build on This general integration layer is what API Monitoring watches for health and uptime, and what Developer Resources documents for teams building against it. Every other PolicyIQ | Gateway capability (insurer, KYC, payment and communication connections) is a specific application of this same standard pattern. ### One standard pattern and one connection point for every partner - A standard integration pattern used across every connected partner - A single connection point instead of one per partner - The foundation for Insurer, KYC, Payment and Communication APIs - Consistent data exchange regardless of which partner is on the other end ### What fewer, more maintainable integrations change - Fewer, more maintainable integrations - Faster onboarding of new partners - Less risk from partner-side API changes ### How Insurance API Integration Layer works - Connect once: A system connects to PolicyIQ | Gateway's single connection point instead of building one integration per partner. - Use one standard pattern: The same integration pattern is used across every connected partner. - Exchange data consistently: Data is exchanged consistently whichever partner is on the other end. - Build specific integrations on top: Insurer, KYC, Payment and Communication APIs are built on this foundation. ### Who needs systems connected to many outside services In PolicyIQ | Gateway, this capability is used by technology teams at agencies, insurers and insurtech companies who need their systems connected to many outside services, and by PolicyIQ products themselves, which connect to each other and to partners through it. ### Many insurers, KYC services and payment providers, each different Indian insurance businesses connect to many insurers, KYC services, payment providers and messaging channels, each with its own format and behaviour. Building every connection separately multiplies the work and the points of failure. An insurance API integration layer with one standard pattern makes adding and maintaining connections far simpler. ### Example: connecting insurers, KYC, payments and messaging once Imagine an agency that wants to connect to several insurers, a KYC service, a payment provider and a messaging service. Building each connection separately would mean many formats and failure points to maintain. With PolicyIQ | Gateway, the agency's system connects once to PolicyIQ | Gateway's single connection point, data is exchanged in the same consistent way whichever partner is involved, and the specific Insurer, KYC, Payment and Communication APIs build on that one standard pattern. ### Getting started with PolicyIQ | Gateway PolicyIQ | Gateway is the integration layer behind every PolicyIQ product, set up and supported remotely. Technical teams start from the developer documentation, connect once to this standard layer, and add insurer, KYC, payment and messaging connections without building a separate integration for each partner. ### Related PolicyIQ | Gateway capabilities - [PolicyIQ | Gateway Insurer API Integration The insurer-specific application of this layer](https://policyiq.in/products/gateway/insurer-api-integration/) - [PolicyIQ | Gateway Developer Resources Documentation for building on this layer](https://policyiq.in/products/gateway/developer-resources/) - [PolicyIQ | Gateway PolicyIQ | Gateway Overview Every PolicyIQ | Gateway capability in one place](https://policyiq.in/products/gateway/) ### Frequently asked questions **Q: Why not integrate directly with each partner separately?** A: Direct integrations multiply the number of separate connections a team has to build and maintain; a standard layer means connecting once instead of once per partner. **Q: Does a standard integration layer remove partner-specific work?** A: No, partner-specific details (like Insurer API Integration or KYC Verification APIs) still exist, but they build on this same standard pattern rather than starting from scratch. **Q: What is built on top of the integration layer?** A: PolicyIQ | Gateway's Insurer, KYC, Payment and Communication APIs all build on this standard layer. **Q: Is data exchanged the same way for every partner?** A: Yes. The layer provides consistent data exchange regardless of which partner is on the other end. **Q: Is there documentation for the integration pattern?** A: Developer Resources include documentation for the standard Insurance API Integration pattern. ## Insurer API Integration Software (PolicyIQ | Gateway) URL: https://policyiq.in/products/gateway/insurer-api-integration/ PolicyIQ | Gateway ## Insurer API Integration Software Insurer API Integration connects directly to insurer systems for policy and claims data exchange, so information moves between an agency's tools and an insurer's systems without manual re-entry. Policy issuance and claims coordination both depend on data held in an insurer's own systems. Insurer API Integration applies PolicyIQ | Gateway's standard Insurance API Integration layer specifically to insurer connections, feeding capabilities like PolicyIQ | One's Claims Servicing. Without a direct connection, checking a policy or claim's status against an insurer's own records means logging into a separate portal, or picking up the phone. This is what removes that extra step from the daily workflow. ### Copying policy and claims details from insurer portals - Insurer systems each expose different policy and claims data formats - Manual lookups against insurer portals slow down servicing - No real-time visibility into insurer-side policy or claims status - Switching insurers means rebuilding integration work ### Insurer connections monitored alongside everything else This connection is monitored by API Monitoring alongside every other integration, so an insurer-side outage is visible rather than silently causing failed lookups elsewhere. See how this connection supports claims coordination on [PolicyIQ | One's Claims Servicing](https://policyiq.in/products/one/claims-servicing/) page. ### Standard connections to insurer policy and claims systems - Standardised connections to insurer policy and claims systems - Real-time (or near real-time) data exchange for policy and claims data - A consistent integration pattern regardless of which insurer is connected - Monitoring of insurer-side connection health ### What less portal work changes for servicing teams - Faster policy and claims data exchange - Less manual lookup work against insurer portals - Easier onboarding of new insurer connections ### How Insurer API Integration Software works - Connect to the insurer: A standardised connection is made to the insurer's policy and claims systems. - Exchange policy and claims data: Policy and claims data moves in real time or near real time instead of being re-entered by hand. - Keep one pattern: The same integration pattern is used whichever insurer is connected. - Monitor the connection: Insurer-side connection health is monitored, so problems are noticed early. ### Who places business with several insurers In PolicyIQ | Gateway, this capability is used by agencies and insurtech companies that place business with several insurers and want policy and claims data to flow between their tools and insurer systems without manual re-entry. ### Many insurers, many portals: the Indian agency's daily problem Indian insurance agencies commonly work with many insurers, and logging into each insurer portal to copy policy and claims details is slow and error-prone. Insurer API integration with one standard pattern moves that data directly, keeps records consistent and makes it easier to add insurers over time. ### Example: a servicing team that no longer logs into every portal Imagine a servicing team that copies policy and claims details from several insurer portals into the agency's own system every day. With PolicyIQ | Gateway, a standardised connection to each insurer's policy and claims systems exchanges that data in real time or near real time, using the same integration pattern whichever insurer is involved, and insurer-side connection health is monitored, so problems are noticed early rather than discovered in a customer call. ### Getting started with PolicyIQ | Gateway PolicyIQ | Gateway is the integration layer behind every PolicyIQ product, set up and supported remotely. Technical teams start from the developer documentation, connect once to the standard integration layer, and add this connection without building a separate integration for each partner. ### Related PolicyIQ | Gateway capabilities - [PolicyIQ | Gateway Insurance API Integration The standard layer this builds on](https://policyiq.in/products/gateway/insurance-api-integration/) - [PolicyIQ | Gateway API Monitoring Health and uptime for this connection](https://policyiq.in/products/gateway/api-monitoring/) - [PolicyIQ | Gateway PolicyIQ | Gateway Overview Every PolicyIQ | Gateway capability in one place](https://policyiq.in/products/gateway/) ### Frequently asked questions **Q: Can it connect to any insurer?** A: It applies PolicyIQ | Gateway's standard integration pattern to insurer connections. **Q: What happens if an insurer's API changes?** A: Changes are isolated to that specific connection rather than affecting every other integration, and API Monitoring surfaces any resulting issues. **Q: What policy and claims data is exchanged with insurers?** A: Policy and claims data, exchanged in real time or near real time. **Q: Is the insurer connection monitored?** A: Yes. Insurer-side connection health is monitored through PolicyIQ | Gateway. **Q: Does each insurer need a different integration approach?** A: No. A consistent integration pattern is used regardless of which insurer is connected. ## KYC Verification APIs for Insurance (PolicyIQ | Gateway) URL: https://policyiq.in/products/gateway/kyc-verification-apis/ PolicyIQ | Gateway ## KYC Verification APIs for Insurance KYC Verification APIs connect identity verification services into insurance workflows, so a customer's identity can be verified as part of onboarding rather than as a separate manual step. Insurance onboarding requires identity verification before a policy can be issued. KYC Verification APIs apply PolicyIQ | Gateway's standard integration layer to identity verification providers, alongside Payment APIs for the payment side of onboarding. Handling identity verification outside the main onboarding flow (a separate form, a separate system, a manual check) adds friction for the customer and extra work for the team processing it. Built into the flow, verification becomes one connected step instead of a detour. ### Manual identity checks that slow onboarding - Identity verification handled manually or inconsistently at onboarding - Multiple KYC providers with different integration requirements - Onboarding delays while verification is completed separately - Compliance risk from inconsistent verification steps ### KYC provider connections monitored like every integration This connection, like every other integration, is tracked by API Monitoring so verification-provider issues are visible rather than silently blocking onboarding. KYC verification and Payment APIs together cover the two checks most onboarding flows need before a policy can be issued. ### Identity verification inside the onboarding flow - Standardised connections to identity verification providers - Verification as part of the onboarding flow, not a separate step - Consistent handling regardless of which KYC provider is used - Monitoring of verification-provider connection health ### What built-in verification changes for onboarding - Faster, more consistent onboarding - Reduced manual verification work - A clearer compliance trail for identity verification ### How KYC Verification APIs for Insurance works - Start onboarding: A customer begins onboarding in an agency, insurer or partner workflow. - Verify inside the flow: Identity verification runs as part of the onboarding flow, not as a separate manual step. - Use any connected provider: Verification is handled consistently whichever KYC provider is used. - Monitor provider health: The connection to each verification provider is monitored. ### Who onboards insurance customers digitally In PolicyIQ | Gateway, these are used by agencies, insurers and insurtech companies that onboard customers digitally and want identity checks built into their own onboarding journeys. ### Every policy in India needs KYC, and customers expect it online Every insurance policy in India requires KYC, and customers increasingly expect to complete onboarding online. Collecting document copies and checking them separately slows the process and leaves gaps. KYC verification APIs for insurance bring identity checks into the onboarding flow itself, which is faster for customers and more consistent for the business. ### Example: an insurtech verifying identity during sign-up Imagine an insurtech onboarding customers online, collecting identity documents and checking them separately afterwards. With PolicyIQ | Gateway, identity verification runs as part of the onboarding flow itself, through a standardised connection to the verification provider. Verification is handled the same way whichever KYC provider is connected, and the provider connection is monitored, so onboarding is faster for customers and more consistent for the business. ### Getting started with PolicyIQ | Gateway PolicyIQ | Gateway is the integration layer behind every PolicyIQ product, set up and supported remotely. Technical teams start from the developer documentation, connect once to the standard integration layer, and add this connection without building a separate integration for each partner. ### Related PolicyIQ | Gateway capabilities - [PolicyIQ | Gateway Payment APIs The payment side of the same onboarding flow](https://policyiq.in/products/gateway/payment-apis/) - [PolicyIQ | Gateway API Monitoring Health and uptime for this connection](https://policyiq.in/products/gateway/api-monitoring/) - [PolicyIQ | Gateway PolicyIQ | Gateway Overview Every PolicyIQ | Gateway capability in one place](https://policyiq.in/products/gateway/) ### Frequently asked questions **Q: Is KYC verification built into the onboarding flow?** A: Yes, KYC Verification APIs are designed to be part of onboarding rather than a separate manual step afterwards. **Q: Does it matter which KYC provider is used?** A: Verification is handled consistently regardless of which KYC provider is connected. **Q: Is the KYC provider connection monitored?** A: Yes. Verification-provider connection health is monitored. **Q: Can KYC checks reduce fraud risk?** A: Verifying identity properly at onboarding closes one of the main gaps identity-related fraud relies on. ## Insurance Payment APIs for Premiums (PolicyIQ | Gateway) URL: https://policyiq.in/products/gateway/payment-apis/ PolicyIQ | Gateway ## Insurance Payment APIs for Premiums and Payouts Payment APIs connect payment services for premium collection and payouts, so money movement is part of the same connected workflow as policy issuance and claims. Premium collection at onboarding or renewal, and payouts on claims or commissions, both require reliable payment connections. Payment APIs apply PolicyIQ | Gateway's standard integration layer to payment providers, alongside KYC Verification APIs for identity checks. Payment failures or delays are highly visible to customers and POSPs alike, which makes a reliable, monitored connection more important here than almost anywhere else in the workflow. Payment APIs treats these connections with the same monitoring rigor as every other integration. ### Premiums and payouts handled apart from policy records - Premium collection and payouts handled through disconnected payment tools - Manual reconciliation between payments and policy records - Different payment providers requiring separate integration work - Delayed visibility into payment status ### Payment connections monitored and documented Payment connections are tracked by API Monitoring like every other integration, and documented for integrating teams through Developer Resources. Payment status connected here feeds directly into commission and receivable visibility, such as PolicyIQ | One's Finance Controls. ### Premium collection and payouts through one standard connection - Standardised connections to payment providers for premiums and payouts - Payment status visible alongside policy and commission records - Consistent handling regardless of which payment provider is used - Monitoring of payment-provider connection health ### What less manual payment reconciliation changes - Faster premium collection and payout processing - Less manual reconciliation between payments and records - Clearer visibility into payment status ### How Insurance Payment APIs for Premiums works - Connect a payment provider: A standardised connection is made to a payment provider for premiums and payouts. - Collect premiums and make payouts: Money movement becomes part of the same connected workflow as policy issuance and claims. - See payment status: Payment status is visible alongside policy and commission records. - Monitor the provider: Payment-provider connection health is monitored. ### Who collects premiums online or makes payouts In PolicyIQ | Gateway, these are used by agencies, insurers and insurtech companies that collect premiums online or make payouts, and that want payment status to sit next to the related policy and commission records. ### Online premium payment and lapses: why it matters in India Customers in India increasingly pay insurance premiums online, and a renewal that depends on an inconvenient payment step can lapse. Payment information kept separately from policy records also makes reconciliation harder. Insurance payment APIs for premiums and payouts connect payments to the same workflow and records as the policy. ### Example: renewal premiums matched to policies automatically Imagine an agency sending renewal reminders but collecting premiums through a separate process, then matching payments to policies by hand. With PolicyIQ | Gateway, a standardised connection to a payment provider handles premium collection and payouts within the same connected workflow, payment status is visible alongside the policy and commission records, and the payment-provider connection is monitored for problems. ### Getting started with PolicyIQ | Gateway PolicyIQ | Gateway is the integration layer behind every PolicyIQ product, set up and supported remotely. Technical teams start from the developer documentation, connect once to the standard integration layer, and add this connection without building a separate integration for each partner. ### Related PolicyIQ | Gateway capabilities - [PolicyIQ | Gateway KYC Verification APIs Identity checks alongside payments](https://policyiq.in/products/gateway/kyc-verification-apis/) - [PolicyIQ | Gateway Developer Resources Documentation for this integration](https://policyiq.in/products/gateway/developer-resources/) - [PolicyIQ | Gateway PolicyIQ | Gateway Overview Every PolicyIQ | Gateway capability in one place](https://policyiq.in/products/gateway/) ### Frequently asked questions **Q: Can insurance payment APIs handle both premiums and payouts?** A: Yes, it's built to support both premium collection at onboarding or renewal, and payouts such as commissions or claims. **Q: Is payment status visible with the policy?** A: Yes. Payment status is visible alongside policy and commission records. **Q: Does the payment provider affect how payments are handled?** A: No. Payments are handled consistently regardless of which provider is used. **Q: Is the payment connection monitored?** A: Yes. Payment-provider connection health is monitored. ## Insurance Policy Comparison Software (PolicyIQ | Match) URL: https://policyiq.in/products/match/ PolicyIQ | Match ## Insurance policy comparison software for policies and datasets PolicyIQ | Match is insurance policy comparison software that compares policies or datasets and instantly identifies differences and changes, replacing manual side-by-side review. [Book a demo](https://policyiq.in/request-demo/)Explore capabilities ### Policy Version Comparison and Coverage Gaps Compares policies, versions and datasets and lists exactly what changed. PolicyIQ | Match compares insurance policies, datasets and policy versions, instantly identifying additions, removals and modifications instead of requiring manual side-by-side review. ### What problem does PolicyIQ | Match solve? Comparing two policy wordings, a renewed policy against its previous version, or two large datasets by eye is slow and easy to get wrong. PolicyIQ | Match applies structured comparison so differences are surfaced clearly and consistently. ### What capabilities does PolicyIQ | Match include? Six capabilities cover comparison from individual policies through to large datasets and version history. **Insurance Policy Comparison** Compares two or more policies and highlights differences. [Explore Insurance Policy Comparison](https://policyiq.in/products/match/insurance-policy-comparison/) **Insurance Dataset Comparison** Compares structured insurance datasets for differences at scale. [Explore Insurance Dataset Comparison](https://policyiq.in/products/match/insurance-dataset-comparison/) **Policy Change Detection** Detects what changed between two versions of the same policy. [Explore Policy Change Detection](https://policyiq.in/products/match/policy-change-detection/) **Coverage Difference Analysis** Breaks down coverage, condition and wording differences specifically. [Explore Coverage Difference Analysis](https://policyiq.in/products/match/coverage-difference-analysis/) **Policy Version Comparison** Compares successive versions of a policy over its lifetime. [Explore Policy Version Comparison](https://policyiq.in/products/match/policy-version-comparison/) **Comparison API** Connects policy and dataset comparison into existing systems. [Explore Comparison API](https://policyiq.in/products/match/comparison-api/) ### How does PolicyIQ | Match fit with the rest of PolicyIQ? #### Works from structured data Comparison quality depends on structured input, such as data from PolicyIQ | Extract. #### Connected via API The Comparison API connects results into an agency's or insurer's own systems. ### Why insurance policy comparison software beats manual review Comparing insurance policies by eye is slow and unreliable. Policy wordings run to many pages, every insurer formats them differently, and the differences that matter, a condition, an exclusion, a changed sum insured, are easy to miss. The same problem applies to renewals and endorsements, where a few changed lines hide inside a long document, and to data, where a migration or partner file can quietly drop or alter records. PolicyIQ | Match compares two or more policies side by side with consistent logic, detects exactly what changed between versions of the same policy, explains differences by coverage, condition and wording, and compares whole datasets record by record. ### Who uses PolicyIQ | Match? POSP agents and agencies use it to help customers choose between policies and to check renewal terms. Servicing and compliance teams use Policy Change Detection and Policy Version Comparison to review what changed over a policy's life. Operations and data teams at agencies, insurers and insurtechs use Dataset Comparison and the Comparison API to reconcile records between systems. ### How PolicyIQ | Match connects with other PolicyIQ products PolicyIQ | Match can compare data extracted from documents by PolicyIQ | Extract, connected through PolicyIQ | Gateway, and the Comparison API lets agency and insurer systems run comparisons programmatically. ### Getting started with PolicyIQ | Match PolicyIQ | Match is cloud-based and set up remotely. Teams can use it within PolicyIQ, or developers can run policy and dataset comparisons inside their own systems through the Comparison API. ### Further reading [Fraud Detection and Risk Common Fraud Patterns in Claims and Policy Issuance Common fraud patterns in insurance claims and policy issuance, and the everyday checks that help agencies and insurers spot them. Read the article](https://policyiq.in/blog/fraud-detection/common-fraud-patterns-in-insurance-claims-and-policy-issuance/)[Fraud Detection and Risk Fraud Risk in Manual Insurance Workflows The points in manual insurance workflows where fraud risk hides, from unchecked data to unverified identities. Read the article](https://policyiq.in/blog/fraud-detection/where-fraud-risk-shows-up-in-manual-insurance-workflows/) - [Glossary: what is coverage gap analysis?](https://policyiq.in/glossary/#coverage-gap-analysis) - [Glossary: what is data reconciliation?](https://policyiq.in/glossary/#data-reconciliation) Frequently asked questions ### Your questions, answered **Q: What can PolicyIQ | Match compare?** A: PolicyIQ | Match is a policy dataset matching tool that compares insurance policies, structured datasets, and successive versions of the same policy, identifying additions, removals and modifications between them. **Q: Can PolicyIQ | Match connect to existing systems?** A: Yes. The Comparison API connects PolicyIQ | Match into an agency's or insurer's existing systems for batch insurance data reconciliation, instead of using it only as a standalone tool. **Q: Does PolicyIQ | Match explain coverage differences specifically?** A: Yes. Coverage Difference Analysis functions as automated insurance policy audit software, breaking down coverage, condition and wording differences: an insurance coverage gap analysis rather than a simple 'two documents differ' flag. **Q: Can PolicyIQ | Match detect what changed between two versions of a policy?** A: Yes. Policy Change Detection identifies what changed between two versions of the same policy, and Policy Version Comparison extends this across a policy's full version history, not just two snapshots. **Q: Can PolicyIQ | Match compare datasets at scale, not just individual policies?** A: Yes. Insurance Dataset Comparison compares structured insurance datasets for differences at scale, separate from comparing two individual policy documents through Insurance Policy Comparison. **Q: Can PolicyIQ | Match compare policies from different insurers?** A: Yes. Comparison logic is consistent regardless of insurer or product. **Q: Can PolicyIQ | Match show how a policy changed over several years?** A: Yes. Policy Version Comparison compares every version across a policy's full history, not just the latest two. **Q: Is there an API for PolicyIQ | Match?** A: Yes. The Comparison API gives programmatic access to policy and dataset comparison with structured results. ## Insurance Comparison API for Developers (PolicyIQ | Match) URL: https://policyiq.in/products/match/comparison-api/ PolicyIQ | Match ## Insurance Comparison API for Developers The Comparison API connects PolicyIQ | Match's policy and dataset comparison into existing agency or insurer systems, instead of using PolicyIQ | Match only as a standalone tool. An agency or insurer with its own policy administration system can send documents or datasets to PolicyIQ | Match and receive comparison results back programmatically, powering Insurance Policy Comparison, Policy Change Detection and Insurance Dataset Comparison alike. Comparison results that stay locked inside a standalone tool still require someone to move them into wherever they're actually needed. The Comparison API removes that step, so comparison becomes part of an existing system's workflow rather than a side process. ### Comparison results stuck outside your own systems - No easy way to connect comparison results into existing systems - Manual export and review of comparison output - Difficulty running comparisons at scale without a system built for a team - Limited visibility into how comparisons connect to other PolicyIQ products ### How Match connects to Extract and other systems This is also how PolicyIQ | Match connects to other PolicyIQ products, such as comparing data extracted by PolicyIQ | Extract, through PolicyIQ | Gateway. See [PolicyIQ | Gateway](https://policyiq.in/products/gateway/) for how this connects PolicyIQ | Match to other systems. ### Programmatic policy and dataset comparison, structured results - Programmatic access to policy and dataset comparison - Structured comparison results ready for other systems to consume - Connection into PolicyIQ | Extract's structured data via PolicyIQ | Gateway - Support for both individual policy and dataset-scale comparisons ### What removing manual export and review changes - Comparison embedded directly into existing workflows - No manual export or review step required - Comparison that scales beyond what manual review supports ### How Insurance Comparison API for Developers works - Send policies or datasets: An agency, insurer or partner system sends policies or datasets for comparison programmatically. - Run the comparison: PolicyIQ | Match compares them, for individual policies or at dataset scale. - Receive structured results: Structured comparison results come back ready for other systems to use. - Combine with extraction: Data extracted by PolicyIQ | Extract can connect in through PolicyIQ | Gateway. ### Developers building comparison into their own platforms In PolicyIQ | Match, this capability is used by developers and technology teams at agencies, insurers and insurtech companies who want policy and dataset comparison inside their own systems. ### Bringing comparison into platforms Indian insurers already run Many Indian insurance businesses already run their own platforms. An insurance comparison API brings PolicyIQ | Match's comparison into those platforms directly, so comparisons and reconciliations run inside existing workflows without manual exports. ### Example: every partner data file checked automatically Imagine an insurer that wants every incoming partner data file checked against its own records automatically. With the Comparison API, its system sends the datasets for comparison programmatically and receives structured results, the additions, removals and modifications, ready for other systems to act on. The same API handles individual policy comparisons, and it can work with data extracted by PolicyIQ | Extract through PolicyIQ | Gateway. ### Getting started with PolicyIQ | Match PolicyIQ | Match is cloud-based and set up remotely. Teams can use the Comparison API within PolicyIQ, or developers can run the same comparison inside their own systems through the Comparison API, including on data extracted by PolicyIQ | Extract. ### Related PolicyIQ | Match capabilities - [PolicyIQ | Match Insurance Dataset Comparison Large-scale comparisons via this API](https://policyiq.in/products/match/insurance-dataset-comparison/) - [PolicyIQ | Gateway PolicyIQ | Gateway Connects PolicyIQ | Match to other systems](https://policyiq.in/products/gateway/) - [PolicyIQ | Match PolicyIQ | Match Overview Every PolicyIQ | Match capability in one place](https://policyiq.in/products/match/) ### Frequently asked questions **Q: What does an insurance comparison API return?** A: Structured comparison results (additions, removals and modifications) in a format other systems can consume directly. **Q: Can the Comparison API use data extracted by PolicyIQ | Extract?** A: Yes, structured data from PolicyIQ | Extract can feed directly into comparisons run through this API, via PolicyIQ | Gateway. **Q: Does it handle datasets as well as policies?** A: Yes. It supports both individual policy and dataset-scale comparisons. **Q: Are results structured?** A: Yes. Results are structured and ready for other systems to consume. **Q: Can it work with extracted document data?** A: Yes. It can connect to PolicyIQ | Extract's structured data via PolicyIQ | Gateway. ## Insurance Coverage Difference Analysis (PolicyIQ | Match) URL: https://policyiq.in/products/match/coverage-difference-analysis/ PolicyIQ | Match ## Insurance Coverage Difference Analysis Coverage Difference Analysis breaks down coverage, condition and wording differences between policies specifically, rather than only flagging that two documents differ. Knowing that two policies differ isn't as useful as knowing what actually changed in coverage terms. Coverage Difference Analysis takes the output of Insurance Policy Comparison or Policy Change Detection and explains it in coverage, condition and wording terms. A raw list of textual differences between two documents still requires someone with insurance expertise to interpret what it means for the customer. Coverage Difference Analysis is aimed at closing that gap, translating a comparison result into a coverage-level explanation. ### Knowing policies differ isn't knowing what it means - Knowing two documents differ doesn't explain what it means for coverage - Wording and condition changes buried in dense policy language - Difficulty communicating coverage impact to a customer - Reviewers needing to manually interpret raw comparison output ### The interpretive layer on top of comparison results This is the interpretive layer on top of raw comparison results, making Insurance Policy Comparison and Policy Change Detection useful to someone assessing what a difference actually means. Works from the same comparison output as Insurance Policy Comparison and Policy Change Detection, adding interpretation rather than a new comparison step. ### Differences broken down by coverage, condition and wording - A breakdown of differences specifically by coverage, condition and wording - Interpretation of what a comparison result actually means - Input drawn from Insurance Policy Comparison and Policy Change Detection - Output suited for both internal review and customer-facing explanation ### What clearer coverage explanations change - Clearer understanding of what a difference means for coverage - Faster, more confident customer conversations about changes - Less manual interpretation of raw comparison results ### How Insurance Coverage Difference Analysis works - Take the comparison result: Input comes from Insurance Policy Comparison and Policy Change Detection. - Break down differences: Differences are broken down specifically by coverage, condition and wording. - Interpret the result: The analysis explains what a comparison result actually means. - Use it internally or with customers: The output suits internal review and customer-facing explanation. ### Who explains policy differences to customers In PolicyIQ | Match, this capability is used by agencies and advisers explaining policy differences to customers, by servicing teams reviewing what changed at renewal, and by insurer teams reviewing coverage across policy versions. ### Customers need to know whether a difference affects their cover Knowing that two policies differ is not enough; customers need to know whether the difference affects their cover. In India's varied insurance market, conditions and wording can change what a claim will pay. Insurance coverage difference analysis turns raw differences into an explanation people can act on. ### Example: two motor policies, and whether the difference matters Imagine an agency that has found that two motor policies differ, but needs to explain to the customer whether the difference actually affects their cover. Coverage Difference Analysis takes the comparison result and breaks the differences down by coverage, condition and wording, explaining what each one means. The output works for the agency's own review and for a clear, customer-facing explanation. ### Getting started with PolicyIQ | Match PolicyIQ | Match is cloud-based and set up remotely. Teams can use it within PolicyIQ, or developers can run the same comparison inside their own systems through the Comparison API, including on data extracted by PolicyIQ | Extract. ### Related PolicyIQ | Match capabilities - [PolicyIQ | Match Insurance Policy Comparison The comparison this analyses](https://policyiq.in/products/match/insurance-policy-comparison/) - [PolicyIQ | Match Policy Change Detection Changes this explains in coverage terms](https://policyiq.in/products/match/policy-change-detection/) - [PolicyIQ | Match PolicyIQ | Match Overview Every PolicyIQ | Match capability in one place](https://policyiq.in/products/match/) ### Frequently asked questions **Q: Does coverage gap analysis replace reading the policy wording?** A: It's designed to make differences easier to understand, not to replace review of the actual policy wording for final decisions. **Q: Where does the analysis get its input?** A: From Insurance Policy Comparison and Policy Change Detection. **Q: Does it only say that documents differ?** A: No. It breaks differences down by coverage, condition and wording and interprets what they mean. **Q: Can the output be shared with customers?** A: The output is suited for both internal review and customer-facing explanation. ## Insurance Dataset Comparison Software (PolicyIQ | Match) URL: https://policyiq.in/products/match/insurance-dataset-comparison/ PolicyIQ | Match ## Insurance Dataset Comparison Software Insurance Dataset Comparison compares structured insurance datasets for differences at scale, beyond comparing a single pair of policies. Operations and underwriting teams sometimes need to compare entire datasets (a book of business before and after a system migration, for example) rather than one policy at a time. Insurance Dataset Comparison applies PolicyIQ | Match's comparison logic at that scale. Manually sampling a handful of records after a migration or bulk update leaves most of the dataset unchecked. Structured comparison across the full dataset is what actually confirms nothing was lost or altered unexpectedly, rather than hoping the sample was representative. ### Checking large datasets by eye, or by sampling - Comparing large datasets by eye isn't practical - Migrations or system changes creating uncertainty about what changed - No structured way to audit differences at scale - Manual sampling that can miss important discrepancies ### The same comparison engine, applied to whole datasets This shares the same underlying comparison engine as Insurance Policy Comparison, and results can be consumed programmatically through the Comparison API for large datasets. Structured data from PolicyIQ | Extract is well suited as an input for large-scale dataset comparisons. ### Additions, removals and changes found at scale - Structured comparison of datasets, not just individual policies - Identification of additions, removals and modifications at scale - The same underlying comparison engine as Insurance Policy Comparison - Programmatic access via the Comparison API for large datasets ### What full-dataset reconciliation changes after a migration - Reliable comparison at a scale manual review can't match - Faster audits after migrations or system changes - Fewer missed discrepancies from manual sampling ### How Insurance Dataset Comparison Software works - Load the datasets: Two structured insurance datasets are brought together for comparison. - Compare at scale: The datasets are compared record by record, not just as a pair of policies. - Identify changes: Additions, removals and modifications are identified across the full dataset. - Automate for large volumes: Large datasets can be compared programmatically through the Comparison API. ### Who reconciles records between insurance systems In PolicyIQ | Match, this capability is used by operations and data teams reconciling records between systems, by technology teams checking data after a migration or bulk update, and by insurers and agencies matching their records against partner files. ### Data moves between agency, insurer and partner systems constantly Insurance businesses in India move data between agency systems, insurer files and partner platforms all the time. Sampling a few records after a migration leaves most of the dataset unchecked. Insurance dataset comparison across every record confirms nothing was lost or altered. ### Example: checking every record after a system migration Imagine an agency migrating many policy records from an old system to a new one. Spot-checking a sample leaves most of the records unchecked. With Insurance Dataset Comparison, the old and new datasets are compared record by record, and additions, removals and modifications are identified across the whole dataset, using the same comparison engine as policy comparison. For very large datasets, the comparison can run programmatically through the Comparison API. ### Getting started with PolicyIQ | Match PolicyIQ | Match is cloud-based and set up remotely. Teams can use it within PolicyIQ, or developers can run the same comparison inside their own systems through the Comparison API, including on data extracted by PolicyIQ | Extract. ### Related PolicyIQ | Match capabilities - [PolicyIQ | Match Insurance Policy Comparison The same comparison for individual policies](https://policyiq.in/products/match/insurance-policy-comparison/) - [PolicyIQ | Match Comparison API Programmatic access for large datasets](https://policyiq.in/products/match/comparison-api/) - [PolicyIQ | Match PolicyIQ | Match Overview Every PolicyIQ | Match capability in one place](https://policyiq.in/products/match/) ### Frequently asked questions **Q: When would I use this instead of Insurance Policy Comparison?** A: Use Insurance Policy Comparison for individual policies and Insurance Dataset Comparison when comparing larger structured datasets, such as a full book of business. **Q: What does a dataset comparison find?** A: Additions, removals and modifications across structured datasets at scale. **Q: Is it the same engine as policy comparison?** A: Yes. It uses the same underlying comparison engine as Insurance Policy Comparison. **Q: Can large datasets be compared automatically?** A: Yes. Programmatic access is available via the Comparison API. ## Compare Two or More Insurance Policies (PolicyIQ | Match) URL: https://policyiq.in/products/match/insurance-policy-comparison/ PolicyIQ | Match ## Compare Two or More Insurance Policies Side by Side Insurance Policy Comparison compares two or more policies and highlights differences, so an agency or customer can see exactly what separates one policy from another. Choosing between similar policies from different insurers, or checking a renewal against the original, means comparing coverage, conditions and wording line by line. Insurance Policy Comparison does that comparison directly rather than leaving it to manual review. Two policies that look similar on the surface can differ in ways that only matter at claim time: a sub-limit, an exclusion, a condition buried in dense wording. Structured comparison surfaces exactly those differences instead of relying on a reviewer to notice them by chance. ### Line-by-line comparison is slow and easy to get wrong - Comparing two policies line by line is slow and easy to get wrong - Wording differences between insurers are hard to spot manually - No structured way to summarise what's different - Comparisons repeated from scratch for each new pair of policies ### The base comparison behind coverage and version analysis Coverage Difference Analysis breaks the result down specifically by coverage, condition and wording, and Policy Version Comparison applies the same comparison across a policy's history. Comparison quality improves with structured input, such as data already extracted by PolicyIQ | Extract. ### Two or more policies side by side, differences highlighted - Side-by-side comparison of two or more policies - Highlighted differences rather than a raw side-by-side dump - A foundation for Coverage Difference Analysis - Consistent comparison logic regardless of insurer or product ### What faster, more reliable comparison changes - Faster policy comparison - Fewer missed differences between policies - Clearer summaries for customers or internal review ### How Compare Two or More Insurance Policies works - Choose the policies: Two or more policies are selected for comparison. - Compare side by side: The policies are compared side by side with consistent logic, whichever insurer or product they come from. - Highlight differences: Differences are highlighted rather than shown as a raw side-by-side dump. - Go deeper: The comparison feeds Coverage Difference Analysis, which explains differences by coverage, condition and wording. ### Who compares policies for customers and renewals In PolicyIQ | Match, this capability is used by POSP agents and agencies helping customers choose between policies, by servicing teams checking renewal terms, and by insurer and insurtech teams reviewing policy documents. ### Wording differences between insurers matter at claim time Indian customers often compare cover from several insurers, and policy wording differs in ways that matter at claim time. Comparing documents by eye is slow and easy to get wrong. Being able to compare two or more insurance policies with highlighted differences makes advice clearer and faster. ### Example: two insurers' health policies compared side by side Imagine a customer choosing between health policies from two insurers, each with long, differently formatted wording. With PolicyIQ | Match, the agency compares the policies side by side using consistent comparison logic, and the differences are highlighted rather than presented as a raw dump of both documents. For a deeper explanation of what each difference means, the comparison feeds Coverage Difference Analysis. ### Getting started with PolicyIQ | Match PolicyIQ | Match is cloud-based and set up remotely. Teams can use it within PolicyIQ, or developers can run the same comparison inside their own systems through the Comparison API, including on data extracted by PolicyIQ | Extract. ### Related PolicyIQ | Match capabilities - [PolicyIQ | Match Coverage Difference Analysis A detailed breakdown of what differs](https://policyiq.in/products/match/coverage-difference-analysis/) - [PolicyIQ | Match Policy Version Comparison The same comparison across policy history](https://policyiq.in/products/match/policy-version-comparison/) - [PolicyIQ | Match PolicyIQ | Match Overview Every PolicyIQ | Match capability in one place](https://policyiq.in/products/match/) ### Frequently asked questions **Q: How many policies can be compared at once?** A: It's built to compare two or more policies. **Q: Does it work across different insurers?** A: Yes, comparison logic is designed to work consistently regardless of which insurers issued the policies being compared. **Q: Are differences highlighted?** A: Yes. Differences are highlighted rather than presented as a raw side-by-side dump. **Q: Does the comparison logic change by insurer?** A: No. Comparison logic is consistent regardless of insurer or product. **Q: How do I understand what a difference means?** A: Coverage Difference Analysis builds on the comparison to break differences down by coverage, condition and wording. ## Insurance Policy Change Detection (PolicyIQ | Match) URL: https://policyiq.in/products/match/policy-change-detection/ PolicyIQ | Match ## Insurance Policy Change Detection Policy Change Detection detects what changed between two versions of the same policy, flagging exactly what was added, removed or modified. A renewed or endorsed policy can differ from its prior version in ways that are easy to miss on a read-through. Policy Change Detection compares the two versions directly and reports the specific changes. Explaining a change to a customer, or defending it in an audit, is much easier with a precise list of what was added, removed or modified than with a general sense that "something changed." Policy Change Detection produces exactly that list. ### Renewals and endorsements reviewed without a list of changes - Renewed or endorsed policies reviewed without a clear list of what changed - Manual read-throughs missing subtle differences - No audit trail of what changed between versions - Difficulty explaining a change to a customer or auditor ### The change-focused counterpart to version comparison This is the change-focused counterpart to Policy Version Comparison, and Coverage Difference Analysis provides the detailed breakdown of what a detected change actually means for coverage. The same detection logic extends across a policy's full history in Policy Version Comparison. ### Additions, removals and modifications between two versions - Direct comparison between two versions of the same policy - A specific list of additions, removals and modifications - The basis for the broader Policy Version Comparison across a policy's full history - Input for Coverage Difference Analysis to explain what changes mean ### What an auditable record of changes gives you - Clear visibility into what changed at renewal or endorsement - An auditable record of policy changes - Easier customer conversations about what's different ### How Insurance Policy Change Detection works - Take two versions: Two versions of the same policy are compared directly. - Detect changes: Additions, removals and modifications are identified. - List them clearly: The result is a specific list of what changed. - Explain and extend: Changes feed Coverage Difference Analysis, and the same logic underlies Policy Version Comparison across a full history. ### Who checks renewal and endorsement documents In PolicyIQ | Match, this capability is used by servicing teams checking renewal and endorsement documents, by agencies confirming what changed for a customer, and by insurer and audit teams reviewing policy updates. ### Small wording changes at renewal can matter at claim time Policies change at renewal and through endorsements, and a small change in wording or cover can matter at claim time. Checking every changed document line by line by hand is impractical at volume. Insurance policy change detection lists exactly what was added, removed or modified. ### Example: this year's renewal against last year's policy Imagine a renewal document arriving with a few changes compared with last year's policy, buried somewhere in many pages of wording. With PolicyIQ | Match, the two versions of the same policy are compared directly and the result is a specific list of what was added, removed or modified. Those changes can then be explained through Coverage Difference Analysis, and the same logic extends to a policy's full history through Policy Version Comparison. ### Getting started with PolicyIQ | Match PolicyIQ | Match is cloud-based and set up remotely. Teams can use it within PolicyIQ, or developers can run the same comparison inside their own systems through the Comparison API, including on data extracted by PolicyIQ | Extract. ### Related PolicyIQ | Match capabilities - [PolicyIQ | Match Policy Version Comparison Comparison across a policy's full history](https://policyiq.in/products/match/policy-version-comparison/) - [PolicyIQ | Match Coverage Difference Analysis What a detected change means for coverage](https://policyiq.in/products/match/coverage-difference-analysis/) - [PolicyIQ | Match PolicyIQ | Match Overview Every PolicyIQ | Match capability in one place](https://policyiq.in/products/match/) ### Frequently asked questions **Q: Does change detection work on any two policy documents?** A: It's built to compare two versions of the same policy specifically, rather than two unrelated policies: for that, see Insurance Policy Comparison. **Q: What does it report?** A: A specific list of additions, removals and modifications between two versions of the same policy. **Q: How does it relate to Policy Version Comparison?** A: It is the basis for Policy Version Comparison, which applies the same logic across a policy's full version history. **Q: Can it explain what a change means?** A: Its results are input for Coverage Difference Analysis, which explains what changes mean. ## Insurance Policy Version Comparison (PolicyIQ | Match) URL: https://policyiq.in/products/match/policy-version-comparison/ PolicyIQ | Match ## Insurance Policy Version Comparison Policy Version Comparison compares successive versions of a policy over its full lifetime, not just the two most recent versions. A policy renewed or endorsed multiple times accumulates a history of versions, and understanding how coverage evolved over that history can matter for a claim or a compliance review. Policy Version Comparison extends Policy Change Detection across the whole sequence rather than one pair at a time. A dispute or compliance question rarely stops at the most recent renewal: it can require tracing a coverage term back through several earlier versions. Having that full history readily comparable, rather than reconstructed by hand from a filing cabinet or shared drive, changes how quickly that question can be answered. ### Years of renewals and endorsements, no clear history - Policies renewed or endorsed multiple times accumulate a hard-to-trace history - No single view of how coverage evolved over a policy's lifetime - Compliance reviews needing a full history, not just the latest two versions - Manual reconstruction of version history from scattered documents ### Change detection applied across a full version history This uses the same underlying comparison as Policy Change Detection, applied across a full version history rather than a single before/after pair. Coverage Difference Analysis can be applied to any pair of versions surfaced here, for a detailed explanation of a specific change. ### Every version of a policy compared, not just the last two - Comparison across a policy's full version history, not just one pair - The same underlying logic as Policy Change Detection, applied across every version - A clearer picture of how coverage evolved over time - Support for compliance or audit review ### What a complete change history makes easier - A complete view of a policy's change history - Easier compliance and audit review - Less manual reconstruction of version history ### How Insurance Policy Version Comparison works - Gather the versions: All successive versions of a policy are brought together, not just the latest pair. - Apply change detection to each: The same logic as Policy Change Detection is applied across every version. - See how cover evolved: The result gives a clearer picture of how coverage evolved over the policy's lifetime. - Support review: The history supports compliance or audit review. ### Who reviews long-running policies In PolicyIQ | Match, this capability is used by servicing and compliance teams reviewing long-running policies, by agencies explaining how a customer's cover has changed over years of renewals, and by insurer audit teams. ### Policies renewed for years rarely tell the whole story on their own Many insurance policies in India renew year after year, with endorsements along the way, so the current document rarely tells the whole story. Insurance policy version comparison shows how cover evolved across the policy's full lifetime, which helps with disputes, audits and advice. ### Example: when did this condition enter a commercial policy? Imagine a commercial policy that has renewed for several years, with endorsements along the way, and a question about when a particular condition changed. Comparing only the latest two versions would not answer it. Policy Version Comparison applies change detection across every version in the policy's history, giving a clear picture of how coverage evolved, which supports both advice to the customer and compliance or audit review. ### Getting started with PolicyIQ | Match PolicyIQ | Match is cloud-based and set up remotely. Teams can use it within PolicyIQ, or developers can run the same comparison inside their own systems through the Comparison API, including on data extracted by PolicyIQ | Extract. ### Related PolicyIQ | Match capabilities - [PolicyIQ | Match Policy Change Detection The pairwise comparison this extends](https://policyiq.in/products/match/policy-change-detection/) - [PolicyIQ | Match Coverage Difference Analysis What each version's changes mean for coverage](https://policyiq.in/products/match/coverage-difference-analysis/) - [PolicyIQ | Match PolicyIQ | Match Overview Every PolicyIQ | Match capability in one place](https://policyiq.in/products/match/) ### Frequently asked questions **Q: Is this different from Policy Change Detection?** A: Policy Change Detection compares two specific versions; Policy Version Comparison extends that across a policy's entire history. **Q: Does it compare more than two versions?** A: Yes. It compares across a policy's full version history, not just one pair. **Q: What logic does it use?** A: The same underlying logic as Policy Change Detection, applied across every version. **Q: Who benefits from version history?** A: Compliance and audit reviewers, and agencies explaining how a customer's cover changed over time. ## AI Chatbot for Insurance Companies (PolicyIQ | Assist) URL: https://policyiq.in/products/assist/ PolicyIQ | Assist ## AI chatbot for insurance companies and agencies PolicyIQ | Assist is an AI chatbot for insurance companies and agencies that answers insurance questions for customers, POSP agents and employees, guiding them to answers instead of a support queue. [Book a demo](https://policyiq.in/request-demo/)Explore capabilities ### Insurance Chatbot for WhatsApp and Website Answers policy questions for customers, POSP agents and staff, in more than one language. PolicyIQ | Assist is an AI chatbot for insurance that answers customer, POSP agent and employee questions about policies, claims and renewals, across web, WhatsApp and multiple languages. ### What problem does PolicyIQ | Assist solve? The same questions about policy coverage, renewal status or claim progress get asked repeatedly across customer support, POSP networks and internal teams. PolicyIQ | Assist gives each audience a guided way to get an answer directly, rather than waiting on a person to look it up. ### What capabilities does PolicyIQ | Assist include? Seven capabilities cover AI-guided support across customers, POSP agents and internal teams. **Insurance AI Chatbot** A conversational assistant trained on insurance questions and workflows. [Explore Insurance AI Chatbot](https://policyiq.in/products/assist/insurance-ai-chatbot/) **Customer Support Assistant** Answers customer questions about policies, claims and renewals. [Explore Customer Support Assistant](https://policyiq.in/products/assist/customer-support-assistant/) **POSP Agent Assistant** Helps POSP agents find answers without waiting on a support desk. [Explore POSP Agent Assistant](https://policyiq.in/products/assist/posp-agent-assistant/) **Employee Knowledge Assistant** Surfaces internal knowledge for employees handling insurance queries. [Explore Employee Knowledge Assistant](https://policyiq.in/products/assist/employee-knowledge-assistant/) **Policy Information Assistant** Answers specific questions about an individual policy. [Explore Policy Information Assistant](https://policyiq.in/products/assist/policy-information-assistant/) **Multilingual Chatbot** Handles conversations in multiple languages. [Explore Multilingual Chatbot](https://policyiq.in/products/assist/multilingual-chatbot/) **WhatsApp & Website Integration** Brings the assistant to the channels customers already use. [Explore WhatsApp & Website Integration](https://policyiq.in/products/assist/whatsapp-and-website-integration/) ### How does PolicyIQ | Assist fit with the rest of PolicyIQ? #### Three audiences, one assistant Customer Support, POSP Agent and Employee Knowledge assistants share the same underlying platform. #### Connected to real data Policy Information Assistant draws on policy records rather than generic answers. ### Why an AI chatbot for insurance companies needs insurance knowledge Insurance customers ask the same kinds of questions again and again: what a policy covers, when it renews, how to start a claim, which documents are needed. In India many of these questions arrive on WhatsApp, outside office hours, and in languages other than English. Answering them all by phone or email ties up support teams and leaves customers waiting. A general-purpose chatbot can talk, but it does not understand insurance workflows and cannot be trusted with questions about a specific policy. PolicyIQ | Assist is trained on insurance questions and workflows, and policy-specific questions are answered by the Policy Information Assistant from the actual policy record, not from generic text. ### Who uses PolicyIQ | Assist? Insurance companies and brokers use the Customer Support Assistant to answer routine customer questions on WhatsApp and their websites. Brokers and insurers with POSP networks use the POSP Agent Assistant so agents get product and process answers while they are with a customer. Insurer and brokerage staff use the Employee Knowledge Assistant as a single point of reference for internal questions. ### How PolicyIQ | Assist connects with other PolicyIQ products The Policy Information Assistant draws on policy records such as those held in PolicyIQ | One, so answers about a specific policy reflect real data. WhatsApp and website channels connect through PolicyIQ | Gateway's Communication APIs. ### Getting started with PolicyIQ | Assist PolicyIQ | Assist is cloud-based and set up remotely, and runs on the channels people already use: WhatsApp and an agency's or insurer's website, with no separate app or portal login for customers. ### Further reading [Insurance AI and Automation AI Chatbot for Insurance in India: How to Choose The four kinds of insurance chatbot in India, what to test before choosing, and where a policy-aware assistant fits. Read the article](https://policyiq.in/blog/insurance-ai/ai-chatbot-for-insurance-in-india-how-to-choose/)[Insurance AI and Automation How AI Chatbots Support Insurance Customers How AI chatbots answer policy, renewal and claims questions for customers and agents, and when to hand over to a person. Read the article](https://policyiq.in/blog/insurance-ai/how-ai-chatbots-can-support-insurance-customers-and-agents/)[Insurance AI and Automation What AI Automation Covers Beyond Chatbots in Insurance Beyond chatbots: where AI automation helps insurance teams with documents, data checks, comparisons and routine servicing work. Read the article](https://policyiq.in/blog/insurance-ai/what-ai-automation-covers-beyond-chatbots-in-insurance/) - [Glossary: what is conversational AI?](https://policyiq.in/glossary/#conversational-ai) - [How PolicyIQ approaches responsible AI](https://policyiq.in/responsible-ai/) Frequently asked questions ### Your questions, answered **Q: What can PolicyIQ | Assist answer?** A: PolicyIQ | Assist is an insurance conversational AI platform built to answer insurance questions (about policies, claims, renewals and general product information) for customers, POSP agents and employees. **Q: Does PolicyIQ | Assist work on WhatsApp?** A: Yes. WhatsApp & Website Integration brings this genai virtual assistant for policyholders to the channels customers already use, rather than requiring a separate app. **Q: Can PolicyIQ | Assist reply in more than one language?** A: Yes. As a customer service chatbot built for insurance agencies and their teams, PolicyIQ | Assist uses Multilingual Chatbot to handle conversations in multiple languages, so customers and agents can use it in the language they're most comfortable with. **Q: Can PolicyIQ | Assist help POSP agents directly, not just customers?** A: Yes. The POSP Agent Assistant helps POSP agents find answers without waiting on a support desk, alongside the Employee Knowledge Assistant, which surfaces internal knowledge for employees handling insurance queries. **Q: Can PolicyIQ | Assist answer questions about a specific policy?** A: Yes. The Policy Information Assistant answers specific questions about an individual policy, rather than only general product information. **Q: Is PolicyIQ | Assist trained on insurance specifically?** A: Yes. The Insurance AI Chatbot behind PolicyIQ | Assist is trained on insurance questions and workflows rather than general-purpose conversation. **Q: Do customers need to download an app?** A: No. PolicyIQ | Assist runs on WhatsApp and on an agency's or insurer's website. **Q: Does PolicyIQ | Assist replace the support team?** A: No. It answers routine questions and hands policy-specific questions to the Policy Information Assistant, so people can focus on complex cases that need judgement. [Read: How AI Chatbots Can Support Insurance Customers and Agents](https://policyiq.in/blog/insurance-ai/how-ai-chatbots-can-support-insurance-customers-and-agents/) ## Insurance Customer Support Assistant (PolicyIQ | Assist) URL: https://policyiq.in/products/assist/customer-support-assistant/ PolicyIQ | Assist ## Insurance Customer Support Assistant The Customer Support Assistant answers customer questions about policies, claims and renewals directly, so common questions don't all need a person to answer. Customers often ask the same handful of questions (coverage details, claim status, renewal dates) that don't need a specialist to answer. The Customer Support Assistant applies PolicyIQ | Assist's Insurance AI Chatbot specifically to these customer-facing questions. Support teams tend to spend a disproportionate amount of time on a small set of recurring questions. Handling those through a guided assistant frees the team to spend more time on the calls and conversations that genuinely need a person's judgement. ### The same coverage and claim questions, every day - Customers asking the same coverage and status questions repeatedly - Support queues that build up during busy periods - Inconsistent answers depending on who responds - Delayed responses outside working hours ### Policy-specific questions handed to the right assistant For a specific policy's details, this hands off to the Policy Information Assistant, and reaches customers through WhatsApp & Website Integration. General questions are answered directly here; anything requiring a specific policy's data is handed off automatically. ### Guided answers, hand-off for policy details, WhatsApp and website - Guided answers to common customer questions - Hand-off to Policy Information Assistant for policy-specific queries - Availability through WhatsApp & Website Integration - Consistent answers regardless of who (or what) is responding ### What shorter support queues change - Faster answers to common customer questions - Reduced support queue volume - More consistent customer experience ### How Insurance Customer Support Assistant works - Customer asks: A customer asks about a policy, claim or renewal on the website or WhatsApp. - Guided answer: Common questions get guided, consistent answers straight away. - Policy-specific hand-off: Questions about the customer's own policy are handed to the Policy Information Assistant. - People handle the rest: Complex or sensitive requests stay with the support team, who now have more time for them. ### Who gets a steady flow of routine customer questions In PolicyIQ | Assist, this capability is used by agencies and insurers that receive a steady flow of routine customer questions, and by their support teams, who can focus on complex cases instead of answering the same questions repeatedly. ### Indian customers expect answers on WhatsApp, evenings included Customers in India increasingly expect quick answers on WhatsApp and websites, including in the evenings and at weekends. Many questions, such as renewal dates, claim steps and documents needed, repeat every day. An insurance customer support assistant answers them consistently and instantly, while people stay responsible for the conversations that need judgement. ### Example: how to start a claim, answered without a phone call Imagine an agency's support line receiving the same handful of questions every day: how to start a claim, which documents are needed, when a renewal is due. With the Customer Support Assistant on WhatsApp and the website, customers get guided, consistent answers to common questions immediately, policy-specific questions are handed to the Policy Information Assistant, and the support team spends its time on the complex conversations that need a person. ### Getting started with PolicyIQ | Assist PolicyIQ | Assist is cloud-based and set up remotely, and runs on the channels people already use through WhatsApp and Website Integration. It works alongside the other PolicyIQ | Assist assistants, handing policy-specific questions to the Policy Information Assistant. ### Related PolicyIQ | Assist capabilities - [PolicyIQ | Assist Policy Information Assistant Specific answers about one policy](https://policyiq.in/products/assist/policy-information-assistant/) - [PolicyIQ | Assist WhatsApp & Website Integration Where customers reach this assistant](https://policyiq.in/products/assist/whatsapp-and-website-integration/) - [PolicyIQ | Assist PolicyIQ | Assist Overview Every PolicyIQ | Assist capability in one place](https://policyiq.in/products/assist/) ### Frequently asked questions **Q: What questions can an insurance customer support chatbot answer?** A: General questions about products, processes and common concerns; policy-specific questions are handled by the Policy Information Assistant. **Q: Does it replace human support entirely?** A: No, it's designed to handle repeatable questions so human support can focus on judgement calls and exceptions. **Q: Where can customers use it?** A: Through WhatsApp and Website Integration, on WhatsApp and on an agency's or insurer's website. **Q: Are answers consistent?** A: Yes. Answers are consistent regardless of who, or what, is responding. **Q: What happens with a question about a specific policy?** A: It is handed off to the Policy Information Assistant, which answers from the actual policy record. ## Employee Knowledge Assistant for Insurers URL: https://policyiq.in/products/assist/employee-knowledge-assistant/ PolicyIQ | Assist ## Employee Knowledge Assistant for Insurers The Employee Knowledge Assistant surfaces internal knowledge for employees handling insurance queries, so process and policy questions don't rely on asking a colleague. Internal teams need quick access to process documentation, product details and policy rules, often spread across multiple internal sources. The Employee Knowledge Assistant applies PolicyIQ | Assist's Insurance AI Chatbot to an organisation's own internal knowledge. New employees in particular tend to rely heavily on more experienced colleagues for answers that already exist somewhere in internal documentation: they just can't find it quickly. A guided assistant surfaces that same information without requiring someone else's time. ### Process knowledge stuck with a few experienced people - Internal process and policy questions repeated across teams - Knowledge concentrated in a few experienced employees - New employees taking longer to get up to speed - Documentation scattered across multiple internal sources ### Like the agent assistant, but for internal teams This mirrors the POSP Agent Assistant, but for internal employees rather than independent agents, and can hand off to the Policy Information Assistant for policy-specific questions. Built on the same Insurance AI Chatbot foundation as every other PolicyIQ | Assist capability, applied to internal knowledge specifically. ### Answers to internal process and product questions in one place - Guided answers to internal process and product questions - A single point of reference instead of scattered documentation - Hand-off to Policy Information Assistant for policy-specific questions - Consistent answers regardless of which employee is asking ### What faster onboarding of new staff changes - Faster onboarding for new employees - Less dependency on a few experienced staff for common questions - More consistent internal knowledge across teams ### How Employee Knowledge Assistant for Insurers works - Employee asks: An employee asks an internal process or product question. - One point of reference: The assistant answers from a single point of reference instead of scattered documentation. - Policy-specific hand-off: Questions about a particular policy go to the Policy Information Assistant. - Consistent answers: Every employee gets the same answer to the same question. ### Who handles insurance queries inside insurers and agencies In PolicyIQ | Assist, this capability is used by employees at insurers and agencies who handle insurance queries, including new staff learning processes and experienced staff who need a quick, reliable reference. ### Detailed processes, scattered documents: an insurer's knowledge problem Insurance processes and products are detailed, and knowledge is often spread across documents, emails and experienced colleagues. In growing Indian insurance teams, that slows new staff and produces inconsistent answers. An employee knowledge assistant for insurers puts internal knowledge in one place that answers instantly. ### Example: a new servicing employee processing an endorsement Imagine a new employee in an insurer's servicing team unsure of the steps for processing an endorsement. Instead of interrupting a colleague or searching several documents, they ask the Employee Knowledge Assistant, which answers from a single point of reference. If the question concerns a specific customer's policy, it is handed to the Policy Information Assistant, and every employee asking the same question gets the same answer. ### Getting started with PolicyIQ | Assist PolicyIQ | Assist is cloud-based and set up remotely, and runs on the channels people already use through WhatsApp and Website Integration. It works alongside the other PolicyIQ | Assist assistants, handing policy-specific questions to the Policy Information Assistant. ### Related PolicyIQ | Assist capabilities - [PolicyIQ | Assist POSP Agent Assistant The equivalent for independent agents](https://policyiq.in/products/assist/posp-agent-assistant/) - [PolicyIQ | Assist Policy Information Assistant Answers about one specific policy](https://policyiq.in/products/assist/policy-information-assistant/) - [PolicyIQ | Assist PolicyIQ | Assist Overview Every PolicyIQ | Assist capability in one place](https://policyiq.in/products/assist/) ### Frequently asked questions **Q: Does an internal knowledge assistant replace documentation?** A: It's designed to surface that documentation more easily, not replace the underlying source material. **Q: Can new employees use it right away?** A: Yes, that's part of the intent: giving new employees a consistent way to get answers without relying on a colleague's availability. **Q: Can the assistant answer policy-specific questions?** A: Policy-specific questions are handed off to the Policy Information Assistant, which answers from the actual policy record. **Q: Do all employees get the same answer?** A: Yes. Answers are consistent regardless of which employee is asking. **Q: What replaces scattered documentation?** A: The assistant provides a single point of reference for internal process and product questions. ## AI Chatbot Software for Insurance Teams (PolicyIQ | Assist) URL: https://policyiq.in/products/assist/insurance-ai-chatbot/ PolicyIQ | Assist ## AI Chatbot Software for Insurance Teams The Insurance AI Chatbot is the conversational assistant underlying PolicyIQ | Assist, trained on insurance questions and workflows rather than general-purpose conversation. This is the core assistant that Customer Support Assistant, POSP Agent Assistant and Employee Knowledge Assistant each apply to a specific audience, and that Policy Information Assistant applies to a specific policy. A generic chatbot can hold a conversation, but insurance questions need more than conversation: they need an assistant that recognises what a policy schedule, a claim status or a renewal date actually is. The Insurance AI Chatbot is built around that insurance-specific understanding. ### Repeated questions, after-hours gaps and generic bots - Repeated questions consuming support team time - No consistent first line of response outside business hours - Generic chatbots that don't understand insurance-specific questions - Difficulty scaling support as customer or agent volume grows ### The base assistant behind every PolicyIQ | Assist capability Multilingual Chatbot extends this same assistant to multiple languages, and WhatsApp & Website Integration brings it to the channels people already use. Every audience-specific assistant in PolicyIQ | Assist builds on this same base, rather than each being a separate product. ### A conversational assistant trained on insurance questions - A conversational assistant trained on insurance questions and workflows - The base capability behind Customer Support, POSP Agent and Employee Knowledge assistants - Multilingual support through Multilingual Chatbot - Deployment across web and WhatsApp through WhatsApp & Website Integration ### What a consistent first response changes - Faster first response to common questions - Reduced repetitive load on support teams - Consistent answers regardless of time of day ### How AI Chatbot Software for Insurance Teams works - Ask a question: A customer, POSP agent or employee asks a question in natural language. - Answer from insurance knowledge: The conversational assistant, trained on insurance questions and workflows rather than general conversation, responds. - Hand off for specific policies: Questions about a particular policy are passed to the Policy Information Assistant, which answers from the actual policy record. - Reach people where they are: The same chatbot runs on websites and WhatsApp, in multiple languages. ### Three audiences: customers, POSP agents and employees The Insurance AI Chatbot powers PolicyIQ | Assist for three audiences: customers asking about policies, claims and renewals; POSP agents who need quick product and process answers; and employees handling insurance queries internally. ### The same policy, renewal and claim questions, often after hours Insurance customers and agents in India ask many of the same questions about policies, renewals and claims, often outside office hours and on WhatsApp. General-purpose chatbots lack insurance context. AI chatbot software for insurance teams answers routine questions consistently, frees staff for complex cases and hands specific policy questions to an assistant grounded in real records. ### Example: a late-evening health claim question on WhatsApp Imagine a customer messaging their agency's WhatsApp number late in the evening to ask what documents are needed for a health claim. The Insurance AI Chatbot, trained on insurance questions and workflows, answers straight away. If the customer then asks when their own policy renews, the question is handed to the Policy Information Assistant, which answers from the actual policy record. The same chatbot serves agents and employees, on the website as well as WhatsApp, in more than one language. ### Getting started with PolicyIQ | Assist PolicyIQ | Assist is cloud-based and set up remotely, and runs on the channels people already use through WhatsApp and Website Integration. It works alongside the other PolicyIQ | Assist assistants, handing policy-specific questions to the Policy Information Assistant. ### Related PolicyIQ | Assist capabilities - [PolicyIQ | Assist Customer Support Assistant Applied to customer questions](https://policyiq.in/products/assist/customer-support-assistant/) - [PolicyIQ | Assist Multilingual Chatbot The same assistant in multiple languages](https://policyiq.in/products/assist/multilingual-chatbot/) - [PolicyIQ | Assist PolicyIQ | Assist Overview Every PolicyIQ | Assist capability in one place](https://policyiq.in/products/assist/) ### Frequently asked questions **Q: Is the insurance chatbot the same for every audience?** A: It's the same underlying assistant, applied differently for customers, POSP agents and employees through Customer Support Assistant, POSP Agent Assistant and Employee Knowledge Assistant. **Q: Can it be used outside business hours?** A: It's designed to provide a consistent first response regardless of time of day. **Q: Which channels does the chatbot work on?** A: It is deployed across websites and WhatsApp through WhatsApp and Website Integration. **Q: Does the chatbot support more than one language?** A: Yes. Multilingual support comes through the Multilingual Chatbot. **Q: How are questions about a specific policy answered?** A: They are handed to the Policy Information Assistant, which draws on the actual policy record rather than general information. ## Multilingual Insurance AI Chatbot (PolicyIQ | Assist) URL: https://policyiq.in/products/assist/multilingual-chatbot/ PolicyIQ | Assist ## Multilingual Insurance AI Chatbot The Multilingual Chatbot handles insurance conversations in multiple languages, so customers and agents can use PolicyIQ | Assist in the language they're most comfortable with. India's insurance customers and POSP agents span many languages, and a support experience limited to one language excludes many of them. Multilingual Chatbot extends the same Insurance AI Chatbot across languages rather than running separate assistants per language. Maintaining a separate assistant for every language would multiply the work needed every time a product detail or process changes. Extending one assistant across languages instead keeps updates consistent, since there is only one underlying source of truth to maintain. ### Support in one language leaves part of your audience out - Customers and agents more comfortable in languages other than English - Support limited to one language excluding part of the audience - Running separate assistants per language is hard to maintain - Inconsistent quality of translated responses ### Every assistant, in every supported language This applies across every other PolicyIQ | Assist capability (customer, POSP agent and employee conversations alike) rather than being a separate, standalone tool. Available through the same WhatsApp & Website Integration as every other PolicyIQ | Assist conversation. ### One assistant with consistent answers across languages - The same Insurance AI Chatbot extended across multiple languages - Consistent underlying answers regardless of language - Coverage across customer, POSP agent and employee use cases - Availability through WhatsApp & Website Integration ### What wider language access changes - Wider accessibility for non-English speaking customers and agents - One assistant to maintain instead of several per language - Consistent answer quality across languages ### How Multilingual Insurance AI Chatbot works - Choose a language: A customer, agent or employee writes in the language they are most comfortable with. - Same assistant, any language: The same Insurance AI Chatbot handles the conversation in that language. - Consistent answers: The underlying answers stay consistent whatever the language. - Available on familiar channels: The chatbot is available on WhatsApp and websites through WhatsApp and Website Integration. ### Customers, agents and employees who prefer their own language The Multilingual Chatbot is used across PolicyIQ | Assist's audiences: customers, POSP agents and employees who prefer to communicate in a language other than English. ### Many customers and POSPs in India are more comfortable outside English India is linguistically diverse, and many insurance customers and POSP agents are more comfortable outside English, especially in smaller towns. Limiting service to one language excludes them. A multilingual insurance AI chatbot lets people ask in the language they prefer while answers stay consistent. ### Example: a customer in a smaller town writing in their own language Imagine a customer in a smaller town who is more comfortable writing in their own language than in English. With the Multilingual Chatbot, they message on WhatsApp in the language they prefer, and the same Insurance AI Chatbot handles the conversation, with the underlying answers consistent whatever the language. The same applies to POSP agents and employees who prefer to work in a language other than English. ### Getting started with PolicyIQ | Assist PolicyIQ | Assist is cloud-based and set up remotely, and runs on the channels people already use through WhatsApp and Website Integration. It works alongside the other PolicyIQ | Assist assistants, handing policy-specific questions to the Policy Information Assistant. ### Related PolicyIQ | Assist capabilities - [PolicyIQ | Assist Insurance AI Chatbot The assistant this extends across languages](https://policyiq.in/products/assist/insurance-ai-chatbot/) - [PolicyIQ | Assist WhatsApp & Website Integration Where multilingual conversations happen](https://policyiq.in/products/assist/whatsapp-and-website-integration/) - [PolicyIQ | Assist PolicyIQ | Assist Overview Every PolicyIQ | Assist capability in one place](https://policyiq.in/products/assist/) ### Frequently asked questions **Q: Does language affect answer quality?** A: It's designed to give consistent underlying answers regardless of language, though quality should be confirmed per language as part of verification. **Q: Does the multilingual chatbot cover agents and employees too?** A: Yes. It covers customer, POSP agent and employee use cases. **Q: Is it a separate chatbot for each language?** A: No. It is the same Insurance AI Chatbot extended across multiple languages. **Q: Where is it available?** A: Through WhatsApp and Website Integration. ## AI Policy Information Assistant (PolicyIQ | Assist) URL: https://policyiq.in/products/assist/policy-information-assistant/ PolicyIQ | Assist ## AI Policy Information Assistant for Insurers The Policy Information Assistant answers specific questions about an individual policy (coverage, premium, renewal date) by drawing on the actual policy record rather than general product information. Many customer and agent questions aren't general product questions but specific to one policy. The Policy Information Assistant is what Customer Support Assistant, POSP Agent Assistant and Employee Knowledge Assistant hand off to once a question turns policy-specific. An assistant that guesses at a specific policy's details risks giving a confident but wrong answer, which is worse in insurance than simply not answering. Grounding every response in the real policy record is what makes this hand-off safe to rely on. ### "What does my policy cover?" needs the actual policy - Policy-specific questions requiring a person to look up records manually - Delays answering "what does my policy cover" style questions - Risk of generic or incorrect answers if not tied to real data - Repeated lookups for the same policy across different conversations ### Answers drawn from real policy records This capability connects to policy records such as those kept in PolicyIQ | One's Policy Management, through PolicyIQ | Gateway, rather than working from static product information alone. Every other PolicyIQ | Assist audience assistant hands policy-specific questions to this same capability. ### Answers grounded in records, not generic information - Answers grounded in actual policy records, not generic information - Connection to policy records such as those in PolicyIQ | One - A hand-off point from Customer Support, POSP Agent and Employee Knowledge assistants - Consistent, record-based answers regardless of who's asking ### What policy-specific answers change - Faster answers to policy-specific questions - Reduced risk of incorrect, generic answers - Fewer manual look-ups for the same information ### How AI Policy Information Assistant works - Receive a policy question: A question about a specific policy arrives directly or is handed off from another assistant. - Look up the record: The assistant draws on the actual policy record, such as those held in PolicyIQ | One. - Answer from facts: It answers about coverage, premium or renewal date from that record, not from general product information. - Stay consistent: The answer is record-based and consistent whoever is asking. ### Customers, agents and staff asking about one policy The Policy Information Assistant serves customers asking about their own policy, POSP agents checking a customer's policy during a conversation, and employees answering policy-specific queries, through hand-offs from the other PolicyIQ | Assist assistants. ### The questions that matter most are about a specific policy The most important insurance questions are about a specific policy: what is covered, what the premium is, when it renews. Generic chatbot answers risk being wrong for that customer. An AI policy information assistant grounded in actual policy records gives answers people can rely on, which is essential for trust in AI-assisted service. ### Example: does my health policy cover this treatment, and when does it renew? Imagine a customer asking whether their health policy covers a particular treatment and when it renews. A generic chatbot could only describe the product in general. The Policy Information Assistant instead draws on the customer's actual policy record, such as one held in PolicyIQ | One, and answers from that record. The same record-based answer is given whether the question comes from the customer, their POSP agent or an employee. ### Getting started with PolicyIQ | Assist PolicyIQ | Assist is cloud-based and set up remotely, and runs on the channels people already use through WhatsApp and Website Integration. It works alongside the other PolicyIQ | Assist assistants, which hand policy-specific questions to it. ### Related PolicyIQ | Assist capabilities - [PolicyIQ | Assist Customer Support Assistant Hands specific policy questions here](https://policyiq.in/products/assist/customer-support-assistant/) - [PolicyIQ | One PolicyIQ | One Policy Management The records this assistant draws on](https://policyiq.in/products/one/policy-management/) - [PolicyIQ | Assist PolicyIQ | Assist Overview Every PolicyIQ | Assist capability in one place](https://policyiq.in/products/assist/) ### Frequently asked questions **Q: How does it avoid giving wrong answers about a policy?** A: It answers from actual policy records rather than generating a plausible-sounding response, so answers are grounded in real data. **Q: Which systems does it pull policy data from?** A: It connects to policy records such as those kept in PolicyIQ | One's Policy Management, through PolicyIQ | Gateway. **Q: What kinds of questions can it answer?** A: Specific questions about an individual policy, such as coverage, premium and renewal date. **Q: Which assistants hand off to it?** A: The Customer Support, POSP Agent and Employee Knowledge assistants hand policy-specific questions to it. **Q: Why ground answers in policy records?** A: So answers reflect the customer's actual policy rather than generic product information, avoiding unsupported answers about a specific policy. ## POSP Agent AI Assistant Software (PolicyIQ | Assist) URL: https://policyiq.in/products/assist/posp-agent-assistant/ PolicyIQ | Assist ## POSP Agent AI Assistant Software The POSP Agent Assistant helps POSP agents find answers to product and process questions without waiting on a support desk, so an agent can keep a customer conversation moving. A POSP agent mid-conversation with a customer often needs a quick answer about a product or process rather than a delayed reply from a support team. The POSP Agent Assistant applies PolicyIQ | Assist's Insurance AI Chatbot to that specific need. As a POSP network grows, so does the range of product knowledge every individual agent is expected to hold. A shared assistant means every agent, regardless of experience, can reach the same consistent guidance in the moment they need it. ### Agents waiting on a support desk mid-sale - Agents needing quick answers mid-conversation with a customer - Waiting on a support desk slows down a sale - Inconsistent product knowledge across a growing agent network - No single reference point for common process questions ### General product answers, with customer policy details on hand-off Where a question is specific to a customer's own policy rather than a general product question, this connects through to the Policy Information Assistant. Available through WhatsApp & Website Integration, so agents can reach it from wherever they already work. ### Product and process answers for agents, on WhatsApp and web - Guided answers to product and process questions for POSP agents - Hand-off to Policy Information Assistant for a specific customer's policy - Availability through WhatsApp & Website Integration - Consistent guidance regardless of which agent is asking ### What faster answers in live conversations change - Faster answers during live customer conversations - Less dependency on a central support desk - More consistent product knowledge across the network ### How POSP Agent AI Assistant Software works - Agent asks: A POSP agent asks a product or process question, often while with a customer. - Guided answer: The assistant gives guided, consistent answers without waiting for a support desk. - Policy-specific hand-off: Questions about a particular customer's policy go to the Policy Information Assistant. - Keep the conversation moving: The agent gets what they need quickly and continues with the customer. ### POSP agents across a network, and the teams supporting them In PolicyIQ | Assist, this capability is used by POSP agents across an agency's or insurer's network, and by the agencies and insurers who support them and want consistent guidance for every agent. ### POSP networks reach towns far from head office POSP networks in India extend into towns far from a brokerage's head office, and agents often need an answer while sitting with a customer. Waiting for a support desk can lose the sale. A POSP agent AI assistant available on WhatsApp gives every agent the same reliable guidance instantly. ### Example: an add-on cover question answered at the customer's table Imagine a POSP agent sitting with a customer who asks a detailed question about a product's add-on cover. Rather than calling the agency's support desk and making the customer wait, the agent asks the POSP Agent Assistant on WhatsApp and gets a guided answer. If the question is about the customer's existing policy, it is handed to the Policy Information Assistant, and every agent in the network receives the same consistent guidance. ### Getting started with PolicyIQ | Assist PolicyIQ | Assist is cloud-based and set up remotely, and runs on the channels people already use through WhatsApp and Website Integration. It works alongside the other PolicyIQ | Assist assistants, handing policy-specific questions to the Policy Information Assistant. ### Related PolicyIQ | Assist capabilities - [PolicyIQ | Assist Employee Knowledge Assistant The equivalent for internal teams](https://policyiq.in/products/assist/employee-knowledge-assistant/) - [PolicyIQ | Assist Policy Information Assistant Answers about one specific policy](https://policyiq.in/products/assist/policy-information-assistant/) - [PolicyIQ | Assist PolicyIQ | Assist Overview Every PolicyIQ | Assist capability in one place](https://policyiq.in/products/assist/) ### Frequently asked questions **Q: Does it work for agents across a whole POSP network?** A: Yes, it's designed to give consistent answers to any POSP agent asking, not just a specific team. **Q: Can it answer questions about a specific customer's policy?** A: For customer-specific questions, it hands off to the Policy Information Assistant, which reads from the actual policy record. **Q: Is the guidance the same for every agent?** A: Yes. Guidance is consistent regardless of which agent is asking. **Q: Where can agents use it?** A: Through WhatsApp and Website Integration. **Q: Can agents ask in their own language?** A: The Multilingual Chatbot extends PolicyIQ | Assist across multiple languages, covering POSP agent use cases. ## WhatsApp & Website Insurance Chatbot (PolicyIQ | Assist) URL: https://policyiq.in/products/assist/whatsapp-and-website-integration/ PolicyIQ | Assist ## WhatsApp & Website Insurance Chatbot WhatsApp & Website Integration brings PolicyIQ | Assist to the channels customers already use, rather than requiring a separate app or portal login. Customers in India widely use WhatsApp for everyday communication, alongside an agency's or insurer's own website. WhatsApp & Website Integration connects PolicyIQ | Assist's Insurance AI Chatbot to both, using the communication connections PolicyIQ | Gateway provides. An assistant only helps if people can actually reach it easily. Meeting customers on WhatsApp and a familiar website, rather than asking them to download something new, removes the biggest barrier to a question actually getting asked. ### Customers message on WhatsApp, not your portal - Customers expecting to reach support through WhatsApp, not a separate app - Website visitors with no easy way to ask a quick question - Fragmented presence across channels with different tools for each - Missed opportunities to answer a question the moment it's asked ### Every assistant, on WhatsApp and your website Every other PolicyIQ | Assist capability (Customer Support, POSP Agent, Employee Knowledge and Policy Information assistants, in any supported language) becomes reachable through these channels. Built on [PolicyIQ | Gateway's Communication APIs](https://policyiq.in/products/gateway/communication-apis/), the same layer used for renewal reminders and other notifications. ### One assistant on WhatsApp and embedded on your site - PolicyIQ | Assist available directly on WhatsApp - PolicyIQ | Assist embedded on an agency's or insurer's website - The same underlying assistant across both channels - Connection through PolicyIQ | Gateway's Communication APIs ### What answering where customers already are changes - Support available where customers already are - More questions answered at the moment they're asked - One assistant to maintain across channels instead of separate tools ### How WhatsApp & Website Insurance Chatbot works - Add to WhatsApp: PolicyIQ | Assist becomes available directly on WhatsApp. - Embed on the website: The same assistant is embedded on an agency's or insurer's website. - Keep one assistant: Both channels use the same underlying assistant, so answers match. - Connect through Gateway: The connection runs through PolicyIQ | Gateway's Communication APIs. ### Agencies and insurers serving people on familiar channels In PolicyIQ | Assist, this capability is used by agencies and insurers that want to serve customers, POSP agents and employees on the channels they already use, without asking anyone to download a separate app or log in to a portal. ### WhatsApp is how many Indian customers prefer to reach you WhatsApp is one of the most widely used messaging apps in India, and many customers would rather message than call or log in to a portal. A WhatsApp and website insurance chatbot meets them where they are, with the same answers on both channels. ### Example: customers who never log in, but message every day Imagine an agency whose customers rarely log in to its portal but message it on WhatsApp every day. With WhatsApp & Website Integration, PolicyIQ | Assist is available directly on WhatsApp and embedded on the agency's website, using the same underlying assistant on both, so answers match wherever the customer asks. The connection runs through PolicyIQ | Gateway's Communication APIs, and no separate app or login is needed. ### Getting started with PolicyIQ | Assist PolicyIQ | Assist is cloud-based and set up remotely, and runs on the channels people already use through WhatsApp and Website Integration. WhatsApp and Website Integration works alongside the other PolicyIQ | Assist assistants, handing policy-specific questions to the Policy Information Assistant. ### Related PolicyIQ | Assist capabilities - [Guide Guide WhatsApp for insurance agents and agencies](https://policyiq.in/blog/policy-servicing/whatsapp-for-insurance-agents-and-brokers/) - [PolicyIQ | Gateway PolicyIQ | Gateway Communication APIs The connection this integration uses](https://policyiq.in/products/gateway/communication-apis/) - [PolicyIQ | Assist Customer Support Assistant Reachable through these channels](https://policyiq.in/products/assist/customer-support-assistant/) - [PolicyIQ | Assist PolicyIQ | Assist Overview Every PolicyIQ | Assist capability in one place](https://policyiq.in/products/assist/) ### Frequently asked questions **Q: Does this require a separate app for customers?** A: No, it's built to work through WhatsApp and an agency's or insurer's existing website, not a new app customers need to install. **Q: What powers the connection to WhatsApp?** A: PolicyIQ | Gateway's Communication APIs provide the underlying connection. **Q: Is it the same assistant on WhatsApp and the website?** A: Yes. The same underlying assistant runs on both channels. **Q: Do customers need to log in anywhere?** A: No separate app or portal login is required; customers use WhatsApp or the website. **Q: Can the assistant answer in other languages on WhatsApp?** A: The Multilingual Chatbot is available through WhatsApp and Website Integration.