Salespeople are told that they should qualify a customer and find out about their vehicle requirements rather than asking about budget.
This seems to make sense. Have any of you gone in to buy a car, or anything else, and been insulted with the budget question before a salesperson has even asked about how you plan to use the product, or what features you might be interested in?
But even if this is the case, would it be fair to say that you have a rough idea of the amount of money you will be spending on a purchase?
What I need to know, for Choose-O-Matic, is whether we should use a price filter to try and point the consumer in the direction of the right range of vehicles for them to consider. Additionally, if we do include it, should it be the first item in the list for consumers to adjust, or the last item?
Subscribe to:
Post Comments (Atom)
2 comments:
I say yes - do include it, and it should be first, but then I'm biased!
Just remember that sales people and web sites are not the same thing - or necessarily comparable (although we all draw parallels all the time).
Every time you leave prices off a web site, the instant assumption / question from consumers is "where is it" or (just like when you crop out parts of cars in photos) "what are you hiding".
It's weird, possibly because the web is mainly, in people's minds, anonymous - so it's not the same as someone coming up to you in a store and saying "how much do you have in the bank". Also remember our underlying theme is empowerment - and being able to dictate a price is part of that.
Now - as to how price should be handled (an exact value, pre-defined ranges or completely user flexible) - that's an interesting question ;-)
Mark - you should do less thinking. It can't be good for you.
I think, after lengthy consultation in the pub (where were you?), we should have price - it should not be the first option and it should be fixed fuzzy logic that provides for a flexible budget.
Clear, or just murkier than ever?
Post a Comment