Customers
The core customer entity in the Tiquo CRM — profiles, identity, activity, and relationships
Customers are the core entity in the Tiquo CRM. A customer profile represents an individual person who interacts with your business.
Customer profiles store identity details, contact information, activity history, and relationships. They act as the central record linking together orders, bookings, enquiries, memberships, wallet cards, and other operational data.
Each customer has a unique identity within the organization and a complete timeline of their interactions with the business.
Customer Profiles
A customer profile aggregates all data associated with an individual.
This includes:
- Personal information
- Contact details
- Company relationships
- Memberships
- Orders
- Bookings
- Enquiries
- Analytics
- Activity history
- Documents
- Wallet cards
- Social connections
Customer profiles provide a complete view of the customer's interactions across the platform.
Creating Customers
Customers can be created in several ways:
- Manually by staff in the CRM
- Automatically during booking flows
- Automatically when an order is created
- Automatically when an enquiry is submitted
- By importing customer data
The platform allows customers to be created with minimal information to support fast workflows in hospitality environments.
A customer can be created with any of the following:
- First and last name
- Email address
- First name and valid phone number
Customer Identifiers
Each customer has two identifiers.
UUID
The UUID is the system-generated identifier.
- Automatically generated by the platform
- Always 32 characters
- Cannot be edited
- Unique across the organization
The UUID is primarily used internally by the system.
Customer Number
The customer number is the human-readable identifier.
- Unique across the organization
- Editable
- Can be imported from external systems
- Minimum length 5 characters
- Maximum length 32 characters
This allows organizations migrating from other systems to retain their existing customer identifiers.
Both the UUID and the customer number can be used to identify a customer across the platform.
Contact Information
Customer profiles can store multiple contact details.
Customers may have:
- Multiple email addresses
- Multiple phone numbers
- Multiple addresses
Each email address must be unique across customer profiles. The same email address cannot exist on two different customers.
Phone numbers can appear on multiple customer profiles.
Company Relationships
Customers can be linked to companies.
Companies allow organizations to group customers who belong to the same organization, employer, or tenant.
Companies can define corporate email domains. When a customer's email address matches a company domain, the customer is automatically associated with that company.
This applies to both existing customers and new customers.
A customer may belong to multiple companies if they have multiple email addresses associated with different domains.
Customer Status
Customer profiles display status indicators.
| Status | Description |
|---|---|
| Active | The customer is not banned from the system |
| Online | The customer is currently active in a live flow such as a booking or transaction process |
| Offline | The customer is not currently active in a live interaction |
Customer Analytics
Customer profiles include analytics calculated from the customer's activity.
Examples include:
- Predictive Customer Lifetime Value (CLV)
- Expected Next Order Date Range
- Average Order Value
- Total Orders
- Total Spend
These metrics provide insight into customer behavior and value.
Predictive CLV is calculated using a proprietary AI model that evaluates hundreds of behavioral, transactional, and cohort-based signals across the platform.
Customer Activity
Each customer has an activity timeline that records events associated with that customer.
The timeline provides a complete operational history of interactions with the business.
Activity Categories
Customer activity is grouped into the following categories:
- Orders
- Customers
- Bookings
- Payments
- System
Activity Types
Activity events may include:
- Auth
- Access
- Order
- Payment
- Cart
- Booking
- Enquiry
- Visit
- Scan
- Communication
- Settings
- Configuration
- Data
- Security
- Compliance
- Notification
- Integration
- Report
- Export
Activity Sources
Activity can originate from multiple sources:
- System
- Staff
- Customer
- API
- Webhook
- Integration
- Physical
- Automated
Activity entries are permanent and cannot be edited or deleted.
Customer Orders, Bookings, and Enquiries
Customer profiles display transactional activity through three sections:
- Orders
- Bookings
- Enquiries
These allow staff to view and manage all activity related to a customer from a single place.
Deduplication and Merging
Customers are not automatically deduplicated. Multiple customer records may exist for the same individual.
Staff can manually review and merge duplicate records using the Deduplicate & Merge action on the customer profile.
The platform helps identify potential duplicates by suggesting matches based on information such as:
- Name
- Contact details
When customers are merged, all historical data from both profiles is preserved and associated with the resulting merged customer profile.
This includes:
- Bookings
- Orders
- Enquiries
- Memberships
- Wallet cards
- Activity history
Merged profiles cannot be unmerged.
Customer Addresses
Customers can store multiple addresses on their profile.
Addresses may be used for purposes such as:
- Billing
- Shipping
- Contact records
Door Access
Customer profiles can include door access permissions.
Door access controls which physical doors a customer can open.
This can be used in environments such as:
- Coworking spaces
- Private members clubs
- Hospitality venues
- Secure facilities
- Event access control
Door permissions may include:
- Assigned door
- Start date
- End date
- Notes
Customer Connections
Customers can be connected to other customers through the Social Graph.
Connections represent relationships between individuals and help businesses understand customer networks.
Connections can be:
- Manually created by staff
- Automatically inferred by the platform
Automatic connections may be inferred from signals such as:
- Shared company domains
- Referrals
- Interactions
- Bookings or purchases
Connections are bidirectional, meaning each connection appears on both customer profiles.
Why Customers Matter
Customers are the central data entity in Tiquo. Most operational activity across the platform is associated with a customer profile.
By linking transactions, interactions, relationships, and analytics together, the customer profile provides a complete operational and behavioral view of each individual interacting with the business.