SCALAR
LegacyId
Legacy iAdvize identifier, encoded as an integer.
link GraphQL Schema definition
- scalar LegacyId
link Require by
- BotSome bot that interacts with visitors.
- Clientnull
- ClosedConversationFiltersFilters on the ClosedConversation resource (indexed conversation)
- ConnectedUserFiltersCriteria available to filter a list of connected users.
- ConnectorConnector
- ConnectorConversationClosingFormValueConversation closing form value type
- ConnectorVersionParameterParameter for connector version
- Conversationnull
- ConversationTagInputnull
- DeveloperExternal or internal developer that implements applications that interact with iAdvize
- ExpertAn ambassador who interacts with visitors.
- IbbuManagerAn Ibbu manager user internal to iAdvize
- Mutationnull
- OpenConversationFiltersFilters on the open conversation resource (indexed conversation)
- ProfessionalA professional agent employed by a brand ('Admin', 'Manager' or 'Operator')
- ProfessionalCreateInputContains input data for the professionalCreate mutation to create a professional user
- ProfessionalPermissionPermission granted to a user
- ProfessionalRoleWithPermissionsProfessional Role with its associated user permissions and the role on which it is based
- ProfessionalSetExternalIdInputInput for the `professionalSetExternalId` mutation.
- ProfessionalSetGroupInputInput for the `professionalSetGroup` mutation.
- ProfessionalSetProjectsInputInput for the `professionalSetProjects` mutation.
- ProfessionalSetSkillsInputInput for the `professionalSetSkills` mutation.
- ProfessionalUnsetExternalIdInputInput for the `professionalUnsetExternalId` mutation.
- ProfessionalUnsetGroupInputInput for the `professionalUnsetGroup` mutation.
- ProfessionalUpdateInputInput for the `professionalUpdate` mutation. Besides `userId`, all fields are optional, which allows updating only the desired user information.
- Projectnull
- Querynull
- RoutingGroupThanks to the routing groups, you can organise your teams in a flexible way by grouping your agents according to their role (agent, supervisor or administrator), group (i.e: contact centre) or skills (i.e: mobile, photography). A routing group is given a name and a set of segments defining which agents to include in the group.
- RoutingRuleRouting rules determine how to distribute conversations from a set of targeting rules to a set of routing groups, according to a routing mode.
- RoutingSegmentUserDynamicRouting group segment used to dynamically match agents based on their skills.
- RoutingSegmentUserGroupsRouting group segment used to match agents based on their groups.
- RoutingSegmentUserIdsRouting group segment used to match agents based on their identifier.
- RoutingSegmentUserSkillsRouting group segment used to match agents based on their skills.
- SearchClosedConversationsFiltersFilters for search closed conversations query
- Usernull
- UserAvailabilityInputInput for updating the availability status of an operator
- UserCreateInputInput containing the properties of the user to be created
- UserDeleteInputInput for the `userDelete` mutation.
- UserDeletePayloadReturn type of the `userDelete` mutation.
- UserGroupUser groups allow information and user exchanges to be compartmentalised in the iAdvize administration. For more information regarding user groups, please see the following documentation: https://help.iadvize.com/hc/en-gb/articles/203280696-Use-the-user-groups.
- UserUpdateInputInput containing the properties of the user to be created