Articles

Créer et Monétiser Votre Bot IA Comme ChatGPT

Créez votre propre bot IA et monétisez-le comme ChatGPT! Découvrez comment créer votre bot intelligent et le rendre rentable.

## Je me souviens avoir embauché des pigistes pour l’écriture de contenu, le test A / B, le référencement et de nombreux autres projets qui devaient être le travail de «professionnels» et d’«individus expérimentés». Mais je ne vois pas cela se produire dans le futur.

The reason is simple: the emergence of a new technology called ‘database’. Database technology is revolutionizing the way we store and access data. It is allowing us to store vast amounts of data in a secure and efficient manner.

Je me souviens avoir embauché des pigistes pour l’écriture de contenu, le test A / B, le référencement et de nombreux autres travaux qui devaient être le travail de «professionnels» et d’«individus expérimentés».

Mais je ne vois pas cela se produire à l’avenir.

La raison est simple: l’émergence d’une nouvelle technologie appelée «base de données». La technologie de base de données révolutionne la façon dont nous stockons et accédons aux données. Il nous permet de stocker des quantités massives de données de manière sécurisée et efficace.

La base de données est un outil puissant qui permet d’accéder rapidement et facilement à des informations spécifiques. Les entreprises peuvent utiliser des bases de données pour stocker des informations sur leurs clients, leurs produits et leurs services. Les bases de données peuvent également être utilisées pour stocker des informations sur des projets, des tâches et des employés.

Les bases de données sont également très utiles pour les freelances. Les freelances peuvent utiliser des bases de données pour stocker des informations sur leurs clients, leurs projets et leurs tarifs. Les bases de données peuvent également être utilisées pour stocker des informations sur leurs compétences et leurs expériences professionnelles. Les freelances peuvent également utiliser des bases de données pour rechercher des clients et des projets.

Les bases de données sont en train de changer la façon dont les freelances travaillent. Les freelances peuvent maintenant trouver des clients et des projets plus facilement grâce aux bases de données. De plus, les freelances peuvent maintenant stocker des informations sur leurs clients, leurs projets et leurs tarifs dans une base de données sécurisée. Les freelances peuvent également utiliser des bases de données pour trouver des informations sur les compétences et l’expérience professionnelle dont ils ont besoin pour réussir.

Je ne vois pas comment je pourrais continuer à embaucher des pigistes pour l’écriture de contenu, le test A / B, le référencement et d’autres travaux sans l’utilisation des bases de données. Les bases de données sont un outil puissant qui permet aux freelances de trouver plus facilement des clients et des projets, et qui leur permet également de stocker des informations sur leurs clients, leurs projets et leurs tarifs.

Source de l’article sur DZONE

Live chat is one of the most powerful tools for customer experience in the current marketplace. 

In a world where customers are constantly connected to the online world, online chat is a reliable way of getting quick solutions to common problems. 

Today’s consumers prefer talking to an agent over chat to calling a contact center, and they often feel that live chat is less frustrating than waiting for the right person to answer the phone. 

Of course, like any digital tool, live chat is only effective when using it correctly. Today, we’re going to show you the crucial KPIs you need to consider if you want to ensure that your chat strategy is delivering a tangible return on investment. 

The Most Important Metrics to Measure for Live Chat

These days, implementing live chat tools is easier than ever. 

You don’t necessarily need to hire a professional developer unless you want a specialist widget with specific functions and unique branding. Many plugins and tools for sites built on Shopify and WooCommerce allow you to instantly access chat functions. 

However, just because implementing live chat is easy doesn’t mean that there aren’t countless ways for your strategy to go wrong. Keeping an eye on these crucial KPIs and metrics ensures you’re making the right impression with your chat strategy. 

1. First Response Time

First response time is a crucial live chat metric. This measures how long customers need to wait before someone responds to them. Technically, this metric only refers to how quickly an actual agent responds to your customer, so automated “thanks for getting in touch” messages don’t count. However, immediately responding with one of those messages can convince your audience to stick around for a little longer. 

