Use the contact page to reach the concerned department and request a product walkthrough. Please include organisation type, required modules, approximate user count, preferred timeline and integration needs. Do not send passwords, identity documents, health information or real customer/policy data in an initial enquiry.
Make the product demonstration productive
Important: Confirm feature availability, service commitments, legal text and contact details before relying on or publishing this information. Product capability is not a claim of regulatory approval or insurer partnership.
Share the organisation type, primary insurance lines, approximate user groups, current tools and the workflows you want to improve. Avoid sending policyholder personal data or confidential documents through a general enquiry form.
A useful demo can cover lead capture, customer records, servicing queues, POSP workflows, commission visibility, renewal tasks, reporting or integration planning based on your priorities.
After the walkthrough, document open questions, required integrations, data migration considerations, security expectations, success criteria and the proposed next step such as a requirements workshop or scoped proposal.
A demonstration may use sample or illustrative data. Confirm which capabilities are production-ready, which require configuration, and which are planned or dependent on external systems.
Expanded guide · Insurance technology
A productive demonstration starts with your business context. Tell the team whether you represent an insurance broker, IMF, corporate agent, POSP network, corporate insurance department or technology partner. Identify the processes you want to improve, such as lead management, policy tracking, commission reconciliation, renewals, service requests, reporting or document handling.
A typical walkthrough may cover user roles, lead and customer records, task queues, policy information, renewal reminders, commission reports, dashboards and administration settings. If integrations are important, discuss the external provider, data fields, access approval and sandbox availability. A demonstration should clearly distinguish working functionality from mock-ups, planned features or custom development.
Before the meeting, gather a short list of current tools, recurring bottlenecks, approximate user numbers, reporting needs and any migration constraints. Avoid sending real customer or policy data in an initial enquiry. Sample or anonymised records are usually sufficient for a first discussion. If detailed data is required later, use an approved secure process and appropriate agreements.
The next step may be a requirements workshop, a written scope, an implementation estimate or a limited proof of concept. Confirm who owns each action, what must be validated, and how success will be measured. A request for a demonstration does not itself create a subscription, implementation commitment or insurer integration.
Choose whether you are a new or existing customer, select the product module and department, and share the details needed to route your request. Do not enter passwords, payment card data, or sensitive policyholder health information.
Department
No matching pages found.
