Contact Master

Contact Master - User Guide

1. Introduction 📝

The Contact Master is used to store and manage the details of key personnel associated with your Parties (Customers and Suppliers). It ensures that different departments in your organization (Sales, Accounts, Logistics) know exactly whom to contact for specific business activities like order follow-ups, payment reminders, or statutory documentation.

â„šī¸

Key Objectives of Contact Master:

  1. Touchpoint Management: Categorize contacts by their business role (e.g., Finance head vs. Procurement manager).
  2. Communication Hub: Centralize mobile numbers and multiple email addresses for automated or manual communication.
  3. Branch Specificity: Link contacts to specific party locations (branches).

2. Getting Started with Contact Master 🚀

Accessing the Module

To access the Contact Master module, navigate to the Common Masters > Contact section from the main menu.

The Index Page

Upon opening, the Index Page displays a comprehensive list of all personnel associated with your business partners. Here, you can:

  • Search/Filter: Look for specific personnel by Contact Name, Party, or Branch.
  • Quick Navigation: Click on a Contact Name to edit or view their specific details.
  • Action Buttons:
    • Create New: Open the contact registration form.
    • Import: Bulk import contacts via Excel (available during initial onboarding).
    • Export to Excel: Download the complete contacts database to a spreadsheet.
    • Daily Activity Email: Configure global email recipients who should receive automated daily activity digests.

Contact Master Index Page

Daily Activity Email Configuration

Clicking the Daily Activity Email button opens a dedicated setup screen (/dailyactivityemailmodify). This allows administrators to specify one or more recipient email addresses separated by semicolons (;). These recipients automatically receive the daily executive summary reports of operations and activities logged within the system.

Contact Master Details

Selecting a contact opens the Details View, which captures essential communication and role data:

  • Employee Identity: Capture the person’s Title, Name, and Corporate Designation.
  • Business Mapping: Link the individual to a specific Party and Branch.
  • Communication Matrix: Multiple fields for Cell numbers, Telephones, and Emails to ensure you always have a touchpoint.
  • Role Assignment: Define the “Type of Contact” to control how the system interacts with this person for automated alerts.

Contact Master Details Screen


3. Structural Breakdown đŸ—ī¸

Each contact record is defined by its relationship to a Party and a specific role:

  • Party & Branch Link: Every contact must be linked to a valid Party ID and a specific Branch ID.
  • Identity Details: Title (Mr./Mrs./Ms./Dr.), First Name, Last Name, and Designation.
  • Communication Channels:
    • Primary and Secondary Cell numbers (10 digits).
    • Primary and Secondary Telephone/Landline numbers.
    • Up to Four Email Addresses to ensure redundancy and group communication.
  • Contact Type: A critical classification used by the system to filter recipients for different operational modules (see below).

4. Contact Type & Business Roles đŸˇī¸

The Contact Type determines how the system routes automated notifications, transaction alerts, and statutory documents. ERP Crystal supports specialized roles as well as a consolidated general role:

  • Type M (Multiple / General): Represents an all-inclusive touchpoint who handles multiple operational functions (e.g., small enterprise proprietor or chief coordinator).
  • Specialized Roles: Departmental contacts such as Orders, Indents, Accounts / Invoicing, and Logistics.
âš ī¸

Mutual Exclusivity Rule for Contact Types:

  • Type ‘M’ vs Specific Roles: A branch location cannot mix general and specific contacts. If a contact is assigned Type M (Multiple) for a branch, no other specialized contacts (e.g., Orders or Indents) can be created for that branch.
  • Specific Roles First: Conversely, if any specialized contact role already exists for a branch, the system blocks the creation of a Type M contact for that same branch.
  • One Contact per Role per Branch: You cannot register multiple contacts under the same specialized type for a single branch. Each specialized operational role must belong to a single primary contact.

5. Business Validations & Rules đŸ›Ąī¸

To maintain high data quality for communication, the system enforces:

FeatureValidation Rule
Mandatory CommunicationAt least ONE communication field must be filled: Telephone 1, Cell No 1, or Email 1. You cannot save a “silent” contact.
The “Multiple” RuleIf a branch has a contact marked as type “M” (Multiple), the system prevents adding other specific types (like Orders or Indents) to that branch.
Unique Roles per BranchEach specialized role (e.g., Orders, Accounts) is strictly unique per branch location. Duplicate role assignments for the same branch are rejected.
Format SafetyMobile numbers are strictly validated to 10 digits; email addresses are validated for standard @ and domain structure.

6. Bulk Management & Import Logic 📂

The Contact Master supports bulk onboarding through Excel:

  • Export to Excel: Downloads the existing directory of contacts into a structured spreadsheet.
  • Download Model: Downloads the standard Excel template titled ImportContactMst.xlsx.
  • Initial Setup Restriction: Bulk import is strictly permitted only when the Contact Master is empty (0 records). If any contacts already exist in the database, the import button is deactivated, and an advisory banner informs the user: “You may Import Contact Mst only when Contact Master is empty.” This safeguard prevents inadvertent overwrites and branch role conflicts during production.
  • Two-Tier Audit Engine:
    • Tier 1: Format Checks (Z-Codes): Validates text lengths, numeric restrictions (10-digit mobile numbers), and mandatory communication fields.
    • Tier 2: Business Logic Audit (Codes A–F):
      • Code A: Invalid Party ID or Branch ID (party and branch must exist and be active).
      • Code B: Malformed primary email formats (Email1, Email2, or Email3).
      • Code C: Malformed supplementary email address (Email4).
      • Code D: Invalid or inactive Contact Type code.
      • Code E: Duplicate Party, Branch, and Contact Type within the uploaded spreadsheet.
      • Code F: Role collision between Type M (Multiple) and specific contact roles for the same branch.

7. Best Practices 💡

  • Use Designations: Always fill the “Designation” field to help your sales and finance teams understand the contact’s seniority.
  • Email Redundancy: Use Email 1 for the individual and Email 2/3 for a department alias (e.g., accounts@customer.com) to ensure messages are delivered even if a person is on leave.
  • Branch Linking: If a procurement manager handles three different branches, you must create a contact record for each branch to ensure they appear in branch-specific reports.