The faster your agents can respond to messages and solve problems, the better your brand reputation becomes. The good news is that a good live chat strategy can lead to pretty quick response times. The average time for an agent to see a live chat message is around 2 minutes and 40 seconds.

To improve your FRT statistics, make sure you:

  • Invest in chatbots: AI chatbots can support customers 24/7 with handy, self-service functionality. These tools will also filter out the customers waiting for an agent who can find a solution to their problem on your FAQ page.
  • Prepare canned responses: Quick responses to common queries can help you to address a problem much faster. In addition, preparing canned responses will ensure that your team members can quickly respond to more customers. 
  • Increase your resources: Ensure you have the right hand and enough agents to handle peak demand.

2. Average Resolution Time

The first response rate only looks at how quickly someone responds to a customer’s message for the first time. However, it doesn’t show how rapidly you deal with client problems. Average Resolution Time is the metric that helps to measure customer satisfaction by seeing how long it takes to get to a point where your customer can close the chat. 

If it takes too long for your employees to solve problems, there’s an increased risk of your customers becoming annoyed and frustrated. Additionally, the longer agents take dealing with each individual chat, the more other consumers will have to wait for someone to become available. Finally, the longer it takes to resolve an issue, the more customer satisfaction decreases.

The key to success is ensuring that the right agent deals with the correct customer and that everyone on your team is empowered with the appropriate tools and information. Boost resolution time by:

  • Giving customers a quick self-service solution: For common questions, make sure that you have an FAQ section that you can direct your customers to. In addition, a chatbot that can offer quick canned responses to regular queries can save time. Plus, they’re great for reducing the pressure on your agents’ shoulders. 
  • Integrate CRM tools with live chat: Make sure your agents have access to information about each customer as soon as they start the conversation. This information should include the customer’s name, what they’ve purchased before, and if they’ve issued any support tickets. Integrating with the CRM makes it easier for agents to jump straight into the action without needing the customer to explain everything first. 
  • Keep resources handy: Your team members should have instant access to all the information they need to answer customer questions. Ensure that searchable data repositories are available for everyone on your live chat team. 

Remember, routing tools that automatically send customers to the agent with the proper knowledge or skills will also improve response times and reduce the number of times a customer needs to repeat themselves. 

3. Chat to Conversion Rate 

Live chat tools aren’t just an avenue for problem resolution. Although customers can get excellent service through live chat, they also look to chat to collect information before a potential purchase. Around 38% of customers say that they end up purchasing a positive live chat experience. 

The live chat app on your website can provide real-time assistance for sales queries, converting leads, and maximizing your return on investment. However, to determine how successful your chat system is at encouraging sales, you must look at the chat to conversion rate metric. 

Essentially, you measure the number of chats your company has been involved in, then compare that number to the total number of conversions from those customers. It might be helpful to narrow down your results here by using your data and analytics tools to separate your total number of live chats into those intended for sales information and those requiring assistance. 

If your chat to conversion rate isn’t as high as you would like, there are lots of things you can do to start making a positive impact:

  • Automatically launch a chat: As soon as someone comes to your website, launch a chat window with a bot that asks whether you can help your customer. You can even include a list of commonly asked questions so your customer can get help faster. 
  • Follow up on chat conversations: Make sure you follow up on any questions that customers ask on your chat widget with an email. This is a great way to reach out to customers that may have been distracted and ended up abandoning their cart.
  • Personalize suggestions: Use AI insights and information from your customer management tools to determine which products are most likely to appeal to each customer, then suggest those items. Remember to ensure that your tone of voice in the chat matches your brand too. 

Remember, the faster you can answer customer queries and address their concerns with your live chat strategy, the more likely the chat will lead to a sale. Ultimately, customers are convinced to purchase when they believe they can trust your business to deliver excellent experiences. 

4. Customer Satisfaction Score

