Contact the Relevant Department

For pricing, product walkthroughs, implementation proposals, integrations and support enquiries, contact the concerned department through your verified official business email or published business contact channel. Before launch, replace this placeholder contact guidance with monitored contact details and test delivery end to end.

Contact the Relevant Department Request a Demo

Route your enquiry to the right team

Sales and product demonstration
Pricing and commercial proposals
Implementation, integrations and support
Responsible enquiry handling

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.

Route your enquiry to the right team

Sales and product demonstration

Use this route to discuss product capabilities, business workflows, user requirements and a tailored demonstration. Share enough context for the team to direct the request without including sensitive customer records.

Pricing and commercial proposals

Provide the modules of interest, approximate user count, branches, implementation needs and any required integrations. The concerned department can assess scope and prepare the appropriate commercial response.

Implementation, integrations and support

Describe the intended outcome, current system, urgency and any known dependency. Existing customers should use their agreed support channel for account-specific or production issues.

Responsible enquiry handling

Forms should collect only necessary information, show a clear privacy notice and route requests to an authorised mailbox or ticketing system. Automatic delivery, ticket creation and response tracking must be configured and tested.

Expanded guide · Insurance technology

Contact the right team for your enquiry

Sales and product enquiries
Contact the sales team to discuss insurance CRM, policy administration, POSP management, commission workflows, accounting ERP, analytics or AI-assisted operations. Include the type of organisation, business objective, approximate user count and desired timeline. This helps route the enquiry to the appropriate team and avoids unnecessary back-and-forth.
Pricing and implementation
For subscription plans, custom development, data migration, integrations, training or enterprise deployment, request a written scope and estimate from the concerned department. The final proposal should identify deliverables, assumptions, dependencies, milestones, payment terms and support arrangements. Do not treat indicative package labels as a binding quotation.
Support and technical discussions
Existing customers should use their agreed support channel and provide a concise issue description, affected module, time of occurrence and non-sensitive reference details. Never include passwords, access tokens, full payment card details or unnecessary customer information in an ordinary contact form. Critical incidents should follow the escalation process defined in the applicable service agreement.
Contact form quality and privacy
A contact form should collect only the information needed to respond, explain how the information will be used and link to the applicable privacy notice. Enquiry delivery should be tested, including confirmation messages, spam protection and routing to an actively monitored mailbox. Replace all placeholder contact details with verified company information before launch.