We see data privacy and IT security as a very important aspect and also as an asset in our offering. We’re completely hosted in the EU, and provide you with all the necessary documents in order to be transparent about the data flows and measurements we take. Because it’s all about transparency right?

From all the processes we did (and we’re automating millions of interactions each months for companies like ERGO, SwissLife, Decathlon or – even health insurance like – Barmenia) it’s all about communicating. And until now, not one process was stopped because of GDPR issues.

Parloa offers different hosting options:

1. SaaS: your account is hosted in our Azure tenant with the other clients -> “classical SaaS”
2. Dedicated SaaS: your account is hosted in a dedicated cluster in our Azure tenant
3. Hosting at Customer’s Azure Tenant: Parloa is fully hosted in your Azure tenant

Parloa offers different hosting options:

1. SaaS: your account is hosted in our Azure tenant with the other clients -> “classical SaaS”
2. Dedicated SaaS: your account is hosted in a dedicated cluster in our Azure tenant
3. Hosting at Customer’s Azure Tenant: Parloa is fully hosted in your Azure tenant

Donec sodales sagittis magna. Sed consequat, leo eget bibendum sodales, augue velit cursus nunc, quis gravida magna mi a libero.

There are two ways how we can integrate.

1st option (and also the favorite option) is an integration via SIP. So, we’re connecting with a SIP trunk of yours and send a correlation ID in the SIP header which can be used to get context data from an API we provide.

2nd option is an integration via PSTN (“öffentliches Netz”). So, we’re providing a number which can easily be forwarded to. In order to get context data we have two options here:

1. We call different numbers when forwarding the call back to an agent and link the context data to the dedicated number (so the called number in your system is the identifier)
2. You call different numbers when forwarding the call to Parloa and we link the context data to the dedicated number (so the called number in Parloa is the identifier)

tbd.

Parloa offers different hosting options:

1. SaaS: your account is hosted in our Azure tenant with the other clients -> “classical SaaS”
2. Dedicated SaaS: your account is hosted in a dedicated cluster in our Azure tenant
3. Hosting at Customer’s Azure Tenant: Parloa is fully hosted in your Azure tenant

Donec sodales sagittis magna. Sed consequat, leo eget bibendum sodales, augue velit cursus nunc, quis gravida magna mi a libero.

There are two ways how we can integrate.

1st option (and also the favorite option) is an integration via SIP. So, we’re connecting with a SIP trunk of yours and send a correlation ID in the SIP header which can be used to get context data from an API we provide.

2nd option is an integration via PSTN (“öffentliches Netz”). So, we’re providing a number which can easily be forwarded to. In order to get context data we have two options here:

1. We call different numbers when forwarding the call back to an agent and link the context data to the dedicated number (so the called number in your system is the identifier)
2. You call different numbers when forwarding the call to Parloa and we link the context data to the dedicated number (so the called number in Parloa is the identifier)

tbd.

Parloa offers different hosting options:

1. SaaS: your account is hosted in our Azure tenant with the other clients -> “classical SaaS”
2. Dedicated SaaS: your account is hosted in a dedicated cluster in our Azure tenant
3. Hosting at Customer’s Azure Tenant: Parloa is fully hosted in your Azure tenant

Donec sodales sagittis magna. Sed consequat, leo eget bibendum sodales, augue velit cursus nunc, quis gravida magna mi a libero.