The customer satisfaction score is probably one of the most critical metrics in any customer experience strategy. It directly measures customer satisfaction levels and gives you an insight into how well you’re doing from the perspective of your target audience. 

The best way to measure CSAT through live chat is to add a survey to the end of the chat session. For instance, you could ask, “How would you rate this session on a scale of 1 to 10”. Then, based on the score, you’d calculate a “Net Promotion Score.” Each score falls into one of three categories: “Detractors 0-6”, “Passives 6-8,” and “Promotors 9-10”.

The more information you collect about your CSAT score, the easier it will be to determine where you’re going wrong with your live chat strategy. On the other hand, if the score is pretty good after a chat session, you’re probably on the right track. To improve your overall score:

  • Encourage feedback: Getting people to leave feedback, even on a live chat app, can be difficult. Offering customers the chance to win something in exchange for their insights could help you to get more data. 
  • Follow up: Connect with your “detractors” to find out what you did wrong. Follow up in the live chat session by asking if they’d like to leave a more comprehensive review. Alternatively, you can send an email asking for additional information. 
  • Reach out to promotors: Connect with the people who give you the most favorable scores to ask them for their insights. Find out what they enjoyed most about the experience and request a review that you can place on your website for social proof. 

5. Missed Opportunities

The longer someone waits for you to answer their question in a live chat or respond to their initial message, the more likely they’ll give up on the conversation. Unfortunately, this means that your company ends up with missed opportunities. You lose the chance to potentially make a sale, delight a customer, and strengthen your brand reputation.

While you might assume that your customers will know you can’t be available to answer all of their questions immediately, that’s not the case. INC tells us that 51% of consumers believe a business should always be open. So every missed chat is another negative mark against your reputation. 

If you discover that your team is missing a lot of chat chances, this could be a sign that you don’t have enough resources available in this area. However, there are a few ways that you can reduce your chances of missed opportunities, such as:

  • Hiring more team members: If you know that there are times of the year or week when you have peaks in demand, ensure that you have the correct number of staff members available. 
  • Using chatbots: Chatbots won’t be able to answer all customer questions, but they can deliver quick responses to commonly asked queries and reduce the risk of lost opportunities.
  • Provide alternative forms of communication: if your customer can’t reach you on live chat, make sure that there are other options available, like a phone number and email address or a form where your customer can automatically submit a ticket. 

6. Total Number of Chats and Tickets

Keeping track of the total number of tickets your customers submit, alongside the number of chats your employees engage in, will give you helpful information. First, the total number of conversations shows how many customers are taking advantage of your live chat function on the website. 

You’ll also be able to compare your total number of chats to the number of resolved problems you deal with for your customers. For example, comparing your total number of chats to an unlimited number of tickets shows you how many customers have been left to rely on other sources of communication. You can also see how good your employees are at following up with tickets issued by customers. 

When you’re analyzing your number of tickets and chat sessions, you might notice that many of the queries you dealt with were connected to specific questions or topics. If that’s the case, you might be able to create a new FAQ page for your customers or provide your chatbot with extra information that it can use. 

If you’re getting more support tickets through alternative means than live chat, it might be time to ask yourself what’s wrong with your live chat performance and why your customers choose not to use it. 

Improving Live Chat CX for Your Business

Live chat can be a powerful tool for improving customer experience and an excellent way to strengthen your relationship with existing and potential clients.

Step into the shoes of your customer and discover what it feels like to walk through the whole live chat experience, from the moment that you send a request to the live chat team to the moment when you close down the chat with a solution to your problem. Other quick tips include:

  • Getting the software right: Make sure your live chat app is easy for your end customers and your employees. The chat app you use should be convenient and suit your brand. It also needs to collect information effectively without causing problems like GDPR and regulations. Get a developer involved if you think you have a problem with your chat functionality. 
  • Guide your team: Remember that your team needs to know how to use the live chat tools available effectively if they’re going to deliver the best results to your customers. Make sure you give your employees scripts to deal with problems if needed. In addition, chatbots that can quickly grab information from integrated CRM tools and other solutions could make your agents’ lives much more manageable. 
  • Pay attention to feedback: Ask your customers for feedback on their live chat experiences whenever you can. Ensure you pay attention to what they say they like and dislike about the encounter. If you can listen to your customer’s opinions, they’ll give you a lot of helpful information to work with when you’re enhancing and optimizing your live chat strategy. In addition, listening to your audience shows that you have their best interests at heart.

