diff --git a/README.md b/README.md index e1b0ee6..a2b4be5 100644 --- a/README.md +++ b/README.md @@ -1,12 +1,12 @@ # Web chat service desk extension starter -This repo provides a set of example and starter kit service desk integrations for use with Watson Assistant web chat – to allow end-users on web chat to escalate to a human agent. We provide starter kits to common live agent platforms, like Genesys Cloud, and also show you how to build custom integrations to other platforms. +This repo provides a set of example and starter kit service desk integrations for use with watsonx Assistant web chat – to allow end-users on web chat to escalate to a human agent. We provide starter kits to common live agent platforms, like Genesys Cloud, and also show you how to build custom integrations to other platforms. ## Overview -This repo provides an example development and production build environment as well as code examples for adding your own client-side service desk integration with web chat for Watson Assistant. You can use the tools in this repo to build an independently deployable JavaScript bundle of your integration, or you can copy the example code into your own application for build and deployment. These integrations can be shared between teams and also can be submitted as potential contributions to the main web chat project. If you're interested in contributing to this project or proposing that your integration be offered in Watson Assistant, see [CONTRIBUTING.md](./CONTRIBUTING.md). +This repo provides an example development and production build environment as well as code examples for adding your own client-side service desk integration with web chat for watsonx Assistant. You can use the tools in this repo to build an independently deployable JavaScript bundle of your integration, or you can copy the example code into your own application for build and deployment. These integrations can be shared between teams and also can be submitted as potential contributions to the main web chat project. If you're interested in contributing to this project or proposing that your integration be offered in watsonx Assistant, see [CONTRIBUTING.md](./CONTRIBUTING.md). -**Important:** This is an open source project of example implementations to help people get started on their own custom code. Any custom code used with Watson Assistant is the responsibility of the developer and is not covered by IBM support. If you find a bug in these examples, please submit a pull request with a fix. See [CONTRIBUTING.md](./CONTRIBUTING.md). +**Important:** This is an open source project of example implementations to help people get started on their own custom code. Any custom code used with watsonx Assistant is the responsibility of the developer and is not covered by IBM support. If you find a bug in these examples, please submit a pull request with a fix. See [CONTRIBUTING.md](./CONTRIBUTING.md). To find out if your company's tool is feasible for this approach, check out our Adoption Guide [here](./docs/ADOPTION_GUIDE.md). If you'd like some help to build an integration, [you can contact us](https://www.ibm.com/watson/assistant-integrations/?utm_medium=webchatbyosd). @@ -68,8 +68,8 @@ This repo can be used as an isolated tool to build and test your integration wit There are two basic types of integrations provided in this repo. -1. A seamless integration with the existing web chat UI. The user will use the web chat input field to send messages to an agent and messages from an agent will be displayed in the same message list along with messages from Watson Assistant. These integrations require fully implementing the service desk integration API provided by web chat. -2. A custom panel implementation embedding a 3rd party chat widget. The user will switch to a different panel where they will see a different UI created by a 3rd party. A different field from the standard web chat input field will generally be available and messages to and from the agent will be displayed in a separate view and not part of the messages from Watson Assistant. These integrations generally require a lot less code and only require embedding another existing widget into web chat, but can result in an inconsistent user or visual experience. +1. A seamless integration with the existing web chat UI. The user will use the web chat input field to send messages to an agent and messages from an agent will be displayed in the same message list along with messages from watsonx Assistant. These integrations require fully implementing the service desk integration API provided by web chat. +2. A custom panel implementation embedding a 3rd party chat widget. The user will switch to a different panel where they will see a different UI created by a 3rd party. A different field from the standard web chat input field will generally be available and messages to and from the agent will be displayed in a separate view and not part of the messages from watsonx Assistant. These integrations generally require a lot less code and only require embedding another existing widget into web chat, but can result in an inconsistent user or visual experience. ## Prerequisites @@ -77,7 +77,7 @@ The scripts and some of the code in this repository rely on having [Node.js](htt ## Displaying the chat history to your human agent ("agent app") -Watson Assistant will pass configuration needed to display a chat history widget in your live agent application interface. This agent application will contain a copy of the conversation your customer had with Watson Assistant for your live agent to be able to view. Visit [the agent app documentation](https://web-chat.global.assistant.watson.cloud.ibm.com/docs.html?to=service-desks-custom-sd#agent-app) to learn more. +watsonx Assistant will pass configuration needed to display a chat history widget in your live agent application interface. This agent application will contain a copy of the conversation your customer had with watsonx Assistant for your live agent to be able to view. Visit [the agent app documentation](https://web-chat.global.assistant.watson.cloud.ibm.com/docs.html?to=service-desks-custom-sd#agent-app) to learn more. ## Development diff --git a/src/egain/webChat/README.md b/src/egain/webChat/README.md index 0b6f494..6edbd20 100644 --- a/src/egain/webChat/README.md +++ b/src/egain/webChat/README.md @@ -1,6 +1,6 @@ # eGain ServiceDesk Integration Example -This is a functioning service desk integration between Watson Assistant and eGain's Advisor Desktop. +This is a functioning service desk integration between watsonx Assistant and eGain's Advisor Desktop. **Important:** This is a reference implementation that provides an example of a fully functional integration. Make any necessary changes and perform robust testing before deploying this integration in production. @@ -8,7 +8,7 @@ This reference implementation supports the core features of an eGain integration ## Overview -The integration example consists of client-side code that runs in the user's browser and manages the communication between the user and agent. This is an integration of eGain's Advisor Desktop with service desk API that is fully supported by the Watson Assistant web chat integration. (For more information about this API, see [ServiceDesk API](https://github.com/watson-developer-cloud/assistant-web-chat-service-desk-starter/blob/main/docs/API.md)). +The integration example consists of client-side code that runs in the user's browser and manages the communication between the user and agent. This is an integration of eGain's Advisor Desktop with service desk API that is fully supported by the watsonx Assistant web chat integration. (For more information about this API, see [ServiceDesk API](https://github.com/watson-developer-cloud/assistant-web-chat-service-desk-starter/blob/main/docs/API.md)). ## Prerequisites diff --git a/src/enghouse/README.md b/src/enghouse/README.md index 737cf6a..ddc83dd 100644 --- a/src/enghouse/README.md +++ b/src/enghouse/README.md @@ -1,6 +1,6 @@ # Enghouse Interactive CCaaS Integration Example -The **Enghouse CCaaS** integration enables integration between IBM Watson Assistant (WA) and Enghouse Interactive (EI) CCaaS tenants' live agents. +The **Enghouse CCaaS** integration enables integration between watsonx Assistant (WA) and Enghouse Interactive (EI) CCaaS tenants' live agents. ## Overview @@ -12,9 +12,9 @@ The integration attempts to make it as simple as possible for Watson Assistance The EI CCaaS integration consists of two main components: hosting web page and backend Contact Center platform . Below is client side component Architecture: -![EI CCaaS Watson Assistant Integration Architecture Overview](ibmWatson.jpg) +![EI CCaaS watsonx Assistant Integration Architecture Overview](ibmWatson.jpg) -The client-side component manages the communication between the user and the agent. It implements the service desk API that is fully supported by the Watson Assistant web chat integration. (For more information about this API, see [ServiceDesk API](https://github.com/watson-developer-cloud/assistant-web-chat-service-desk-starter/blob/main/docs/API.md)). +The client-side component manages the communication between the user and the agent. It implements the service desk API that is fully supported by the watsonx Assistant web chat integration. (For more information about this API, see [ServiceDesk API](https://github.com/watson-developer-cloud/assistant-web-chat-service-desk-starter/blob/main/docs/API.md)). The communication uses the EI CustomChat widget component. This can be referenced using the EI CCaaS default page or a [hosting page](./client/watsonExample.html) can set the `watsonAssistantChatOptions` prior to loading the EnghouseCCaaSWatsonAssistant.js for more advanced features, e.g.: @@ -98,10 +98,10 @@ If the Assistant URL provided to you by Enghouse Interactive was: The complete list of parameters that may be passed to the standard EI CCaaS Watson page URL are: -- *integrationID* - Watson Assistant Integration ID -- *region* - Watson Assistant region -- *serviceInstanceID* - Watson Assistant Instance ID -- *subscriptionID* - Watson Assistant Subscription ID +- *integrationID* - watsonx Assistant Integration ID +- *region* - watsonx Assistant region +- *serviceInstanceID* - watsonx Assistant Instance ID +- *subscriptionID* - watsonx Assistant Subscription ID - *ccName* - the display name of the contact centre, displayed prior to agent answering chat (default is "Contact Centre") - *ccURL* - the URL-encoded "widget" URL. This may also be set (un-encoded) via the Dialog as the *CCURL* variable (overrides URL if both set). - *agentIcon* - the URL-encoded URL of the agent icon (default is an Enghouse Interactive swirl logo). This may also be set (un-encoded) in the Dialog as the *AgentIcon* variable (overrides URL if both set). diff --git a/src/enghouse/VG_TravelDemo-dialog.json b/src/enghouse/VG_TravelDemo-dialog.json index e767e8f..89d5cfb 100644 --- a/src/enghouse/VG_TravelDemo-dialog.json +++ b/src/enghouse/VG_TravelDemo-dialog.json @@ -1935,7 +1935,7 @@ "CCURL": "https://ccsp.ei.eilabonline.biz/SocialConnectorHelperAPI/api/customchat/getWidgetConfiguration?WidgetId=5dae9357-0660-ed11-8160-00155dfe5104", "LiveCSR": false, "AgentIcon": "EI_swirl_up.png", - "SC_TestOP": "Watson Assistant Live Agent handover test", + "SC_TestOP": "watsonx Assistant Live Agent handover test", "firstName": "CustomerName", "my_credentials": { "user": "a0e67977-e38e-45cc-b222-884d415eff09", diff --git a/src/example/webChat/client/src/exampleServiceDesk.ts b/src/example/webChat/client/src/exampleServiceDesk.ts index fb4aa74..6a81ba4 100644 --- a/src/example/webChat/client/src/exampleServiceDesk.ts +++ b/src/example/webChat/client/src/exampleServiceDesk.ts @@ -71,7 +71,7 @@ class ExampleServiceDesk implements ServiceDesk { async startChat(connectMessage: MessageResponse, startChatOptions?: StartChatOptions): Promise { // Most service desks have a way to embed a custom iFrame into the agent view, as well as a way to pass metadata // into that iFrame. startChatOptions.agentAppInfo contains metadata for you to be able to render the conversation - // history with Watson Assistant to your agents in a custom iFrame and this data should be passed via whatever + // history with watsonx Assistant to your agents in a custom iFrame and this data should be passed via whatever // methods the service desk you are using uses. // In your real implementation you will want to grab this.user and this.sessionID to make available to your service desk. diff --git a/src/example/webChat/client/src/serviceDeskTemplate.ts b/src/example/webChat/client/src/serviceDeskTemplate.ts index 8cf9ced..c3892c8 100644 --- a/src/example/webChat/client/src/serviceDeskTemplate.ts +++ b/src/example/webChat/client/src/serviceDeskTemplate.ts @@ -58,7 +58,7 @@ class ServiceDeskTemplate implements ServiceDesk { * * Most service desks have a way to embed a custom iFrame into the agent view, as well as a way to pass metadata * into that iFrame. startChatOptions.agentAppInfo contains metadata for you to be able to render the conversation - * history with Watson Assistant to your agents in a custom iFrame and this data should be passed via whatever + * history with watsonx Assistant to your agents in a custom iFrame and this data should be passed via whatever * methods the service desk you are using uses. * * @param connectMessage The original server message response that caused the connection to an agent. It will diff --git a/src/flex/agentApp/README.md b/src/flex/agentApp/README.md index 0f61a26..ecdf6ad 100644 --- a/src/flex/agentApp/README.md +++ b/src/flex/agentApp/README.md @@ -1,12 +1,12 @@ -# Twilio Flex Watson Assistant Agent App +# Twilio Flex IBM watsonx Assistant Agent App -This is a functioning agent app integration between Watson Assistant and Twilio Flex. +This is a functioning agent app integration between watsonx Assistant and Twilio Flex. **Important:** This is a reference implementation that provides an example of a fully functional integration. Make any necessary changes and perform robust testing before deploying this integration in production. ## Overview -This integration provides agents in Twilio Flex with a transcript of the conversation between the end user and Watson Assistant. To learn more about transferring between end users and agents in Twilio Flex please see: +This integration provides agents in Twilio Flex with a transcript of the conversation between the end user and watsonx Assistant. To learn more about transferring between end users and agents in Twilio Flex please see: - [Twilio Flex Service Desk for WebChat](../webChat/) - [Twilio Flex Service Desk for Phone](https://cloud.ibm.com/docs/assistant?topic=assistant-deploy-phone-flex) @@ -33,12 +33,12 @@ npm ci To deploy your plugin, open a terminal and run the following command: ```bash -twilio flex:plugins:deploy --major --changelog "Adds the Watson Assistant Agent App" --description "Enables the service desk agent to get a quick view of the conversation history between the visitor and Watson Assistant." +twilio flex:plugins:deploy --major --changelog "Adds the watsonx Assistant Agent App" --description "Enables the service desk agent to get a quick view of the conversation history between the visitor and watsonx Assistant." ``` This command will upload the plugin to Twilio Flex, but it is not enabled for all users until it is released. You can release the plugin by executing this command: ```bash -twilio flex:plugins:release --name "Plugin Release - Watson Assistant Agent App" --description "Enabling plugin Watson Assistant Agent App" --plugin plugin-watson-assistant-agent-app@latest +twilio flex:plugins:release --name "Plugin Release - watsonx Assistant Agent App" --description "Enabling plugin watsonx Assistant Agent App" --plugin plugin-watson-assistant-agent-app@latest ``` For more details on deploying your plugin, refer to the [deploying your plugin guide](https://www.twilio.com/docs/flex/developer/plugins/cli/deploy-and-release). diff --git a/src/flex/webChat/README.md b/src/flex/webChat/README.md index 1c0a85c..725bc57 100644 --- a/src/flex/webChat/README.md +++ b/src/flex/webChat/README.md @@ -1,6 +1,6 @@ # Twilio Flex integration example -This is a functioning service desk integration between Watson Assistant and the Twilio Flex contact center. +This is a functioning service desk integration between watsonx Assistant and the Twilio Flex contact center. **Important:** This is a reference implementation that provides an example of a fully functional integration. Make any necessary changes and perform robust testing before deploying this integration in production. @@ -35,7 +35,7 @@ The following Twilio resources provide some useful guides on Twilio Flex custom 1. Run `npm install` to install the dependencies. -1. Run `npm run dev` to start the middleware server, which authorizes the user with Twilio and helps in setting up the integration. At run time, the Watson Assistant web chat will call the `/auth` API hosted here for the necessary authentication information. +1. Run `npm run dev` to start the middleware server, which authorizes the user with Twilio and helps in setting up the integration. At run time, the watsonx Assistant web chat will call the `/auth` API hosted here for the necessary authentication information. **Note:** By default, the local server uses an unsecure `http://` connection. For a production deployment, you must host the server API at a secure public URL using `https://`. @@ -57,7 +57,7 @@ You should now be able to start a web chat session in a browser, and within the - **Agent transfers:** The event listeners set up in [twilioFlex.ts](./client/src/twilioFlex.ts) listen for participants joining and leaving the channel. This example implementation uses the `memberLeft` event to close the chat if an agent leaves; you will need to modify this behavior to support agent transfers. -- **Conversation topic:** The example implementation sends the `message_to_human_agent` attribute from the dialog as the first message to the agent when the conversation starts. However, several other attributes are available within the `connectMessage` object that is passed to the `startChat()` function. For more information, see the documentation for the `topic` property of the `connect_to_agent` response type in the Watson Assistant [API reference](https://cloud.ibm.com/apidocs/assistant/assistant-v2#message). +- **Conversation topic:** The example implementation sends the `message_to_human_agent` attribute from the dialog as the first message to the agent when the conversation starts. However, several other attributes are available within the `connectMessage` object that is passed to the `startChat()` function. For more information, see the documentation for the `topic` property of the `connect_to_agent` response type in the watsonx Assistant [API reference](https://cloud.ibm.com/apidocs/assistant/assistant-v2#message). - **Agent name and avatar:** The agent name is available in the example implementation. The web chat provides a method to display the agent avatar, but this is not implemented for Twilio Flex. diff --git a/src/genesys/agentApp/README.md b/src/genesys/agentApp/README.md index 92d852c..3fc6dce 100644 --- a/src/genesys/agentApp/README.md +++ b/src/genesys/agentApp/README.md @@ -1,12 +1,12 @@ -# Genesys PureCloud Watson Assistant Agent App +# Genesys PureCloud IBM watsonx Assistant Agent App -This is a functioning Agent App integration between Watson Assistant and Genesys PureCloud. +This is a functioning Agent App integration between watsonx Assistant and Genesys PureCloud. **Important:** This is a reference implementation that provides an example of a fully functional integration. Make any necessary changes and perform robust testing before deploying this integration in production. ## Overview -This integration provides agents in Genesys PureCloud with a transcript of the conversation between the end user and Watson Assistant. To learn more about transferring between end users and agents in Genesys PureCloud, please see: +This integration provides agents in Genesys PureCloud with a transcript of the conversation between the end user and watsonx Assistant. To learn more about transferring between end users and agents in Genesys PureCloud, please see: - [Genesys Service Desk for WebChat](../webChat/) - [Genesys Service Desk for Phone](https://cloud.ibm.com/docs/assistant?topic=assistant-deploy-phone-genesys) @@ -29,7 +29,7 @@ To start up a server in `localhost`, follow these steps: ## Authentication 1. Follow the steps to create an [OAuth Client for Genesys](https://help.mypurecloud.com/articles/create-an-oauth-client/). When choosing the **Grant Type**, choose **Implicit Grant (Browser)**. - - For **App Name**, you can specify any name for the application (for example, `Watson Assistant - Agent App OAuth`). + - For **App Name**, you can specify any name for the application (for example, `watsonx Assistant - Agent App OAuth`). - In the **Authorized Redirect URI(s)** field, specify the URL where you will be hosting the Agent Application. If you're using `ngrok`, specify the URL in the following format: ``` https://.grok.io/WatsonAssistantAgentAppWidgetProxy.html diff --git a/src/genesys/agentApp/public/js/WatsonAssistantAgentAppWidgetProxy.js b/src/genesys/agentApp/public/js/WatsonAssistantAgentAppWidgetProxy.js index 3ef03a4..86e36a4 100644 --- a/src/genesys/agentApp/public/js/WatsonAssistantAgentAppWidgetProxy.js +++ b/src/genesys/agentApp/public/js/WatsonAssistantAgentAppWidgetProxy.js @@ -151,7 +151,7 @@ async function initializeApplication() { if (sessionHistoryKey) { window.location.href = `https://web-chat.global.assistant.watson.cloud.ibm.com/loadAgentAppFrame.html?session_history_key=${sessionHistoryKey}`; } else { - console.error('Could not load Watson Assistant Agent App, session history key is missing'); + console.error('Could not load IBM watsonx Assistant Agent App, session history key is missing'); } } diff --git a/src/genesys/webChat/README.md b/src/genesys/webChat/README.md index 91af9c5..cc1163d 100644 --- a/src/genesys/webChat/README.md +++ b/src/genesys/webChat/README.md @@ -1,6 +1,6 @@ # Genesys Cloud Integration Usage Example -This is a functioning service desk integration between Watson Assistant and Genesys Cloud. +This is a functioning service desk integration between watsonx Assistant and Genesys Cloud. **Note:** This integration relies on a 3rd party library that is downloaded at runtime by the user's browser. IBM is not responsible for the behavior or maintenance of this library. @@ -23,7 +23,7 @@ The Genesys Cloud integration consists of two main components: client-side code ![Genesys Architecture Overview](./server/architecture/arch-overview.png) -The client-side component manages the communication between the user and the agent. It implements the service desk API that is fully supported by the Watson Assistant web chat integration. (For more information about this API, see [ServiceDesk API](https://github.com/watson-developer-cloud/assistant-web-chat-service-desk-starter/blob/main/docs/API.md)). The middleware server is responsible for generating authentication tokens based on the Genesys Cloud organization credentials. The tokens are used to authenticate the client-side Web Chat Genesys service desk implementation when making API calls to the Genesys Chat APIs. +The client-side component manages the communication between the user and the agent. It implements the service desk API that is fully supported by the watsonx Assistant web chat integration. (For more information about this API, see [ServiceDesk API](https://github.com/watson-developer-cloud/assistant-web-chat-service-desk-starter/blob/main/docs/API.md)). The middleware server is responsible for generating authentication tokens based on the Genesys Cloud organization credentials. The tokens are used to authenticate the client-side Web Chat Genesys service desk implementation when making API calls to the Genesys Chat APIs. The communication uses the Genesys guest chat SDK, which can be found at [Guest Chat Client - JavaScript](https://developer.mypurecloud.com/api/rest/client-libraries/javascript-guest/index.html). This SDK is based on WebSocket, which enables two-way communication. For some advanced functions, the integration also uses the Genesys [REST API](https://developer.mypurecloud.com.au/api/rest/v2/). diff --git a/src/genesys/webChat/client/src/stockMessages.ts b/src/genesys/webChat/client/src/stockMessages.ts index cf6fc0b..5df793f 100644 --- a/src/genesys/webChat/client/src/stockMessages.ts +++ b/src/genesys/webChat/client/src/stockMessages.ts @@ -22,7 +22,7 @@ interface TEMPLATES { } export const messages: TEMPLATES = { - PREFIX_MESSAGE_TO_AGENT: 'This customer needs assistance, below is a summary of the requested need.', // 'In the Watson Assistant widget to the right you can review the entire conversation', + PREFIX_MESSAGE_TO_AGENT: 'This customer needs assistance, below is a summary of the requested need.', // 'In the watsonx Assistant widget to the right you can review the entire conversation', SUMMARY: (topic: any) => `Summary: ${topic !== undefined ? topic : messages.MISSING_TOPIC}`, POSTFIX_MESSAGE_TO_AGENT: 'To respond directly to the customer address them here.', MESSAGE_TO_USER: `Live agent support
I'll notify you when an agent answers your request. Response times vary based on availability.`, diff --git a/src/incontact/webChat/README.md b/src/incontact/webChat/README.md index 9aca607..d8b414f 100644 --- a/src/incontact/webChat/README.md +++ b/src/incontact/webChat/README.md @@ -1,6 +1,6 @@ # NICE inContact Integration Example -This is a functioning service desk integration between Watson Assistant and NICE inContact. +This is a functioning service desk integration between watsonx Assistant and NICE inContact. **Important:** This is a reference implementation that provides an example of a fully functional integration. Make any necessary changes and perform robust testing before deploying this integration in production. @@ -16,7 +16,7 @@ Note: This implementation only supports UserHub accounts, and has not been teste The NICE inContact integration consists of two main components: client-side code that runs in the user's browser, and server-side code that you host. -The client-side component manages the communication between the user and the agent. It implements the service desk API that is fully supported by the Watson Assistant web chat integration. (For more information about this API, see [ServiceDesk API](https://github.com/watson-developer-cloud/assistant-web-chat-service-desk-starter/blob/main/docs/API.md)). +The client-side component manages the communication between the user and the agent. It implements the service desk API that is fully supported by the watsonx Assistant web chat integration. (For more information about this API, see [ServiceDesk API](https://github.com/watson-developer-cloud/assistant-web-chat-service-desk-starter/blob/main/docs/API.md)). The communication uses the Patron API, which can be found at [Patron APIs](https://developer.niceincontact.com/API/PatronAPI). diff --git a/src/kustomer/webChat/README.md b/src/kustomer/webChat/README.md index 868e569..c630420 100644 --- a/src/kustomer/webChat/README.md +++ b/src/kustomer/webChat/README.md @@ -1,6 +1,6 @@ # Kustomer Integration Example -This is a functioning service desk integration between Watson Assistant and Kustomer. +This is a functioning service desk integration between watsonx Assistant and Kustomer. **Important:** This is a reference implementation that provides an example of a fully functional integration. Make any necessary changes and perform robust testing before deploying this integration in production. @@ -30,12 +30,12 @@ The following Kustomer resources provide some useful guides on Kustomer custom c where `{api_key}` is the API key you generated in the previous step. 1. In the Kustomer UI, create a new attribute on the Conversation klass with the following values: - - **Display Name**: `Watson Assistant Session History` + - **Display Name**: `watsonx Assistant Session History` - **Type**: **Single line text** 1. Within the Conversation klass, go to the **Insight Cards** tab. -1. Click **Create Insight Card** and create an Insight Card with the name `Watson Assistant Chat History`. Set the view location to **Insight Panel Card**. +1. Click **Create Insight Card** and create an Insight Card with the name `watsonx Assistant Chat History`. Set the view location to **Insight Panel Card**. 1. Click **View Code** and then click **Convert to Code**. When asked to confirm, type `CONVERT` and then click **I understand, please convert**. Copy and paste the following code: diff --git a/src/kustomer/webChat/client/src/kustomerServiceDesk.ts b/src/kustomer/webChat/client/src/kustomerServiceDesk.ts index 9d959d9..8f7424e 100644 --- a/src/kustomer/webChat/client/src/kustomerServiceDesk.ts +++ b/src/kustomer/webChat/client/src/kustomerServiceDesk.ts @@ -41,12 +41,12 @@ import { * Default message that is sent to the agent when the conversation is escalated to the agent. */ const WATSON_TRANSFER_MESSAGE = - 'Watson Assistant has transferred a chat. Please look at the chat history to get the full context of the conversation.'; + 'watsonx Assistant has transferred a chat. Please look at the chat history to get the full context of the conversation.'; /** * Default name for the conversation title that is created in Kustomer */ -const CONVERSATION_TITLE = 'Watson Assistant Chat'; +const CONVERSATION_TITLE = 'watsonx Assistant Chat'; class KustomerServiceDesk implements ServiceDesk { agentProfile: AgentProfile; diff --git a/src/oracle/webChat/README.md b/src/oracle/webChat/README.md index fb2f970..567852f 100644 --- a/src/oracle/webChat/README.md +++ b/src/oracle/webChat/README.md @@ -1,6 +1,6 @@ # Oracle Cloud B2C Service Integration Example -This is a functioning service desk integration between Watson Assistant and Oracle Cloud's [B2C Service](https://docs.oracle.com/en/cloud/saas/b2c-service/21b/index.html) (previously Oracle Service Cloud). +This is a functioning service desk integration between watsonx Assistant and Oracle Cloud's [B2C Service](https://docs.oracle.com/en/cloud/saas/b2c-service/21b/index.html) (previously Oracle Service Cloud). **Important:** This is a reference implementation that provides an example of a fully functional integration. Make any necessary changes and perform robust testing before deploying this integration in production. @@ -14,7 +14,7 @@ You can refer to these Oracle docs and resources for more information about usin The Oracle B2C Service integration consists of two main components: client-side code that runs in the user's browser, and server-side code that you host. -The client-side component manages the communication between the user and the agent. It implements the service desk API that is fully supported by the Watson Assistant web chat integration. (For more information about this API, see [ServiceDesk API](https://github.com/watson-developer-cloud/assistant-web-chat-service-desk-starter/blob/main/docs/API.md)). +The client-side component manages the communication between the user and the agent. It implements the service desk API that is fully supported by the watsonx Assistant web chat integration. (For more information about this API, see [ServiceDesk API](https://github.com/watson-developer-cloud/assistant-web-chat-service-desk-starter/blob/main/docs/API.md)). The communication uses the B2C Service, where details can be found at [B2C Service APIs](https://docs.oracle.com/en/cloud/saas/b2c-service/21b/cxscc/rest-endpoints.html). @@ -52,7 +52,7 @@ You should now be able to start a web chat session in a browser, and within the - **Agent transfers:** This example implementation does not implement support for agent transfer. -- **Conversation topic:** The example implementation sends the conversation transcript between the user and the bot as the first message to the agent when the conversation starts, and the user will first receive the greeting message set within your Oracle B2C center. Note that several other attributes are available within the `connectMessage` object that is passed to the `startChat()` function. For more information, see the documentation for the `topic` property of the `connect_to_agent` response type in the Watson Assistant [API reference](https://cloud.ibm.com/apidocs/assistant/assistant-v2#message). +- **Conversation topic:** The example implementation sends the conversation transcript between the user and the bot as the first message to the agent when the conversation starts, and the user will first receive the greeting message set within your Oracle B2C center. Note that several other attributes are available within the `connectMessage` object that is passed to the `startChat()` function. For more information, see the documentation for the `topic` property of the `connect_to_agent` response type in the watsonx Assistant [API reference](https://cloud.ibm.com/apidocs/assistant/assistant-v2#message). - **Typing indicator:** Support for both agent typing and user typing are implemented in this example code. However, the user typing indicator fails to render in Oracle's chat window, likely due to some API bug. This needs further investigation.