<?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>Robert Cooper, Author at Wildix Blog</title>
	<atom:link href="https://blog-dev.wildix.com/author/robert-cooper/feed/" rel="self" type="application/rss+xml" />
	<link>https://blog-dev.wildix.com/de/author/robert-cooper/</link>
	<description>From VoIP to Unified Communications and WebRTC</description>
	<lastBuildDate>Sun, 21 Aug 2022 21:17:23 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.0.2</generator>

<image>
	<url>https://blog-dev.wildix.com/wp-content/uploads/2019/05/cropped-W-blue-1-copy-32x32.png</url>
	<title>Robert Cooper, Author at Wildix Blog</title>
	<link>https://blog-dev.wildix.com/de/author/robert-cooper/</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>In Business Communications, Don’t Just Plan for Disaster: Plan for Continuity</title>
		<link>https://blog-dev.wildix.com/plan-for-continuity/</link>
					<comments>https://blog-dev.wildix.com/plan-for-continuity/#respond</comments>
		
		<dc:creator><![CDATA[Robert Cooper]]></dc:creator>
		<pubDate>Mon, 22 Aug 2022 07:00:39 +0000</pubDate>
				<category><![CDATA[Expert Perspectives]]></category>
		<guid isPermaLink="false">https://blog.wildix.com/?p=87296</guid>

					<description><![CDATA[<p>Whether you’re in the Scouts or in business, there’s always a reason to be prepared. Sure, running a company doesn’t mean you risk literally getting lost in the woods. But business owners still face risks that are nearly as severe, and that can and can leave their business just as lost. These can include pandemics, &#8230; </p>
<p class="link-more"><a href="https://blog-dev.wildix.com/plan-for-continuity/" class="more-link">Continue reading<span class="screen-reader-text"> "In Business Communications, Don’t Just Plan for Disaster: Plan for Continuity"</span></a></p>
<p>The post <a href="https://blog-dev.wildix.com/plan-for-continuity/">In Business Communications, Don’t Just Plan for Disaster: Plan for Continuity</a> appeared first on <a href="https://blog-dev.wildix.com">Wildix Blog</a>.</p>
]]></description>
		
					<wfw:commentRss>https://blog-dev.wildix.com/plan-for-continuity/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Earning Trust: An Essential Start to Any Sale</title>
		<link>https://blog-dev.wildix.com/earning-trust-essential-start-sale/</link>
					<comments>https://blog-dev.wildix.com/earning-trust-essential-start-sale/#respond</comments>
		
		<dc:creator><![CDATA[Robert Cooper]]></dc:creator>
		<pubDate>Thu, 12 Dec 2019 11:05:15 +0000</pubDate>
				<category><![CDATA[Expert Perspectives]]></category>
		<guid isPermaLink="false">https://blog.wildix.com/?p=37205</guid>

					<description><![CDATA[<p>Suppose, when starting the day at your office, you notice an employee hasn’t come in yet. Let’s say his name is Dave. You, the manager, got in at 8. Pretty soon, it turns to 9, then to 10 o’clock. Still no Dave to be seen. It’s only later, at 1 o’clock — more than halfway &#8230; </p>
<p class="link-more"><a href="https://blog-dev.wildix.com/earning-trust-essential-start-sale/" class="more-link">Continue reading<span class="screen-reader-text"> "Earning Trust: An Essential Start to Any Sale"</span></a></p>
<p>The post <a href="https://blog-dev.wildix.com/earning-trust-essential-start-sale/">Earning Trust: An Essential Start to Any Sale</a> appeared first on <a href="https://blog-dev.wildix.com">Wildix Blog</a>.</p>
]]></description>
		
					<wfw:commentRss>https://blog-dev.wildix.com/earning-trust-essential-start-sale/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>A Wildix Response to Communication Trends</title>
		<link>https://blog-dev.wildix.com/wildix-response/</link>
					<comments>https://blog-dev.wildix.com/wildix-response/#respond</comments>
		
		<dc:creator><![CDATA[Robert Cooper]]></dc:creator>
		<pubDate>Wed, 02 May 2018 19:00:05 +0000</pubDate>
				<category><![CDATA[Product & Feature Highlights]]></category>
		<guid isPermaLink="false">https://blog.wildix.com/?p=12108</guid>

					<description><![CDATA[<p>On April 3, 2018, there was an opinion piece posted on the Channel Partner’s blog titled “9 UC Trends Your Customers Are Talking About&#8221; written by Rhonda Trainor. The 9 trends were: Communications shift away from email.  The rise of BYOD.  Wired hardware is almost nonexistent.  Web-based communications systems. Collaboration goes beyond the conference room. Video: &#8230; </p>
<p class="link-more"><a href="https://blog-dev.wildix.com/wildix-response/" class="more-link">Continue reading<span class="screen-reader-text"> "A Wildix Response to Communication Trends"</span></a></p>
<p>The post <a href="https://blog-dev.wildix.com/wildix-response/">A Wildix Response to Communication Trends</a> appeared first on <a href="https://blog-dev.wildix.com">Wildix Blog</a>.</p>
]]></description>
		
					<wfw:commentRss>https://blog-dev.wildix.com/wildix-response/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>More Than a Phone System</title>
		<link>https://blog-dev.wildix.com/more-than-a-phone-system/</link>
					<comments>https://blog-dev.wildix.com/more-than-a-phone-system/#respond</comments>
		
		<dc:creator><![CDATA[Robert Cooper]]></dc:creator>
		<pubDate>Wed, 09 Aug 2017 09:01:01 +0000</pubDate>
				<category><![CDATA[Expert Perspectives]]></category>
		<guid isPermaLink="false">https://blog.wildix.com/?p=8102</guid>

					<description><![CDATA[<p>The Real Productivity Gains of WebRTC UC A new phone system is always a reason to celebrate – particularly if your last update was a decade ago or more – but sometimes the features that are most useful get overlooked or lost as your team adapts to your new tools. A new Wildix UC&#38;C setup &#8230; </p>
<p class="link-more"><a href="https://blog-dev.wildix.com/more-than-a-phone-system/" class="more-link">Continue reading<span class="screen-reader-text"> "More Than a Phone System"</span></a></p>
<p>The post <a href="https://blog-dev.wildix.com/more-than-a-phone-system/">More Than a Phone System</a> appeared first on <a href="https://blog-dev.wildix.com">Wildix Blog</a>.</p>
]]></description>
		
					<wfw:commentRss>https://blog-dev.wildix.com/more-than-a-phone-system/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>WebRTC Call Center Solutions</title>
		<link>https://blog-dev.wildix.com/webrtc-call-center-solutions/</link>
					<comments>https://blog-dev.wildix.com/webrtc-call-center-solutions/#respond</comments>
		
		<dc:creator><![CDATA[Robert Cooper]]></dc:creator>
		<pubDate>Tue, 18 Jul 2017 12:13:53 +0000</pubDate>
				<category><![CDATA[Expert Perspectives]]></category>
		<guid isPermaLink="false">https://blog.wildix.com/?p=7896</guid>

					<description><![CDATA[<p>At Wildix, it’s important to think about all the areas of our business where a positive impact can be made by making thoughtful and educated decisions. Considering call center solutions is one of those decisions. The technology you use for your call center should provide real time insights into when your clients are calling, what &#8230; </p>
<p class="link-more"><a href="https://blog-dev.wildix.com/webrtc-call-center-solutions/" class="more-link">Continue reading<span class="screen-reader-text"> "WebRTC Call Center Solutions"</span></a></p>
<p>The post <a href="https://blog-dev.wildix.com/webrtc-call-center-solutions/">WebRTC Call Center Solutions</a> appeared first on <a href="https://blog-dev.wildix.com">Wildix Blog</a>.</p>
]]></description>
		
					<wfw:commentRss>https://blog-dev.wildix.com/webrtc-call-center-solutions/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
