10. Digital, Omnichannel and Ecosystem Distribution

Introduction and Context

Insurance distribution has moved from a product-centred model, in which insurers sold through branches, agents and brokers, towards a connected model in which customers may discover, compare, purchase, service and renew policies through several interacting channels. Websites, mobile applications, contact centres, social platforms, aggregators, partner ecosystems and embedded interfaces now form part of the distribution architecture of an insurer.

This change is not simply a matter of transferring an existing form from paper to a website. Digital distribution changes how customers search for information, how risk is assessed, how advice is delivered, how transactions are authenticated and how relationships are maintained after sale. It also changes the competitive boundaries of insurance. A bank, automobile manufacturer, online retailer, health platform or travel company may become an important point of insurance access without being an insurer itself.

For insurance managers, the central challenge is to create a seamless customer journey while preserving suitability, trust, regulatory compliance, underwriting discipline and economic viability. The relevant question is not whether a digital channel should replace an agency or contact-centre channel. It is how the channels should be designed to complement one another and how customers should be allowed to move between them without losing context.

Digital, omnichannel and ecosystem distribution are therefore strategic capabilities. They involve channel design, technology architecture, data governance, service operations, partner management, customer relationship management and organisational change.

Learning Objectives

After studying this chapter, the learner should be able to:

1. Distinguish among multichannel, cross-channel, omnichannel and ecosystem distribution.

2. Design connected web, mobile, contact-centre and assisted-service journeys.

3. Explain the role of APIs, platforms, insurtech and embedded insurance.

4. Evaluate channel economics, customer experience, operational risks and migration choices.

5. Apply frameworks for selecting partners and governing ecosystem relationships.

6. Assess the regulatory, ethical, cybersecurity and data-protection implications of digital distribution.

7. Recommend strategies for digital adoption, channel migration and continuous improvement.

From Multiple Channels to a Connected Distribution System

A channel is a route through which a customer receives information, advice, completes a transaction or obtains service. Traditional channels include tied agents, brokers, bancassurance representatives, branches and telephone contact centres. Digital channels include insurer websites, applications, messaging interfaces, comparison platforms and partner applications.

A multichannel insurer offers more than one channel, but the channels may operate independently. A customer who begins a proposal online may have to repeat information when contacting the call centre. A cross-channel arrangement permits limited movement between channels, such as requesting a call-back after an online quotation. An omnichannel system integrates channels so that customer identity, consent, interaction history, documents, quotes and service status are available across authorised touchpoints. The objective is continuity rather than merely abundance of channels.

An ecosystem extends the idea further. It consists of an insurer, customers, intermediaries, technology providers, data providers, service firms and non-insurance businesses whose capabilities combine to create customer value. For example, an automobile ecosystem may involve a manufacturer, dealer, financing company, insurer, roadside-assistance provider, repair network and telematics platform. The customer may experience one mobility service even though several organisations participate in fulfilment.

The distinction matters because each model creates different managerial requirements. Multichannel management focuses on availability and channel performance. Omnichannel management focuses on orchestration, identity, data continuity and service consistency. Ecosystem management adds partner incentives, shared governance, interoperability, liability allocation and strategic dependence.

The Customer Journey as the Unit of Design

Insurance distribution should be designed around customer journeys rather than internal departmental boundaries. A journey may include need recognition, search, education, quotation, advice, application, underwriting, payment, policy issuance, first use, claim notification, claim settlement, renewal and advocacy. Different journeys have different levels of emotional intensity and customer involvement. A motor renewal may be relatively routine, while a health claim may require reassurance, empathy and human assistance.

Journey mapping identifies the customer’s goal, actions, questions, emotions, information requirements, channel choices, failure points and backstage processes. It should also identify the moments at which a customer is likely to abandon the journey or seek human help. A well-designed digital journey does not eliminate assistance; it makes assistance available at the point where complexity, vulnerability or uncertainty increases.

For example, a customer purchasing travel insurance may search on a mobile device, compare coverage on a marketplace, obtain clarification through a chatbot, speak to a licensed adviser about exclusions, pay through the application and later submit a claim using a mobile upload. Omnichannel design requires that the adviser sees the relevant quotation and that the claim system recognises the policy without requiring the customer to re-enter basic details.

A useful design principle is “capture once, use appropriately.” Information should be collected once where possible, validated at the source and reused only for legitimate, disclosed and consented purposes. This reduces friction but must not result in indiscriminate data sharing.

