Understanding connected actions
A connection, controlled actions
Section titled “A connection, controlled actions”A connector connects ELChat to a tool you already use. Depending on the tool, ELChat can then read information, search for an item or perform an action you have authorized.
You do not need to know the technical operation of the connection to manage it.
What a connector does
Section titled “What a connector does”A connector can give ELChat the ability to:
- consult information;
- search for an element;
- create or modify a data;
- trigger an action in an external service.
Available tools depend on the ELChat implementation of the connector, external account permissions and your configuration.
Three levels of authorisation
Section titled “Three levels of authorisation”For each action, ELChat can apply a mode:
| Mode | Behaviour |
|---|---|
| Automatic | The action can be executed without further validation when other conditions are met |
| Confirmation | The action awaits the agreement of the defined actor before its execution |
| Refusal | Action is not permitted |
The rules can distinguish between the administrator and the visitor.
Example
With a calendar connector:
- check availability may be automatic;
- creating an appointment can request confirmation;
- delete an event may be refused.
This example illustrates a possible policy. The really visible tools and their modes depend on your connector and settings.
Why governance is important
Section titled “Why governance is important”It makes it possible to adapt automation to the risk:
- simple reading to save time;
- validation for an engaging action;
- blocking for unwanted action.
Identifiers and security
Section titled “Identifiers and security”Depending on the service, the connection uses an authorization window or identifiers provided by the platform. Never share keys, secrets or chips in a message, capture or knowledge base.