- What Is Customer Connections?
Customer Connections, internally known as Combo Meeting, is a relationship-centric module designed to manage structured meetings and interactions between two customers inside the same organization.
Unlike standard calendars or appointments, this module is not about time alone — it is about intentional connections:
Who met whom, why they met, when they met, and what came out of it.
It creates a traceable relationship layer between customers, fully integrated with folders, statuses, tags, automations, and team ownership.
- Why This Module Exists
In many organizations, customers are not isolated entities:
-
Partners meet prospects
-
Clients meet vendors
-
Investors meet startups
-
Buyers meet sellers
Customer Connections exists to formalize these interactions, replacing informal notes, chats, and memory with structured, auditable data.
- Core Concept: A Connection Is a Record
Each Combo Meeting record represents one intentional connection event between:
-
A primary customer
-
A secondary (connected) customer
This record contains:
-
Date & time
-
Duration (calculated in 15-minute blocks)
-
Address / location
-
Notes
-
Status
-
Assigned team members
It is not just a meeting — it is a relationship milestone.
- Folder-Based Intelligence (Why This Is Powerful)
Customer Connections is governed by Folder Pairing Rules.
Only customers belonging to compatible folders can be connected.
Example:
-
Folder A: Investors
-
Folder B: Startups
➡ Investors can only be connected with Startups
➡ Startups can only be connected with Investors
This prevents:
-
Invalid meetings
-
Random connections
-
Data pollution
And enforces business logic at the system level, not by memory.
- Multi-Customer & Multi-Member Reality
This module understands real business complexity:
Multiple Customers
-
One meeting can be created for multiple primary customers
-
Each creates its own relationship record
-
All remain independently trackable
Multiple Team Members
-
Multiple users can be assigned
-
Responsibility is visible
-
Ownership is auditable
This makes the module usable for sales teams, account managers, partnerships, and operations.
- Time Is Structured, Not Free-Text
Meetings are not vague timestamps.
They are:
-
Defined by start time
-
Measured in 15-minute intervals
-
Stored as structured
time_json
This allows:
-
Duration analysis
-
Time conflict prevention (future-ready)
-
Calendar-style reasoning
-
Precise reporting
- Table Experience: Designed for Relationships
The Customer Connections table is not flat.
It is hierarchical:
Main Row
-
Primary customer
-
Summary of connections
Expandable Sub-Rows
-
Each connected customer
-
Individual status
-
Editable inline
-
Independent lifecycle
This design mirrors real relationships, not spreadsheets.
- Status Is the Heart of the Workflow
Statuses define where the relationship stands.
Examples:
-
Planned
-
Completed
-
Follow-up needed
-
Canceled
-
Successful introduction
Statuses are:
-
Fully customizable
-
Multi-language
-
Inline editable
-
Automation-aware
Changing a status can trigger automations instantly.
- Automation: Relationships That React
Customer Connections is deeply wired into the automation engine.
Events that trigger workflows:
-
Meeting created
-
Meeting edited
-
Status changed
-
Meeting canceled
Automations can:
-
Send emails
-
Notify team members
-
Update customer fields
-
Trigger follow-up tasks
This turns meetings into living workflows, not dead data.
- Field Customization: One View Never Fits All
Every organization works differently.
That’s why the module supports:
-
Drag-and-drop column ordering
-
Show / hide fields
-
Custom labels
-
Customer fields + meeting fields
-
Dynamic custom fields
Each user sees only what matters to them.
- Filtering That Understands Context
Filters are not generic — they are relationship-aware:
-
Customer name
-
Folder
-
Date range
-
Status
-
Team member
-
Tags
This allows users to:
-
Find meetings quickly
-
Track outcomes
-
Audit interactions
-
Prepare follow-ups
- Security & Isolation by Design
Every record is protected by:
-
Organization isolation
-
Role-based access
-
Folder validation
-
User permissions
No customer can be connected unless:
-
Folder logic allows it
-
User has permission
-
Data belongs to the same organization
- Performance & Scalability
The module is built for growth:
-
Server-side pagination
-
Lazy loading of sub-rows
-
Indexed queries
-
Cached field configuration
It scales from dozens to thousands of meetings smoothly.
- Final Perspective
Customer Connections is not a calendar.
It is relationship infrastructure.
It captures:
-
Intent
-
Context
-
Ownership
-
Outcome
And turns customer interactions into structured, automated, and scalable business intelligence.
