Features to boost outbound activities
Fueling your outbound sales
VCC live for inbound contact centers
Transforming customer service for tbi bank
Key channels VCC Live supports
Email, social and more for SYKES and Huawei
Selected integrations for VCC Live users
Handle calls without leaving Salesforce
Powerful BI for next-level sales
92% of calls within SLA
94% voicemail detection rate
Explore more
Check out our history
Last revised: May 26, 2021
We use cookies to enhance your experience with us. This cookie policy provides information about how VCC Live uses cookies and other similar tracking technologies on its website.
Cookies are small text files that are stored by your browser on your computer or mobile device to save certain information or image files, such as pixels. Through the information saved and returned, the respective website recognizes that you have already accessed and visited it with the browser you use on that device. The next time you visit our website on the same device, the information saved in the cookies will subsequently be transmitted either to our website (“first party cookie”) or to another website to which the cookie belongs (“third party cookie”).
We track the use of the site and we use this information to be able to design and display the website in an optimum way in line with your preferences. Cookies give us an understanding for how our web service is being used and helps us with development and improvements.
Only the cookie itself is identified on your device, the used cookies can’t identify you personally.
Cookies set by the website owner are called “first-party cookies”. Cookies set by parties other than the website owner are called “third-party cookies”. Third-party cookies enable third-party features or functionality to be provided on or through the website or service you are using (such as advertising, analytics). The third parties that set these third-party cookies can recognize your computer both when it visits the website or service in question and also when it visits certain other websites or services.
Cookies that are not strictly necessary to make the services available on our website are only used when you provide us with your consent. When you actively accept the use of cookies via the cookie banner on our website, you consent to the use of cookies. You can customize your cookie settings at any time, for example by activating or deactivating individual cookie categories. You can find out how to deactivate or delete cookies in your browser under the last point of this Cookie Policy.
To get information about the personal data we process in connection with our website and your data protection rights, please see our Privacy Policy.
We divide the cookies we use into the following categories based on their purpose and function:
.
These cookies are essential in order to enable you to move around our website and use its features, such as accessing secure areas of the website. Without these cookies, we would not be able to provide you with services like enabling appropriate content based on your type of device. The website cannot function properly without these cookies.
These cookies are used exclusively by this website and are therefore first party cookies. This means that all information stored in the cookies will be returned to this website.
The following strictly necessary cookies are used on our website:
| Name | Provider | Purpose | Expiry | Type |
| rc::a | This cookie is used to distinguish between humans and bots. This is beneficial for the website, in order to make valid reports on the use of their website. |
Persistent | HTML | |
| rc::b | This cookie is used to distinguish between humans and bots. | Session | HTML | |
| rc::c | This cookie is used to distinguish between humans and bots. | Session | HTML | |
| rc::d-# | This cookie is used to distinguish between humans and bots. | Persistent | HTML | |
| loglevel | vcc.live | During the chat conversation there are different statuses of the operator and the visitor, it is recorded at loglevel level in the file. Used for debugging purposes (when was the message sent etc.). |
Persistent | HTML |
| socketCluster.authToken | vcc.live | A framework used for socket type communication between the server and the website. Enables communication between the visitor and an operator. |
Persistent | HTML |
| entity | vcc.live | A protocol which allows the fetching of resources, such as HTML documents. It is the foundation of any data exchange on the Web and it is a client-server protocol, which means requests are initiated by the recipient, usually the Web browser. |
Persistent | HTML |
| workbox-precache-https___ vcc_live_ #precached-details-models |
vcc.live | Enables the website to be loaded faster on mobile and enables you to save the website to your phone so that it can be visited offline too. |
Persistent | IDB |
| webchatClientId | vcc.live | Used for identifying the conversation so the user can continue the same conversation he/she started. |
Persistent | HTML |
| CookieConsent | Cookiebot | Stores the user’s cookie consent state for the current domain. | 1 year | HTTP |
| CONSENT | YouTube | Used to detect if the visitor has accepted the marketing category in the cookie banner. This cookie is necessary for GDPR-compliance of the website. |
6 106 days | HTTP |
Strictly necessary cookies cannot be activated or deactivated individually. However, you can deactivate all cookies in your browser at any time.
.
Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously. These cookies allow us to see if our websites are working well – for example we can see which pages visitors go to most often, and if they get error messages. These cookies may be set by us or by third-party providers whose services we have added to our pages.
The following statistics cookies are used on our website:
| Name | Provider | Purpose | Expiry | Type |
| _ga | Registers a unique ID that is used to generate statistical data on how the visitor uses the website. | 2 years | HTTP | |
| _gat | Used by Google Analytics to throttle request rate | 1 day | HTTP | |
| _gid | Registers a unique ID that is used to generate statistical data on how the visitor uses the website. | 1 day | HTTP | |
| collect | Used to send data to Google Analytics about the visitor’s device and behavior. Tracks the visitor across devices and marketing channels. |
Session | Pixel | |
| e.gif | Albacross | Used to distinguish between different users coming from the same IP-address. | Session | Pixel |
| _dc_gtm_UA-# | Google Tag Manager | Used by Google Tag Manager to control the loading of a Google Analytics script tag. | 1 day | HTTP |
| __hstc | HubSpot | Cookie for tracking visitors. | 13 months | HTML |
| hubspotutk | HubSpot | This cookie keeps track of a visitor’s identity. It is passed to HubSpot on form submission and used when deduplicating contacts. | 13 months | HTML |
| __hssc | HubSpot | This cookie keeps track of sessions. This is used to determine if HubSpot should increment the session number and timestamps in the __hstc cookie. |
30 minutes | HTML |
| __hssrc | HubSpot | Whenever HubSpot changes the session cookie, this cookie is also set to determine if the visitor has restarted their browser. If this cookie does not exist when HubSpot manages cookies, it is considered a new session. |
Session | HTML |
| nQ_cookieId | Albacross | Sets a unique ID for a specific visitor. This ID can be used to recognize the visitor upon re-entry and implement any preference choices made. The cookie also allows the website to track the visitor on multiple websites for marketing purposes. |
1 year | HTTP |
.
Marketing cookies are used to track visitors across websites and to gather information about the websites visited by you. These cookies are used to deliver adverts more relevant to you and your interests. They are also used to limit the number of times you see an advertisement as well as help measure the effectiveness of the advertising campaign.
The following marketing cookies are used on our website:
| Name | Provider | Purpose | Expiry | Type |
| loc | Oracle | Geolocation, which is used to help providers determine how users who share information with each other are geographically located (state level). |
13 months | HTTP |
| uvc | Oracle | Detects how often the social sharing service, AddThis, encounters the same user. | 13 months | HTTP |
| xtc | Oracle | Registers the user’s sharing of content via social media. | 13 months | HTTP |
| IDE | Used by Google DoubleClick to register and report the website user’s actions after viewing or clicking one of the advertiser’s ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user. |
2 years | HTTP | |
| test_cookie | Used to check if the user’s browser supports cookies. | 1 day | HTTP | |
| fr | Used by Facebook to deliver a series of advertisement products such as real time bidding from third party advertisers. |
3 months | HTTP | |
| tr | Used by Facebook to deliver a series of advertisement products such as real time bidding from third party advertisers. |
Session | Pixel | |
| _fbp | Used by Facebook to deliver a series of advertisement products such as real time bidding from third party advertisers. |
3 months | HTTP | |
| nQ_userVisitId | Albacross | Sets a unique ID for a specific visitor. This ID can be used to recognize the visitor upon re-entry and implement any preference choices made. The cookie also allows the website to track the visitor on multiple websites for marketing purposes. | 1 day | HTTP |
| VISITOR_INFO1_LIVE | YouTube | Tries to estimate the users’ bandwidth on pages with integrated YouTube videos. | 179 days | HTTP |
| YSC | YouTube | Registers a unique ID to keep statistics of what videos from YouTube the user has seen. | Session | HTTP |
| yt-remote-cast-installed | YouTube | Stores the user’s video player preferences using embedded YouTube video. | Session | HTML |
| yt-remote-connected-devices | YouTube | Stores the user’s video player preferences using embedded YouTube video. | Persistent | HTML |
| yt-remote-device-id | YouTube | Stores the user’s video player preferences using embedded YouTube video. | Persistent | HTML |
| yt-remote-fast-check-period | YouTube | Stores the user’s video player preferences using embedded YouTube video. | Session | HTML |
| yt-remote-session-app | YouTube | Stores the user’s video player preferences using embedded YouTube video. | Session | HTML |
| yt-remote-session-name | YouTube | Stores the user’s video player preferences using embedded YouTube video. | Session | HTML |
| yt.innertube::nextId | YouTube | Registers a unique ID to keep statistics of what videos from YouTube the user has seen. | Persistent | HTML |
| yt.innertube::requests | YouTube | Registers a unique ID to keep statistics of what videos from YouTube the user has seen. | Persistent | HTML |
| _GRECAPTCHA | This cookie is used to distinguish between humans and bots. This is beneficial for the website, in order to make valid reports on the use of their website. | 179 days | HTTP | |
| __ptq.gif | HubSpot | Sends data to the marketing platform Hubspot about the visitor’s device and behaviour. Tracks the visitor across devices and marketing channels. |
Session | Pixel |
| bcookie | Used by the social networking service, Linkedin, for tracking the use of embedded services. | 2 years | HTTP | |
| bscookie | Used by the social networking service, Linkedin, for tracking the use of embedded services. | 2 years | HTTP | |
| lidc | Used by the social networking service, Linkedin, for tracking the use of embedded services. | 1 day | HTTP | |
| UserMatchHistory | Used to track visitors on multiple ebsites, in order to present relevant advertisement based on visitor’s preferences. | 29 days | HTTP |
.
We and our third-party partners may use other, similar technologies from time to time, like web beacons, pixels and other tracking technologies. Pixels are tiny graphics files that contain a unique identifier that enable us to recognize when someone has visited our website or in the case of web beacons, opened an email that we have sent them. This allows us, for example, to monitor the traffic patterns of visitors from one page within our website to another, to deliver or communicate with cookies, to understand whether you have come to our website from an online advertisement displayed on a third-party website, to serve targeted advertisements to you and others like you, to improve site performance, and to measure the success of marketing campaigns. While you may not have the ability to specifically reject or disable these tracking technologies, in many instances, these technologies are reliant on cookies to function properly; accordingly, in those instances, declining cookies will impair the functionality of these technologies.
Most browsers give you the ability to manage cookies to suit you. In some browsers you can set up rules to manage cookies on a site-by-site basis, giving you more fine-grained control over your privacy. This means you can disallow cookies from all sites except those that you trust. Browser manufacturers provide help pages relating to cookie management in their products. We have collected a short list of the main manufacturer’s help pages for your convenience below:
Please note that generally deactivating cookies may lead to functional restrictions on our website.
We may update this Cookie Policy from time to time in order to reflect, for example, changes to the cookies we use or for other operational, legal or regulatory reasons. Therefore, please review this Cookie Policy regularly to stay informed about our use of cookies and related technologies. The updated Cookie Policy will be effective as of the time of posting, or on such later date as may be specified in the updated Cookie Policy. The date at the top of this Cookie Policy indicates when it was last updated. When we change this Cookie Policy, we will update the “Last Modified” date above.