Architecture of an Omnichannel Insurance Operation

Omnichannel distribution depends on both customer-facing interfaces and supporting architecture. The visible website or application is only one layer of the system. A mature arrangement generally includes the following layers:

• Experience layer: websites, mobile applications, portals, messaging interfaces, kiosks and adviser screens.
• Engagement layer: contact-centre tools, campaign management, chat, notifications, appointment scheduling and assisted-service functions.
• Core business layer: product configuration, rating, underwriting, policy administration, billing, claims and commission systems.
• Integration layer: APIs, event streams, middleware and identity services connecting internal and external systems.
• Data and intelligence layer: customer records, interaction histories, analytics, fraud controls, reporting and decision models.
• Control layer: consent, access management, audit trails, security monitoring, compliance controls and records management.

An API, or application programming interface, is a defined method by which one system requests or exchanges data or functionality with another. APIs may allow a partner to obtain a quotation, initiate a policy, verify identity, report a claim or receive policy-status updates. Proper API design requires authentication, authorisation, data minimisation, rate controls, error handling, monitoring and clear responsibility for data quality.

A customer relationship management platform provides a shared view of interactions and opportunities. It should not be treated merely as a sales database. In an omnichannel environment it can support consent management, case ownership, service history, next-best action, complaints tracking and escalation. Its value depends on integration with policy and claims systems; a profile that is not linked to actual policy status can create misleading service experiences.

Identity resolution is another critical capability. Customers may use different email addresses, telephone numbers or devices across channels. The insurer must distinguish between a single customer with several identifiers and several customers sharing an identifier, such as family members using one email address. Weak identity resolution can create privacy breaches, duplicate communication and incorrect decisions.

Designing Web, Mobile, Contact-Centre and Assisted Journeys

Web journeys

Websites are particularly useful for education, product comparison, quotation, self-service and lead generation. Effective insurance websites explain coverage in plain language, distinguish benefits from exclusions, display assumptions used in a quote and provide access to relevant documents. Progressive disclosure is valuable: basic information is presented first, while technical detail is available when needed. Important exclusions should not be hidden behind design features that make them practically invisible.

Forms should be short, logically sequenced and capable of saving progress. Validation should occur close to the point of entry. The system should explain why sensitive information is required and should provide accessible alternatives where digital completion is difficult. A web journey should also accommodate customers who need advice rather than forcing every customer into an automated sale.

Mobile journeys

Mobile applications provide persistent identity, notifications, geolocation, camera-based document capture and access to connected devices. These capabilities are useful for policy cards, roadside assistance, wellness services, claim photographs and renewal reminders. Mobile design must account for limited screen size, intermittent connectivity, device loss and shared devices.

Biometric authentication or device-based authentication may improve convenience, but it does not remove the need for strong recovery procedures and fraud controls. Notifications should be timely and proportionate. Excessive promotional messages can reduce trust and lead customers to disable important service alerts.

Contact-centre journeys

The contact centre remains important for complex products, complaints, vulnerable customers, claims and moments when a digital process fails. An omnichannel contact centre should provide the agent with the customer’s recent activity, unfinished applications, documents, previous explanations and relevant policy information. Screen-pop functionality can reduce repetition, but it must be designed with privacy and role-based access controls.

Contact-centre performance should not be evaluated only by average handling time. Excessive pressure to shorten calls may increase repeat contacts, complaints and unsuitable sales. More balanced measures include first-contact resolution, customer effort, quality assurance, complaint recurrence, outcome accuracy and successful digital assistance.

Assisted digital journeys

Assisted digital service lies between self-service and traditional advice. An agent may send a secure link, co-browse a page, explain a coverage option, complete a form on behalf of a customer with permission or arrange a video consultation. The customer should remain aware of which actions are being taken, what information is being recorded and whether the interaction constitutes regulated advice.

Assistance is especially important for older customers, people with disabilities, customers with limited digital skills and customers experiencing distress during a claim. Digital inclusion is not achieved by offering a digital channel alone; it requires accessible design, alternative routes and staff capability.

Digital Advice, Automation and Decision Quality

Automation can support pre-filling, document classification, eligibility checks, fraud screening, customer-service responses and claims triage. Rules-based automation is generally easier to explain and audit. Machine-learning models may identify patterns that are difficult to specify manually, but they introduce risks related to bias, opacity, data drift and inappropriate proxies.