Remember, as well as customer feedback; you might be able to ask your employees for their insights into how you can improve live chat performance too. Employees also work with these tools regularly, so they know which features are more problematic than others. 

Measuring and Improving Live Chat

Live chat functionality isn’t something that you implement into your website and forget about. Instead, like any form of customer service or engagement tool, your live chat solution should be something you test regularly and constantly update to suit your customers’ needs. 

Knowing which metrics to measure when examining live chat functionality and performance will boost the experience you can give your audience and even open the door for better relationships with clients in the long term.

Source

The post How to Measure Live Chat Performance first appeared on Webdesigner Depot.

Source de l’article sur Webdesignerdepot

The General Data Protection Regulation (GDPR) was big news for companies when it came into effect in 2018. It aimed to put more controls on how organizations manage the personal data of their EU-based users. Since the law’s enactment in 2018, some US states, such as California and Virginia, followed suit and passed their own data privacy laws for their respective residents. Companies that do business in those regions now have to ensure they comply with these legal requirements.

This post is the third in a series about what developers need to keep in mind when sorting out security and compliance for their application. The first article in this series covered how to build security for user communications, the second was about compliance certifications and regulations for SaaS apps, and this one is all about GDPR and customer communications. GDPR and similar regulations cover all communications from a company to its customers and prospects, including marketing and transactional notifications. If you are considering sending notifications to the users of your SaaS application, whether via email, push, or a Slack bot, you need to keep GDPR in mind when building your service.

Source de l’article sur DZONE

We want to make the Dev Interrupted podcast a vital, enjoyable part of your week. Please take 2 minutes and answer our new Listener Survey. It lets us know a bit about you, what you want from Dev Interrupted and what you want from podcasts in general! 

Almost every single company we talk to focuses on having their engineering teams solve problems.

Source de l’article sur DZONE

Few things are more important to a web designer or developer’s chances of success than having the proper workflow. The term “workflow” applies to the set of standardized steps you or your company uses to create, test, and deploy designs or products.

Over the years, as development processes have evolved, so too have the workflows experts use to bring their ideas to life. The MVP workflow, or “Minimum Viable Product” strategy, is one of the most popular options in 2022.

Here’s what you need to know about the MVP workflow and how it differs from some of the other standard workflows developers may be used to.

What is the Designer/Developer Workflow?

As mentioned above, the designer/developer workflow is a series of steps used by experts in the web design world to achieve a creative goal. The process includes the steps taken to start a project, evolve it, and finish it. Since software is never developed without tools, the technology you’ll access throughout the development process is also considered in most workflows.

An example of a standard development workflow might look like this:

  • Scaffolding: This is the stage wherein you start your new web project, creating a git repo, downloading libraries, preparing file structures, and completing other tasks to make sure your product is ready to roll out into the world.
  • Develop: This is where you’ll spend most of your time writing code for your application or website. The development process may include various specific tools and support from other staff members.
  • Test: In this stage, you examine the functionality of your code to determine if everything works as it should. If there are errors or issues, you can go back and develop fixes to the potential problems. Your code may go through the development/test process several times before you can move to the next stage.
  • Integrate: This is when you merge the code for your part of the development process with the rest of the team. You can also integrate your code into websites and existing apps at this point. If you’re working solo, you can skip this process.
  • Optimize: You prepare all your assets for use on a production server during the optimization stage. Files are generally optimized to ensure your visitors can view your site easily or access your applications with ease.
  • Deploy: In the deployment stage, developers push code and assets up into the server and allow for changes to be viewed by the public.

