search

PriceComparisonStandardsGroup / AddOns

7 stars 9 forks source link

Interpretation of free addons #15

Open tommichaelis opened 8 years ago

tommichaelis commented 8 years ago

As a free addon is optional, but free, it's not necessarily clear how the addon should be shown on PCWs. There appear to be two options:

  1. Show the addon as 'included' (in the same way as a bundled addon is shown)
  2. Show the addon as not included, but addable for no cost

Option 1 causes issues if the addon is not automatically included after click through - the customer may see that the addon is included and clicks through on the PCW, but then the addon is not included on the insurer's site. This may cause confusion to the customer, and they may end up not including the addon after clicking through to the partners site as they thought it was already included.

Option 2 is safer - the customer has to explicitly add the addon on the PCW, so this should be transmitted in the deeplink. However it still presents opportunity for confusion if the addon is included automatically after clickthrough and also gives a somewhat worse user experience on the PCW's side as the user sees policies with fewer ticks.

Unless there is clarification on this, uSwitch is planning to implement Option 1, for better user experience. We will be communicating to partners implementing the addons standard that we expect free addons to be automatically selected when the customer clicks through, and that we will show it as included on the PCW.

DaveFoxOpenGI commented 8 years ago

In my view, the FCA do not want any Addon to be pre-selcted and then needing the customer to remove it if they do not want it (regardless of price). So just because this optional add-on is 'Free' I do not see wht it should be automatically included - as the Customer would then have to remove it - contravening what the FCA require.

tommichaelis commented 8 years ago

I've assumed that because the 'GuidanceOnClickThrough' document suggests it would have been possible to have a deeplink that didn't include free addons, the assumption was that these addons would be shown as included on the partner's site. Also, I'm not sure what the point of having a 'Free' type is if it's behaviour is identical to an 'Incremental' type with a price of 0. So I think the spec as we currently have it is more in keeping with my Option 1.

However, I do think both options are reaonable, and certainly Option 2 feels potentially nicer in some regards (there's certainly less scope for the customer to end up with something they didn't want). @DaveFoxOpenGI - is OpenGI currently planning on implementing this with free addons not automatically included?

DaveFoxOpenGI commented 8 years ago

We are allowing both 1) a free 'thing' to be either bundled (and hence always included with the main policy) or 2) selectable as a 'free' optional extra. Scenario 1) the addon cann be de-selected so on deep link we do not need to be told it has been 'selected' because fundamentally it will always be included due to it being bundled. Scenario 2) Because it is an add-on it cannot be included yb default with the customer havng to remove it.. i.e. a 'Free Gift' should not be auto included but should be selectable, and hence would be passed thru on deep link to let the site know what was selcted on the PCW ..