{"id":5900,"date":"2019-05-14T14:00:49","date_gmt":"2019-05-14T18:00:49","guid":{"rendered":"https:\/\/zux.zsm.mybluehost.me\/majoctobre2019\/?p=5900"},"modified":"2021-09-20T11:27:06","modified_gmt":"2021-09-20T15:27:06","slug":"corrections-in-conversational-ivr-part-2-article-en-anglais","status":"publish","type":"post","link":"https:\/\/www.nuecho.com\/fr\/corrections-in-conversational-ivr-part-2-article-en-anglais\/","title":{"rendered":"Correction d\u2019erreurs dans la RVI conversationnelle \u2013 2e partie (Article en anglais)"},"content":{"rendered":"<p><span style=\"font-weight: 400;\">In <\/span><a target=\"_blank\" href=\"https:\/\/www.nuecho.com\/news-events\/corrections-in-conversational-ivr-part-1\/\" rel=\"noopener\"><span style=\"font-weight: 400;\">Part 1<\/span><\/a><span style=\"font-weight: 400;\"> of this two-part post, we explored corrections and change management for conversational IVR in two main situations: during the confirmation step of an input collection dialogue, and after the final summary and confirmation of multi-step transactions.<\/span><\/p>\n<p><span style=\"font-size: 18px;\">In Part 2, we will discuss corrections occurring elsewhere in the conversation. As was the case in Part 1, we will focus on corrections made to elements of information collected in the course of a multi-step dialogue, or slots. We will not tackle intent changes, which include events like digressions, task switching, canceling a transaction halfway through or requesting to speak to an agent.<\/span><\/p>\n<p><span style=\"font-size: 18px;\">For most examples, we will, once again, refer to the bill payment use case described in Part 1.<\/span><\/p>\n<p>&nbsp;<\/p>\n<h1><span style=\"font-weight: 400;\">Immediate corrections<\/span><\/h1>\n<p><span style=\"font-weight: 400;\">This situation may occur when the caller realizes that she provided an incorrect value when answering a question and wants to fix that mistake immediately, for example:<\/span><\/p>\n<blockquote>\n<p style=\"text-align: left;\"><span style=\"font-weight: 400;\">IVR: From which account?<br \/>\n<\/span><span style=\"font-weight: 400;\">Caller: checking <\/span><b>huh savings<\/b><span style=\"font-size: 18px;\"> <\/span><\/p>\n<\/blockquote>\n<p><span style=\"font-weight: 400;\">Since there is only one slot corresponding to an entity \u201caccount type\u201d, we can safely assume that the second occurrence of the \u201caccount type\u201d entity is the correct value to fill in the \u201cfrom account\u201d slot. Considering that the entire transaction will be summarized and confirmed before submitting it, the dialogue can move on to the next step without further confirmation, or by using an implicit confirmation, like \u201cOK, from your savings account\u201d.<\/span><\/p>\n<p>&nbsp;<\/p>\n<h1><span style=\"font-weight: 400;\">Answering an earlier question<\/span><\/h1>\n<p><span style=\"font-weight: 400;\">The caller is further down in the transaction and realizes she has said the wrong payee:<\/span><\/p>\n<blockquote><p><span style=\"font-weight: 400;\">IVR: Which bill do you want to pay?<br \/>\n<\/span><span style=\"font-weight: 400;\">Caller: American Express<br \/>\n<\/span><span style=\"font-weight: 400;\">IVR: What\u2019s the payment amount?<br \/>\n<\/span><span style=\"font-weight: 400;\">Caller: <\/span><b>Oh no that\u2019s Visa<br \/>\n<\/b><span style=\"font-weight: 400;\">IVR: Alright, I will make the payment to Visa<br \/>\n<\/span><span style=\"font-weight: 400;\">IVR: What\u2019s the amount?<\/span><\/p><\/blockquote>\n<p><span style=\"font-weight: 400;\">In this case, once again, an implicit confirmation is appropriate following the correction, to reassure the caller that the request was well understood, and to allow her the opportunity to make another correction, should the request be misunderstood.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Once the correction is completed, the dialogue continues with the next logical step. Note that the dialogue model should always be flexible enough to allow the addition of transitions or the use of different versions of a collection prompt, to ensure more natural dialogues.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">As was described in Part 1, it should also be possible for the caller to only provide the item he or she wants to change without giving the new value, for example:<\/span><\/p>\n<blockquote><p><span style=\"font-weight: 400;\">IVR: Which bill do you want to pay?<br \/>\n<\/span><span style=\"font-weight: 400;\">Caller: American Express<br \/>\n<\/span><span style=\"font-weight: 400;\">IVR: What\u2019s the payment amount?<br \/>\n<\/span><span style=\"font-weight: 400;\">Caller: <\/span><b>Change the payee<br \/>\n<\/b><span style=\"font-weight: 400;\">IVR: Sure, which bill do you want to pay?<br \/>\n<\/span><span style=\"font-weight: 400;\">Caller: Visa<br \/>\n<\/span><span style=\"font-weight: 400;\">IVR: What\u2019s the payment amount?<\/span><\/p><\/blockquote>\n<p><span style=\"font-weight: 400;\">In this case, the IVR will empty the \u201cpayee\u201d slot, but it should also use some form of acknowledgement (here, a simple \u201cSure\u201d) to tell the caller that the change request was understood. If the caller provides both the item to change and the new value (e.g. \u201cthe bill I want to pay is Visa\u201d), then the dialogue should replace the slot value with the new value, implicitly confirm the change and move on to the next step.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Other corrections described in Part 1 will also apply within an ongoing task, as long as the impacted slots are already filled and that the dialogue is able to correctly interpret the caller\u2019s utterance. Whenever the interpretation is ambiguous or impossible to infer, the dialogue should fall back to repair or error handling strategies.<\/span><\/p>\n<p>&nbsp;<\/p>\n<h1><span style=\"font-weight: 400;\">Precocious corrections<\/span><\/h1>\n<p><span style=\"font-weight: 400;\">While the previous examples all refer to legitimate correction attempts, the dialogue should also anticipate situations where the caller tries to &#8211; or seems to try to &#8211; change something that was not already provided. How to react will mostly depend on how the correction is expressed.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">If the caller specifically mentions that she wants to change an item that was not yet collected, it is reasonable for the IVR to respond with a soft warning and continue:<\/span><\/p>\n<blockquote><p><span style=\"font-weight: 400;\">IVR: Which bill do you want to pay?<br \/>\n<\/span><span style=\"font-weight: 400;\">Caller: Visa<br \/>\n<\/span><span style=\"font-weight: 400;\">IVR: What\u2019s the amount?<br \/>\n<\/span><span style=\"font-weight: 400;\">Caller: <\/span><b>Change the date<br \/>\n<\/b><span style=\"font-weight: 400;\">IVR: Sorry, I haven\u2019t collected the payment date yet. Let\u2019s continue.<br \/>\n<\/span><span style=\"font-weight: 400;\">IVR: What\u2019s the payment amount?<\/span><\/p><\/blockquote>\n<p><span style=\"font-weight: 400;\">However, if the caller prematurely provides a value for the empty slot, then the IVR should record it and populate the corresponding slot:<\/span><\/p>\n<blockquote><p><span style=\"font-weight: 400;\">IVR: Which bill do you want to pay?<br \/>\n<\/span><span style=\"font-weight: 400;\">Caller: Visa<br \/>\n<\/span><span style=\"font-weight: 400;\">IVR: What\u2019s the amount?<br \/>\n<\/span><span style=\"font-weight: 400;\">Caller: <\/span><b>Change the date for May 1st<br \/>\n<\/b><span style=\"font-weight: 400;\">IVR: Alright, I will make the payment on May 1st<br \/>\n<\/span><span style=\"font-weight: 400;\">IVR: What\u2019s the payment amount?<\/span><\/p><\/blockquote>\n<p><span style=\"font-weight: 400;\">Obviously, in this case, the IVR will not collect the date, <\/span><i><span style=\"font-weight: 400;\">unless <\/span><\/i><span style=\"font-weight: 400;\">it turns out that the caller wants to record a recurring payment\u2026<\/span><\/p>\n<p><span style=\"font-weight: 400;\">A task can branch into different paths (on this topic, you can consult my colleague <\/span><a target=\"_blank\" href=\"https:\/\/www.nuecho.com\/news-events\/dialogflow-distilled-on-preemptive-slot-filling-versus-branching\/\" rel=\"noopener\"><span style=\"font-weight: 400;\">Pascal Desch\u00eanes\u2019s post<\/span><\/a><span style=\"font-weight: 400;\">), and this impacts slot assignment for a given entity. This raises an important question: is it possible to assign this entity to a slot prior to branching?<\/span> <span style=\"font-weight: 400;\">For example, if the caller provides a single date early in the bill payment task, before selecting the one-time payment recurrence value, should that date be assigned to the \u201cpay-date\u201d slot (as opposed to a \u201cstart date\u201d or an \u201cend date\u201d slot)? In other words, should we define temporary slots for preemptive slot filling purposes? In the case of the date being assigned to the \u201cpay date\u201d slot preemptively, it is probably reasonable to do so. However, this requires some logic to either render the \u201cpay date\u201d slot obsolete once a \u201crecurring\u201d value is assigned to the \u201crecurrence\u201d slot, or to proceed with a disambiguation step to determine whether the pay date is a start or an end date.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">In summary, how to handle correction attempts in the course of a multi-step transaction will depend on several factors like context, what is known of the caller, what slots have been filled or not, the timing of the correction attempt, or how many items the caller is trying to change at once. Though as designers we aim at handling most situations gracefully and adapt to callers\u2019 behaviour, it is also essential to determine when a correction attempt is just not relevant, and react accordingly.<\/span><\/p>\n<p>&nbsp;<\/p>\n<h1><span style=\"font-weight: 400;\">Finding the right dialogue model<\/span><\/h1>\n<p><span style=\"font-weight: 400;\">The correction use cases that were explored in this two-part post shed light on the need for any conversational dialogue model to be very flexible and adaptable, in order to provide the VUI designer with the right handles to create natural and efficient conversations with the user. This is true not only for IVRs, but also for voicebots, and other truly conversational interfaces.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Finding a dialogue model that provides such flexibility and adaptability is proving to be a challenge. Our team has experienced with various dialogue engines on the market, and we have also explored the possibility of developing our own engine. We met various obstacles and faced a few more serious roadblocks.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">We are currently working on adapting the Rasa Core dialogue engine for a conversational IVR solution, with VoiceXML integration. Our approach is promising but we are, unsurprisingly, facing numerous and interesting challenges. We will share our experience in a short blogpost series, coming up in June. Stay tuned!<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"<p>In Part 1 of this two-part post, we explored corrections and change management for conversational IVR in two main situations: during the confirmation step of an input collection dialogue, and after the final summary and confirmation of multi-step transactions. In Part 2, we will discuss corrections occurring elsewhere in the conversation. As was the case [&hellip;]<\/p>\n","protected":false},"author":9,"featured_media":3423,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_et_pb_use_builder":"off","_et_pb_old_content":"","_et_gb_content_width":"","om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[5,40],"tags":[],"class_list":["post-5900","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blogue","category-ivr-fr"],"aioseo_notices":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v26.9 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Correction d\u2019erreurs dans la RVI conversationnelle \u2013 2e partie (Article en anglais) &#183; AI Virtual Voice Experts with Google Dialogflow CX - CCAI - Nu Echo<\/title>\n<meta name=\"description\" content=\"Does your FAQ stand for Fail to Answer Questions?\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.nuecho.com\/fr\/corrections-in-conversational-ivr-part-2-article-en-anglais\/\" \/>\n<meta property=\"og:locale\" content=\"fr_FR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Correction d\u2019erreurs dans la RVI conversationnelle \u2013 2e partie (Article en anglais) &#183; AI Virtual Voice Experts with Google Dialogflow CX - CCAI - Nu Echo\" \/>\n<meta property=\"og:description\" content=\"Does your FAQ stand for Fail to Answer Questions?\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.nuecho.com\/fr\/corrections-in-conversational-ivr-part-2-article-en-anglais\/\" \/>\n<meta property=\"og:site_name\" content=\"AI Virtual Voice Experts with Google Dialogflow CX - CCAI - Nu Echo\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/nuechoinc\/\" \/>\n<meta property=\"article:published_time\" content=\"2019-05-14T18:00:49+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2021-09-20T15:27:06+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.nuecho.com\/wp-content\/uploads\/2019\/05\/mistake-968334_1920.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"1920\" \/>\n\t<meta property=\"og:image:height\" content=\"1280\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"Linda Thibault\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@nuecho\" \/>\n<meta name=\"twitter:site\" content=\"@nuecho\" \/>\n<meta name=\"twitter:label1\" content=\"\u00c9crit par\" \/>\n\t<meta name=\"twitter:data1\" content=\"Linda Thibault\" \/>\n\t<meta name=\"twitter:label2\" content=\"Dur\u00e9e de lecture estim\u00e9e\" \/>\n\t<meta name=\"twitter:data2\" content=\"6 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/www.nuecho.com\/fr\/corrections-in-conversational-ivr-part-2-article-en-anglais\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.nuecho.com\/fr\/corrections-in-conversational-ivr-part-2-article-en-anglais\/\"},\"author\":{\"name\":\"Linda Thibault\",\"@id\":\"https:\/\/www.nuecho.com\/fr\/#\/schema\/person\/4a8a590b9f56308799644f4e62e209cd\"},\"headline\":\"Correction d\u2019erreurs dans la RVI conversationnelle \u2013 2e partie (Article en anglais)\",\"datePublished\":\"2019-05-14T18:00:49+00:00\",\"dateModified\":\"2021-09-20T15:27:06+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.nuecho.com\/fr\/corrections-in-conversational-ivr-part-2-article-en-anglais\/\"},\"wordCount\":1203,\"publisher\":{\"@id\":\"https:\/\/www.nuecho.com\/fr\/#organization\"},\"image\":{\"@id\":\"https:\/\/www.nuecho.com\/fr\/corrections-in-conversational-ivr-part-2-article-en-anglais\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.nuecho.com\/wp-content\/uploads\/2019\/05\/mistake-968334_1920.jpg\",\"articleSection\":[\"Blogue\",\"RVI\"],\"inLanguage\":\"fr-FR\"},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.nuecho.com\/fr\/corrections-in-conversational-ivr-part-2-article-en-anglais\/\",\"url\":\"https:\/\/www.nuecho.com\/fr\/corrections-in-conversational-ivr-part-2-article-en-anglais\/\",\"name\":\"Correction d\u2019erreurs dans la RVI conversationnelle \u2013 2e partie (Article en anglais) &#183; AI Virtual Voice Experts with Google Dialogflow CX - CCAI - Nu Echo\",\"isPartOf\":{\"@id\":\"https:\/\/www.nuecho.com\/fr\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/www.nuecho.com\/fr\/corrections-in-conversational-ivr-part-2-article-en-anglais\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/www.nuecho.com\/fr\/corrections-in-conversational-ivr-part-2-article-en-anglais\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.nuecho.com\/wp-content\/uploads\/2019\/05\/mistake-968334_1920.jpg\",\"datePublished\":\"2019-05-14T18:00:49+00:00\",\"dateModified\":\"2021-09-20T15:27:06+00:00\",\"description\":\"Does your FAQ stand for Fail to Answer Questions?\",\"breadcrumb\":{\"@id\":\"https:\/\/www.nuecho.com\/fr\/corrections-in-conversational-ivr-part-2-article-en-anglais\/#breadcrumb\"},\"inLanguage\":\"fr-FR\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.nuecho.com\/fr\/corrections-in-conversational-ivr-part-2-article-en-anglais\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"fr-FR\",\"@id\":\"https:\/\/www.nuecho.com\/fr\/corrections-in-conversational-ivr-part-2-article-en-anglais\/#primaryimage\",\"url\":\"https:\/\/www.nuecho.com\/wp-content\/uploads\/2019\/05\/mistake-968334_1920.jpg\",\"contentUrl\":\"https:\/\/www.nuecho.com\/wp-content\/uploads\/2019\/05\/mistake-968334_1920.jpg\",\"width\":1920,\"height\":1280},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.nuecho.com\/fr\/corrections-in-conversational-ivr-part-2-article-en-anglais\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/www.nuecho.com\/fr\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Correction d\u2019erreurs dans la RVI conversationnelle \u2013 2e partie (Article en anglais)\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.nuecho.com\/fr\/#website\",\"url\":\"https:\/\/www.nuecho.com\/fr\/\",\"name\":\"AI Virtual Voice Experts with Google Dialogflow CX - CCAI - Nu Echo\",\"description\":\"Nu Echo\",\"publisher\":{\"@id\":\"https:\/\/www.nuecho.com\/fr\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.nuecho.com\/fr\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"fr-FR\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/www.nuecho.com\/fr\/#organization\",\"name\":\"Nu Echo - Conversation AI | IA Conversationnelle\",\"url\":\"https:\/\/www.nuecho.com\/fr\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"fr-FR\",\"@id\":\"https:\/\/www.nuecho.com\/fr\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/www.nuecho.com\/wp-content\/uploads\/2019\/03\/bottom-logo.png\",\"contentUrl\":\"https:\/\/www.nuecho.com\/wp-content\/uploads\/2019\/03\/bottom-logo.png\",\"width\":138,\"height\":27,\"caption\":\"Nu Echo - Conversation AI | IA Conversationnelle\"},\"image\":{\"@id\":\"https:\/\/www.nuecho.com\/fr\/#\/schema\/logo\/image\/\"},\"sameAs\":[\"https:\/\/www.facebook.com\/nuechoinc\/\",\"https:\/\/x.com\/nuecho\",\"https:\/\/ca.linkedin.com\/company\/nu-echo\"]},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.nuecho.com\/fr\/#\/schema\/person\/4a8a590b9f56308799644f4e62e209cd\",\"name\":\"Linda Thibault\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"fr-FR\",\"@id\":\"https:\/\/www.nuecho.com\/fr\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/www.nuecho.com\/wp-content\/uploads\/2020\/01\/NuEcho_1704-214671_Web-150x150.jpg\",\"contentUrl\":\"https:\/\/www.nuecho.com\/wp-content\/uploads\/2020\/01\/NuEcho_1704-214671_Web-150x150.jpg\",\"caption\":\"Linda Thibault\"},\"description\":\"Linda Thibault is VUI design specialist, passionate about CX, speech technologies and conversational user interfaces.\",\"sameAs\":[\"https:\/\/www.linkedin.com\/in\/linda-thibault-7b9893\/\"],\"url\":\"https:\/\/www.nuecho.com\/fr\/author\/lthibault\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Correction d\u2019erreurs dans la RVI conversationnelle \u2013 2e partie (Article en anglais) &#183; AI Virtual Voice Experts with Google Dialogflow CX - CCAI - Nu Echo","description":"Does your FAQ stand for Fail to Answer Questions?","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.nuecho.com\/fr\/corrections-in-conversational-ivr-part-2-article-en-anglais\/","og_locale":"fr_FR","og_type":"article","og_title":"Correction d\u2019erreurs dans la RVI conversationnelle \u2013 2e partie (Article en anglais) &#183; AI Virtual Voice Experts with Google Dialogflow CX - CCAI - Nu Echo","og_description":"Does your FAQ stand for Fail to Answer Questions?","og_url":"https:\/\/www.nuecho.com\/fr\/corrections-in-conversational-ivr-part-2-article-en-anglais\/","og_site_name":"AI Virtual Voice Experts with Google Dialogflow CX - CCAI - Nu Echo","article_publisher":"https:\/\/www.facebook.com\/nuechoinc\/","article_published_time":"2019-05-14T18:00:49+00:00","article_modified_time":"2021-09-20T15:27:06+00:00","og_image":[{"width":1920,"height":1280,"url":"https:\/\/www.nuecho.com\/wp-content\/uploads\/2019\/05\/mistake-968334_1920.jpg","type":"image\/jpeg"}],"author":"Linda Thibault","twitter_card":"summary_large_image","twitter_creator":"@nuecho","twitter_site":"@nuecho","twitter_misc":{"\u00c9crit par":"Linda Thibault","Dur\u00e9e de lecture estim\u00e9e":"6 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.nuecho.com\/fr\/corrections-in-conversational-ivr-part-2-article-en-anglais\/#article","isPartOf":{"@id":"https:\/\/www.nuecho.com\/fr\/corrections-in-conversational-ivr-part-2-article-en-anglais\/"},"author":{"name":"Linda Thibault","@id":"https:\/\/www.nuecho.com\/fr\/#\/schema\/person\/4a8a590b9f56308799644f4e62e209cd"},"headline":"Correction d\u2019erreurs dans la RVI conversationnelle \u2013 2e partie (Article en anglais)","datePublished":"2019-05-14T18:00:49+00:00","dateModified":"2021-09-20T15:27:06+00:00","mainEntityOfPage":{"@id":"https:\/\/www.nuecho.com\/fr\/corrections-in-conversational-ivr-part-2-article-en-anglais\/"},"wordCount":1203,"publisher":{"@id":"https:\/\/www.nuecho.com\/fr\/#organization"},"image":{"@id":"https:\/\/www.nuecho.com\/fr\/corrections-in-conversational-ivr-part-2-article-en-anglais\/#primaryimage"},"thumbnailUrl":"https:\/\/www.nuecho.com\/wp-content\/uploads\/2019\/05\/mistake-968334_1920.jpg","articleSection":["Blogue","RVI"],"inLanguage":"fr-FR"},{"@type":"WebPage","@id":"https:\/\/www.nuecho.com\/fr\/corrections-in-conversational-ivr-part-2-article-en-anglais\/","url":"https:\/\/www.nuecho.com\/fr\/corrections-in-conversational-ivr-part-2-article-en-anglais\/","name":"Correction d\u2019erreurs dans la RVI conversationnelle \u2013 2e partie (Article en anglais) &#183; AI Virtual Voice Experts with Google Dialogflow CX - CCAI - Nu Echo","isPartOf":{"@id":"https:\/\/www.nuecho.com\/fr\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.nuecho.com\/fr\/corrections-in-conversational-ivr-part-2-article-en-anglais\/#primaryimage"},"image":{"@id":"https:\/\/www.nuecho.com\/fr\/corrections-in-conversational-ivr-part-2-article-en-anglais\/#primaryimage"},"thumbnailUrl":"https:\/\/www.nuecho.com\/wp-content\/uploads\/2019\/05\/mistake-968334_1920.jpg","datePublished":"2019-05-14T18:00:49+00:00","dateModified":"2021-09-20T15:27:06+00:00","description":"Does your FAQ stand for Fail to Answer Questions?","breadcrumb":{"@id":"https:\/\/www.nuecho.com\/fr\/corrections-in-conversational-ivr-part-2-article-en-anglais\/#breadcrumb"},"inLanguage":"fr-FR","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.nuecho.com\/fr\/corrections-in-conversational-ivr-part-2-article-en-anglais\/"]}]},{"@type":"ImageObject","inLanguage":"fr-FR","@id":"https:\/\/www.nuecho.com\/fr\/corrections-in-conversational-ivr-part-2-article-en-anglais\/#primaryimage","url":"https:\/\/www.nuecho.com\/wp-content\/uploads\/2019\/05\/mistake-968334_1920.jpg","contentUrl":"https:\/\/www.nuecho.com\/wp-content\/uploads\/2019\/05\/mistake-968334_1920.jpg","width":1920,"height":1280},{"@type":"BreadcrumbList","@id":"https:\/\/www.nuecho.com\/fr\/corrections-in-conversational-ivr-part-2-article-en-anglais\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.nuecho.com\/fr\/"},{"@type":"ListItem","position":2,"name":"Correction d\u2019erreurs dans la RVI conversationnelle \u2013 2e partie (Article en anglais)"}]},{"@type":"WebSite","@id":"https:\/\/www.nuecho.com\/fr\/#website","url":"https:\/\/www.nuecho.com\/fr\/","name":"AI Virtual Voice Experts with Google Dialogflow CX - CCAI - Nu Echo","description":"Nu Echo","publisher":{"@id":"https:\/\/www.nuecho.com\/fr\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.nuecho.com\/fr\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"fr-FR"},{"@type":"Organization","@id":"https:\/\/www.nuecho.com\/fr\/#organization","name":"Nu Echo - Conversation AI | IA Conversationnelle","url":"https:\/\/www.nuecho.com\/fr\/","logo":{"@type":"ImageObject","inLanguage":"fr-FR","@id":"https:\/\/www.nuecho.com\/fr\/#\/schema\/logo\/image\/","url":"https:\/\/www.nuecho.com\/wp-content\/uploads\/2019\/03\/bottom-logo.png","contentUrl":"https:\/\/www.nuecho.com\/wp-content\/uploads\/2019\/03\/bottom-logo.png","width":138,"height":27,"caption":"Nu Echo - Conversation AI | IA Conversationnelle"},"image":{"@id":"https:\/\/www.nuecho.com\/fr\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.facebook.com\/nuechoinc\/","https:\/\/x.com\/nuecho","https:\/\/ca.linkedin.com\/company\/nu-echo"]},{"@type":"Person","@id":"https:\/\/www.nuecho.com\/fr\/#\/schema\/person\/4a8a590b9f56308799644f4e62e209cd","name":"Linda Thibault","image":{"@type":"ImageObject","inLanguage":"fr-FR","@id":"https:\/\/www.nuecho.com\/fr\/#\/schema\/person\/image\/","url":"https:\/\/www.nuecho.com\/wp-content\/uploads\/2020\/01\/NuEcho_1704-214671_Web-150x150.jpg","contentUrl":"https:\/\/www.nuecho.com\/wp-content\/uploads\/2020\/01\/NuEcho_1704-214671_Web-150x150.jpg","caption":"Linda Thibault"},"description":"Linda Thibault is VUI design specialist, passionate about CX, speech technologies and conversational user interfaces.","sameAs":["https:\/\/www.linkedin.com\/in\/linda-thibault-7b9893\/"],"url":"https:\/\/www.nuecho.com\/fr\/author\/lthibault\/"}]}},"_links":{"self":[{"href":"https:\/\/www.nuecho.com\/fr\/wp-json\/wp\/v2\/posts\/5900","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.nuecho.com\/fr\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.nuecho.com\/fr\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.nuecho.com\/fr\/wp-json\/wp\/v2\/users\/9"}],"replies":[{"embeddable":true,"href":"https:\/\/www.nuecho.com\/fr\/wp-json\/wp\/v2\/comments?post=5900"}],"version-history":[{"count":8,"href":"https:\/\/www.nuecho.com\/fr\/wp-json\/wp\/v2\/posts\/5900\/revisions"}],"predecessor-version":[{"id":8989,"href":"https:\/\/www.nuecho.com\/fr\/wp-json\/wp\/v2\/posts\/5900\/revisions\/8989"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.nuecho.com\/fr\/wp-json\/wp\/v2\/media\/3423"}],"wp:attachment":[{"href":"https:\/\/www.nuecho.com\/fr\/wp-json\/wp\/v2\/media?parent=5900"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.nuecho.com\/fr\/wp-json\/wp\/v2\/categories?post=5900"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.nuecho.com\/fr\/wp-json\/wp\/v2\/tags?post=5900"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}