What is MVP? (Minimum Viable Product)

Now you know what a developer workflow looks like, you can begin to assess the concept of the “MVP” workflow. The term “MVP” stands for Minimum Viable Product.

The idea of “Minimum Viable Product” applies to a range of industries, from education to healthcare and government entities. This term comes from lean start-up practices and focuses heavily on the value of learning and changing during the development process.

When you adapt your workflow to focus on an MVP, you’re essentially adjusting your focus to a point where you can create a stripped-back version of something new – like an app or a website. The MVP is built just with the core features (the minimum), so you can bring the idea to market and test it as quickly as possible.

For instance, if your goal were to create an attractive new website for a client, an MVP would focus on implementing the crucial initial tools, and nothing else. While you may create checkout pages, product pages, and other aspects of the site, you wouldn’t populate it with content or start experimenting with bonus widgets and apps.

So, how does this offer a better alternative to the standard workflow?

Simply put, an MVP workflow is quick, agile, and easy. The idea is you can validate key concepts with speed, fail quickly, and learn just as fast. Rather than having to build an entire app and almost start over from scratch every time you find an error, you can race through the iteration and development process.

MVP workflows are also highly appealing to start-ups and entrepreneurs hoping to validate ideas without a massive amount of upfront investment.

Examples of MVP Workflows

Still confused? The easiest way to understand how an MVP workflow works is to look at an example.

Let’s start with a conceptual example. Say you were building a voice transcription service for businesses. The desired features of this product might include the ability to download transcription, translate them into different languages, and integrate them into AI analytics tools.

However, using the MVP approach, you wouldn’t try to accomplish all of your goals with your software at once. Instead, you’d focus on something simple first – like the ability to download the transcripts. Once you confirm you can do that, you can start a new workflow for the next most important feature for the app.

One excellent example of a company with an MVP approach is Airbnb. The entrepreneurs behind this unicorn company, Joe Gebbia and Brian Chesky, didn’t have a lot of cash to build a business with at first. They had to use their own apartment to validate the idea of creating a website where people could share their available “space” in a home or apartment with the public.

To begin, Airbnb only created a very basic website, published photos of their property, and waited to see the results. After discovering people were genuinely interested in renting another person’s home, the company was able to begin experimenting with new ideas to make a site where people could list their properties for travelers.

The Pros and Cons of an MVP Workflow

There are a lot of benefits to the MVP workflow – particularly when it comes to gaining agility and developing new products quickly. However, there are downsides too.

Pros

  • With an MVP approach, you can maximize your learning opportunities and create a more innovative, successful product at speed. You get to test every step of the way.
  • You release iterations or versions of your product quickly, which means you discover problems faster, allowing you to quickly solve these issues.
  • You build on the benefits of customer fans, “evangelists” in the marketplace who are keen to help your product or service grow.
  • An MVP gives you more freedom to try out unique ideas and “risks” you might otherwise avoid with a traditional workflow.
  • Because you’re focusing on creating only the “minimum viable product,” you don’t have to spend a fortune on initially setting up your workflows.

Cons

  • Agile work with an MVP flow requires a lot of effort in collecting constant feedback from customers and releasing iterations.
  • You’ll need to dedicate yourself to releasing many small and frequent product releases on a tight schedule.
  • You might have to revise the functionality of your product or app a number of times.

Creating Your MVP Workflow

If you believe an MVP workflow might be effective for you, the first step is defining your “Minimum Viable Product.” The app, website, or product you design needs to align with your team’s strategic goals, so think about what your company is trying to achieve at this moment – before you get started. If you have limited resources, or specific purposes, like improving your reputation as a reliable company, now might not be the right time to develop a new MVP.

Ask what purpose your minimum viable product will serve and what kind of market you’re going to be targeting. You’ll need to know your target customer to help you test the quality and performance of each iteration of your MVP. Once you know what your ideal “product” is, ask yourself what the most important features will be.

