<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic How is Sinch Contact Pro different from SAP BCM?  Is it on-premise or Cloud? in Contact Pro</title>
    <link>https://community.sinch.com/t5/Contact-Pro/How-is-Sinch-Contact-Pro-different-from-SAP-BCM-Is-it-on-premise/m-p/4611#M11</link>
    <description>&lt;P&gt;Sinch Contact Pro is available via either cloud service or on-premise deployment. Most organizations today prefer to run their contact center operations in the Cloud, but some organization do still require an on-premise deployment due to e.g., governmental or industry regulations, regional infrastructure issues, preference for CAPEX versus OPEX, etc.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The new Sinch Contact Pro offering is built on the same code line as the old SAP Contact Center on-premise solution (formerly known as SAP BCM) and includes a modern HTML user interface called "Communication Panel" that runs in a standard web browser. On-premise customers can choose either the old Communication Desktop (CDT) desktop application or the new browser-based Communication Panel user interface. Cloud customers use the new browser-based Communication Panel; the old CDT desktop application is not available via the Cloud service.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Sinch Contact Pro cloud service runs in a regional AWS data center.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://community.sinch.com/t5/Sinch-Contact-Center/Sinch-Contact-Center-Solution-Brief/td-p/3992" target="_blank" rel="noopener"&gt;&lt;EM&gt;Learn more about Sinch Contact Pro&lt;/EM&gt;&lt;/A&gt;&lt;EM&gt;.&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 09 Dec 2021 15:36:33 GMT</pubDate>
    <dc:creator>John_Burton</dc:creator>
    <dc:date>2021-12-09T15:36:33Z</dc:date>
    <item>
      <title>How is Sinch Contact Pro different from SAP BCM?  Is it on-premise or Cloud?</title>
      <link>https://community.sinch.com/t5/Contact-Pro/How-is-Sinch-Contact-Pro-different-from-SAP-BCM-Is-it-on-premise/m-p/4611#M11</link>
      <description>&lt;P&gt;Sinch Contact Pro is available via either cloud service or on-premise deployment. Most organizations today prefer to run their contact center operations in the Cloud, but some organization do still require an on-premise deployment due to e.g., governmental or industry regulations, regional infrastructure issues, preference for CAPEX versus OPEX, etc.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The new Sinch Contact Pro offering is built on the same code line as the old SAP Contact Center on-premise solution (formerly known as SAP BCM) and includes a modern HTML user interface called "Communication Panel" that runs in a standard web browser. On-premise customers can choose either the old Communication Desktop (CDT) desktop application or the new browser-based Communication Panel user interface. Cloud customers use the new browser-based Communication Panel; the old CDT desktop application is not available via the Cloud service.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Sinch Contact Pro cloud service runs in a regional AWS data center.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://community.sinch.com/t5/Sinch-Contact-Center/Sinch-Contact-Center-Solution-Brief/td-p/3992" target="_blank" rel="noopener"&gt;&lt;EM&gt;Learn more about Sinch Contact Pro&lt;/EM&gt;&lt;/A&gt;&lt;EM&gt;.&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 09 Dec 2021 15:36:33 GMT</pubDate>
      <guid>https://community.sinch.com/t5/Contact-Pro/How-is-Sinch-Contact-Pro-different-from-SAP-BCM-Is-it-on-premise/m-p/4611#M11</guid>
      <dc:creator>John_Burton</dc:creator>
      <dc:date>2021-12-09T15:36:33Z</dc:date>
    </item>
  </channel>
</rss>

