Initial concepts
So, what we can do with the Platform?
How do I know if my company needs a chatbot?
Register and login
First Steps - Creating your project
Choose your plan
Profile
Permission System
Project Dashboard
Platform Glossary
Changing the Platform Language
2-Factor Authentication
Invalid authentication code
General settings
Artificial Intelligence
Agent Builder
Zero Shot Learning
WeniGPT
Weni Platform AI Module
Repository - Overview
What is an Intelligence?
Intents and Entities
Hands-on
Creating an Intelligence
Training your Intelligence
Strength of Intelligence
Testing your intelligence
Interactions
Translating your dataset
Versioning
Settings
API
Integrate an intelligence to your project in the Weni Platform
Introduction to Content Intelligence
Integrating a Content Intelligence
Interface Updates
Glossary
Guidance and Best Practices
Flows
Expressions and Variables Introduction
Variables Glossary
Expressions Glossary
Flows Creation
Flows introduction
Flow editor and tools
Action cards
Decision cards
Adding Media to the message
Call Webhook: Making requests to external services
Split by Intent: Using Classification Artificial Intelligence
Import and export flows
Using expressions to capture the user's location
Viewing reports on the platform
Route markers
Studio
Contacts and Messages
Groups
Messages
Triggers and Campaigns
Adding a trigger
Triggers Types
Tell a flow to ignore triggers and keywords
Campaign introduction
How to create a Campaign
Editing events
Creating contact from an external Webhook
Contact history
How to download, extract, transform and combine archived data from Weni Flows
Channels
Settings
Channels Introduction
Adding a Facebook Channel (RapidPro)
Adding a Viber channel
How a SMS Integration Works
WebSocket Connection
General API concepts and Integrations
How to create a channel on twitter
How to create a channel on Instagram
Main steps to active Whatsapp for UNICEF
Adding Discord as a channel
Creating a Slack Channel
Adding a Viber channel (RapidPro)
Creating a Microsoft Teams channel
Weni Integrations
How to use the integrations module
Adding a Web channel
Adding a Telegram channel
How to create a channel with whatsApp demo
Whatsapp: Weni Express Integration
How to create template Messages: Whatsapp
Creating a Microsoft Teams Channel
Whatsapp Business API
Integrations
Human Attendance
Weni Chats: Introduction to the Chats module
Weni Chats: Setting Up Human Attendance
Weni Chats: Human Service Dashboard
Weni Chats: Human Service Management
Weni Chats: Attendance distribution rule
Weni Chats: Using active triggering of flows
Weni Chats: CoPilot
Ticketer: Ticketer on Rapid Pro
Ticketer: How to integrate Rocket.Chat as a ticket service on the Weni Plataform
How to send message templates through RocketChat
RocketChat call routing
RCAdmin API: Agent-Activity
U-Partners - Proper use of features
Using groups to organize human attendance
Data and BI
How to Install and Use the Weni Data Connector for Power BI
Incremental Update - Power BI
Explore Weni's Database Documentation
Tips for Data Modeling in Power BI
Filter using Contact Fields in Power BI
UX Writing
- All Categories
- Human Attendance
- Using groups to organize human attendance
Using groups to organize human attendance
Updated by Manu da Silva
The use of groups to organize contacts that are in human attendance is essential.
Adding contacts to the control group
In this article we will refer to the control group as Human Attendance.
You must add the contact to this group in the stream that you open a ticket, as shown earlier.
It is important to mention that if you open tickets in different streams, you need to do this in all flows.
Ignoring control group participants on triggers
Just adding to this group is not enough, but just the basis you need to know which contacts need to be ignored in automatic messages while they are in attendance.
To do this, you must add this group to the list of skipped groups for each of the triggers configured in your project, as exemplified in the image below.
With this configured, the chatbot will not interrupt human service and the functionality will run as expected.
Removing contacts from the control group
It is important to remember to remove contact from this group when the human service session is complete. For this, there is a specific trigger
type: 'start a flow when a ticket is closed':
This can be an extremely simple flow, where the only action is to remove the contact from the Human attendance
control group:
How do I send custom fields?
The custom fields to be sent must be defined in the body of the Ticket card, in the json format, with each field as the custom_fields
attribute, represented by its key and value.
note: the value of each field may or may not be between ""
.
Next, look at an example, showing the configuration of custom fields, where the origin
field with its value set to the source result
, between ""
because it is of the string type