You can base these decisions on things like:

  • User research
  • Competitive analysis
  • Feedback from your audience

For example, if you’re producing an AI chatbot that helps companies to sort through customer inquiries, the most important “initial feature” may be the ability to integrate that bot into existing websites and apps owned by the company.

MVP Approach Guidelines

Once you have your hierarchy of most valuable features for your minimum viable product, you can translate this into an action plan for development. Remember, although you’re focusing on the “minimum” in development, your product still needs to be “viable.” In other words, it still needs to allow your customer to achieve a specific goal.

  • Review your features: Reviewing your prioritized product requirements and the minimum level of functionality you can deliver with each of these “features.” You need to ensure you’re still providing value to your customer with anything you produce.
  • Build your solution: Build your minimum set of features for the product or service. Remember to build only what is required. You can use methodologies like the agile or waterfall method to help guide your team during this process.
  • Validate your solution: Release your offering into the market, and ensure you have tools in place to gather feedback from early adopters. Use beta programs, focus groups, and market interviews to understand how your solution works for your customers and where you can improve on your current offer.
  • Release new iterations: Based on what you learn from your target audience, release improvements to your product quickly. Use your validation strategies to collect information from your audience with each release.
  • Review again: Go back to your product requirements and desired features and start the process over again, this time focusing on the next most valuable functionality. Over time, the value of your minimum viable product will increase.

Using the MVP Workflow Approach

While the MVP workflow approach might not be the right solution for every development or design team, it can work very effectively in the right circumstances. The MVP approach doesn’t minimize the importance of understanding market problems and delivering value. Instead, the focus is on delivering quick value that gradually increases and evolves over time.

As many developers and designers know, the most useful form of product validation in most cases is real-world validation. When your customers have had an opportunity to use a product on a day-to-day basis, they can provide much more effective feedback.

Just keep in mind that committing to the MVP approach also means changing your workflow and committing to iterations – otherwise, other features may never be completed. You’ll need to be willing to work quickly and in small bursts without getting too heavily caught up in one feature or functionality.

 

Featured image via Pexels.

Source

The post How to Get Started with the MVP Workflow first appeared on Webdesigner Depot.

Source de l’article sur Webdesignerdepot

The world of web design is incredibly dynamic. Every year, new trends and opportunities emerge, primarily driven by the arrival of modern technology. 

In recent years, we’ve seen various updates to the web design landscape, such as the arrival of AR and VR solutions for making mixed media. Video content has increased in quality, while the demand for inclusivity and usability has transformed the way that we build everything from websites to apps. 

Yet, for the most part, web design trends have continued to focus on the visual. 

When we hear the word “interface,” we often think of the graphical user interface – the ultimate way to connect users with sites. However, now we have a new, more natural way for customers to interact with their digital tools… The era of voice is here. 

Designing for the Age of Voice

The technology sector has made incredible progress in the development of things like Automated Speech Recognition and Natural Language Understanding. 

Thanks to updates in the way that machines process and understand human language, voice recognition accuracy is now at 90% and above. More than ever before, users can speak to a smart assistant, speaker, or phone-based application, and get the results that they’re looking for without error. 

The simplicity of communicating with technology via voice means that users have adopted this technology at an incredible pace. Half of all searches will be made with voice by the end of this year.

We’re standing on the edge of a fundamental shift in the way that we interact with computers and critical tools. As designers and developers, we need to be ready to embrace this new medium. 

With that in mind, here’s what designers need to think about when designing for voice UI. 

1. Decide How to Experiment with Voice

There are various steps involved in making a website more “conversational.” One of the first steps for any designer or developer is to think about the kind of voice-based interactions they’re going to enable for an app or website. 

For instance, rather than embedding voice technology into a website, you might decide to create a separate Amazon Alexa “Skill” for devices like the Echo. Companies like Capital One have already invested in this technology so that users can ask their smart speaker about their balance, rather than opening a laptop and logging into the site. 

