Building a Quick Quote process

From SchemeServe Help
Jump to: navigation, search

Introduction

Note: This is a guide for your in house web-designers and developers only. ADM Networks do not support HTML and Javascript usage and thus any action taken using the information below is at your own risk.


It is understood that for some types of insurance (for example; motor insurance) that it might be best to offer a “quick” and indicative quote prior to developing a full quotation. This can be facilitated in SchemeServe using the steps given below:


Creating a Quick Quote Page

Assumption: You have already created a Scheme and the questions necessary for a full quotation.


Assumption: For this example the SchemeId for the Scheme is 1 – you will need to substitute your own SchemeId where appropriate.


  1. Create a page for the Quick Quote process to be visible on
  2. On this page, Click the Source View and add HTML to represent the form you want for your quick quote (for example: You might want to include Postcode and the Property Construction Date as input fields for Landlord's insurance)
  3. You can add an HTML button for the user to click for a quote OR alternatively you can add JavaScript later to automatically reconfigure the quote every time a change is made to the values in the fields
  4. You should add a button or HTML link that the user can use to access a full quotation if they're happy with the quick quote. You could use Javascript to show this button only once the quick quote process is complete. NOTE: The URL that you link to for this should be similar to this: https://TEST.schemeserve.com/getquote/agent.aspx?schemeId=SCHEME_ID_1 Where “TEST” is the subdomain of the SchemeServe website you are using and the “SCHEME_ID” is changed to represent the Scheme ID that you are using.
  5. Save your changes before proceeding
  6. Go to the custom JavaScript process
  7. Add the custom JavaScript that calculates the quick quote based on the HTML form you have created. This will need to use values entered by the user to lookup up premium combinations. Developers should keep this JavaScript as concise as possible to minimize the risks of length and unmanageable JavaScript in the future.