AyMINE – Technical documentation
Interfaces to other systems
Enterprise Architect Connector
Business excelenece
Balance Scroecards
Task & Project Control
- Helpdesk ticket - reply to customer
- Test
- Qualification of user or contact
- Project role
- What makes up the methodology / QMS
- dragdrop
- Location
- My areas
- Kanban Task Overview
- Personal Task
- Internal helpdesk
- Customer Care Centre
- Project baseline
- Return project plan by baseline
- Project Schedule
- Processing time sheets
- Records managed by a project
- Activation buttons
- Why some data can't be deleted
- Starting events
- Qualification of user or contact
- task_taskobjects
- Project
- Reminders and Messages
- eventobj_raisingevents
- decision_decobjects
- eventobj_startingevents
- eventobj_eventbuttons
- Type of tests
- Deal management
- FMEA - Detection
- FMEA - Features
- FMEA Methodology | AyMINE
- FMEA - Occurence analysis
- FMEA Severity analysis
- FMEA
- Management of responsibilities - RACI Matrix
- RACI Matrix for Project
- Improvements and Preventive Measures
- Notice – example of use
- tskproblem_terminology
- 8D report
- Task Scheduling
- Administration of the Task Management Module
- Adminitration of areas, projects, calendars
- Discussion
- GDPR and record of qualifications
- System rights for the task management module
- Project Planning
- Employee Tasks
- Incident and Quality Issue Management
- Collaborative Resolution of Multiple Problems
- List of business areas
- Required qualifications
- Plan template / strategy
- Decision
- Configuration Package
- Record template
- Change management process in a project
- Task list
- Requirements
- Team Member
- Right to Manage Qualifications
- Input requirements
- Obligation
- Competencies and Skills
- Problems, tickets and their management
- Meeting
- Package definition
- Phrases and terms
- Data Area
- Risk
- Task
- Business event
- Task, project & quality management
- Records and protocols
- Directives and Policies
- Events
- Risk Pattern
- Information
- Project definition
- Activity log
- eventinstances
- Personal calendar
- Objects of decision making
- Event activation buttons
- Objects affected by the problem
- Variant decision-making
- Recorded activities
- Self-Reminders
- QMS and Task Management
- Objects related to the task pattern
- Effect of the task on the right to modify the atta
- Level of Competence
- Manager approval with the task report
- Region / project / methodology
- Manage your marks
- tskdefusertask
- Quality Management System (QMS)
- tsktask_batasks
- Project Team
- Events and meetings
- Events and meetings
- List of event instances
- moduleclientoptions
- Processed objects
- Mark patterns
- Notification events
Interprocess management
Human Resources
- hrstcontract
- roles
- Human resources
- Digital Personnel Archive
- Personalistics – User Permissions and roles
- Registration of job seekers
- Manage department / division data
- Job Position
- Worker
- Worker overview
- An overview of your staff
- Responsible HR Manager
- Synchronizing staff and system users
- modulesafety
Asset Management
- Products, assets and sales
- Tendering and purchasing
- Analytical model
- Product Supplier
- Product Categories
- Product or Product Property
- Project Goal
- Business Offer
- Offers summaries
- Recalculate bid
- Offer and Price Access Rights
- Creating and processing orders
- System order status query
- Order Reports
- Pricing
- Pricing – volume discounts
- Products and Goods
- Product status and change
- Product Units
- Quality criteria
- Why are the Quality criteria usefull
- DFMEA - Product FMEA
- Hara | Hazarad & Risk Analysis
Customer Relationship - CRM
- Contacts and directories module (
- System Permissions and CRM Module Settings
- Customer Order Overview
- Address books
- Address book list and management
- Privacy policy
- Send bulk messages in compliance with GDPR
- Bulk email footer
- Unsubscribe and set preferences
for bulk mail - How to correctly forget a person's details
- Bulk Emails
- Contracts
- Partner in a contract
- Message patterns
- Groups of contacts
- Order overview for customer groups
- Directory or people and companies
- Contact per person or company
- Quickly available contacts
Finance management
System modules
System management
- moduleclientoptions
- digiSign
- formattedtexts
- System Configuration
- Processes in use
- Client
- Public Client
- Configure gateways for external messages
- E-mails and external communication
- Email messages
- Rules for external messages
- Secure business communication
- Send SMS directly from CRM
- Call directly from CRM
- Documents and files
- Additional functions with files
- Copying and moving files between objects
- Picture presentation
- Public link to the document
- Recent Files
- Dashboard
- Object location on the board
- Client items
- Revisions and comments
- Securing posts and internal discussions
- Translations
- Record Relationships
- Relation types
- sysrole
- User Processes
- System module
- System User
- User administration
- User Administration
- Secure login to the sytem
- Connecting users to VOIP PBX
- Secure Key Wallet
Framework
- frmobjectextension
- introhelp
- introhelp_mobile
- introhelp_aplikace
- versioninfo
- releases
- AyMINE modules and basic types
- cliplink
- introhelp_settings
- introhelp_deleting
- introhelp_dragdrop
- list_filtering
- AyMINE intro
- AyMINE access security
- AyMINE Modules
- Object locks
- System rights
- introhelp_keyshortcuts
- introhelp_shortcuts
- introhelp_icons
- list
- introhelp_generalinfo
- introhelp_objectdetail
- introhelp_objectlist
- introhelp_privateobjectnotes
- AyMINE User Rights Control
- introhelp_dashboard
Contact Groups
Contact groups are used to divide contacts according to various criteria. Within a CRM, they are used for profiling customer segments, defining service conditions, and managing business and marketing communication.
- How to segment contacts
- Managing responsibility for customer care
- Good to know
- Protection of business information
- Business classification of contacts
How to segment contacts
Common ways to segment contacts into groups:
- Distinguishing customers from business contacts
- Segmenting customers according to the type of products they purchase
- Linking customers with price lists and provided discounts
- Dividing contacts for customer support
- Groups can be assigned price lists to differentiate, for example, VIP customers
- Groups allow you to distinguish people's interests and direct communication accordingly. Groups can be used to define preferences or consents of recipients of bulk messages
Below are descriptions of common customer groups in more detail.
Price lists for customers
For each customer group it is possible to define its own price lists. Customers can therefore have prices set individually or according to different business criteria.
In the detail of a customer group you can select price lists that are applied to orders from all customers in the group.
If a customer belongs to multiple groups and each defines its own price lists, they are applied within an order according to their priorities.
SLA conditions for customer groups
Each customer group can be assigned an SLA contract. The SLA contract is automatically assigned to every new reported problem. The SLA can be changed for a problem—typically when its severity is reduced. Therefore, a default SLA level is always defined for a customer group and applies until the severity of the problem is evaluated.
Managing responsibility for customer care
For each process area, it is possible to define separately who is responsible for a customer group and which processing area it belongs to.
If these settings are filled in, every message coming from a customer belonging to a particular group is assigned to the configured worker for processing. In addition to the worker, a user group can also be specified, which further restricts who has access to the communication.
Helpdesk area
Helpdesk settings are an example of configuration for a process group.
The area where helpdesk tickets are processed allows issues from different customer groups to be handled separately. If the area is not filled in, the ticket is created in the area defined by the module settings—see the administration of the tsk module.
Public groups
A group can be made public. When you give a group a public name and optionally a description, recipients can unsubscribe from the group themselves and withdraw their consent. This helps you meet GDPR requirements and also provides evidence of when and how people expressed their consent. More about published groups and GDPR message consent here.
In the contact list
In the list of contacts assigned to a group you can see when and how the contact joined the group—whether they subscribed themselves via the web or were assigned by someone. Columns with information about group membership are color-coded for better clarity.
Good to know
A customer group is not an address book
The system allows you to organize contacts into multiple address books. Address books also define access rights, allowing you to limit who can see which contacts.
Customer groups, on the other hand, are part of a single address book but may contain contacts from multiple address books. A user who has access to a customer group but not to contacts from another address book does not gain that access simply because those contacts are included in the group.
Don't forget information protection
Protection of business information
Business information is always among the most important assets in a company, so protecting it deserves attention.
Did you know: More than 60% of salespeople admit that when they leave a company, they take customer contacts with them?
Sensitive business information
Sales teams need a variety of business data for their work, especially:
- What each customer buys
- Product margins and what discounts can be offered
- Who has the final say on purchases at the customer
- Which communication approaches work with which customers
- How individual customers pay
- Communication history
If you do not provide this information to the sales team, the whole department will be much less effective. At the same time, you need to ensure that the information cannot leak outside the company.
How to provide and protect business information
The most effective advice is quite simple: prevent exports to Excel, PDF, and other formats as much as possible. Creating and taking away documents is tempting. If it is easy and uncontrolled, you effectively have no control over the data. If you fail to implement this simple step, most other protections become almost useless.
Protection also assumes that the data is stored in a system that supports security controls (for example, AyMINE).
Additional recommendations:
- Salespeople must know that data usage is monitored
- Salespeople should communicate from the CRM, not directly from their personal email
- Monitor how salespeople work
- Use customer groups for segmentation. Do not allow exporting customers together with their group membership (AyMINE does not support this by default). There is no reasonable business case for needing such exports.
Protecting communication with customers
Customer communication is generally visible to employees who have permission to see customer information. However, there are ways to protect it:
- Give each salesperson and employee access only to the contacts they actually work with
- Store messages in separate folders for sales and delivery teams so operational staff can focus only on implementation
- Provide the KAM (Key Account Manager) with complete information—but only about the customers they work with
- If communication relates to a project, assign messages to the project so that only users with project access can see them
- Marking a message as private ensures only the recipient can read it, although others may still see that a message was received
Lead, Prospect — what do these terms mean?
Business classification of contacts
In marketing, the terms lead, prospect, and customer are commonly used. Let’s look at their meaning and some limitations.
These labels originated to divide contact groups according to how they are handled within the marketing process. We can describe them as types and subtypes of potential customers.
First, however, it should be noted that contact groups are not suitable for classifying leads, prospects, or other marketing types. Status flags (business status) from a classification list are more appropriate.
Lead
A lead is contact information for someone who is already interested in the products. The concept of “interest” is very broad, and often includes people who show curiosity but are not seriously considering a purchase or cooperation.
Because this category is so broad, it is usually divided more precisely:
- Cold – a person showing minimal interest, for example someone who visited the website once but did nothing further
- Warm – someone who has shown repeated interest or requested more details, such as viewing technical documentation, using a calculator or visualization tool
- Hot – someone actively communicating and expressing interest, for example by calling for information or agreeing to a meeting
Historically the term “lead” refers to someone who has already been guided toward interest in the company or its products.
Prospect
A prospect refers to a contact who is already actively interested in doing business. Typically they are asking about price lists, business terms, or arranging a meeting to discuss cooperation.
Like leads, prospects are often further classified by salespeople. The exact categories depend on the products, services, and sales process. The following are examples rather than formal stages:
- Bargain Hunter – waits for the most advantageous offer and focuses primarily on saving money
- Staller – hesitates because they are afraid of making a mistake and tends to compare alternatives
- Value Buyer – looks for the best price/performance ratio and may respond well to add-ons or additional services
- Sitting Duck – initiates communication because they want to solve their need and are interested in cooperation; typically they have not yet explored alternatives and may become a customer if the communication is convincing
Dead contact
A dead contact is someone with whom communication has taken place or who was once a lead, but it is clear that they have no real interest. Communication may still continue even though the salesperson knows it will never lead to business.
For example, a representative of a very small company requesting services that are clearly designed only for large organizations.
This type rarely appears in sales manuals—authors prefer to ignore it. However, experienced salespeople know many contacts end up here.
Why not use customer groups for marketing types
- Changes between these types usually do not affect internal responsibilities, so using groups would provide little benefit
- Status changes can occur frequently—sometimes a single phone call can turn an interested prospect into a dead contact