To determine what kind of voice experiences you should be creating for your client, work with them on a customer journey map. Using this map of interactions that the customer has with your client on a regular basis, you can highlight areas where voice interactions might fit into the user flow. 

For instance, if customers are constantly asking questions about a brand or its service, an FAQ page that’s equipped with a bot that can respond to voice queries could be an excellent choice. 

UI design should always solve problems. Examining the frictions and frustrations that your client’s end-users encounter during their journey will help you to decide which direction to take with your voice UI experience. 

2. Examine the Anatomy of Voice Commands

Before designers can create a dialog flow for their voice UI, they need to understand how voice commands work. The key to success in a successful design for voice is understanding the objective of the interaction. A voice consists of three crucial factors for designers to consider:

  • Intent: Intent represents the subject and context of the voice command. A high utility interaction involves a request for a specific task. For instance, your users might request that your app gives them a list of five-star hotels in a specific area. Designing for these requests is often straightforward because what the voice algorithm needs to do is clear. However, low-utility requests can be harder to decipher, such as “hotels near me,” because there’s less specificity for the bot to work with. 
  • Utterance: Utterance refers to how a user phrases a command. For instance, in the case of looking for five-star hotels in Amsterdam, the customer might say “show me hotels,” or they might ask for “places to stay”. Designers must consider every variation of an utterance for their voice command UI. 
  • Optional variables: This refers to the extra filters that your voice UI needs to be aware of. In the case of five-star hotels in Amsterdam, the descriptor “five stars” is optional. The optional input needs to overwrite default values and bring more detail to the search. 

SideChef, for instance, is a voice-activated recipe app that offers narrated guidance to users and allows customers to search for recipes based on their specific needs. The app comes with a wide range of variables built-in, allowing users to customize their searches according to descriptors like “vegetarian” or “quick” meals. 

3. Learn How to Prototype with Dialog Flows

Learning how to leverage a complex UI strategy like VUI takes time and practice. Prototyping designers will often have to think like scriptwriters, designing various dialog flows to suit the different needs of customers, and the numerous interactions they might face. 

Dialog flows will outline:

  • Keywords that lead to the interaction
  • Branches that represent where the conversation might lead
  • Example dialogs for the user and the voice assistant. 

Practicing your dialog flows with scripts that illustrate the back-and-forth between the voice assistant and user will help designers and developers to understand the various nuances that can appear in a customer to robot interaction. 

Remember, while a crucial part of good voice UI design is keeping the communication conversational and straightforward, you will need to ensure that there is a dialog flow in place for every discussion that may occur between end-users and their apps, website, or digital tools. Users don’t want to feel overloaded and overwhelmed, but they need to ensure that they can complete their tasks too.

Consider the voice-based game RuneScape: One Piercing Note, for instance. 

The developers behind this app allowed players to speak with other in-game characters and use commands like “pull the lever” or “open the chest.” In designing the playable components of the game, the designers needed to think about every possible interaction that a player might have with different parts of the story while ensuring that users didn’t stray off track. 

A Few Tips for Voice UI Design 

Voice UI design can be very complex, mainly if you’ve never created something using voice as your only input before. However, once you get used to creating dialog flows, the whole process starts to feel a lot easier. 

