<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Building an IVR with Twilio</title>
	<atom:link href="http://blogs.blackacid.org/2008/12/10/building-an-ivr-with-twilio/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.blackacid.org/2008/12/10/building-an-ivr-with-twilio/</link>
	<description>Experiments in Real Time</description>
	<lastBuildDate>Thu, 11 Dec 2008 17:08:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1-alpha</generator>
	<item>
		<title>By: Jeff Lawson</title>
		<link>http://blogs.blackacid.org/2008/12/10/building-an-ivr-with-twilio/comment-page-1/#comment-166</link>
		<dc:creator>Jeff Lawson</dc:creator>
		<pubDate>Thu, 11 Dec 2008 17:08:00 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.blackacid.org/?p=28#comment-166</guid>
		<description>Hi Adam,

Great post, I love your clean IVR design and thought process!  A couple notes and ideas that I thought I&#039;d offer:

1.  In menu.xml, you don&#039;t need separate  blocks for each option, you could just as easily use For sales, press1.  For service, press 2....  Your solution works as well, so maybe it&#039;s just personal preference :)

2.  If you have multiple exit paths, and keeping track of the failure-counter in the URLs is difficult, you can keep track of failures in a cookie instead!  Twilio is a well-behaved HTTP client, so you can use cookies to track data across many pages.  You can even use PHP sessions, etc.

Again, great post!  Keep the awesome ideas coming.

-jeff</description>
		<content:encoded><![CDATA[<p>Hi Adam,</p>
<p>Great post, I love your clean IVR design and thought process!  A couple notes and ideas that I thought I&#8217;d offer:</p>
<p>1.  In menu.xml, you don&#8217;t need separate  blocks for each option, you could just as easily use For sales, press1.  For service, press 2&#8230;.  Your solution works as well, so maybe it&#8217;s just personal preference :)</p>
<p>2.  If you have multiple exit paths, and keeping track of the failure-counter in the URLs is difficult, you can keep track of failures in a cookie instead!  Twilio is a well-behaved HTTP client, so you can use cookies to track data across many pages.  You can even use PHP sessions, etc.</p>
<p>Again, great post!  Keep the awesome ideas coming.</p>
<p>-jeff</p>
]]></content:encoded>
	</item>
</channel>
</rss>
