diff --git a/README.md b/README.md
index 6d6ef16d..f5bcf541 100644
--- a/README.md
+++ b/README.md
@@ -8,11 +8,11 @@ A simple web page that allows users to communicate with the [Azure Health Bot](h
1.Deploy the website:
-[](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2Fmicrosoft%2FHealthBotContainerSample%2Fmaster%2Fazuredeploy.json)
+[](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2Fmicrosoft%2FHealthBotContainerSample%2Flive_agent_handoff%2Fazuredeploy.json)
2.Set the following environment variables:
-`APP_SECRET`
+`AUTH_JWT_SECRET`
`WEBCHAT_SECRET`
@@ -51,5 +51,19 @@ Pass your preferred geographic endpoint URI by setting the environment variable:
**Note:** If you are deploying the code sample using the "Deploy to Azure" option, you should add the above secrets to the application settings for your App Service.
-## Agent webchat
-If the agent webchat sample is also required, [switch to the live agent handoff branch](https://github.com/Microsoft/HealthBotContainerSample/tree/live_agent_handoff)
+## Live agent handoff sample
+
+The live agent handoff sample is wrapper around the standard webchat that is generally used by end users. This sample is intended for testing the handoff scenario that is built-in to your Health Bot instance.
+
+To access the sample you should follow the deployment instructions and request the `/agent.html` path from your browser. This will load a dummy login page that illustrates the agent experience (you can provide any values to access the agent portal). Within the agent portal you can issue agent commands to interact with end users that are talking with your bot.
+
+The wrapper adds to the server.js file an agent flagging function: `function isAgentAuthenticated(req)` which will serve the agent webchat if a `true` value is returned. You should implement custom logic in this function that returns a `true` value once your agent has been authenticated.
+
+**IMPORTANT:**
+The sample login page is for testing and demonstration purposes only. You MUST authenticate agent access in a production deployment of the agent webchat. The agent webchat provides access to sensitive end user information.
+
+## Customizing the webchat
+
+You can send programmed messages to the agent webchat by invoking the `function talk(message)`. In the sample we have added example buttons with issue some of the built-in agent commands.
+
+[Learn more about agent webchat functionality](https://docs.microsoft.com/en-us/HealthBot/handoff)
diff --git a/azuredeploy.json b/azuredeploy.json
index 38b2c5c5..3fa7836d 100644
--- a/azuredeploy.json
+++ b/azuredeploy.json
@@ -47,10 +47,10 @@
"description": "Location for all resources."
}
},
- "appSecret": {
+ "authJwtSecret": {
"type": "securestring",
"metadata":{
- "description": "Healthbot application secret."
+ "description": "Healthbot end user authentication JWT secret."
}
},
"webchatSecret": {
@@ -68,7 +68,7 @@
},
"branch": {
"type": "string",
- "defaultValue": "master",
+ "defaultValue": "live_agent_handoff",
"metadata": {
"description": "The branch of the GitHub repository to use."
}
@@ -109,8 +109,8 @@
"alwaysOn": "[variables('alwaysOn')]",
"appSettings": [
{
- "name": "APP_SECRET",
- "value": "[parameters('appSecret')]"
+ "name": "AUTH_JWT_SECRET",
+ "value": "[parameters('authJwtSecret')]"
},
{
"name": "WEBCHAT_SECRET",
@@ -170,8 +170,8 @@
"siteConfig": {
"appSettings": [
{
- "name": "APP_SECRET",
- "value": "[parameters('appSecret')]"
+ "name": "AUTH_JWT_SECRET",
+ "value": "[parameters('authJwtSecret')]"
},
{
"name": "WEBCHAT_SECRET",
diff --git a/public/agent.html b/public/agent.html
new file mode 100644
index 00000000..eac639b4
--- /dev/null
+++ b/public/agent.html
@@ -0,0 +1,48 @@
+
+
+
+