Webitel: Documentation

Lookups (Creation and Configuration Manual)

1. Description

Lookups (Fig. 1) are structured system settings used to standardize and automate business processes for handling Cases.

They allow storing the configurations applied in Case processing workflows, defining categories, priorities, statuses, sources of Cases, and assigning responsibility for each Case.

Using lookups helps to avoid errors, speed up operator work, and ensure a unified approach to Case processing.

Creation, editing, and configuration of lookups are performed in the section: CRM → Configuration → Lookups.

Configuration.jpg
Fig. 1. "Lookups"

1.1. Contact Groups Lookup

The "Contact Groups" lookup (Fig. 2) contains the names of groups that a Contact can belong to. A Contact may belong to groups assigned during creation or editing. Certain Contact Groups may be accessible only to specific users. Contact Groups can be used as executor groups for Cases. A Contact may belong to one or multiple groups, or not belong to any.

Contact groups.jpg
Fig. 2. Lookup "Contact Groups"

To create a "Contact Groups" lookup (Fig. 2), follow these steps:

  1. Navigate to CRM Configuration Lookups Contact Groups.

  2. Click the Add icon image-20250408-114508.png , which will open the "Add Contacts" modal window (Fig. 3).

Add group.jpg
Fig. 3. Modal window "Add group”
  1. Select the group type: static or dynamic.

Important! When creating a contact group, you can select one of two types — static or dynamic.
When a Case is registered, the system checks its Service. If a dynamic group is selected for the Service, the condition will be verified, and the corresponding values will be set for the "Group" or "Assignee" fields: a static target group (Group) and/or a target contact (Assignee).

1.1.1. Static Group

If a static group is selected:

Static.jpg
Fig. 4. "General" tab of the static group creation page
  1. In the "General" tab (Fig. 4), fill in the fields:

  • Name — required, editable. The user-defined name of the group.

  • Description — optional, editable.

  • State — required, editable. Enabled by default image-20250408-102532.png . The group can be active or inactive, and can or cannot be assigned to a Case (the "Assignee Group" field) or a dynamic group. Only active groups can be used for selection.

  1. Click the Save button.

After saving the "General" details (Fig. 4), the Permissions section becomes available (Fig. 5).

Permissions.jpg
Fig. 5. "Permissions" tab

To add a user to the group and assign permissions:

  1. Navigate to the Permissions tab (Fig. 5).

  2. Click the Add icon image-20250408-114508.png , to open the "New Grantee" modal window (Fig. 6).

  3. In the modal window, select a Role.

  4. Click one of the buttons:

    • Add — adds a new grantee; the user remains on the "Permissions" tab.

    • Close or the close icon image-20250408-105909.png closes the window without saving changes; the user returns to the "Permissions" tab.

Modal window - New grantee.jpg
Fig. 6. "New Grantee" modal window

1.1.2. Dynamic Group

If a dynamic group is selected:

Dynamic group.jpg
Fig. 7. "General" tab of the dynamic group creation page
  1. In the General tab (Fig. 7), fill in the following fields:

  • Name — required, editable.

  • Description — optional, editable.

  • State — required, editable. Enabled by default image-20250408-102532.png . The group can be active or inactive and can or cannot be assigned to a Case (the "Assignee Group" field). Only active groups can be selected.

  • Default Group — required, editable. Only a Contact Group of type Static can be selected.

  1. Click the Save button.

After saving the "General" details (Fig. 7), the “Conditions” and “Permissions” sections become available.

To add a new Condition:

  1. Navigate to the Conditions tab (Fig. 8).

Conditions - dynamic group.jpg
Fig. 8. "Conditions" tab
  1. Click the Add button or the icon image-20250408-112929.png . This opens the "Add Condition" modal window (Fig. 9).

Add condition.jpg
Fig. 9. "Add Condition" modal window
  1. In the Add Condition modal window (Fig. 9), fill in:

  • Condition — required, editable field.

  • Contact Group — required field. Select a static group from the "Contact Groups" directory. Only static groups can be selected in this field.

  • Assignee — optional field. Select a Contact from the members of the selected static Contact Group.

  1. Click the Save button.

Conditions_table.jpg
Fig. 10. Conditions tab view when records exist

Important: When the user drags and drops conditions by holding the icon (Fig. 10), the record changes its position in the table. Conditions are unique across all three fields.

Conditions are evaluated top to bottom in the list.

To add a user to the group and assign Permissions:

  1. Navigate to the Permissions tab (Fig. 11).

Permitions_dynamic group.jpg
Fig. 11. "Permissions" tab
  1. Click the Add icon" image-20250408-114508.png , to open the New Grantee modal window (Fig. 12).

  2. In the New Grantee modal window, select a Role.

  3. Click one of the buttons:

    • Add — adds the new grantee.

    • Close or the close icon image-20250408-105909.png closes the window without saving changes.

New grantee - dynamic.jpg
Fig. 12. "New Grantee" modal window

1.2. Priorities Lookup

The Priorities Lookup (Fig. 13) contains the list of priorities that can be assigned to a Case.

Priorities.jpg
Fig. 13. “Priorities” Lookup

To populate the "Priorities" lookup:

  1. Navigate to CRM → Configuration → Lookups → Priorities.

  2. On the priorities list page (Fig. 13), click the Add icon image-20250408-115646.png . The system will open the new record creation page (Fig. 14).

New_Priorities.jpg
Fig. 14. “General” tab of the new lookup creation page
  1. In the General tab (Fig. 14), fill in the following fields:

  • Name — required, editable.

  • Description — optional, editable.

  • Color — required, editable.

  1. Click the Save button.

1.3. Closure Reasons Lookup

The Closure Reasons Lookup contains the list of reasons used to close a Case when it is moved to the final status. Multiple closure reasons lookups can be created in the system for different use cases.

Closure reasons.jpg
Fig. 15. “Closure Reasons” Lookup

To create a new "Closure Reasons" lookup:

  1. Navigate to CRM → Configuration → Lookups → Closure Reasons.

  2. Click the Add icon image-20250408-115646.png , to open the new lookup creation page (Fig. 16).

Closure reason_New.jpg
Fig. 16. “General” tab of the new lookup creation page
  1. In the General tab (Fig. 16), fill in the following fields:

    • Name — required, editable.

    • Description — optional, editable.

  2. Click the Save button.

Once the "General" section (Fig. 16) is saved, the Reasons section (Fig. 17) becomes available.

After creating the "Closure Reasons" lookup, you can populate it with specific reasons that will be available when closing Cases:

  1. Go to the Reasons tab (Fig. 17).

Reasons.jpg
Fig. 17. “Reasons” tab
  1. Click the Add button or icon image-20250408-112929.png . The Add Reason modal window will open (Fig. 18).

Add reason.jpg
Fig. 18. “Add Reason” modal window
  1. In the modal window, fill in the following fields:

    • Name — required, editable.

    • Description — optional, editable.

  2. Click the Save button.

1.4. Statuses Lookup

The Statuses Lookup (Fig. 19) contains the list of statuses (processing stages) that a Case can have. Multiple status lookups can be created in the system for different use cases.

Statuses.jpg
Fig. 19. "Statuses" Lookup

To create a new lookup:

  1. Go to CRM → Configuration → Lookups → Statuses (Fig. 19).

  2. Click the Add icon image-20250408-115646.png , to open the new lookup creation page (Fig. 20).

General_Statuses.jpg
Fig. 20. "General" tab of the new lookup creation page
  1. In the General tab (Fig. 20), fill in the following fields:

    • Name — required, editable.

    • Description — optional, editable.

  2. Click the Save button.

After saving the "General" section (Fig. 20), the Statuses section becomes available (Fig. 21).

To add a new status:

  1. Go to the Statuses tab (Fig. 21).

Statuses_New.jpg
Fig. 21. "Statuses" tab
  1. Click the Add button or icon image-20250408-112929.png . The Add Status modal window will open (Fig. 22) with the following fields

  • Name — required, editable.

  • Description — optional, editable.

Add status.jpg
Fig. 22. "Add Status" modal window
  1. Click the Save button.

Mandatory conditions in the system:

  • There must be only ONE initial status.

  • There must be AT LEAST one final status.

  • The first status is created by default as both initial and final.

  • The second and all subsequent statuses are created as regular (neither initial nor final). They can be manually marked as initial or final if needed.

Statuses_status.jpg
Fig. 23. Statuses displayed on the "Statuses" tab

Important! The system must have only ONE active Initial status → only one “Initial” toggle can be enabled at a time.

  • If the user enables the “Initial” toggle on a second status, the previous one will be automatically disabled.

  • If the user disables the only “Initial” status, a warning modal window will open (Fig. 24).

