Skip to content

Customer Support and Configuration Assistance

 

Mochadocs Customer Support assists organizations with the configuration of Mochadocs Contract Lifecycle Management (CLM) based on the train-the-trainer principle. The objective is to transfer knowledge to the customer organization, enabling users to independently manage, maintain, and further optimize Mochadocs CLM over time. This service is included in the Mochadocs Enterprise MANAGE Subscription.

 

What is included in Customer Support?

 

Customer Support can provide guidance and assistance with:

 

  • Configuring entities, departments, and locations
  • Setting up contract types
  • Configuring Object and Properties
  • Defining notifications, including end date notice periods notifications
  • Configuring user roles and permissions
  • Creating dynamic lists
  • Explaining best practices for contract registration and contract management
  • Answering functional questions related to the use of the system

 

Train-the-Trainer Approach

 

Mochadocs focuses on training a limited number of key users within the organization. These key users are supported and trained to:

 

  • Understand the Mochadocs CLM configuration
  • Perform configuration changes independently
  • Support and train new users
  • Answer internal questions
  • Maintain and expand knowledge within the organization

This approach helps organizations become self-sufficient.

 

Configuration Responsibility

 

While Mochadocs provides guidance, recommendations, and support, the responsibility for the Mochadocs CLM configuration always remains with the customer organization.

 

Mochadocs can advise on configuration options and share best practices, but does not assume ownership of configuration decisions, business rules, or the accuracy and completeness of the data entered into the system.

 

Guiding Principle

 

The primary goal of Customer Support is to enable organizations to independently manage and optimize Mochadocs Contract Lifecycle Management (CLM). Knowledge, ownership, and responsibility for the configuration should ultimately reside within the customer organization, ensuring long-term sustainability and successful adoption of the platform.