|Term / Abbreviation||Definition|
After Call Work (Time allotted for tasks that are necessary after handling a customer, e.g. CRM updates, Sales Codes, taking notes etc.
A term commonly used in service and call center context, referring to users of the service that answer to → Customer calls.
To avoid confusion we keep the term → "User" in this Knowledge Base as to avoid conflict with other role concepts like "Team Member, Owner, Operator, Attendant etc...".
Can mean two things in context:
In most cases used synonymous with "Customer" in the context of this Knowledge Base.
The term "Caller" generally applies to someone externally calling (inbound) to the → Service, which triggers the gathering of → KPI metrics inside of a → Session.
Establishes the means to connect Nimbus data sources to other systems, either to retrieve or store data.
Access to contacts usually requires special permissions to see the Calendar and presence status, but of course may also involve external contacts with just a telephone number or mail address.
Cross Selling Code which describes what kind of cross selling the Nimbus user has tried during the customers call.
CSC can be defined in Nimbus Service Settings.
→ See "Caller". A person calling a Nimbus service.
In Nimbus reporting there are two types of tables → Fact table, and Dimension table. A Dimension table is a table that keeps descriptive information that can slice and dice the data of the fact table
A ruleset / requirement set of → Skills required that a Nimbus user must fulfill in order to receive a → Task.
Also see Distribution Profiles and Policies.
|E.164||Phone number format used in some parts of the system (for example PSTN Numbers, contact details) |
→ See Wikipedia.
Facts are business process events and metrics gathered with appropriate measures. A fact table is a table that keeps numeric data that might be aggregated in the reporting visualizations.
|KPI||Key Performance Indicators - data calculated from → Facts gathered during a → Session / call. Examples for KPI are "% of lost calls" or "Time that a customer spent in Queue".|
|OU||Organization Unit. Used to organize teams of people with same background for definition in programming rule-sets (e.g. for call-routing or access management).|
Mainly used in context of Roles and Permissions to refer to "Partner Administrators".
Luware has an integration partner program in place that allows for quick turnaround times. Our partners help with your Nimbus onboarding, setup and training needs.
Public Switched Telephone Network - synonymous with the telephone numbers we know of today.
→ Refer to Installation Prerequisites for technical information on phone numbers and PSTN.
Redirect On No Answer. A Nimbus user in MS Teams is given "RONA" status if they ignore a service call or do not answer it within a set period of time seconds.
Ensures that the call doesn't get lost and is instead redirected to the queue (or handled otherwise via the workflow). Also used in Nimbus Reporting Model.
Mainly mentioned in terms of reporting. A call session is created once a customer is connected to the service. In extension, the term "session" is also used for Nimbus users to aggregate their daily interactions with Nimbus.
Service Level Agreement. A threshold value that defines whether or not a → Fact calculation formula is meeting business criteria or not.
Service tasks are the middle layer between callers and service. Tasks are created when calls are accepted by any Nimbus service.
A task is "handled" by accepting calls from the queue or "not handled" (e.g. aborted by caller or not taken by Nimbus user). Every task ends with a specific result according to the Nimbus Reporting Model and is shown in Reporting UIs.
Task Completion Code which describes the reason why the customer called.
TCC can be defined in Nimbus Service Settings
|TTS||Text To Speech - a software engine to translate written text into an emulated voice that also factors in regional / language differences and nuances such as intonation.|
|UPN||User Principal Name - A UPN (for example: firstname.lastname@example.org) consists of the user name (logon name), separator (the @ symbol), and domain name (UPN suffix).|
Has various meanings depending on context:
A sequence of steps (or "Activities") that describes how an incoming → caller is processed.