A digital recommendation should be appropriate to the customer’s circumstances and the nature of the product. Personalisation becomes problematic when it manipulates rather than assists choice, exploits vulnerability or uses data beyond reasonable customer expectations. A “next-best action” model should therefore be constrained by product suitability, consent, fairness, explainability and human review requirements.

Human intervention should be designed, not merely promised. Organisations need thresholds for referral, override procedures, quality testing, model monitoring and complaint-based feedback. Where an automated decision has significant consequences, customers should receive meaningful information about the decision and a practical route for review, subject to applicable law.

Insurtech Platforms, Marketplaces and Embedded Insurance

Insurtech refers broadly to technology-enabled innovation in insurance. It includes digital brokers, automated underwriting services, claims platforms, telematics, health applications, fraud analytics, identity services, cloud infrastructure and customer-engagement tools. An insurtech provider may be a distributor, a technology supplier, a managing agent, a data intermediary or a competitor. Strategic evaluation must therefore examine both capability and role.

Digital marketplaces aggregate products or providers and enable customers to compare price, features and sometimes service quality. They can increase reach and transparency, but comparison based primarily on price may encourage underinsurance or obscure differences in exclusions, limits and claims support. Insurers should assess the quality of information presented by the marketplace and the incentives created by ranking, commission and sponsored placement.

Embedded insurance integrates an insurance offer into a non-insurance purchase or service. Examples include travel cover during ticket booking, device protection at the point of sale, motor cover within a vehicle platform and payment protection associated with finance. Embedded distribution can reduce search costs and connect cover with a relevant risk event. Its weaknesses may include low customer attention, limited understanding of terms, unclear responsibility among partners and the danger that insurance becomes an unnoticed add-on.

The commercial model must specify who owns the customer relationship, who provides advice, who handles complaints, who communicates renewal terms, who controls data and who is responsible when an API or partner process fails. The insurance product must remain suitable even when sold in a highly simplified interface.

Evaluating Ecosystem Partnerships

Partnership selection should begin with a customer problem rather than a fashionable technology. A partner may provide reach, trust, data, distribution capability, service infrastructure or a complementary product. The insurer should test whether the partnership creates incremental value or merely shifts existing customers from one channel to another at a higher cost.

A structured evaluation can consider:

1. Strategic fit with target segments and product objectives.

2. Customer value and improvement in convenience, relevance or protection.

3. Regulatory permissions, conduct capability and reputational standards.

4. Technical interoperability, resilience and information-security maturity.

5. Data rights, consent, retention and restrictions on secondary use.

6. Economics, including acquisition cost, revenue sharing, claims cost and exit cost.

7. Operational accountability for sales, service, complaints and incidents.

8. Scalability, portability and dependence on the partner.

Partnership contracts should define service levels, audit rights, incident notification, business continuity, subcontracting, model changes, data deletion, customer communications and termination assistance. Governance should include joint operating committees and clear escalation paths rather than relying solely on contractual language.

Channel Economics and Migration Strategy

Digital channels are often assumed to be inexpensive because they reduce manual processing. This assumption can be misleading. Digital distribution may require substantial investment in platforms, cybersecurity, analytics, content, integration, compliance testing and continuous optimisation. The correct comparison is total cost to serve and customer value over the relationship, not the cost of a single online transaction.

Relevant measures include conversion rate, quotation-to-bind ratio, abandonment rate, cost per acquired customer, cost per active policy, renewal rate, digital servicing rate, contact deflection, repeat contact, complaint rate, claim-cycle time, fraud incidence and customer lifetime value. Metrics should be segmented by product, customer group, channel and journey stage. A high conversion rate accompanied by poor persistency or high complaints does not indicate a successful channel.

Channel migration should be managed as a behavioural and organisational change programme. Customers may be encouraged to use digital billing, document access or renewal through convenience, education and appropriate incentives. They should not be forced into digital channels when a reasonable alternative is needed. Employees and intermediaries must also be included. Agents can become digital advisers who generate leads, support remote meetings and help customers use self-service tools.

A staged migration commonly begins with low-risk informational and servicing activities, followed by transactions, claims notifications and more complex advice. Each stage should have service safeguards, monitoring and a rollback plan. Migration decisions should be based on evidence of customer readiness and operational stability rather than an arbitrary timetable.

Risks, Limitations and Common Mistakes

