Providing direct feedback to a product salesperson Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 23, 2019 at 23:30 UTC (7:30pm US/Eastern)Asked to speak to prospective employees about a company I'm dissatisfied withIs it fair to apply for jobs where the interest with the service/product niche isn't a good match?Proper response after finding out that another team works on the projectRequest from client of ex-employer for recommendations of new providerHow can I (being lower on my dept's ladder) respectfully tell a 3rd party salesman to wait?Appropriate way for a non-IT analyst to report bug and propose fix?Can NOT receiving negative feedback hurt me in the long run?How to respond to unprofessional emailReturning to a Company in a Different PositionRumors spreading about me leaving my current job
Protagonist's race is hidden - should I reveal it?
Can gravitational waves pass through a black hole?
Are Flameskulls resistant to magical piercing damage?
Pointing to problems without suggesting solutions
tabularx column has extra padding at right?
Does using the Inspiration rules for character defects encourage My Guy Syndrome?
Compiling and throwing simple dynamic exceptions at runtime for JVM
Is "ein Herz wie das meine" an antiquated or colloquial use of the possesive pronoun?
A journey... into the MIND
What's the connection between Mr. Nancy and fried chicken?
What is the difference between 准时 and 按时?
Kepler's 3rd law: ratios don't fit data
A German immigrant ancestor has a "Registration Affidavit of Alien Enemy" on file. What does that mean exactly?
What is her name?
2 sample t test for sample sizes - 30,000 and 150,000
How to create a command for the "strange m" symbol in latex?
How to break 信じようとしていただけかも知れない into separate parts?
What helicopter has the most rotor blades?
Who can become a wight?
Can I take recommendation from someone I met at a conference?
Why isn't everyone flabbergasted about Bran's "gift"?
What is the evidence that custom checks in Northern Ireland are going to result in violence?
Why did Bronn offer to be Tyrion Lannister's champion in trial by combat?
Coin Game with infinite paradox
Providing direct feedback to a product salesperson
Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 23, 2019 at 23:30 UTC (7:30pm US/Eastern)Asked to speak to prospective employees about a company I'm dissatisfied withIs it fair to apply for jobs where the interest with the service/product niche isn't a good match?Proper response after finding out that another team works on the projectRequest from client of ex-employer for recommendations of new providerHow can I (being lower on my dept's ladder) respectfully tell a 3rd party salesman to wait?Appropriate way for a non-IT analyst to report bug and propose fix?Can NOT receiving negative feedback hurt me in the long run?How to respond to unprofessional emailReturning to a Company in a Different PositionRumors spreading about me leaving my current job
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
I work in tech in a decision making capacity on an Analytics team, and have just moved positions in the last couple of months.
In my former role, I inherited a team using a data analysis product, well known in our field, that seemed well suited to the needs of the organization from a reporting / analysis standpoint.
However, our experience with the product was not good, support was lacking, the product itself was expensive, and new features the product released seemed like they were taking the organization in a direction that would not make it any more useful for us.
The software would periodically ask for feedback on how we were using it, and whether we'd recommend it to peers. I took every opportunity to provide a low rating and some reasoning each time I was asked, but didn't specifically speak to our representative due to being busy with other tasks. The product still worked technically for our use case and it didn't seem worth creating an issue based on our frustrations with the product. There were bigger fish to fry.
Now, in my new role, a salesperson for the same product has found me on a networking site. They know my former role and that we were customers, and have reached out to ask me to set up a meeting with my new employer.
I am in a position to recommend new software and solutions in my new role, but obviously I'm not at all interested in recommending this product to my current employer. We already have a suite of data analysis tools, which, while not perfect either, are an improvement over the product on offer.
Now, here's my dilemma. I've been bugged in many roles by persistent salespeople who want to get a conversation started. I don't blame them, although I find it distracting and would prefer to avoid having multiple conversations to convince them I'm not interested. In this case, I can supply a laundry list of reasons why I was dissatisfied with their offering in my former role, and I feel like it would be quicker to just explain that my prior experience was not a good one, and that I would not under any circumstance recommend their product, rather than remaining vague and giving my usual answer (something along the lines of "we already have a satisfactory platform implemented", which doesn't sit well with salespeople who want to convince me their product is superior).
Is there any reason why I should avoid being honest and explaining that I'm a dissatisfied customer? I don't think it reflects poorly on my current or previous employer, and I'm not speaking for anyone who would like to consider new products in this area as it's ultimately my decision, but I paused on the send button and want to make sure I'm not about to make a mistake.
professionalism sales
New contributor
add a comment |
I work in tech in a decision making capacity on an Analytics team, and have just moved positions in the last couple of months.
In my former role, I inherited a team using a data analysis product, well known in our field, that seemed well suited to the needs of the organization from a reporting / analysis standpoint.
However, our experience with the product was not good, support was lacking, the product itself was expensive, and new features the product released seemed like they were taking the organization in a direction that would not make it any more useful for us.
The software would periodically ask for feedback on how we were using it, and whether we'd recommend it to peers. I took every opportunity to provide a low rating and some reasoning each time I was asked, but didn't specifically speak to our representative due to being busy with other tasks. The product still worked technically for our use case and it didn't seem worth creating an issue based on our frustrations with the product. There were bigger fish to fry.
Now, in my new role, a salesperson for the same product has found me on a networking site. They know my former role and that we were customers, and have reached out to ask me to set up a meeting with my new employer.
I am in a position to recommend new software and solutions in my new role, but obviously I'm not at all interested in recommending this product to my current employer. We already have a suite of data analysis tools, which, while not perfect either, are an improvement over the product on offer.
Now, here's my dilemma. I've been bugged in many roles by persistent salespeople who want to get a conversation started. I don't blame them, although I find it distracting and would prefer to avoid having multiple conversations to convince them I'm not interested. In this case, I can supply a laundry list of reasons why I was dissatisfied with their offering in my former role, and I feel like it would be quicker to just explain that my prior experience was not a good one, and that I would not under any circumstance recommend their product, rather than remaining vague and giving my usual answer (something along the lines of "we already have a satisfactory platform implemented", which doesn't sit well with salespeople who want to convince me their product is superior).
Is there any reason why I should avoid being honest and explaining that I'm a dissatisfied customer? I don't think it reflects poorly on my current or previous employer, and I'm not speaking for anyone who would like to consider new products in this area as it's ultimately my decision, but I paused on the send button and want to make sure I'm not about to make a mistake.
professionalism sales
New contributor
add a comment |
I work in tech in a decision making capacity on an Analytics team, and have just moved positions in the last couple of months.
In my former role, I inherited a team using a data analysis product, well known in our field, that seemed well suited to the needs of the organization from a reporting / analysis standpoint.
However, our experience with the product was not good, support was lacking, the product itself was expensive, and new features the product released seemed like they were taking the organization in a direction that would not make it any more useful for us.
The software would periodically ask for feedback on how we were using it, and whether we'd recommend it to peers. I took every opportunity to provide a low rating and some reasoning each time I was asked, but didn't specifically speak to our representative due to being busy with other tasks. The product still worked technically for our use case and it didn't seem worth creating an issue based on our frustrations with the product. There were bigger fish to fry.
Now, in my new role, a salesperson for the same product has found me on a networking site. They know my former role and that we were customers, and have reached out to ask me to set up a meeting with my new employer.
I am in a position to recommend new software and solutions in my new role, but obviously I'm not at all interested in recommending this product to my current employer. We already have a suite of data analysis tools, which, while not perfect either, are an improvement over the product on offer.
Now, here's my dilemma. I've been bugged in many roles by persistent salespeople who want to get a conversation started. I don't blame them, although I find it distracting and would prefer to avoid having multiple conversations to convince them I'm not interested. In this case, I can supply a laundry list of reasons why I was dissatisfied with their offering in my former role, and I feel like it would be quicker to just explain that my prior experience was not a good one, and that I would not under any circumstance recommend their product, rather than remaining vague and giving my usual answer (something along the lines of "we already have a satisfactory platform implemented", which doesn't sit well with salespeople who want to convince me their product is superior).
Is there any reason why I should avoid being honest and explaining that I'm a dissatisfied customer? I don't think it reflects poorly on my current or previous employer, and I'm not speaking for anyone who would like to consider new products in this area as it's ultimately my decision, but I paused on the send button and want to make sure I'm not about to make a mistake.
professionalism sales
New contributor
I work in tech in a decision making capacity on an Analytics team, and have just moved positions in the last couple of months.
In my former role, I inherited a team using a data analysis product, well known in our field, that seemed well suited to the needs of the organization from a reporting / analysis standpoint.
However, our experience with the product was not good, support was lacking, the product itself was expensive, and new features the product released seemed like they were taking the organization in a direction that would not make it any more useful for us.
The software would periodically ask for feedback on how we were using it, and whether we'd recommend it to peers. I took every opportunity to provide a low rating and some reasoning each time I was asked, but didn't specifically speak to our representative due to being busy with other tasks. The product still worked technically for our use case and it didn't seem worth creating an issue based on our frustrations with the product. There were bigger fish to fry.
Now, in my new role, a salesperson for the same product has found me on a networking site. They know my former role and that we were customers, and have reached out to ask me to set up a meeting with my new employer.
I am in a position to recommend new software and solutions in my new role, but obviously I'm not at all interested in recommending this product to my current employer. We already have a suite of data analysis tools, which, while not perfect either, are an improvement over the product on offer.
Now, here's my dilemma. I've been bugged in many roles by persistent salespeople who want to get a conversation started. I don't blame them, although I find it distracting and would prefer to avoid having multiple conversations to convince them I'm not interested. In this case, I can supply a laundry list of reasons why I was dissatisfied with their offering in my former role, and I feel like it would be quicker to just explain that my prior experience was not a good one, and that I would not under any circumstance recommend their product, rather than remaining vague and giving my usual answer (something along the lines of "we already have a satisfactory platform implemented", which doesn't sit well with salespeople who want to convince me their product is superior).
Is there any reason why I should avoid being honest and explaining that I'm a dissatisfied customer? I don't think it reflects poorly on my current or previous employer, and I'm not speaking for anyone who would like to consider new products in this area as it's ultimately my decision, but I paused on the send button and want to make sure I'm not about to make a mistake.
professionalism sales
professionalism sales
New contributor
New contributor
New contributor
asked 4 hours ago
economyeconomy
1113
1113
New contributor
New contributor
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
Is there any reason why I should avoid being honest and explaining that I'm a dissatisfied customer?
Yes. It invites a back-and-forth discussion that takes too long.
You take a risk whenever you communicate with an outside party. Unless you are the owner of the company, it's safer to ask for permission to send feedback in the first place.
Assuming you asked for and received permission, which takes time, you now have to send a reply to the salesperson. Even if your comments are negative, the fact that you reply at all creates an opening for the salesperson. You are now a lead.
The salesperson will have an answer for every objection you have. The problems you saw were fixed in the latest version. They have fired all of those terrible customer service reps. They have hired a new team of software developers that know exactly what you need.
Salespeople are rarely interested in feedback -- they have one goal, which is to sell their product. It's their job to generate orders, even if the product has weaknesses (most do). It's not like if you tell them the product's problems they won't sell it anymore. The company has other teams devoted to user feedback. Don't try to serve as their quality control for free.
By providing feedback you are almost implicitly saying "If you fix all these problems I will buy your product." Which is probably not the case. By providing feedback you are also implicitly asking them to give you updates when the product changes.
Simply saying "no thank you" -- or not replying at all -- requires no explanation or further action, and lets you carry on doing your more important work. And it's not dishonest.
I agree with your overall assessment, not sure I specifically agree with your second point about requiring permission to communicate externally. businesses don't operate in a vacuum and it's part of my job to know the space and make decisions on what tools can help us deliver. I'd say that's implicit permission as stated in my question.
– economy
3 hours ago
@economy yes I am speaking generally. You may already have permission/authority by nature of your position.
– mcknz
1 hour ago
add a comment |
You can be completely honest without engaging with the salesperson beyond a "to the point" email. You're under no obligation to provide any explanation as to why you're not interested.
"We already have a satisfactory platform implemented. We're not
interested in looking at anything else at this time or in having any
further conversations. Thanks for reaching out to me."
Then simply delete any further email communication from this salesperson. If they call you simply let it go to voicemail and then delete the message.
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "423"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
noCode: true, onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
economy is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fworkplace.stackexchange.com%2fquestions%2f134280%2fproviding-direct-feedback-to-a-product-salesperson%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Is there any reason why I should avoid being honest and explaining that I'm a dissatisfied customer?
Yes. It invites a back-and-forth discussion that takes too long.
You take a risk whenever you communicate with an outside party. Unless you are the owner of the company, it's safer to ask for permission to send feedback in the first place.
Assuming you asked for and received permission, which takes time, you now have to send a reply to the salesperson. Even if your comments are negative, the fact that you reply at all creates an opening for the salesperson. You are now a lead.
The salesperson will have an answer for every objection you have. The problems you saw were fixed in the latest version. They have fired all of those terrible customer service reps. They have hired a new team of software developers that know exactly what you need.
Salespeople are rarely interested in feedback -- they have one goal, which is to sell their product. It's their job to generate orders, even if the product has weaknesses (most do). It's not like if you tell them the product's problems they won't sell it anymore. The company has other teams devoted to user feedback. Don't try to serve as their quality control for free.
By providing feedback you are almost implicitly saying "If you fix all these problems I will buy your product." Which is probably not the case. By providing feedback you are also implicitly asking them to give you updates when the product changes.
Simply saying "no thank you" -- or not replying at all -- requires no explanation or further action, and lets you carry on doing your more important work. And it's not dishonest.
I agree with your overall assessment, not sure I specifically agree with your second point about requiring permission to communicate externally. businesses don't operate in a vacuum and it's part of my job to know the space and make decisions on what tools can help us deliver. I'd say that's implicit permission as stated in my question.
– economy
3 hours ago
@economy yes I am speaking generally. You may already have permission/authority by nature of your position.
– mcknz
1 hour ago
add a comment |
Is there any reason why I should avoid being honest and explaining that I'm a dissatisfied customer?
Yes. It invites a back-and-forth discussion that takes too long.
You take a risk whenever you communicate with an outside party. Unless you are the owner of the company, it's safer to ask for permission to send feedback in the first place.
Assuming you asked for and received permission, which takes time, you now have to send a reply to the salesperson. Even if your comments are negative, the fact that you reply at all creates an opening for the salesperson. You are now a lead.
The salesperson will have an answer for every objection you have. The problems you saw were fixed in the latest version. They have fired all of those terrible customer service reps. They have hired a new team of software developers that know exactly what you need.
Salespeople are rarely interested in feedback -- they have one goal, which is to sell their product. It's their job to generate orders, even if the product has weaknesses (most do). It's not like if you tell them the product's problems they won't sell it anymore. The company has other teams devoted to user feedback. Don't try to serve as their quality control for free.
By providing feedback you are almost implicitly saying "If you fix all these problems I will buy your product." Which is probably not the case. By providing feedback you are also implicitly asking them to give you updates when the product changes.
Simply saying "no thank you" -- or not replying at all -- requires no explanation or further action, and lets you carry on doing your more important work. And it's not dishonest.
I agree with your overall assessment, not sure I specifically agree with your second point about requiring permission to communicate externally. businesses don't operate in a vacuum and it's part of my job to know the space and make decisions on what tools can help us deliver. I'd say that's implicit permission as stated in my question.
– economy
3 hours ago
@economy yes I am speaking generally. You may already have permission/authority by nature of your position.
– mcknz
1 hour ago
add a comment |
Is there any reason why I should avoid being honest and explaining that I'm a dissatisfied customer?
Yes. It invites a back-and-forth discussion that takes too long.
You take a risk whenever you communicate with an outside party. Unless you are the owner of the company, it's safer to ask for permission to send feedback in the first place.
Assuming you asked for and received permission, which takes time, you now have to send a reply to the salesperson. Even if your comments are negative, the fact that you reply at all creates an opening for the salesperson. You are now a lead.
The salesperson will have an answer for every objection you have. The problems you saw were fixed in the latest version. They have fired all of those terrible customer service reps. They have hired a new team of software developers that know exactly what you need.
Salespeople are rarely interested in feedback -- they have one goal, which is to sell their product. It's their job to generate orders, even if the product has weaknesses (most do). It's not like if you tell them the product's problems they won't sell it anymore. The company has other teams devoted to user feedback. Don't try to serve as their quality control for free.
By providing feedback you are almost implicitly saying "If you fix all these problems I will buy your product." Which is probably not the case. By providing feedback you are also implicitly asking them to give you updates when the product changes.
Simply saying "no thank you" -- or not replying at all -- requires no explanation or further action, and lets you carry on doing your more important work. And it's not dishonest.
Is there any reason why I should avoid being honest and explaining that I'm a dissatisfied customer?
Yes. It invites a back-and-forth discussion that takes too long.
You take a risk whenever you communicate with an outside party. Unless you are the owner of the company, it's safer to ask for permission to send feedback in the first place.
Assuming you asked for and received permission, which takes time, you now have to send a reply to the salesperson. Even if your comments are negative, the fact that you reply at all creates an opening for the salesperson. You are now a lead.
The salesperson will have an answer for every objection you have. The problems you saw were fixed in the latest version. They have fired all of those terrible customer service reps. They have hired a new team of software developers that know exactly what you need.
Salespeople are rarely interested in feedback -- they have one goal, which is to sell their product. It's their job to generate orders, even if the product has weaknesses (most do). It's not like if you tell them the product's problems they won't sell it anymore. The company has other teams devoted to user feedback. Don't try to serve as their quality control for free.
By providing feedback you are almost implicitly saying "If you fix all these problems I will buy your product." Which is probably not the case. By providing feedback you are also implicitly asking them to give you updates when the product changes.
Simply saying "no thank you" -- or not replying at all -- requires no explanation or further action, and lets you carry on doing your more important work. And it's not dishonest.
edited 3 hours ago
answered 4 hours ago
mcknzmcknz
19.9k86480
19.9k86480
I agree with your overall assessment, not sure I specifically agree with your second point about requiring permission to communicate externally. businesses don't operate in a vacuum and it's part of my job to know the space and make decisions on what tools can help us deliver. I'd say that's implicit permission as stated in my question.
– economy
3 hours ago
@economy yes I am speaking generally. You may already have permission/authority by nature of your position.
– mcknz
1 hour ago
add a comment |
I agree with your overall assessment, not sure I specifically agree with your second point about requiring permission to communicate externally. businesses don't operate in a vacuum and it's part of my job to know the space and make decisions on what tools can help us deliver. I'd say that's implicit permission as stated in my question.
– economy
3 hours ago
@economy yes I am speaking generally. You may already have permission/authority by nature of your position.
– mcknz
1 hour ago
I agree with your overall assessment, not sure I specifically agree with your second point about requiring permission to communicate externally. businesses don't operate in a vacuum and it's part of my job to know the space and make decisions on what tools can help us deliver. I'd say that's implicit permission as stated in my question.
– economy
3 hours ago
I agree with your overall assessment, not sure I specifically agree with your second point about requiring permission to communicate externally. businesses don't operate in a vacuum and it's part of my job to know the space and make decisions on what tools can help us deliver. I'd say that's implicit permission as stated in my question.
– economy
3 hours ago
@economy yes I am speaking generally. You may already have permission/authority by nature of your position.
– mcknz
1 hour ago
@economy yes I am speaking generally. You may already have permission/authority by nature of your position.
– mcknz
1 hour ago
add a comment |
You can be completely honest without engaging with the salesperson beyond a "to the point" email. You're under no obligation to provide any explanation as to why you're not interested.
"We already have a satisfactory platform implemented. We're not
interested in looking at anything else at this time or in having any
further conversations. Thanks for reaching out to me."
Then simply delete any further email communication from this salesperson. If they call you simply let it go to voicemail and then delete the message.
add a comment |
You can be completely honest without engaging with the salesperson beyond a "to the point" email. You're under no obligation to provide any explanation as to why you're not interested.
"We already have a satisfactory platform implemented. We're not
interested in looking at anything else at this time or in having any
further conversations. Thanks for reaching out to me."
Then simply delete any further email communication from this salesperson. If they call you simply let it go to voicemail and then delete the message.
add a comment |
You can be completely honest without engaging with the salesperson beyond a "to the point" email. You're under no obligation to provide any explanation as to why you're not interested.
"We already have a satisfactory platform implemented. We're not
interested in looking at anything else at this time or in having any
further conversations. Thanks for reaching out to me."
Then simply delete any further email communication from this salesperson. If they call you simply let it go to voicemail and then delete the message.
You can be completely honest without engaging with the salesperson beyond a "to the point" email. You're under no obligation to provide any explanation as to why you're not interested.
"We already have a satisfactory platform implemented. We're not
interested in looking at anything else at this time or in having any
further conversations. Thanks for reaching out to me."
Then simply delete any further email communication from this salesperson. If they call you simply let it go to voicemail and then delete the message.
edited 2 hours ago
answered 2 hours ago
joeqwertyjoeqwerty
2,485518
2,485518
add a comment |
add a comment |
economy is a new contributor. Be nice, and check out our Code of Conduct.
economy is a new contributor. Be nice, and check out our Code of Conduct.
economy is a new contributor. Be nice, and check out our Code of Conduct.
economy is a new contributor. Be nice, and check out our Code of Conduct.
Thanks for contributing an answer to The Workplace Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fworkplace.stackexchange.com%2fquestions%2f134280%2fproviding-direct-feedback-to-a-product-salesperson%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown