Jump to: navigation, search

Legal Terms for Social Engagement 9.0.0

Overview

IMPORTANT - THIS DOCUMENT MUST BE READ IN FULL AND TERMS ACCEPTED PRIOR TO THE DEPLOYMENT OR UPGRADE OF GENESYS SOCIAL ENGAGEMENT

The release of Genesys Social Engagement version 9.0.0 ("Product") introduces some significant changes over earlier versions of the product.

Prior to deploying (or upgrading) and using the Product (and subsequent versions) you agree to review the remainder of this document, after which you will select the click-to-accept option to be bound by these Terms. If you do not agree to these Terms, in whole or in part, you will reject the Terms and refrain from deploying or otherwise using the product. If you are deploying (or upgrading) the product on behalf of an organization or entity ("Customer"), then you are agreeing to these Terms on behalf of that Customer and you represent and warrant that you have the authority to bind the Customer to these Terms. In that case, "you" and "your" refers to you and that Customer.

Social Engagement Channels

Channels in the Product are used to source and dispatch data to and from Twitter and Facebook and potentially other Social Networks ("Social Media Providers"). You, or authorized persons working with the Customer may setup channels for the purposes of enabling engagement around Customer’s business on Social Media. Customers will not setup channels for the purpose of monitoring competitors branded social networking pages or for uses outside of the need to engage and manage conversations regarding their business on Social Media.

The Customer’s usage of Social Media will be bound by the Social Media Providers: Rules, and Terms of Service, that may be found on Social Media Providers branded web pages. Notwithstanding any term in the Agreement to the contrary, Genesys reserves the right to suspend the Product, or portion thereof, or reject or cancel the transmission of any information through the Product based upon (i) reasonable belief that the use of the Product is in violation of applicable laws or Social Media Providers Terms of Service (ii) Customer’s use unreasonably burdening the platform running the Product (e.g., use of broad search criteria) or (iii) an imminent compromise to the security or integrity of the platform running the Product. As practicable depending on the circumstances, Genesys will provide written notice of the suspension and keep Customer reasonably informed of Genesys’ efforts to restore the Customer’s use of the Product.

Customer Interactions Stored in the Genesys Data Center

In order to facilitate the use of the analytics component of the Product, Genesys will store a copy of the customer’s inbound and outbound Twitter and Facebook posts, comments, and messages ("Customer Interactions") in a Genesys-managed software-as-a-service environment/data center, for a maximum of 4 months, after which the data will be deleted from the Genesys-managed software-as-a-service environment/data center. Customer will not use the Product to receive or transmit sensitive data, including but not limited to personal health information, personally identifiable information, passwords and sensitive account access information, and credit card information. Provided that Customer is fully compliant with the limitations in this Agreement, Genesys shall maintain reasonable, appropriate administrative, physical, and technical safeguards for protection of the security, confidentiality and integrity of Customer Interactions while such interactions are stored with the Genesys-managed software-as-a-service environment/data center center