Digital distribution creates several connected risks. Cybersecurity failures can expose personal and financial information or disrupt claims and payments. Third-party outages can interrupt an entire journey when the insurer has outsourced a critical capability. Poorly designed interfaces can cause customers to select inadequate cover or misunderstand exclusions. Automated underwriting can reproduce historical bias. Excessive personalisation can become intrusive surveillance.

Common mistakes include launching an application without integrating it with policy administration, measuring downloads rather than meaningful use, treating chatbots as a substitute for service design, ignoring accessibility, allowing inconsistent product wording across channels, and failing to test journeys under stressful conditions. Another mistake is to regard a partner as merely a source of leads. In an ecosystem, the partner’s conduct becomes part of the insurer’s customer experience and may affect the insurer’s reputation and regulatory exposure.

Resilience requires redundancy, tested recovery procedures, manual workarounds and clear customer communication during outages. Security should follow a defence-in-depth approach involving encryption, secure development, least-privilege access, multifactor authentication, monitoring, penetration testing and staff awareness. Privacy should be embedded at the design stage through data minimisation, purpose limitation, retention controls and privacy impact assessment.

Ethical, Regulatory and Governance Considerations

Digital insurance must comply with applicable insurance, consumer-protection, privacy, electronic-transaction, accessibility, cybersecurity and outsourcing requirements. Specific rules vary by jurisdiction, but recurring principles include fair treatment, informed consent, transparent communication, suitable advice, secure handling of information, accurate records and accountable governance.

The customer should be able to identify the insurer, intermediary and relevant service provider. Disclosures must be understandable and presented at a time when they can influence the decision. Consent should not be bundled unnecessarily with unrelated marketing permissions. Customers should have practical mechanisms to correct information, complain, obtain assistance and challenge an inappropriate outcome.

Governance should cover product approval, digital-content approval, algorithm oversight, partner due diligence, vulnerability assessment, incident response and periodic conduct reviews. Boards and senior managers need meaningful reporting, not only technical uptime statistics. Useful reporting combines customer outcomes, operational resilience, data incidents, complaints, fairness indicators and financial performance.

Illustrative Case: Meridian General Insurance’s Connected Motor Journey

Background

Meridian General Insurance, a fictional mid-sized insurer, sold motor policies through agents, branches and a call centre. It launched a mobile quotation service after observing that many customers began their search on smartphones. The application was not integrated with the agent and call-centre systems.

Situation and problem

Customers who abandoned the mobile journey had to repeat their information when calling. Agents could not see online quotations, and renewal reminders directed customers to a website that did not recognise their existing credentials. Conversion appeared satisfactory, but complaints about repetition and inconsistent prices increased. The insurer also discovered that its marketplace partner displayed a simplified description that did not adequately communicate a major excess.

Analysis

Meridian mapped the quotation, purchase, policy-service and claim-notification journeys. It found three major issues: fragmented identity, inconsistent product content and unclear ownership of customers referred by the marketplace. It also found that the mobile application generated leads but did not distinguish customers seeking information from customers ready to buy.

Approach and solution

The insurer created a shared customer identity service and integrated the application, CRM and policy platform through controlled APIs. An unfinished quotation could be resumed by the customer or securely transferred to an authorised agent. The call centre received the customer’s consented interaction history and was trained to provide assisted digital support rather than restart the sale.

Meridian established a single approved content library for web, mobile, marketplace and agent materials. The marketplace contract was revised to specify disclosure standards, complaint escalation, data use and incident reporting. The insurer added a coverage-comparison screen showing key exclusions and introduced a human referral when customer answers indicated uncertainty or a complex risk.

Migration was staged. Existing customers first received digital document access and renewal reminders, while non-digital alternatives remained available. Performance reporting combined conversion, persistency, repeat contacts, complaints, customer effort and claims outcomes.

Outcome

The fictional case assumes that Meridian reduced repeated data collection, improved continuity between agents and digital channels, and gained better visibility of marketplace conduct. The principal improvement was not the application itself but the integration of people, process, content, data and governance around the customer journey.

Learning points

The case demonstrates that omnichannel capability is an operating model rather than a collection of interfaces. It also shows why partner governance, consistent disclosures and assisted service are essential to responsible digital growth. Finally, migration should be judged by customer and business outcomes, not by the number of users registered on a platform.

Current Developments and Emerging Directions

