quick note to tell someone to verify something

Quick note to tell someone to verify something verification#
Quick note to tell someone to verify something free#

And for sales and metrics use just the data from the first one.īased on the given information this could solve your task.First, let’s talk about the 3 common mistakes people make when writing a polite follow up email so you know what to correct when writing your next email. And make the first one (at least in the description) less attractive for the kids. Your primary goal is to get rid of the kids accounts, but keep the conversion convenient for the teachers. They'll find a mail adress or google a given questions. Thought #2: As you described your problem purely from the side of sales effort due to kids accounts you don't need their mail for further sales process. But as you described this is a additional potential point of conversion loss.

So those kids (if not instructed by the teacher - do not harm your profits) I assume your business model is to sell to the teachers. It's more the noise in your data and sales effort. I think your problem aren't the kids or the (technical) costs they produce.

Quick note to tell someone to verify something verification#

I wouldn't worry about users' time, it seems like they're having fun playing your game, you should be proud! I'd be tempted to say: so what if your conversion rate from demo to sales looks bad - will the change increase your sales? I doubt that 'fixing' the conversion rate by adding a verification roadblock in front of your demo, to make sure that your denominator only includes 'serious' people, will increase your sales. From what you are saying ( 'waste of time, and messes up our metrics on the value of having the demo'), this sounds like at least the demo isn't causing you to bleed cash and maybe you have more of a metrics problem. Think carefully about the cost of these measures compared with the cost of your current situation. You can also ask yourself - since you're going to ask the user to jump through some hoops and provide information required for verification - what else would you be able to offer to that user that would be valuable to them? For example, if your product sends email reports, could you use the email to send an example report and make that part of the value proposition for your demo? That might increase the value to the user of doing the legwork to verify themselves. You can let the user into the demo for a few seconds and then ask them for the phone number to continue.

Informing users of the purpose of info collection is good UX practice in general but note that some regulations such as GDPR or plain-old consumer protection regulations might make this a stronger requirement. It doesn't always need to be spelled in legalese, e.g. if you're asking for email or phone number for verification only, make it clear that you'll only use it for verification and don't intend to spam the user later. Make the purpose plain and stick to it, e.g.

Quick note to tell someone to verify something free#

instead of 'Please enter your phone number for verification purposes', you can have something like 'Let's get started with your free demo! First, what's your phone number? We'll use this to send you an access code.' You can ask verifying information, and don't need to offer justification for why - you don't need to say, for example 'we ask this to make sure you're a serious prospect.' You can make it less painful by:Īsking for info with an upbeat tone, e.g.