<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Pascal Deschênes - AI Virtual Voice Experts with Google Dialogflow CX - CCAI - Nu Echo</title>
	<atom:link href="https://www.nuecho.com/author/pdeschenes/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.nuecho.com/author/pdeschenes/</link>
	<description>Nu Echo</description>
	<lastBuildDate>Mon, 20 Sep 2021 15:25:22 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>

<image>
	<url>https://www.nuecho.com/wp-content/uploads/2019/11/cropped-favicon-32x32.png</url>
	<title>Pascal Deschênes - AI Virtual Voice Experts with Google Dialogflow CX - CCAI - Nu Echo</title>
	<link>https://www.nuecho.com/author/pdeschenes/</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Dialogflow Distilled: On Preemptive Slot-filling versus Branching</title>
		<link>https://www.nuecho.com/dialogflow-distilled-on-preemptive-slot-filling-versus-branching/#utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=dialogflow-distilled-on-preemptive-slot-filling-versus-branching</link>
		
		<dc:creator><![CDATA[Pascal Deschênes]]></dc:creator>
		<pubDate>Thu, 02 May 2019 18:11:16 +0000</pubDate>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[Dialogflow]]></category>
		<category><![CDATA[IVA]]></category>
		<guid isPermaLink="false">https://zux.zsm.mybluehost.me/?p=3005</guid>

					<description><![CDATA[<p>As we gain experience with Google Dialogflow, we like to take a step back and identify usage patterns to feed in our development practices. This blog post aims at depicting and distilling one of such patterns: preemptive slot-filling versus branching. Let’s say that one of your chatbot requirements is to perform a banking payment to [&#8230;]</p>
<p>The post <a href="https://www.nuecho.com/dialogflow-distilled-on-preemptive-slot-filling-versus-branching/">Dialogflow Distilled: On Preemptive Slot-filling versus Branching</a> first appeared on <a href="https://www.nuecho.com">AI Virtual Voice Experts with Google Dialogflow CX - CCAI - Nu Echo</a>.</p>
<p>The post <a href="https://www.nuecho.com/dialogflow-distilled-on-preemptive-slot-filling-versus-branching/">Dialogflow Distilled: On Preemptive Slot-filling versus Branching</a> appeared first on <a href="https://www.nuecho.com">AI Virtual Voice Experts with Google Dialogflow CX - CCAI - Nu Echo</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>As we gain experience with Google Dialogflow, we like to take a step back and identify usage patterns to feed in our development practices. This blog post aims at depicting and distilling one of such patterns: preemptive slot-filling versus branching.</p>
<p>Let’s say that one of your chatbot requirements is to perform a banking payment to a specific merchant. This is a fairly standard transaction involving a single intent capturing a few slots such as amount, account, merchant and a date.</p>
<p>&gt; <a href="https://medium.com/cxinnovations/dialogflow-distilled-on-preemptive-slot-filling-versus-branching-9b662eeed027" target="_blank" rel="noopener noreferrer">Read full version on Medium</a></p><p>The post <a href="https://www.nuecho.com/dialogflow-distilled-on-preemptive-slot-filling-versus-branching/">Dialogflow Distilled: On Preemptive Slot-filling versus Branching</a> first appeared on <a href="https://www.nuecho.com">AI Virtual Voice Experts with Google Dialogflow CX - CCAI - Nu Echo</a>.</p><p>The post <a href="https://www.nuecho.com/dialogflow-distilled-on-preemptive-slot-filling-versus-branching/">Dialogflow Distilled: On Preemptive Slot-filling versus Branching</a> appeared first on <a href="https://www.nuecho.com">AI Virtual Voice Experts with Google Dialogflow CX - CCAI - Nu Echo</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Dialogflow and Beyond</title>
		<link>https://www.nuecho.com/google-dialogflow-and-beyond/#utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=google-dialogflow-and-beyond</link>
		
		<dc:creator><![CDATA[Pascal Deschênes]]></dc:creator>
		<pubDate>Mon, 21 Jan 2019 18:48:27 +0000</pubDate>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[Dialogflow]]></category>
		<guid isPermaLink="false">https://zux.zsm.mybluehost.me/?p=3256</guid>

					<description><![CDATA[<p>Nu Echo has been using Google Dialogflow for some time now and would like to take a moment to share our thoughts about using the platform for chatbot and intelligent virtual agent projects within enterprise organizations. In this blog post, we will describe what Dialogflow is good for, its current limitations, and how we work [&#8230;]</p>
<p>The post <a href="https://www.nuecho.com/google-dialogflow-and-beyond/">Dialogflow and Beyond</a> first appeared on <a href="https://www.nuecho.com">AI Virtual Voice Experts with Google Dialogflow CX - CCAI - Nu Echo</a>.</p>
<p>The post <a href="https://www.nuecho.com/google-dialogflow-and-beyond/">Dialogflow and Beyond</a> appeared first on <a href="https://www.nuecho.com">AI Virtual Voice Experts with Google Dialogflow CX - CCAI - Nu Echo</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p class="graf graf--p graf--hasDropCapModel graf--hasDropCap"><span class="graf-dropCap">Nu</span> Echo has been using <a class="markup--anchor markup--p-anchor external" href="https://dialogflow.com/" target="_blank" rel="noopener noreferrer" data-href="https://dialogflow.com/">Google Dialogflow</a> for some time now and would like to take a moment to share our thoughts about using the platform for chatbot and intelligent virtual agent projects within enterprise organizations. In this blog post, we will describe what Dialogflow is good for, its current limitations, and how we work around those limitations to get the most out of our development. We will also explore our plans for the future as part of our IVA Solutions practice. This article will solely focus on an engineering perspective to kick off this series but please watch for future posts which will touch on dialogue management and conversational aspects to be considered for great IVA development and more!</p>
<h3 class="graf graf--h3">What makes it great!</h3>
<p class="graf graf--p graf--hasDropCapModel graf--hasDropCap"><span class="graf-dropCap">B</span>rowsing around Dialogflow’s website, you can easily find the benefits. Some are accurate, others are less evident as true benefits or are lacking as of yet. Let’s start by considering what some of the true benefits are that we have been able to experience and take advantage of:</p>
<p class="graf graf--p"><strong class="markup--strong markup--p-strong">Quick and easy to start building</strong>: Yes! You can truly create your first bot within a matter of minutes. I think my mother did one in, like, 16 minutes, while cooking her famous apple jelly. You login to the console, create an agent project, create one or two intents, and then try it out within the console. Instant reward. A few more clicks to activate the Phone Gateway integration and then you can, yes, call in (assuming your bot is en-US for now). Small dopamine rush.</p>
<p class="graf graf--p"><strong class="markup--strong markup--p-strong">Built on Google infrastructure</strong>: From within a project, you can tap into the rich Google Cloud ecosystem. Conversation logs get pushed over <a class="markup--anchor markup--p-anchor external" href="https://cloud.google.com/stackdriver/" target="_blank" rel="noopener noreferrer" data-href="https://cloud.google.com/stackdriver/">Stackdriver</a>, fulfillment is only a few <a class="markup--anchor markup--p-anchor external" href="https://cloud.google.com/functions/" target="_blank" rel="noopener noreferrer" data-href="https://cloud.google.com/functions/">Google Cloud Functions</a> or <a class="markup--anchor markup--p-anchor external" href="https://firebase.google.com/docs/functions/" target="_blank" rel="noopener noreferrer" data-href="https://firebase.google.com/docs/functions/">Firebase Functions</a> away, security and containment are directly handled as part of <a class="markup--anchor markup--p-anchor external" href="https://cloud.google.com/iam/" target="_blank" rel="noopener noreferrer" data-href="https://cloud.google.com/iam/">IAM</a>, while <a class="markup--anchor markup--p-anchor external" href="https://cloud.google.com/speech-to-text/" target="_blank" rel="noopener noreferrer" data-href="https://cloud.google.com/speech-to-text/">speech-to-text</a> and <a class="markup--anchor markup--p-anchor external" href="https://cloud.google.com/text-to-speech/" target="_blank" rel="noopener noreferrer" data-href="https://cloud.google.com/text-to-speech/">text-to-speech</a> relies on Google Cloud respective APIs. And frankly, although we are using some beta features, the platform is quite stable.</p>
<p class="graf graf--p"><strong class="markup--strong markup--p-strong">Easy to scale</strong>: Seriously! This is an additional benefit to the point above. No need to worry about any sort of viral effect your bot might experience. There’s not even a dial or knob to tweak or turn on. It’s essentially all done behind the scenes. Coupled with Google Cloud Functions for serverless fulfillment stage and you’re golden.</p>
<p class="graf graf--p"><strong class="markup--strong markup--p-strong">Strong natural language understanding (NLU) capabilities</strong>: So far so good on this front. We definitely have yet to push the limits but its context-based approach appears to be robust. More on that to come in future posts.</p>
<h3 class="graf graf--h3">Where it might fall a little short…</h3>
<p>&gt; <a class="external" href="https://medium.com/cxinnovations/dialogflow-and-beyond-67991b3dc87f" target="_blank" rel="noopener noreferrer">CLICK HERE</a> to read the full blog post</p><p>The post <a href="https://www.nuecho.com/google-dialogflow-and-beyond/">Dialogflow and Beyond</a> first appeared on <a href="https://www.nuecho.com">AI Virtual Voice Experts with Google Dialogflow CX - CCAI - Nu Echo</a>.</p><p>The post <a href="https://www.nuecho.com/google-dialogflow-and-beyond/">Dialogflow and Beyond</a> appeared first on <a href="https://www.nuecho.com">AI Virtual Voice Experts with Google Dialogflow CX - CCAI - Nu Echo</a>.</p>
]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