Several developments are likely to influence insurance distribution. Generative AI may support service agents, summarise interactions, search policy wording and draft personalised explanations. Its use requires controls against fabricated answers, confidential-data leakage, unapproved advice and inconsistent treatment. Retrieval from approved knowledge sources, human review and comprehensive logging are important safeguards.

Open insurance and broader data-sharing arrangements may allow customers to authorise movement of information between providers. These arrangements can reduce friction but increase the importance of consent quality, data accuracy and liability allocation. Real-time data from connected vehicles, homes and wearable devices may enable more dynamic services, although continuous monitoring raises questions of fairness, privacy and customer choice.

Composable technology architectures, cloud services and low-code tools can accelerate experimentation. They can also increase dependency on vendors and create undocumented complexity if governance is weak. Digital identity, electronic signatures, instant payments and automated claims services may make insurance more embedded in everyday transactions.

The durable trend is not the disappearance of human distribution. Rather, human interaction is likely to become more focused on advice, empathy, exceptions, complex risks and trust-building, while routine information and transactions become increasingly automated.

Best-Practice Principles for Managers

Managers designing digital and ecosystem distribution should:

• begin with customer journeys and protection needs, not technology features;
• provide continuity of identity, data and case status across authorised channels;
• make coverage, exclusions, price assumptions and advice status clear;
• design assisted-service and non-digital alternatives into the operating model;
• measure customer outcomes as well as acquisition and digital activity;
• govern APIs, algorithms, vendors and partners throughout their lifecycle;
• apply security, privacy, accessibility and resilience by design;
• test journeys with diverse customers, including vulnerable users;
• train employees and intermediaries to support digital adoption;
• use pilots, evidence and staged migration rather than irreversible transformation.

Chapter Summary

Digital distribution has transformed insurance from a set of separate sales routes into an interconnected service system. Multichannel availability is different from omnichannel continuity, while ecosystem distribution adds external partners, shared capabilities and new governance responsibilities. Effective design begins with customer journeys and integrates web, mobile, contact-centre and assisted-service experiences through identity, CRM, APIs, core insurance systems and controlled data flows.

Insurtech, marketplaces and embedded insurance can expand reach and reduce friction, but they also create risks relating to suitability, transparency, partner conduct, privacy, cybersecurity and operational resilience. Channel economics should be assessed through total cost, customer lifetime value, persistency, service quality and customer outcomes. Migration requires staged implementation, inclusion of agents and employees, and alternatives for customers who need human assistance.

The strategic task for insurance managers is to combine digital convenience with advice, accountability and trust. Technology is valuable when it improves protection and service without weakening fairness, comprehension or control.

Key Terms

API: A defined technical interface that enables systems to exchange data or functionality.

Assisted digital service: Support that helps a customer complete a digital activity with human guidance.

Channel migration: Movement of customers or activities from one distribution or service channel to another.

Customer journey: The sequence of customer interactions and decisions associated with a need, transaction or service outcome.

Digital marketplace: A platform that aggregates and presents products from multiple providers for comparison or purchase.

Embedded insurance: Insurance offered within a non-insurance product, service or transaction.

Ecosystem distribution: Distribution involving an interconnected group of insurers, partners, platforms and service providers.

Identity resolution: The process of determining whether records from different channels relate to the same customer.

Insurtech: Technology-enabled innovation, firms or applications applied to insurance activities.

Multichannel distribution: The provision of more than one channel without necessarily integrating them.

Omnichannel distribution: Integrated channel management that provides continuity of information and service across authorised touchpoints.

Progressive disclosure: Presenting essential information first and additional detail as the user requires it.

Customer effort: The amount of work a customer must perform to obtain a product, service or resolution.

Embedded application programming: Use of integrated interfaces to place insurance functionality inside a partner journey.

Platform governance: Rules and processes controlling access, data, conduct, performance and accountability on a digital platform.

Digital adoption: The extent to which customers and employees use digital processes effectively and repeatedly.

Data minimisation: Collection and use of only the information necessary for a legitimate purpose.

Model drift: Change over time in the performance or accuracy of an analytical or automated decision model.

Customer lifetime value: The expected economic value of a customer relationship over its duration.

First-contact resolution: Resolution of a customer issue during the initial service interaction without avoidable repeat contact.

Review Questions

Short Answer Questions

1. Distinguish between multichannel and omnichannel insurance distribution.

2. What is the role of an API in an ecosystem distribution model?

3. Define embedded insurance and give one suitable example.