Important! The system must have AT LEAST one Final status → at least one “Final” toggle must be enabled.

  • If the user disables the last “Final” status, a warning modal window will also open (Fig. 24).

Status type.jpg
Fig. 24. "Status Type" modal window

1.5. Case Sources Lookup

The Case Sources Lookup (Fig. 25) contains the list of sources from which a Case can be created. This lookup is used by the system or user when filling in the Source field in the Case.

Case sources.jpg
Fig. 25. Case Sources Lookup

To populate the Case Source:

  1. Go to CRM → Configuration → Lookups → Case Sources.

  2. Click the Add icon image-20250408-115646.png , to open the new lookup creation page (Fig. 26).

Case Sources_General.jpg
Fig. 26. "General" tab of the new lookup creation page
  1. In the General tab (Fig. 26), fill in the following fields:

  • Name — required, editable field.

  • Type — required field selected from the list:

    • Call;

    • Chat;

    • Social Network;

    • Email;

    • API;

    • Created manually.

  • Description — optional, editable field.

  1. Click the Save button.

1.6. SLAs Lookup

The SLAs Lookup (Fig. 27) is used to configure rules for calculating the planned response and resolution times for a Case depending on its type or Contact.

SLAs.jpg
Fig. 27. "SLAs" Lookup

A single SLA can be extended with Conditions, specifically Priorities.

When adding a Condition to an SLA, the user selects priorities from the list created in the "Priorities" lookup and enters the response and resolution times for each. This allows configuring different response and resolution times depending on the priority assigned to the Case.

If the Case is classified under a specific Service and has a priority specified in the SLA Condition for that Service, this SLA will be applied to calculate the planned response and resolution times.

If there are no Conditions, the general SLA for the Service is applied. The "SLA" lookup is always linked to a catalog level in the "Service Catalogs" lookup and can also be linked to any lower service level.

When calculating SLA for a Case, the system always applies the SLA from the lowest level of classification for that Case.

To create a new "SLAs" lookup:

  1. Navigate to CRM → Configuration → Lookups → SLAs (Fig. 27).

  2. Click the Add icon image-20250408-142815.png to open the new lookup creation page (Fig. 28).

SLAs_New.jpg
Fig. 28. "General" tab of the new lookup creation page
  1. In the General tab (Fig. 28), fill in the following fields:

  • Name – required, editable.

  • Description – optional, editable.

  • Calendar – required, editable. Used to calculate the "Planned Resolution Time" and "Planned Response Time" fields. Selected from the list of previously created Calendars.

  • Planned Response Time (hh:mm) – required, editable. The number of hours and minutes within which a response must be provided (i.e., changing the status to anything other than the initial status). Always applied if no Conditions are met.

  • Planned Resolution Time (hh:mm) – required, editable. The number of hours and minutes within which the Case must be resolved (i.e., moved to a final status). Always applied if no Conditions are met.

  • Valid From/To – optional, editable. The effective period of the SLA, e.g., as specified in a client agreement.

  1. Click the Save button.

After saving the General details (Fig. 28), the Conditions section becomes available (Fig. 29).

To add a new Condition:

  1. Navigate to the Conditions tab (Fig. 29).

Conditions_SLAs.jpg
Fig. 29. "Conditions" tab
  1. Click the Add button or the icon image-20250408-112929.png . The "Add Condition" modal window opens (Fig. 30).

Add condition_SLAs.jpg
Fig. 30. "Add Condition" modal window
  1. In the window, fill in the following fields:

  • Name — required field.

  • Priority — required multi-select field from the "Priorities" lookup.

  • Planned Response Time (hh:mm) — the time that will be applied to Cases with the selected priorities.

  • Planned Resolution Time (hh:mm) — required field.

Important! The same priority cannot be used in multiple Conditions within the same SLA. The list will only display priorities that have not yet been used in any existing Conditions.

  1. Click the Save button.

1.7. Service Catalogs Lookup

The Service Catalogs Lookup (Fig. 31) is used to classify Cases through a multi-level structure. It allows you to configure Services (categories and subcategories) that can either be selected manually by the operator while processing a Case or assigned automatically by the system.

Before creating a Service Catalog, the following lookups must be configured, as they are used during catalog setup:

  • Statuses;

  • Closure Reasons;

  • SLAs.

