This example adds End Chat capability into the customer-facing Twilio Flex Webchat UI. It includes code for Twilio Functions (found in the serverless directory) as well as frontend UI code built atop Twilio's Flex Webchat UI Sample (found in the flex-webchat-ui directory).

clicking the X closes the window, which ends the chat

The goal here is to create a React Component in flex-webchat-ui that is capable of ending its own chat channel. In order to accomplish this, that component is going to hit a Twilio Function, endChat, with the Chat Channel SID.

However: The endChat Function must also complete the Flex/TaskRouter Task, so it will need its SID. Since there's no easy way to look that up, we start off by populating the taskSid into our Chat Channel's attributes via Studio and the populateChatChannelWithTaskSid Twilio Function. Here's how that looks in order of time:

1. Customer types a message, which kicks off the Studio flow
2. Studio enqueues a new Task into TaskRouter
3. Once the Task is created, Studio runs the populateChatChannelWithTaskSid Function
4. populateChatChannelWithTaskSid adds the taskSid into the chat channel's attributes
5. When the customer closes their chat window, the new React Component calls the endChat Twilio Function
6. endChat sets the Chat Channel to "INACTIVE" and completes the Task

Before beginning with this Flex plugin, you'll want to make sure that:

• You have a working Twilio Flex account
• You have Node.js as well as npm installed
  • npm generally gets installed along with Node.js, but make sure you have it anyway
• You have the latest Twilio CLI installed
• Your Twilio CLI is running the latest Serverless Plugin

Over the course of the configuration process, you'll need several values from your Twilio account. The first five can be found right now in the Twilio Console and Flex Admin pages, but the last one will require you to deploy your Twilio Functions to find (Don't worry, we'll cover that!)

• Account SID
  • Found on the Twilio Console Homepage
  • String starting with "AC..."
• Auth Token
  • Found on the Twilio Console Homepage
  • Secure string of 32 characters that we'll call "blah..." for the sake of communication
• Twilio Workspace SID
  • Found in your TaskRouter Dashboard
  • String starting with "WS..."
• Flex Chat Service Sid
  • Found in your Programmable Chat Dashboard
  • String starting with "IS..."
• Flex Flow Sid
  • Found on the Flex Admin Developer Setup page
  • String starting with "FO..."
• Serverless Runtime Domain
  • We'll grab this after we've deployed our Twilio Functions
  • A web domain that looks something like "foobar-xxx-dev.twilio.io"

We'll be entering these values into two files, neither of which exist yet:

• serverless/.env
• flex-webchat-ui/public/assets/webchat-appConfig.js

To kick things off, rename the example serverless environment file to remove .example, then open it in your editor of choice:

mv serverless/.env.example serverless/.env

vim serverless/.env

You'll notice that this file has temporary string variables for your Account Sid, Auth Token, Twilio Workspace SID, and Flex Chat Service SID. Replace these strings with your actual value.

# Before
ACCOUNT_SID=accountSid
AUTH_TOKEN=authToken
TWILIO_WORKSPACE_SID=workspaceSid

# After
ACCOUNT_SID=AC...
AUTH_TOKEN=blah...
TWILIO_WORKSPACE_SID=WS...
FLEX_CHAT_SERVICE_SID=IS...

Before we can configure the next file, we'll need to deploy our Twilio Functions and grab the Runtime Domain. To do so, we'll be using the Twilio CLI and the Serverless Plugin that you installed as a prerequisiste.

First off, make sure that you have authenticated according to the Twilio CLI documentation.

Then cd into the Functions directory and deploy them:

cd serverless
twilio serverless:deploy

Once everything gets deployed, your response should look something like this:

Deployment Details
Domain: foobar-xxx-dev.twilio.io
Service:
   plugin-supervisor-capacity-functions (ZS...)
Environment:
   dev (ZE...)
Build SID:
   ZB...
View Live Logs:
   Open the Twilio Console
Functions:
   https://foobar-xxx-dev.twilio.io/endChat
   https://foobar-xxx-dev.twilio.io/populateChatChannelWithTaskSid
Assets:

The value we're looking for comes after Domain: – that's your Runtime Domain.

Now we'll populate the UI configuration variables. Start by renaming the example app configuration file to remove .example, then open it in your editor of choice

mv flex-webchat-ui/public/assets/webchat-appConfig.example.js flex-webchat-ui/public/assets/webchat-appConfig.js

vim flex-webchat-ui/public/assets/webchat-appConfig.js

Just like before, this new file contains temporary strings that you simply have to replace with the actual values:

var appConfig = {
    // change to your AccountSid
    accountSid: "AC...",
    // change to your Flex Flow SID
    flexFlowSid: "FO...",
    // change to your runtimeDomain
    runtimeDomain: "http...",
    colorTheme: {
        overrides: brandedColors
    }
}

And now the example is fully configured! Now we have one more step: Setting up Studio to use the populateChatChannelWithTaskSid Function we deployed earlier.

This is the crucial step: After the chat has been enqueued into TaskRouter/Flex as a new Task, we have to populate our Chat Channel Attributes with the Task SID. To do this:

1. Open Studio in your Twilio Console
2. Edit the default Webchat Flow that was automatically created when you installed Flex
3. Drag a new "Run Function" widget onto your flow, below the "SendMessageToFlex" widget
4. Drag a line from the "SendMessageToFlex" widget's "Task Created" node to the input of your new Run Function widget
5. Configure your Run Function widget:
   • Name it something recognizable like "populateChatChannel"
   • Select the Functions service, by default "customer-end-chat-functions"
   • Select your dev environment
   • Select the populateChatChannelWithTaskSid Function
   • Add two Function Parameters:
     • key: taskSid
       • value: {{widgets.SendMessageToAgent.sid}}
     • key: channelSid
       • value: {{trigger.message.ChannelSid}}
6. Save the Run Function widget
7. Publish your changes

The end result should look something like this:

With this studio customization in-place, the entire example should be set up! You can now run it locally to test and customize it.

In order to develop locally, you can use the Webpack Dev Server by running:

cd flex-webchat-ui
npm install
npm start

This will automatically start up the Webpack Dev Server and open the browser for you. Your app will run on http://localhost:8081. If you want to change that you can do this by setting the PORT environment variable:

PORT=3000 npm start

When you make changes to your code, the browser window will be automatically refreshed.

This software is to be considered "sample code", a Type B Deliverable, and is delivered "as-is" to the user. Twilio bears no responsibility to support the use or implementation of this software.