Skip to main content

Core Entities

This page provides an overview for epilot's core entity data model with all of the built-in entity schemas, including examples and schema definitions.

Relationship Diagram​

graph TB %% Customer Relations Account[Account] Contact[Contact] %% Sales Opportunity[Opportunity] Order[Order] %% Products Product[Product] Price[Price] Tax[Tax] %% Contracts & Billing Contract[Contract] BillingAccount[Billing Account] BillingEvent[Billing Event] %% Metering Meter[Meter] MeterCounter[Meter Counter] %% Sales Flow Opportunity -->|has many| Order %% Customer Relations Contact -->|has many| Opportunity Contact -->|has many| Order Contact -->|has one| Account Contact -->|has many| Contract Contact -->|has many| Ticket Contact -->|has many| BillingAccount Order -->|has many| Product %% Products Product -->|has many| Price Price -->|has one| Tax %% Contracts & Billing Contract -->|has one| BillingAccount Contract -->|has one| Order Contract -->|has many| Meter BillingAccount -->|has many| BillingEvent %% Metering Meter -->|has many| MeterCounter style Account fill:#e1f5ff style Contact fill:#e1f5ff style Opportunity fill:#fff4e1 style Order fill:#fff4e1 style Product fill:#f0e1ff style Price fill:#f0e1ff style Tax fill:#f0e1ff style Contract fill:#e1ffe1 style BillingAccount fill:#e1ffe1 style BillingEvent fill:#e1ffe1

Built-in Entity Schemas​

Customer Relations​

Contact

Contacts store details about customers or individuals managed by the epilot organization.

Account

Accounts store details about companies. Contacts can be linked to an account to represent a business customer.

Partner

Partners store details about collaborating third parties, such as installation partners, OEMs and other business partners.

Ticket

Tickets store customer support requests and help desk inquiries.

Sales​

Opportunity

Opportunities store details about sales leads or product inquiries usually made through journeys.

Order

Orders store details about requested products, pricing and past orders placed by customers.

Product Hub​

Product

Products represent services or products sold by the epilot organization.

Price

Prices configure the pricing models for products.

Tax

Taxes represent the tax rates applied to prices.

Coupon

Coupons represent discounts or promotions that can be applied to products.

Contracts & Billing​

Contract

Contracts store details about service agreements, tariffs and other agreements between customers and the epilot organization.

Billing Account

Billing accounts store billing information and payment details for customers.

Billing Event

Billing events store records of financial transactions, including payments, invoices, and credit notes.

Metering​

Meter

Meters store details about power, gas or water or other devices used to meter consumption.

Meter Counter

Meter counters represent the counters used in meter devices, allowing separate tracking for different consumption types or purposes, such as peak and off-peak energy usage.

Journeys​

Journey

Journeys contain the configuration of a customer journey, which is used to collect data from customers.

Submission

Submissions store raw data collected from Journeys or other outside data sources into epilot.

Messaging​

Message

Messages are email communications sent and received through the epilot platform.

Email Template

Email templates are used as templates containing variables for emails sent from epilot.

Marketing & Analytics​

Campaign

Campaigns store marketing campaign information and configurations.

Target

Targets represent goals or milestones for sales and marketing activities.

Product Recommendation

Product recommendations suggest products to customers based on their preferences and behavior.

System​

File

Files store details about documents, images, templates and other files uploaded to the epilot platform.

Comment

Comments allow users to add notes and have discussions across the platform.

Portal User

Portal users are users registered to use end customer portals or installer portals.