As between Genesys and Customer, the Customer Interactions are the proprietary material of Customer and shall be considered Customer’s Confidential Information. Customer grants Genesys a non-exclusive, non-sublicenseable (except to parties working on Genesys' behalf), non-transferable, royalty-free license to access, process, store, transmit, and otherwise make use of the Customer Interactions as directed by Customer or as necessary to provide the Product capabilities and to otherwise fulfill its obligations under and in accordance with the Agreement.

Data Limits

Genesys does not limit the number of inbound Customer Interactions, but limits imposed by 3rd parties such as Twitter and Facebook apply to inbound Customer Interactions and thus may impact the availability and throughput of such inbound Customer Interactions. Inbound Customer Interactions may include tweets that mention the company’s handle or tweets that mention keywords, or Twitter Direct Messages, or any posts or comments around the customer’s Facebook page or events, or Facebook Private Messages via Facebook or Facebook Messenger.

Genesys does not limit the number of outbound Customer Interactions that are issued in direct response to inbound Customer Interactions.

Service Availability Support and Warranties

Service level targets as set out in the ENCODED_CONTENT MTcwMjICjxhIGhyZWY9Imh0dHBzOi8vZ2VuZXN5cy5teS5zYWxlc2ZvcmNlLmNvbS9zZmMvcC8jVTAwMDAwMDBLTTFHL2EvVTAwMDAwMDA4ZzVFL04zOFUzTFRuN1FlNElUaGphSi5GNDN0SnZLTHV1em85WU1tLlZyWjJUV1UiIHRhcmdldD0iX2JsYW5rIiBjbGFzcz0iZXh0ZXJuYWwgdGV4dCIgcmVsPSJub2ZvbGxvdyI+U3VwcG9ydCBHdWlkZSBmb3IgT24tUHJlbWlzZXMgTGljZW5zZXM8L2E+ END_ENCODED_CONTENT shall come into effect following acknowledged receipt of All Relevant Information being supplied by Customer to Genesys for the Product.

Maintenance must be purchased with new and continued use of the Product. The analytics component of the Product is facilitated by the Genesys-managed software-as-a-service environment/data center. Use of analytics component of the Product is only available for those customers that purchase and continuously maintain Maintenance. Lapse in maintenance coverage terminates any usage right of the analytics component of the Product.

Customers that discontinue Maintenance, may build custom interfaces to Social Media Providers, and continue to use the engagement capabilities of the Product.

Customer acknowledges that the Product is dependent on access to various third party services (including (but not limited to) Twitter and Facebook) and you agree that Genesys is not responsible for the non-availability, delays, failures or interruption affecting the Service or the performance of the Service caused by any such third party services or errors or bugs in software, hardware or the Internet on which the Service relies as you acknowledge that we do not control such third party services and such errors or bugs are inherent in the use of such software, hardware and the Internet.

Disclaimer

THE PRODUCT AND SERVICES ARE PROVIDED ON AN "AS IS" "WHERE IS" AND "AS AVAILABLE" BASIS WITHOUT WARRANTY OF ANY KIND EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. GENESYS MAKES NO REPRESENTATIONS OR WARRANTIES THAT USE OF THE SOCIAL ENGAGEMENT SERVICES WILL BE UNINTERRUPTED, TIMELY, COMPLETE, OR ERROR-FREE.

Do you accept these terms?

Accept button.png

Setting Up Social Engagement

Overview

Social Engagement 8.5.2 introduced new data architecture. From 8.5.2 onwards, the API connectors to Twitter and Facebook are stored in the Genesys Hub. This allows the Genesys Engineering team to quickly adapt to changes to the APIs made by Twitter and Facebook, and thus protect customers from the volatility inherent in connecting to Social Networks via APIs. Now, besides installing Twitter and Facebook drivers on-premise, you must also set up and configure the cloud component (known as Genesys Social Admin).

Important
In release 9.0, Genesys Cloud for Social has been renamed to Genesys Hub. For information about the current active version of the Genesys Hub environment, see the Genesys Hub Release Note.

Legal Terms for Social Engagement 9.0.x

Important
If you have not already done so, please read and accept these terms to continue.

Installing On-premise Components

Important
Regardless of whether you are a new customer or an existing customer upgrading, it’s critical that you have already read and accepted the legal terms referenced above.

For New Social Engagement Customers:

  1. Install Digital Messaging Server.
  2. Install Social Engagement 8.5.x or 9.0.x

For Existing Social Engagement Customers:

  1. Uninstall your existing drivers and remove their configuration options, as described here.
  2. Proceed to install Social Engagement 8.5.x or 9.0.x, as described in the following section.

Installing Social Engagement 8.5.x or 9.0.x

  1. Download the installation packages for Genesys Cloud API Driver for Twitter and Genesys Cloud API Driver for Facebook.
  2. Locate the installation script for each driver (install.exe for windows and install.sh for Linux platforms) and run it.
  3. While running the script you will be asked to enter/confirm:
    • Host Name
    • Configuration Server Host Name
    • Network port
    • Username
    • Password
  4. Select a Digital Messaging Server object.
  5. Answer any other questions and finish the installation.
  6. If you are an existing customer,
    1. In Genesys Administrator Extension, select the Digital Messaging Server object, go to the Options tab, and select Import.
    2. Import the configuration files driver-for-facebook-options.cfg for Facebook and driver-for-twitter-options.cfg for Twitter (usually located in ...SMServer/media-channel-drivers/channel-facebook and .../SMServer/media-channel-drivers/channel-twitter). Select to NOT override the existing configuration options. At this point, you have two new configuration sections: [channel-facebook] and [channel-twitter]. For more information on importing .cfg files, see the Genesys Administrator Extension User Guide.
  7. Use Genesys Administrator Extension to configure your Digital Messaging Server application for the Twitter and Facebook driver channels. For more information about the Digital Messaging Server options, see the Digital Messaging Server Guide.

Preparing for the Cloud Integration

After you have completed the above steps, you can gather the following information:

  1. Identify and note the name of the company/organization that will be using the product—for example, XYZ Corp. This is your Account name for Genesys Social Admin.
  2. For Twitter:
    1. Identify and note the handle, (and optionally, keyword strings) that you plan to use for your Twitter feed:
      • In most instances, using just the Twitter handle used for responding will be a sufficient first step; for example, ‘@XYZCorp_Help’.
      • It is CRITICAL that only the appropriate keywords are used. Twitter does not permit infinite access to the Twitter data feed. If very broad or popular keywords are used inappropriately, too much data will be consumed. If keywords such as: #JustinBieber, #iphone, #awesome were used the likely result would be a data failure.
      • Testing for keywords may be necessary in order to check and see if they are inappropriate. To do this go to https://twitter.com/search-home and enter the keyword(s) you plan to use (one at a time). View the search results and if they are relevant. Only relevant keywords should be used.
    2. Note the login and password credentials for any twitter handles you intend to use with Social Engagement.
  3. For Facebook:
    1. Identify and note the names of the of the Facebook pages that you plan to use.
    2. Note the login and password credentials for the user that has administrator access to these Facebook pages.

Note also the following:

  • Ports—Both Twitter and Facebook drivers (installed in Digital Messaging Server) connect to the Social Admin platform (in the Genesys Hub) using HTTPS on standard port 443. All API calls must go over HTTPS.
  • Copy, Paste, Save—In the first seven steps of the following setup you will have to copy and save various pieces of text in order to use them in later steps. Please have a plain-text editor ready on your desktop and be prepared to save text (along with descriptions regarding the text) from steps 1 through 7.

Cloud Integration

Contents of this section:

  1. Set up an account
  2. Create a Twitter account channel
  3. Create a Twitter service channel
  4. Create a Facebook account channel
  5. Create a Facebook service channel
  6. Define an Admin user
  7. Configure connections
  8. Using more than one Twitter handle

1. Set up your company/organization account

The first step of deploying Social Engagement requires you to create an Account within the Social Admin component of Social Engagement.

  1. Navigate to https://socialanalytics.genesyscloud.com/gse/signup. You should see a form titled "Setup your Social Engagement Software."
  2. Setup Form
  3. Populate the fields. Note and copy the value of Company/Org. Name to your text file (for example, Company/Org. Name: ##> ACME XYZ123 Corp.) You'll use this text in a later step of this setup.
  4. Click Continue.
  5. Go to your email inbox and open the email titled "Confirmation required for Genesys Social Engagement deployment". If you don't see it, check your spam folder.
  6. Follow the steps described in the email and select the option to log in using the email and password you've just created.
  7. After successfully logging in, navigate to the top right hand corner of the screen and click on the small gear icon to access Settings.
  8. Hub Settings Icon.png

  9. In the next view, click the Accounts options.
  10. Click the pencil icon to open the edit view for the account that you have just created
  11. In the edit view of your account, copy and paste the value of the API key field to your text file. You'll need it in a later stage of this setup.
  12. API key
  13. At this point it is not necessary to make any changes to the other fields and attributes on this form.

2. Create a Twitter channel with the type Twitter:Account

The Twitter Channel with channel type 'Twitter:Account' is the mechanism you will use to authenticate to Twitter. Please be ready with your organization's Twitter handle (login) and Twitter password before proceeding.

Important
Your company or organization may use multiple Twitter handles. Step 8 below describes how to handle this situation.
  1. Navigate to the top right hand corner of the screen and click the small gear icon, then click Settings on the drop-down that appears.
  2. In the following view, select Channels, then click the green + icon to create a new channel.
  3. Settings-Channels

    The New Channel window displays.

    New Channel
  4. From the Channel Type drop-down, select Twitter:Account.
  5. Add a Channel Name. Please use the form <your channel's Twitter handle> - Twitter Account. Example: @Genesys - Twitter Account.
  6. Optionally, add a description that indicates the planned usage of the channel.
  7. Click Save and Proceed.
  8. An extended form displays. On it is a Channel ID, as shown in the figure below. Make a note of this Channel ID—it will be needed for a later step
  9. GSE Tw-channel-ID.png
  10. Click Login to Twitter.
  11. GSE Tw-login-to.png
  12. Enter the Twitter credentials for your organization: username (handle) or email, and the password associated with your Twitter account. IMPORTANT: Also check Remember me.
  13. GSE Tw-authorize.png
  14. A window that displays Access_token successfully saved indicates that you have successfully authenticated to Twitter.

3. Create a Twitter channel with the type Twitter:Service

A Twitter channel of type Twitter:Service will listen for mentions of your keyword(s) on Twitter.

  1. Navigate to the top right hand corner of the screen, click the small gear icon, and select Settings.
  2. In the following view, select Channels, then click the green + icon to create a new channel
  3. In the New Channel window (see the figure New Channel above):
    1. From the Channel Type drop-down, select Twitter:Service.
    2. Add a Channel Name. Please use the convention '<your channel's Twitter handle> - Twitter Service'. Example: @Genesys - Twitter Service.
    3. Optionally, add a Description.
    4. Click Save & proceed.
  4. An extended form displays.
  5. New Channel, extended
    1. Click in Languages to select one or more languages.
    2. In Keywords, type the handle you will be using to listen for mentions, for example @Genesys, then hit Return or Tab. This will have the effect of sourcing all tweets based on the handle that you use.
  • If there is a need, you may source additional posts by populating other words and phrases in the keyword field; for example, #Genesys.
  • It is not possible to exclude posts with certain mentions, while including others. The inclusion of words or phrases in the keyword field is the only mechanism for sourcing posts from Twitter. If you have a need to use a broader range of words and phrases, it is important to review Best Practices for Managing Keywords in Twitter Service Channels below.
  • Click Yes if you want to Skip Retweets. Skipping retweets means your system will not source tweets that have been retweeted, which may help cut out clutter and noise. You may want to select No if you want to analyze retweets and viral activity.
  • In Twitter Handle(s), just type the Twitter handle that you will be using to respond, example @Genesys. It is only possible to respond with one handle per channel. If you need to create multiple channels for the purpose of responding using different channels, this is addressed later in step 9.
  • To ensure the deletion of personal data (Personally Identifiable Information) from Twitter messages after the on-premise Twitter driver fetches the data, click Do not store personal data.

    This action is not retroactive. Pre-existing personal information remains in the UCS database.

  • Click Update and Proceed.
  • 4. Create a Facebook channel with the type Facebook:Account

    A Facebook channel of this type is the mechanism you will use to authenticate to Facebook. Please be ready with your organization's Facebook administrator login credentials for the relevant page(s) before proceeding. For simplicity, please make sure that you are currently logged into Facebook (with this administrator's password) using the same browser that you are using for this setup.

    1. Navigate to the top right hand corner of the screen and click the small gear icon, then click Settings on the drop-down that appears.
    2. In the following view, select Channels, then click the green + icon to create a new channel.
    3. Settings-Channels

      The New Channel window displays.

      New Channel
    4. From the Channel Type drop-down, select Facebook:Account.
    5. Add a Channel Name. Please use the convention <company name> - Facebook Account. Example: Genesys - Facebook Account.
    6. Optionally, add a description that indicates the planned usage of the channel.
    7. Click Save and Proceed.
    8. An extended form displays.
    9. Update Channel
    10. Make a note of the Channel ID—it will be needed for a later step
    11. Click Login to Facebook. A pop-up appears asking you to log in to Facebook
    12. Facebook Login
    13. Log in with the admin credentials for the Facebook pages that you want to use. It is important that these user credentials have Facebook admin access to all of the Facebook pages to be used.
    14. Once you have logged in and authenticated you should see a message access_token successfully saved, close window. You may close this window.

    5. Create a Facebook channel with the type Facebook:Service

    A Facebook channel of this type is used to listen for posts, comments, and messages on Facebook.

    1. Navigate to the top right hand corner of the screen and click the small gear icon, then click Settings on the drop-down that appears.
    2. In the following view, select Channels, then click the green + icon to create a new channel.
    3. Settings-Channels

      The New Channel window displays.

      New Channel
    4. From the Channel Type drop-down, select Facebook:Service.
    5. Add a Channel Name. Please use the convention <company name> - Facebook Service. Example: Genesys - Facebook Service.
    6. Optionally, add a description that indicates the planned usage of the channel.
    7. Click Save and Proceed.
    8. Update Channel displays.
    9. Update Channel
    10. Make a note of the Channel ID—it will be needed for a later step
    11. Click Facebook Pages to get a drop-down list of all of the Facebook pages that the Facebook user is an administrator of. Select each page that you want to monitor.
    12. Click Facebook Events to get a drop-down list of all of the Facebook Events that the Facebook user is an administrator of. Select each event that you want to monitor.
    13. To ensure the deletion of personal data (Personally Identifiable Information) from Facebook posts after the on-premise Facebook driver fetches the data, click Do not store personal data.

      This action is not retroactive. Pre-existing personal information remains in the UCS database.

    14. Click Update & proceed.

    6. Define an Admin user for the account

    You will also have to create a new admin user login and password in order to facilitate communication with Digital Messaging Server.

    1. Navigate to the top right hand corner of the screen and click the small gear icon, then click Settings on the drop-down that appears.
    2. New User
    3. From the following view, select User Management.
    4. In the First Name field, type the company's name followed by a 1; for example, Genesys1.
    5. In the Last Name field, type admin.
    6. In the Email field, type an email address using a format like the following: Genesys1_Admin@GenSocialEngage.com. Copy and paste this email address to your notepad file as it will be used for a later step of the deployment.
      Important
      This email address will not be used for sending or receiving emails. It is only used to manage logging in, and communications between the cloud and on-premise components of Genesys Social Engagement.
    7. Make sure that Admin is selected in the Roles field.
    8. Click Create.
    9. Now return to User Management. You should see a list of the users associated with the account that you have set up.
      User Management
    10. Click Reset Password for the admin user that you have just created.
    11. Enter a new password, and make a note of it (copy and paste to your text file); also make a note of associated email address. You will use them in a later step of the deployment.

    7. Configure connections

    To configure connections between the on-premise Digital Messaging Server and the cloud-based Account and Channels that you set up in Steps 1 through 5 above, you must set values for certain configuration options.

    1. Import the configuration options files, being sure to select No in response to Do you want to overwrite the existing data?
    2. Set option values both the Twitter and Facebook Drivers. The values are based on the setup in Steps 1–6. Be sure that your text file has all of the text that you've copied and pasted clearly identified. Set the option values by copying and pasting the exact values from your text file (complete descriptions of these options are on this page).
      Option Values
      Option Value
      gsa-account-name Company/Organization name from Step 1
      gsa-api-key API key from Step 1
      gsa-channel-id Facebook—Facebook:Service Channel ID from Step 5
      Twitter—Twitter:Service Channel ID from Step 3
      gsa-channel-name Facebook—Facebook:Service channel name in Step 5
      Twitter—The exact text used in the Twitter:Service channel name from Step 3
      gsa-url-base socialanalytics.genesyscloud.com/api/v2.0
      gsa-user-name The admin email address from Step 6
      gsa-user-password The admin password from Step 6
    3. Sample values are shown in the following figures (click to enlarge). Note that the values of gsa-api-key, gsa-channel-id, and gsa-user-password are masked in these figures for privacy.

      Facebook Sample
      Twitter Sample

    4. Test both channels by submitting posts via Twitter and Facebook, and seeing if they appear in the customer’s Workspace.

    8. Using more than one Twitter handle to respond to customers

    Use this step if a Genesys customer has two or more Twitter handles (for example, @ACMEXYXCorp1, @ACMEXYZCorp2) that they wish to use for conversing with customers on Twitter.

    Important
    The best practice for Facebook is to make the user that is authenticated to Facebook and admin user of ALL of the pages that will be selected for monitoring in step 5. This will mean that the step outlined here will not be necessary for Facebook.
    1. Repeat Steps 2 and 3 above to configure another pair of Twitter:Account and Twitter:Service channels using another twitter handle.
    2. Repeat Step 6 to add another admin and set a password, taking care to note the new email that you use and password. These will be used in a later step.
    3. Log out of https://socialanalytics.genesyscloud.com
    4. GSE logout-genesys.png

    5. Now use the admin credentials just created to log in again to https://socialanalytics.genesyscloud.com
    6. Navigate to the top right hand corner of the screen and click the small gear icon, then click Settings on the drop-down that appears.
    7. Click Default Channels.
    8. Default Channels
    9. From the pulldown, select the Twitter:Account channel that you just created.
    10. Now repeat Step 7: import another Twitter channel configuration template and set the options using the values of the new Twitter:Service handle and the additional admin email and password that you just created.

    Production Toggle

    You can toggle between production and non-production (lab, staging, test) modes using a switch in Hub.

    1. Log in to Hub.
    2. Click Channels in the left-hand menu to get a list of the channels you have access to.
    3. Select a channel and click Edit.
    4. Slide the toggle to the right to engage Production mode.
    GSE854 production-toggle.png

    Note the following:

    • Internal Service Level Agreements (SLAs) apply only to accounts in production mode.
    • Genesys carries out recovery, or assists with it, for Production accounts only.
    • Production mode is indicated in reports.
    • Production mode requires all required licenses to be in place.
    • Switching to Production mode creates a distribution list to send emails and updates in the Hub Status page.
      Hub production mode email list.png

    Best Practices for Managing Keywords in Twitter Service Channels

    When setting up a Twitter:Service channel, you have the option to add any text in the Keyword field. It is important to use only appropriate keywords. If your keywords are very common or popular, your inbound feed may be cluttered with too many useless posts. In extreme scenarios, Twitter may cut off access to data if the data volumes are too high. This might occur for example if you were to input keywords such #awesome or hello.

    Warning
    If a channel's inbound traffic exceeds 300 tweets per minute for a certain keyword, the keyword is removed from the channel automatically. The keyword can be added back by the admin account after 3 days, when the keyword gets unblocked. However, users can request the Genesys representative to add the keyword back before the 3 days block period expires. Users can run recovery on the missing data after the keyword has been added back and there is no risk of the keyword getting blocked while data recovery is running as the recovery uses a different API.

    If one were to set up a channel to monitor mentions of Genesys on Twitter, some appropriate keywords and phrases would include: @Genesys, #Genesys, and Genesys software.

    It is essential to check that keywords you use are not too broad or ambiguous. Go to https://twitter.com/search-home and check the keyword(s) you plan to use (one at a time). You will need to view the search results and assess the results. If there were a company called "United Ultra Local Bank Inc." one might be inclined to use the keyword #United. This would be a mistake, as it would source a flood of unnecessary posts from Twitter users that are submitting posts relating to #United Nations, #United States, Manchester #United, and so on. Even worse would be #Check, savings account, #balance, or overdraft as these are even more generic.

    Feedback

    Comment on this article:

    blog comments powered by Disqus
    This page was last modified on October 16, 2018, at 04:27.