|
|
Francois Vadrot
|
Francois Vadrot
Member since : Feb-27-2008 (Verified)
|
| qPoint Balance |
103 |
| Votes Cast |
2 |
| Comments Posted |
0 |
| Topics/Ideas Posted |
4 |
| Topics/Ideas Tracking |
0 |
| | |
|
Ideas/Topics Posted
|
|
Suppose you want to know satisfaction of a large population about a service (for instance 20,000 subscribers to a newsletter). You don't need to survey the whole population. Depending on involvement's level of the population, you will expect from 10% to 40% of completed answers. So to get some 1,000 respondents, in the worst case, you don't need to question the whole population: you will extract a sample, which is representative of the whole population on one or two criterions (company's size, localization, age...). By now you have to extract and manage samples outside QuestionPro, and then to inject them in dedicated mailing-lists. My suggestion is to offer the possibility of injecting the whole population with criterions (as custom variables) and of extracting samples automatically (with marking of the people). By this way, it would be easier to launch the same survey or different surveys toward different samples.
|
|
|
Preliminary note: I am not sure this suggestion fits in "Survey development". It concerns the general development of QuestionPro. If not, please do create a special topics on this subject: "QuestionPro's development". But please don't delete it, for it could be important to you to know if others customers feel it as I do.
On this post, I suggest to open a bugtracking to customers (at less to enterprise or corporate), allowing to know actual dysfunctions, to propose/declare new ones and to follow their solving.
QuestionPro is a great service, but as every service which grows very quickly and becomes very powerful and complex, there are inevitable dysfunctions. From my own experience, I find very difficult to make support accept the idea of a bug/dysfunction. And when it's obvious that there is a problem, one get always the same laoonic answer: "I will have our developers look into this". And the problem falls in a "black hole".
After months of persistence I convinced support to admit one (wrong codage of headers in e-mail) and to fix it. But I discovered several obvious others about which I have got no positive acceptance, and consistently no news. As you are in a process of making customers participating to Questionpro's development (which suggests opening or IdeaFactory, great idea!), it would be great too to open a bug tracking service to your customers.
Moderator Comments
|
|
|
I would like to be able to manage several invitations e-mail for a specific survey. It would be useful in these cases for example :
1/ I've got different kinds of populations to survey : one kind we know very well, another kind of CEOs, another of people we don't know well. Each kind needs a specific e-mail to invite them properly to look at the survey and to complete it.
2/ I want to send a different invitation e-mail to remind the non-respondents. And to complicate the process, I'll have to launch reminder before a second wave of the survey (corresponding to a second sample).
3/ etc.
To do this, by now, I have to modify e-mail invitation at each time I send an invitation. So I copy/paste in an editor to keep it. Not very practical, and source of errors. An extension of this suggestion would be to manage models (templates) of invitations in a library (as for surveys and questions).
|
|
|
Hi,
By now reminder send invitation e-mail to people who have not completed a survey, i.e. even to people who have partially answered a survey (I have tested it in detail on a test survey, after several respondents complain).
I suggest that either 1/ you let the choice sending reminder to people who have not completed, or to people who have not starded, or 2/ that you change the rule to only send reminder to people who have not started.
It's a communication issue, for people who have started, but not completed, did so for peronal reasons (or forget to clic on end button), and are not very happy to receive a reminder.
Friendly
François
|
Comments Posted
Activity Stream
|
Vote Up
Vote Down
Under Review
Completed
Close