Breadcrumbs

Customer Widget Admin Guide

Expertflow develops a Customer Widget under Expertflow CX as a sample implementation of the web channel.

Customization of Customer Widget

Customers can start the chat using the Customer Widget, which businesses can customize to meet their specific requirements.

Create a Customer Widget in the Unified Admin

The Business administrators can create customized Customer Widgets and that customization can be fetched in Customer Widget applications using a unique Widget Identifier eg: “Web“. It can be created in the Unified AdminCustomer Widget component as per business requirements.

This identifier is case-sensitive.
To check details on the types of configurations that can be applied to the widget, click here.

Other Configurations

The following configurations can be created in the unified-admin => web widget component as per their requirements:

Widget Identifier

image-20231206-052931.png%3Fversion=1%26modificationDate=1701840577513%26cacheVersion=1%26api=v2%26width=482%26height=79?version=2&modificationDate=1767601786592&cacheVersion=1&api=v2&width=300&height=49

Widget Title

image-20231206-052814.png%3Fversion=1%26modificationDate=1701840502084%26cacheVersion=1%26api=v2%26width=482%26height=77?version=2&modificationDate=1767601786657&cacheVersion=1&api=v2&width=300&height=48

Widget Subtitle

image-20231206-053141.png%3Fversion=1%26modificationDate=1701840706832%26cacheVersion=1%26api=v2%26width=482%26height=77?version=2&modificationDate=1767601786686&cacheVersion=1&api=v2&width=300&height=48

Pre Chat Form

image-20231206-053356.png%3Fversion=1%26modificationDate=1701840841978%26cacheVersion=1%26api=v2%26width=482%26height=72?version=2&modificationDate=1767601786718&cacheVersion=1&api=v2&width=300&height=45

Dynamic Form coming from Unified-admin’s form component.

Language

image-20231206-053955.png%3Fversion=1%26modificationDate=1701841201661%26cacheVersion=1%26api=v2%26width=482%26height=72?version=2&modificationDate=1767601786750&cacheVersion=1&api=v2&width=300&height=45

Theme Color

image-20231206-054721.png%3Fversion=1%26modificationDate=1701841648247%26cacheVersion=1%26api=v2%26width=482%26height=241?version=2&modificationDate=1767601786784&cacheVersion=1&api=v2&width=300&height=150

Enable Emoji

image-20231206-054851.png%3Fversion=1%26modificationDate=1701841738443%26cacheVersion=1%26api=v2%26width=138%26height=38?version=2&modificationDate=1767601786814&cacheVersion=1&api=v2&width=173&height=48

Enable File Transfer

image-20231206-060038.png%3Fversion=1%26modificationDate=1701842445020%26cacheVersion=1%26api=v2%26width=172%26height=37?version=2&modificationDate=1767601786844&cacheVersion=1&api=v2&width=215&height=47

Enable Font Resize

image-20231206-060239.png%3Fversion=1%26modificationDate=1701842565443%26cacheVersion=1%26api=v2%26width=170%26height=41?version=2&modificationDate=1767601786874&cacheVersion=1&api=v2&width=213&height=52

Enable Dynamic Link

image-20231206-055821.png%3Fversion=1%26modificationDate=1701842309551%26cacheVersion=1%26api=v2%26width=178%26height=37?version=2&modificationDate=1767601786905&cacheVersion=1&api=v2&width=222&height=47

Enable Download Chat Transcript

image-20231206-055700.png%3Fversion=1%26modificationDate=1701842227310%26cacheVersion=1%26api=v2%26width=218%26height=36?version=2&modificationDate=1767601786935&cacheVersion=1&api=v2&width=250&height=42

Enable Web-RTC

image-20231206-061211.png%3Fversion=1%26modificationDate=1701843138787%26cacheVersion=1%26api=v2%26width=482%26height=636?version=2&modificationDate=1767601786969&cacheVersion=1&api=v2&width=300&height=395

Note: Refer to the RTC Team for FS Configurations.

Enable Callback

image-20231206-061619.png%3Fversion=1%26modificationDate=1701843386768%26cacheVersion=1%26api=v2%26width=482%26height=344?version=2&modificationDate=1767601786998&cacheVersion=1&api=v2&width=300&height=214

Note: Currently, callback is only supported with Expertflow’s ECM.

Enable Webhook Notification

image-20231206-061910.png%3Fversion=1%26modificationDate=1701843556398%26cacheVersion=1%26api=v2%26width=482%26height=96?version=2&modificationDate=1767601787030&cacheVersion=1&api=v2&width=300&height=60


Dynamic custom fields in web widget configuration

Admins can now add and manage dynamic custom fields in each web widget, using an “add” button to define multiple field types that are stored in the widget’s object model and remain editable whenever that specific widget is updated. 

Custom Attributes.png

Once the custom attributes are added , the values of these custom attributes can be added while editing that particular widget.

Customer Identification in CX:

When identifying customers during the pre-conversation process, a specific field needs to be created in Unified Admin, and that is the Pre-conversation Form. The 'Phone' field serves as the Channel Customer Identifier. However, Business Administrators can customize this according to their business needs.

To set up the customer identifier in CX for Web Chat:

Ensure you have at least one required field in the pre-conversation form, such as 'Phone'

When creating the required field, input the label as 'Phone' in the Attribute Name. The system automatically generates an Attribute Key in lowercase, replacing spaces with underscores. For instance, the Attribute Key for 'Phone' will be 'phone,' and it is case-sensitive.

Use the auto-generated key of the chosen field as your customer identifier in the 'ef-cx-custom-values.yaml' file.

  • By default, the 'phone' key is defined in 'CHANNEL_IDENTIFIER' as the customer identifier in the 'helm-values/ef-cx-custom-values.yaml' file, but you can replace it with your preferred choice.

image-20250123-191408.png

Below is the Screenshot for understanding:

image-20250123-191741.png

Customer Name in Conversation View

To ensure personalized interactions in the unified agent conversation view, it is mandatory to create a 'Phone' field for customer identification. The key for this field should be 'phone', and it is case-sensitive.

  • While the 'Phone' is compulsory, other fields can be tailored based on business requirements.

  • For instance, the ’First Name' and ‘Last Name' fields, with the key 'first_name’ and 'last_name', are optional. If provided, the customer's name in the conversation view will display both the first name and last name, creating a more comprehensive and personalized engagement.

Example:

  • First Namefirst_name

  • Last Namelast_name

To see a pictorial representation for better understanding click here.

To learn more about the forms and it’s validation , please refer to this guide.
https://expertflow-docs.atlassian.net/wiki/x/HABiFw