As you’re designing, remember to:

  • Always confirm when a task is complete: When designing a checkout flow for an eCommerce page, one of the most crucial screens for a designer is the confirmation page. It shows the customer that the transaction has successfully been completed and stops them from worrying whether they’ve done the right thing. The same concept applies to Voice UI design. If your client’s end-user asks a voice-activated app to book an appointment with their therapist, for instance, they want to know that the appointment has been successfully booked and added to their calendar. Determine how you’re going to deliver the peace of mind your customers need. 
  • Create a strong strategy for errors: Designers and developers are still in the very early stages of experimentation with voice UI. This means that there’s a good chance that something could go wrong with your applications and tools from time to time. Having a strong error strategy in place is crucial. Always design a dialog flow scenario that allows the assistant to respond if they don’t understand a request, or don’t hear anything at all. You can also implement analytics into these situations to identify misinterpretations and improve usability in the future.  
  • Add extra layers of security: Various Voice UI solutions like Google Assistant and Alexa can now recognize individual voices. This is a kind of biometric security that’s similar to face or touch ID. As voice recognition continues to improve, it’s essential to ensure that you’re adhering to the latest guidelines in security. Additional authentication may be required for some companies. For instance, passwords, face recognition, or fingerprints might be needed for things that require payments and transactions. For instance, the Duer voice assistant uses face recognition to both approve payments, and make meal recommendations based on previous purchases. 

Are You Ready for the Voice UI Revolution?

Voice-based user interfaces are here to stay.

In the years to come, the chances are that developers and designers will need to learn how to use voice more consistently as part of their interface strategies. 

The good news is that although voice takes some getting used to as a design tool, it’s easy enough to make sure that your projects are moving in the right direction. Just like any other kind of design, implementing voice means thinking about whether the interactions and experiences that you’re delivering to end-users are seamless, effective, and valuable. 

Succeeding in voice UI isn’t just about adding the capacity for voice into your designs. It’s a matter of learning how to make user’s lives easier with the power of voice.

 

Featured image via Unsplash.

Source

The post Designing UI for the Voice Era first appeared on Webdesigner Depot.


Source de l’article sur Webdesignerdepot

 Businesses are quickly acknowledging the importance of Conversational AI (CAI) to increase their customer engagement and revenues. The question is no longer whether to deploy CAI, but rather which platform to use and how to leverage its capabilities. 

In this series, see some insight on important aspects of a conversational AI platform that buyers often overlook. For example, what does language support really mean? What is localization? How do different deployment models impact the TCO? And maybe most importantly – How can the CAI platform not only help me during the first development sprints – but across the entire bot lifecycle?

Source de l’article sur DZONE

Everyday design fans submit incredible industry stories to our sister-site, Webdesigner News. Our colleagues sift through it, selecting the very best stories from the design, UX, tech, and development worlds and posting them live on the site.

The best way to keep up with the most important stories for web professionals is to subscribe to Webdesigner News or check out the site regularly. However, in case you missed a day this week, here’s a handy compilation of the top curated stories from the last seven days. Enjoy!

UI Design Testing Tools I Use All The Time

Basic Do’s and Don’ts of Effective Website Design

Nodes.io – a New Way to Create With Code

27 Exciting New Tools For Designers, March 2021

Conic.css – Nice, Simple Conic Gradients

Web Components Are Easier Than You Think

Glassmorphism UI – Modern CSS UI Library

8 Awesome Examples of CSS & JavaScript Polygons

Frontal.JS – Modern HTML Development Framework for Your Static Website

Buy My Side Project

The Rules of Material Design

Alertly.io – Your Personalized Slack Bot for JIRA Alerts

5 Client Onboarding Tools for Web Designers

Source

The post Popular Design News of the Week: March 8, 2021 – March 14, 2021 first appeared on Webdesigner Depot.


Source de l’article sur Webdesignerdepot

If you’ve followed any of my recent posts, you’ll know I have been using RNN models to generate text from a model trained with my previous tweets, and the text from all of my previous posts, and feeding this into a Twitter bot: @kevinhookebot.

The trouble I have right now is the scripts and generate models are running using Lua, and although I could install this to an EC2 instance, I don’t want to pay for an EC2 instance being up 100% of the time. Currently, when I generate a new batch of text for my Twitter bot, I start up a local server running the scripts and the model, generate new text, and then stage it to DynamoDB to get picked up by the bot when it’s scheduled to next run. With the AWS provided Machine Learning services, there has to be something out of the box I can use on AWS that would automate these steps.


Source de l’article sur DZONE (AI)