How To Talk With The Representative Of Uscis Customer Service

Creating valuable products requires getting valuable feedback. Who y'all talk to early on counts for a whole lot.

Shutterstock

A few weeks ago my co-founder and I started privately beta testing our company's second product.

Our starting time product, Exist, has been in public beta for almost a year. We made lots of mistakes which, thankfully, nosotros've learned from.

This time around, we know what to practise differently—and so we tin brand fresh mistakes this time, no doubt. Here are a few lessons I'd honey to share.

Choose your users carefully

Our biggest mistake with beta testing was choosing the wrong users. We tried to protect our fragile egos and only invited people nosotros knew. Our promise was to get honest (simply polite) feedback to aid united states improve the product without beingness thrown into a pit of despair earlier we even launched.

Related: six Tips on Getting Customer Feedback and Making It Actionable

The reality hitting fifty-fifty harder: we heard crickets.

We couldn't go the feedback we needed because we weren't talking to users who cared. Our "users" were people who had five minutes to spare and no real inclination to tell the states what they wanted to exercise with our production.

Why? Because they weren't people who needed our product.Nosotros weren't solving any pains for them. They didn't run into the value and didn't hang around long. Most of them vanished subsequently one login or came back one time a month if nosotros were lucky.

Don't waste time (on both sides) with users you aren't serving. You'll never get the feedback you need from people who don't need you lot.

Doing this right: cull users from your target marketplace

For a new product you lot must wait for users who feel the hurting, run into a need, and are willing to invest to become value.

As you build upward your business over fourth dimension this becomes a lot easier. With our 2d product we're focusing on the same type of customer every bit we did with Exist, so we've already got a targeted group of people from which to pull beta testers. When yous build a relationship with people who employ your products, they're oft more probable to be interested in other projects you lot work on.

Y'all tin see this in other businesses, too. When Basecamp was still known as 37 Signals, it had several products targeting the same user base. Information technology's much easier to observe beta testers, and somewhen paying users, from a pool of people who already know and trust you.

If you're starting out with your first product, you obviously won't have the benefit of an existing user base, simply you can build an audience in other ways. More than six months earlier we launched Exist to the public, I started a regular content serial on our weblog that focused on news and new products in the Quantified Self space. Equally I connected this series every week, nosotros congenital up an archive of content relevant to our target market place and developed an audience of people who were interested in those topics.

We created an electronic mail waiting list for Exist to keep our potential customers updated with our progress, and through regular email updates and creating content they were interested in, we were able to build a relationship with lots of our customers earlier they e'er used our product.

Related: 4 Steps to Alluring and Building Ameliorate Customers

In later rounds of beta testing, nosotros surveyed our waiting listing to find people who were interested in our product and understood its value. In retrospect, we should accept taken this approach much earlier.

Request for feedback

The quicker y'all can become feedback the better. Good ideas go to speak and the duds are silenced.

Misunderstanding your users is dangerous. Yous won't know which management is best for your product, and you lot won't know why customers go out (or why they stay). Feedback is the fix.

It's like shooting fish in a barrel to experience like you're bugging people, specially early on. But like anything in life, you won't know until y'all enquire, and often people are much more willing to aid than y'all call up.

Expecting customers to transport you unsolicited feedback is expecting as well much. Y'all're responsible for starting the conversation.

Doing this right: inquire oftentimes, and in unlike ways

Talking to my customers in existent-time (either in person or via Skype) is one of the best ways I've establish to uncover useful feedback. When you're talking to a user one-on-one this way, you can dig deeper into the niggling things they say and allow them go off on tangents. It's the all-time way to get a well-rounded picture of who this user is and how your production fits into their life.

Only sometimes that's not the kind of feedback you need. When we wanted to know which parts of our product were most popular, we sent out a survey to all our users via e-mail. It wasn't as personal as a one-on-ane call, but we were able to gather data from lots of our users in a brusk period of fourth dimension, and we could ask exactly what we wanted to know.

Sometimes you just want a articulate, overall rating of your production or service. In those cases yous can use a simple question like, "Would you recommend our product to a friend?" or you can enquire your customers to rate your customer service after you've solved their trouble.

The way you inquire for feedback should depend on what blazon of feedback y'all're looking for.

Stick to one major feedback arroyo at a time in the early days. Dilution of responses and user annoyance can occur if it feels similar you are bombarding people. The aforementioned month you're making a concerted endeavour to practice development interviews, don't send out a survey bugging people for like data. Ongoing, focused feedback creates the nearly meaningful insight.

Related: 4 Reasons Y'all're Lucky That Aroused Customer Is Yelling at You lot

Listening to the vocal minority

Ah, the vocal minority. When you're struggling to get feedback, any little bit seems like solid aureate.

This makes it all likewise piece of cake to fall into the vocal minority trap. You hear a handful of users ask for a feature that you've already considered edifice and suddenly you recall every user must want it. Clearly, they just haven't got effectually to telling united states of america! Let's transport it already!

Worse yet, you hadn't considered building a characteristic but six or seven users ask for it on the same twenty-four hours. The next matter you know you're rolling something out without nearly enough context. It's easy to leap the gun from a sense of urgency and demand that isn't really there. Sounds giddy, merely we're all susceptible.

To make things people desire, commencement prove they actually want it.

Doing this right: ostend the hypothesis

Feedback is best used to create a hypothesis for what the bulk of your usersmight want. As Des Traynor says, "Treat every clustering of feedback that you lot see as a hypothesis, and then don't build information technology, verify it."

Yous tin can then exercise further customer development to see if your hypothesis holds upwards.

If it holds up that the majority of users do experience the same way, that's when you can start digging in deeper to find out why they want this item feature and howyou tin solve that trouble for them (it's nearly the friction, not the feature).

For Exist feedback, we utilize Help Scout and tags to keep an ever-updated count of requests for a detail characteristic. It's quick and easy to add a tag when we're replying to a customer, and seeing the number of requests per tag makes information technology easier to choose what to piece of work on next without being overwhelmed past the vocal minority.

Feedback is a multi-faceted role of building a visitor. Whether you're getting too much, you accept confusing or inconsistent feedback, or you're but hearing crickets, you're non alone.

Choose customers carefully, ask for feedback frequently, and ever exam a hypothesis before implementing what you hear from customers.

Information technology's easier said than done, simply every comeback I make in handling client feedback has made me better at edifice the best product for my users.

Related: Bringing a 'Customer-Axial' Focus to Life at Your Visitor

Source: https://www.entrepreneur.com/article/249300

Posted by: estradaalif1955.blogspot.com

Share this post