The system allows you to create multiple Service Catalogs.

Service catalogs.jpg
Fig. 31. "Service Catalogs" Lookup

Cases are always linked to a Catalog. After selecting a Service, the system automatically pulls the corresponding Subservices available to te operator based on their Team or Skills.

  • If Teams are assigned, the Catalog Services will only be visible to operators who belong to these Teams.

  • If Skills are assigned, the Catalog Services will only be available to operators who have the corresponding Skills.

The lookup can support multiple levels of nesting. The two main levels are:

  • Catalog

  • Service

It is not possible to select only the Catalog in a Case. The Service must be selected from the lowest level of the hierarchy.

Location in the system: CRM → Configuration → Lookups → Service Catalogs.

To create a new Service Catalog: Click the Add icon image-20250408-142815.png to open the new record creation page (Fig. 32).

Service catalog_New.jpg
Fig. 32. "General" tab of the new lookup creation page

1.7.1. First Level: Catalog

On the new lookup creation page, in the General tab Name — required, editable.

  • Prefix — required, editable. The Case ID generated under this catalog will include this prefix.

  • SLA — required, editable. The SLA at the catalog level defines the resolution and response times if no SLA is selected at the lower Service level.

  • Code — optional, editable. Can be used for integrations or custom configurations.

  • Description — optional, editable.

  • Statuses — required, editable. Cases created under this catalog can only use statuses from this linked lookup.

  • Closure Reasons — required, editable. Closure reasons from this linked lookup will be available when closing Cases under this catalog.

  • Teams — optional, editable. If Teams are linked to the catalog, Services will only be available to operators who belong to these Teams.

  • Skills — optional, editable. If Skills are linked to the catalog, Services will only be visible to operators who have these specific Skills.

  • State — required, editable. Catalog State: enabled image-20250408-102532.png or disabled. image-20250408-151050.png . It determines whether Services from this Catalog can or cannot be assigned to a Case. The Catalog’s state has higher priority than the states of its lower levels.

Click Save to store the record.

Important! If both Teams and Skills are linked, Services will be available to operators who belong to either assigned Teams OR have the required Skills.

To create the second level (Services), click on the catalog name, for example, Technical support (Fig. 33).

Catalog name.jpg
Fig. 33. Catalog name

1.7.2. Second Level: Services

To create a Service, click the Add button or the icon image-20250408-142815.png , click the Add button or the icon to open the service creation page.

Second level.jpg
Fig. 34. Second level: Services

On the new lookup creation page, in the General tab (Fig. 35), fill in the following fields:

  • Name — required, editable.

  • SLA — required, editable. SLA can be set at each service level. By default, the Case will use the SLA of the selected Service. If no SLA is specified, the SLA from the higher level will apply.

  • Code — optional, editable.

  • Description — optional, editable.

  • Assignee — optional, editable. Since Webitel Contacts can also be Webitel Users, one Contact can be assigned to the Service. If a Dynamic Contact Group is assigned, the Assignee field will be disabled.

  • Assignee Group — optional, editable.

  • State — required, editable. Catalog State: enabled image-20250408-102532.png or disabled. image-20250408-151050.png . It determines whether Services from this Catalog can or cannot be assigned to a Case. The Catalog’s state has higher priority than the states of its lower levels.

Click Save to store the service record.

Subservice.jpg
Fig. 35. "General" tab of the new service creation page

To create the third or any lower level (Subservices), click the name of the previous level, for example, Authorization Issues (Fig. 36), and repeat the same steps as for Service creation.

Sub_service.jpg
Fig. 36. Third level: Subservices

2. Editing a Lookup

To edit a record at any level, click on its name or on the icon image-20250408-152754.png .

To save the changes, be sure to click the Save button.

3. Deleting a Lookup

To delete a lookup, click on the icon image-20250408-152843.png and confirm the action in the modal window (Fig. 37) by clicking the Yes button.

Confirm deletion - modal window.jpg
Fig. 37. “Confirm Deletion” modal window

4. Interface Features

Required fields are marked with "*".

To save the lookup page, click the Save button.

The Save button becomes active:

  • after entering data into required fields when creating a record;
    after modifying any field when editing.

To exit the tab without saving changes, click the Close button.

To save data in a modal window, use the Save button.

To exit without saving, click the Cancel button or the close icon image-20250408-105909.png in the upper right corner.