4. Why is identity resolution important in an omnichannel environment?

5. State two measures that should complement digital conversion rate.

Long Answer Questions

1. Explain how an insurer can design a connected web, mobile and contact-centre journey.

2. Discuss the strategic opportunities and risks of digital marketplaces and embedded insurance.

3. Examine the architecture and governance requirements of an omnichannel insurance operation.

4. Explain how insurers should manage channel migration while preserving inclusion and service quality.

5. Discuss the ethical, regulatory and cybersecurity issues associated with automated digital insurance.

Analytical / Application Questions

1. An insurer has a high online conversion rate but increasing complaints, cancellations and repeat calls. Analyse the possible causes and recommend a measurement and improvement plan.

2. Design a partner-evaluation framework for an insurer considering a partnership with a vehicle manufacturer and telematics platform.

3. A customer begins a health-insurance application online, seeks advice by telephone and later visits an agent. Specify the data, process and governance capabilities required to make this journey seamless and suitable.

22. Multiple Choice Questions with Answers

Question 1

Which feature most clearly distinguishes an omnichannel insurance model from a multichannel model?

A. The insurer offers at least three communication channels

B. The insurer uses digital advertising to attract customers

C. Customer information and journey status continue across authorised channels

D. The insurer allows customers to purchase policies online

Correct Answer: C. Customer information and journey status continue across authorised channels

Question 2

A customer abandons an online quotation and calls the contact centre. Which capability most directly prevents the customer from repeating all information?

A. A shared identity and interaction-history system

B. A higher digital advertising budget

C. A separate call-centre product catalogue

D. A longer online application form

Correct Answer: A. A shared identity and interaction-history system

Question 3

What is the primary strategic characteristic of embedded insurance?

A. It is sold only through a traditional broker

B. It is integrated into a relevant non-insurance transaction or service

C. It excludes all human assistance

D. It is available only after a claim occurs

Correct Answer: B. It is integrated into a relevant non-insurance transaction or service

Question 4

Which metric would best reveal that a high digital conversion rate is not producing healthy customer outcomes?

A. Application page colour preference

B. Number of application downloads

C. Office occupancy rate

D. Persistency and complaint rates after purchase

Correct Answer: D. Persistency and complaint rates after purchase

Question 5

Why should an insurer govern a marketplace partner’s product descriptions?

A. The partner’s presentation can affect customer understanding, suitability and conduct risk

B. Marketplaces determine the insurer’s internal claims reserves

C. The partner automatically becomes the insurer’s underwriter

D. Product descriptions have no effect on customer decisions

Correct Answer: A. The partner’s presentation can affect customer understanding, suitability and conduct risk

Question 6

Which practice best reflects privacy by design in an omnichannel system?

A. Collecting every available data item for possible future use

B. Sharing all customer data with every ecosystem partner

C. Collecting necessary information for specified purposes with appropriate consent and controls

D. Removing all audit records after a transaction

Correct Answer: C. Collecting necessary information for specified purposes with appropriate consent and controls

Question 7

An insurer wants to migrate customers from branch servicing to digital servicing. Which approach is most responsible?

A. Immediately close all branches

B. Use staged migration, provide assistance and retain reasonable alternatives

C. Require customers to use digital channels for complaints

D. Measure success only by application registrations

Correct Answer: B. Use staged migration, provide assistance and retain reasonable alternatives

Question 8

What is a major governance concern when machine-learning models are used in underwriting or customer treatment?

A. The model may create opaque or unfair outcomes because of biased data or proxies

B. The model always eliminates the need for regulatory review

C. The model cannot process any customer information

D. The model makes cybersecurity controls unnecessary

Correct Answer: A. The model may create opaque or unfair outcomes because of biased data or proxies

Question 9

Which partner-evaluation criterion is most relevant to resilience in an insurance ecosystem?

A. The partner’s office decoration

B. The partner’s ability to provide continuity, security and incident response

C. The partner’s preference for printed brochures

D. The partner’s number of social-media followers alone

Correct Answer: B. The partner’s ability to provide continuity, security and incident response

Question 10

In the illustrative Meridian case, what was the central lesson?

A. A mobile application can replace all intermediaries

B. Price comparison is sufficient for suitable insurance sales

C. Omnichannel success requires integration of technology, people, content, process and governance

D. Marketplace partnerships eliminate the need for disclosure

Correct Answer: C. Omnichannel success requires integration of technology, people, content, process and governance