--- title: "Customers" description: "A non-technical overview of Customers in RevCent, focused on what customers represent, why they matter, how they help ecommerce businesses, and how customer records connect the RevCent ecosystem." type: "item" company: "RevCent" canonical: "https://revcent.com/documentation/markdown/ecosystem/item/Customer.md" relationships: - name: "Customer Group" url: "https://revcent.com/documentation/markdown/ecosystem/feature/CustomerGroup.md" - name: "Customer Portal" url: "https://revcent.com/documentation/markdown/ecosystem/feature/CustomerPortal.md" - name: "Customer Card" url: "https://revcent.com/documentation/markdown/ecosystem/item/CustomerCard.md" technical_links: web_app: "https://kb.revcent.com/en/customer" api: section: "https://revcent.com/docs/api/v2#section-customers" operations: - name: "Get Customers" operation_id: "GetCustomers" operation: "https://revcent.com/docs/api/v2#operation-GetCustomers" schema: "https://revcent.com/documentation/files/api/operation/GetCustomers.json" - name: "Create A Customer" operation_id: "CreateCustomer" operation: "https://revcent.com/docs/api/v2#operation-CreateCustomer" schema: "https://revcent.com/documentation/files/api/operation/CreateCustomer.json" - name: "Get A Customer" operation_id: "GetCustomer" operation: "https://revcent.com/docs/api/v2#operation-GetCustomer" schema: "https://revcent.com/documentation/files/api/operation/GetCustomer.json" - name: "Edit A Customer" operation_id: "EditCustomer" operation: "https://revcent.com/docs/api/v2#operation-EditCustomer" schema: "https://revcent.com/documentation/files/api/operation/EditCustomer.json" - name: "Enable A Customer" operation_id: "EnableCustomer" operation: "https://revcent.com/docs/api/v2#operation-EnableCustomer" schema: "https://revcent.com/documentation/files/api/operation/EnableCustomer.json" - name: "Disable A Customer" operation_id: "DisableCustomer" operation: "https://revcent.com/docs/api/v2#operation-DisableCustomer" schema: "https://revcent.com/documentation/files/api/operation/DisableCustomer.json" - name: "Add Card To Customer" operation_id: "AddCardToCustomer" operation: "https://revcent.com/docs/api/v2#operation-AddCardToCustomer" schema: "https://revcent.com/documentation/files/api/operation/AddCardToCustomer.json" - name: "Add Customer To Group" operation_id: "AddCustomerToGroup" operation: "https://revcent.com/docs/api/v2#operation-AddCustomerToGroup" schema: "https://revcent.com/documentation/files/api/operation/AddCustomerToGroup.json" - name: "Remove Customer From Group" operation_id: "RemoveCustomerFromGroup" operation: "https://revcent.com/docs/api/v2#operation-RemoveCustomerFromGroup" schema: "https://revcent.com/documentation/files/api/operation/RemoveCustomerFromGroup.json" - name: "Search Customers" operation_id: "SearchCustomers" operation: "https://revcent.com/docs/api/v2#operation-SearchCustomers" schema: "https://revcent.com/documentation/files/api/operation/SearchCustomers.json" mcp: overview: "https://revcent.com/documentation/markdown/mcp/operation/OverviewCustomer.md" operations: - name: "Get Customers" operation_id: "GetCustomers" markdown: "https://revcent.com/documentation/markdown/mcp/operation/GetCustomers.md" available_via_ai: true - name: "Create A Customer" operation_id: "CreateCustomer" markdown: "https://revcent.com/documentation/markdown/mcp/operation/CreateCustomer.md" available_via_ai: true - name: "Get A Customer" operation_id: "GetCustomer" markdown: "https://revcent.com/documentation/markdown/mcp/operation/GetCustomer.md" available_via_ai: true - name: "Edit A Customer" operation_id: "EditCustomer" markdown: "https://revcent.com/documentation/markdown/mcp/operation/EditCustomer.md" available_via_ai: true - name: "Enable A Customer" operation_id: "EnableCustomer" markdown: "https://revcent.com/documentation/markdown/mcp/operation/EnableCustomer.md" available_via_ai: true - name: "Disable A Customer" operation_id: "DisableCustomer" markdown: "https://revcent.com/documentation/markdown/mcp/operation/DisableCustomer.md" available_via_ai: true - name: "Add Card To Customer" operation_id: "AddCardToCustomer" markdown: "https://revcent.com/documentation/markdown/mcp/operation/AddCardToCustomer.md" available_via_ai: true - name: "Add Customer To Group" operation_id: "AddCustomerToGroup" markdown: "https://revcent.com/documentation/markdown/mcp/operation/AddCustomerToGroup.md" available_via_ai: true - name: "Remove Customer From Group" operation_id: "RemoveCustomerFromGroup" markdown: "https://revcent.com/documentation/markdown/mcp/operation/RemoveCustomerFromGroup.md" available_via_ai: true - name: "Search Customers" operation_id: "SearchCustomers" markdown: "https://revcent.com/documentation/markdown/mcp/operation/SearchCustomers.md" available_via_ai: true bigquery_schema: "https://revcent.com/documentation/files/bigquery/dataset.json" bigquery_tables: - "customer" --- # Customers Customers are one of the most important focal points in RevCent. A customer is not only a contact record. In the RevCent ecosystem, a customer can become the central identity that connects sales, payments, products, subscriptions, trials, shipping, refunds, chargebacks, fraud signals, notes, metadata, groups, AI workflows, voice calls, reporting, and long-term ecommerce behavior. The purpose of this document is to explain the item conceptually for LLMs, AI crawlers, and planning systems. It does not provide technical implementation instructions. For technical details, use the interface-specific links below. ## Technical Links by Interface | Interface | Use This When | Link | |---|---|---| | Web App | A human is learning about or managing Customers through the RevCent web app and Knowledge Base. | [Web Knowledge Base](https://kb.revcent.com/en/customer) | | API | A developer is building a direct integration with the RevCent API. | [API Docs: Customers](https://revcent.com/docs/api/v2#section-customers) | | MCP / AI | An LLM, MCP client, or AI agent needs markdown-oriented guidance for understanding or working with the item. | [MCP Markdown Overview](https://revcent.com/documentation/markdown/mcp/operation/OverviewCustomer.md) | | BigQuery / Reporting | A data analyst, reporting workflow, or AI reporting agent needs schema details for analyzing customer records. The primary table is `customer`. | [BigQuery Tables Schema](https://revcent.com/documentation/files/bigquery/dataset.json) | --- ## What Customers Are Customers are the people or organizations that interact with an ecommerce business through RevCent. A customer can be created manually, through the RevCent API, through connected ecommerce activity, or automatically during a purchase attempt. When a customer makes future purchase attempts, RevCent can associate that activity back to the existing customer record, helping the business avoid treating each sale as an isolated event. In RevCent, the customer becomes a durable business object. It gives the business a way to understand who the customer is, what they have done, what they have purchased, how they have paid, how they have interacted with support, and what future workflows may apply to them. ## Core Purpose The core purpose of Customers in RevCent is to centralize ecommerce identity and connect that identity to commerce activity. Without a central customer record, sales, payments, refunds, subscriptions, shipments, support notes, chargebacks, and AI actions can feel disconnected. With a central customer record, RevCent can build a more complete picture of the customer relationship. That complete picture helps ecommerce businesses provide better support, recover more revenue, personalize communication, evaluate customer value, reduce risk, and automate workflows based on customer behavior. ## Why Customers Matter in Ecommerce Ecommerce businesses are not only managing individual transactions. They are managing customer relationships over time. A single customer may place multiple orders, use multiple payment methods, start a subscription, have a failed renewal, receive a shipment, request a refund, contact support, trigger a fraud review, receive an email, talk with an AI Voice Agent, and appear in multiple reports. RevCent Customers help bring those moments together. This matters because the same event can mean different things depending on the customer. A declined payment from a first-time buyer may require one response. A declined renewal from a high-value subscription customer may require a different response. A refund request from a loyal customer may be handled differently than repeated refund behavior tied to fraud or chargeback risk. The customer record gives RevCent the context needed to make those differences visible. ## How Customers Help Ecommerce Businesses Customers help ecommerce businesses create a more connected operating model. They help customer support teams understand customer history before responding. Instead of only seeing a single order or ticket, support can understand the customer’s purchases, subscriptions, payments, shipments, refunds, notes, and status. They help revenue teams identify recovery opportunities. A customer with a failed payment, pending sale, failed renewal, or salvage opportunity can be handled with more context than a generic failed transaction. They help marketing and retention teams segment customers based on behavior. Businesses can identify VIP customers, winback candidates, subscription customers, high-refund customers, first-time buyers, repeat buyers, customers tied to a specific campaign, or customers associated with custom metadata. They help risk and finance teams investigate disputes, chargebacks, refunds, fraud detections, payment outcomes, and lifetime value. They help AI tools become more useful because the AI can reason from actual customer context rather than a generic prompt. ## Customers as the Central Relationship Hub Customers are one of the main relationship hubs in RevCent. The BigQuery schema reinforces this concept: the customer record is connected to many other ecommerce objects, and many other objects also reference the customer. This does not mean the customer table should be treated as a SQL guide in this document. Instead, it shows the role of the customer as a central anchor across RevCent. Conceptually, a customer can be related to: - Sales and purchase attempts - Product sales and products purchased - Credit card transactions - PayPal transactions - Offline payments and checks - Customer cards and payment method references - Subscriptions and subscription renewals - Trials and trial expirations - Shipments and fulfillment activity - Taxes and discounts - Pending refunds and refund activity - Chargebacks and PayPal disputes - Fraud detections and risk signals - Salvage transactions and payment recovery opportunities - Customer groups and segmentation - Metadata and custom business labels - Notes and support history - Tracking visitors and conversion activity - AI Voice Calls and AI-driven customer interactions This makes the customer one of the strongest organizing concepts in RevCent. Many parts of the platform either start from the customer, connect back to the customer, or become more useful when customer context is available. ## Where Customers Fit in RevCent Customers sit near the center of the RevCent ecosystem. They relate to revenue because sales, transactions, subscriptions, renewals, trials, discounts, refunds, and salvage opportunities can all be viewed through the customer relationship. They relate to payments because stored payment references, transaction outcomes, failed payments, refunds, and recovery workflows are more meaningful when attached to the customer who created them. They relate to products because customers can be associated with the products they purchased, the quantities purchased, and the product-level revenue or refund outcomes tied to those purchases. They relate to shipping because customer orders often result in shipments, delivery questions, fulfillment issues, replacements, and post-purchase support. They relate to support because notes, customer status, historical purchases, refunds, chargebacks, and subscriptions help support teams understand what happened before taking action. They relate to marketing because customer groups, metadata, purchase behavior, and lifetime value can help determine who should receive which message or offer. They relate to risk because fraud detections, chargebacks, refund behavior, customer status, and prior payment outcomes provide context for review. They relate to AI because AI Assistants and AI Voice Agents become more effective when they can work with real customer context. They relate to reporting because BigQuery can analyze customer behavior over time and connect that behavior to sales, payments, products, refunds, subscriptions, and outcomes. ## Customer Identity and Contact Context A customer record can represent basic identity and contact context such as name, email, phone, address, internal customer ID, campaign association, and status. This information matters because many workflows begin by identifying the customer. A support representative may search by email, phone, name, address, or internal ID. An AI Voice Agent may try to match an inbound caller. An AI Assistant may need to understand which customer is tied to a sale, renewal, or note. Customer identity also helps connect RevCent to outside systems. A business may use an internal customer ID, CRM ID, affiliate ID, loyalty ID, or other external reference to connect RevCent customers to broader business systems. ## Customer Status and Business State Customers can have a status that helps a business decide how the customer should be handled. For example, a customer may be active, disabled, blocked, under review, or part of a group that changes how the business interacts with them. Customer status matters because not every customer should receive the same automation. Some customers should receive normal support. Some should receive VIP treatment. Some should be excluded from outreach. Some should be escalated to a human. Some may need fraud or chargeback review before additional action. A strong customer model gives RevCent the context needed to apply these differences consistently. ## Customer Cards and Payment Context Customers can be associated with payment method references, such as customer cards. This is important for ecommerce because payment methods are often part of the customer lifecycle. A stored payment reference can support subscriptions, renewals, trials, payment retries, pending sale recovery, customer portal payment updates, and AI Voice Agent payment recovery conversations. The customer record should be understood as connected to safe payment context, not as a place where sensitive raw payment data is exposed. Businesses can use payment method references for billing workflows while maintaining appropriate separation from sensitive payment data. For ecommerce businesses, this makes the customer record valuable for recurring billing, subscription recovery, trial conversion, and payment support. ## Sales and Purchase History Sales are one of the most important relationships connected to customers. A customer may have one sale, many sales, failed sale attempts, pending sales, successful sales, declined sales, refunded sales, or sales that created subscriptions, trials, shipments, product sales, taxes, discounts, and payment records. This purchase history gives a business a fuller view of the customer. It can show whether the customer is new or returning, what they attempted to buy, what they successfully purchased, how much they have spent, how often they buy, and whether there are unresolved payment or refund issues. For support, this means a customer conversation can start with context. For marketing, it means offers can be based on actual purchases. For finance, it means customer value can be measured. For AI, it means decisions can be based on meaningful commerce history. ## Product-Level Customer Behavior Customer understanding becomes more powerful when product purchases are connected to the customer. A customer may have purchased specific products, purchased multiple quantities, bought a subscription product, bought a trial product, bought from a product group, or purchased a product that later generated shipping, refunds, or support issues. This allows ecommerce businesses to understand product-level customer behavior. Examples include identifying customers who bought a consumable product and may need a reorder reminder, customers who bought one product but not a complementary product, customers with product-specific refund behavior, or customers who qualify for product-specific support. This makes the customer record useful for upsell, cross-sell, reorder, warranty, support, fulfillment, and product performance workflows. ## Transactions and Payment Outcomes Transactions connect customers to actual payment outcomes. A customer can be related to successful payments, declined payments, failed gateway responses, refunds, merchant holds, salvage attempts, subscription renewal payments, trial expiration payments, and payment profile behavior. This matters because payment history is a major part of ecommerce intelligence. A customer who has repeated declines may need payment update outreach. A customer with successful history but a single failed renewal may be a strong recovery candidate. A customer with repeated refunds or chargebacks may require risk review. By tying transactions back to customers, RevCent can help businesses understand not only what was attempted, but who was behind the payment behavior. ## Subscriptions, Renewals, and Trials Customers are central to subscription and recurring billing workflows. A customer can be associated with subscriptions, subscription renewals, overdue renewals, trial starts, trial expirations, subscription status, recurring payment attempts, and renewal outcomes. This is important for businesses with recurring revenue because the customer relationship extends beyond the first purchase. The customer may need renewal reminders, payment recovery, cancellation support, save offers, subscription updates, or long-term retention workflows. When subscriptions and renewals are connected to the customer, RevCent can help businesses understand customer lifecycle state: active subscriber, overdue subscriber, cancelled customer, trial user, trial converted, trial expired, renewal failed, recovered renewal, or winback candidate. ## Shipping and Fulfillment Context Customers are also connected to shipping and fulfillment activity. A customer may have shipments tied to sales, subscriptions, trials, product sales, or renewals. Those shipments may have statuses, tracking details, delivery dates, fulfillment accounts, merged shipments, costs, and related support issues. For ecommerce businesses, shipping context is critical because many support conversations are about delivery. Customers want to know where their order is, whether it shipped, when it will arrive, and what happens if there is a delay. When shipping is connected to the customer, support teams, AI Assistants, and AI Voice Agents can respond with better context. ## Refunds, Chargebacks, and Risk Context Customers can be connected to refunds, pending refunds, chargebacks, PayPal disputes, and fraud detections. This makes the customer record valuable for risk and finance teams. A single refund may be routine. Repeated refunds may suggest a support issue, product problem, policy abuse, or customer dissatisfaction. A chargeback may require investigation into the customer’s purchase, shipment, prior notes, payment history, and support interactions. A fraud detection may require understanding whether the customer has legitimate purchase history or suspicious behavior. Centralizing these relationships around the customer helps businesses make better decisions and avoid reviewing risk events in isolation. ## Salvage Transactions and Revenue Recovery Customers can be connected to salvage transactions and other recovery opportunities. A salvage transaction represents an opportunity to recover revenue from a payment that was not fully collected. When that opportunity is tied to a customer, the business can evaluate recovery in a more intelligent way. For example, the business can consider customer value, prior payment behavior, subscription status, refund history, chargeback history, product purchased, and whether the customer should receive email, voice, or human follow-up. This makes customer context important for deciding when and how to recover revenue. ## Metadata as Custom Customer Context Metadata gives businesses a flexible way to attach custom meaning to customers. Every ecommerce business has its own labels, systems, sources, and internal concepts. Metadata lets RevCent store those business-specific values without requiring every possible custom field to be built directly into the customer record. Examples of customer metadata concepts include affiliate ID, CRM ID, lead source, sales rep, loyalty tier, preferred language, customer tier, risk flag, marketing segment, or internal account owner. Metadata helps customers connect to reporting, AI workflows, email personalization, customer groups, functions, external systems, and segmentation. A key concept is that users may describe metadata without using the word metadata. A request like “show revenue by affiliate” may involve customer metadata. A request like “call gold-tier customers” may involve metadata or customer groups. A request like “sync customers from campaign partner A” may involve metadata, campaign, or third-party shop context. ## Customer Groups and Segmentation Customer Groups help businesses organize customers into reusable segments. A customer group can represent a simple label, such as VIP or Wholesale, or a more meaningful lifecycle state, such as Failed Payment Recovery, Winback Candidate, Subscription Save, Trial Expired, Manual Review, Fraud Review, High LTV, or Do Not Contact. Customer Groups are powerful because they make customer behavior actionable. A group can help determine which customers should receive special support, which should receive retention outreach, which should be excluded from contact, which should trigger AI workflows, and which should appear in a report. In the RevCent ecosystem, customer groups can act as the bridge between customer data and customer action. ## Notes as Customer Memory Notes help preserve customer context that does not fit neatly into structured fields. A note can capture support conversations, refund explanations, AI Voice Agent call outcomes, cancellation requests, shipping issues, escalation instructions, payment promises, human review decisions, or customer preferences. Notes are important because customer history is not only numbers and statuses. Human context matters. A customer may have a long-running support issue, a promised replacement, a manager escalation, or a payment recovery conversation that should be visible in the future. When notes are connected to customers, future human agents, AI Assistants, AI Voice Agents, and reporting workflows can better understand the customer’s history. ## Customer Portals and Self-Service Customer data can also support customer-facing self-service experiences. A Customer Portal can give customers access to relevant account functionality such as reviewing information, managing payment methods, viewing orders, managing subscriptions, and reducing the need for support contact. Because the portal is connected to RevCent customer data, it can offer a more useful experience than a disconnected form or generic support page. For ecommerce businesses, this helps reduce support load while giving customers more control over their relationship with the business. ## Customers and AI Assistants AI Assistants become more useful when customer data is available. An AI Assistant can analyze a customer’s history, summarize support context, review a declined payment, evaluate renewal risk, identify chargeback threats, recommend retention actions, create notes, insert metadata, send emails, or trigger another workflow. The customer record gives AI Assistants business context. Instead of only asking the AI to interpret a single event, RevCent can give the assistant a customer-centered view of what happened and what may need to happen next. This supports workflows such as customer summaries, revenue recovery, support escalation, refund review, subscription save flows, and risk monitoring. ## Customers and AI Voice Agents AI Voice Agents also become more valuable when connected to customers. For inbound calls, customer context can help identify the caller and support questions about orders, shipments, subscriptions, refunds, or payments. For outbound calls, customer context can help decide who should be called, why they should be called, what the agent should discuss, and how the outcome should be recorded. Examples include calling a customer after a failed payment, following up on a subscription renewal issue, checking on a shipment problem, contacting a VIP customer, or assisting with a trial conversion. A voice conversation is much more useful when it is connected to the customer’s actual ecommerce history. ## Customers and Email Templates Email Templates can use customer context to personalize communication. Customer data can help businesses send more relevant messages such as receipts, onboarding emails, payment failure notices, renewal reminders, refund confirmations, shipment updates, winback offers, VIP messages, reorder reminders, and support follow-ups. Emails become more effective when they are based on the customer’s actual behavior: what they purchased, when they purchased, what failed, what shipped, what group they belong to, or what metadata applies to them. ## Customers and Functions Functions can use customer data to extend RevCent workflows with custom business logic. A Function might sync customer data to a CRM, enrich customer metadata, check an external loyalty system, notify a support team, create a task, call an external endpoint, or make a customer-specific decision before another workflow runs. Because customers connect to so many RevCent entities, Functions can use customer context as the starting point for business-specific automation. ## Customers and Reporting BigQuery makes customer data more valuable by allowing businesses to analyze customer behavior over time. The customer table itself includes identity, status, groups, metadata, relationship references, and lifetime value summaries. Other RevCent tables also connect back to customers, allowing customer-centered analysis across sales, transactions, refunds, products, subscriptions, renewals, trials, shipments, chargebacks, fraud detections, voice calls, and more. This means reporting can answer business questions such as: - Which customers have the highest lifetime value? - Which customers are repeat buyers? - Which customers are subscription customers? - Which customers have failed renewals? - Which customers have payment recovery opportunities? - Which customer groups generate the most revenue? - Which customers have high refund or chargeback risk? - Which customers are tied to specific products, campaigns, affiliates, or metadata segments? - Which customers are good candidates for winback, reorder, retention, or VIP outreach? - Which customer interactions were handled by AI Voice Agents or AI Assistants? This reporting value comes from the customer being a relationship hub, not merely a row in a table. ## Short-Term Customer Engagement Short-term engagement happens close to a customer event. Examples include a customer being created, a sale succeeding, a sale declining, a subscription renewal failing, a shipment shipping, a refund being created, a note being added, a trial expiring, or a chargeback occurring. Because the customer record is connected to these events, RevCent can support quick follow-up. A business can send an email, trigger an AI Assistant, call with an AI Voice Agent, create a note, add metadata, update a group, or notify a human. Short-term engagement is valuable because it happens while the customer moment is fresh. ## Long-Term Customer Engagement Long-term engagement uses accumulated customer history. A customer who has not purchased in 90 days, has high lifetime value, repeatedly buys a consumable product, has an overdue subscription, or belongs to a specific metadata segment may require a different long-term strategy. RevCent Customers make long-term engagement possible because the customer record accumulates behavior over time. This can support winback campaigns, reorder reminders, retention workflows, VIP programs, lifecycle marketing, subscription saves, and customer success outreach. ## Customer Data Enables Personalization Personalization is one of the biggest benefits of a centralized customer record. A first-time buyer may receive a welcome flow. A repeat buyer may receive loyalty messaging. A high-value customer may receive priority support. A customer with a failed payment may receive recovery outreach. A subscription customer may receive renewal reminders. A customer who bought one product may receive a related product offer. A customer with a support issue may receive a more careful follow-up. These experiences depend on knowing the customer and their history. ## Customer Data Enables Better Support Support teams need context to provide good service. A centralized RevCent customer record can help support teams understand who the customer is, what they bought, what they paid, whether they were refunded, whether they have subscriptions, whether shipments are open, whether a renewal failed, whether they have notes, whether they are VIP, and whether risk or chargeback context exists. This reduces repeated questions and improves support quality. It also helps human support and AI-powered support work together. AI Voice Agents can create notes from calls. Human agents can add notes that later guide AI workflows. AI Assistants can summarize customer history before a support decision. ## Customer Data Enables Revenue Recovery Revenue recovery depends on customer context. A failed payment, declined sale, pending sale, failed subscription renewal, or salvage opportunity becomes more actionable when the business knows who the customer is, what they bought, what they are worth, what payment history exists, and which communication channel may be appropriate. RevCent Customers help businesses recover revenue through email, AI Voice Agent calls, AI Assistant analysis, Functions, metadata, customer groups, and reporting. ## Customer Data Enables Smarter AI AI works better when it has relevant business context. Customer data gives RevCent AI tools the ability to reason about actual ecommerce history. AI can consider purchase behavior, lifetime value, support notes, subscription state, payment outcomes, refunds, customer groups, metadata, and risk signals. This allows AI Assistants and AI Voice Agents to make more useful decisions and provide more relevant support. A generic AI prompt can only guess. A RevCent AI workflow connected to customer context can reason from the business’s actual customer data. ## Customer Data Enables Segmentation Customer segmentation is how businesses turn many individual customer records into meaningful audiences. Segments can be based on customer groups, metadata, campaign, products purchased, subscription status, last purchase date, lifetime value, refund behavior, chargeback behavior, fraud detections, geography, notes, AI-generated classifications, or external IDs. Segmentation makes the customer record actionable. It helps businesses decide who should receive outreach, who should be excluded, who should be escalated, who should receive special offers, and who should be reviewed by a human. ## Customer Data Enables Automation Once customer data is centralized, automation becomes much more powerful. A business can add customers to groups after purchase, send email after key events, trigger AI Assistants for analysis, trigger AI Voice Agents for payment recovery, sync customer data to external systems, create notes after interactions, generate winback lists, identify high-risk customers, route support differently for VIPs, and update metadata after outcomes. The customer record becomes the common object that lets these automations work together. ## Best-Fit Businesses Customers are foundational for nearly every ecommerce business using RevCent, but the value grows as customer activity becomes more complex. Customer centralization is especially valuable for businesses with repeat purchases, subscriptions, trials, payment declines, refunds, chargebacks, customer support volume, shipping operations, AI workflows, customer segmentation, affiliate tracking, CRM integrations, or long-term customer engagement strategies. The more customer-related activity a business has, the more important the customer record becomes. ## Why This Matters in the RevCent Ecosystem Customers help make RevCent more than a transaction processor. They allow RevCent to become a customer-centered ecommerce operating system. Because customer records connect identity to sales, payments, products, subscriptions, shipping, risk, support, AI, and reporting, businesses can operate around the customer instead of around isolated events. This creates several ecosystem-level advantages: - Sales and payments can be understood as part of a customer relationship. - Support teams can act with full context. - Payment recovery can be prioritized by customer value and history. - Subscription workflows can support long-term retention. - Shipping and fulfillment issues can connect back to the customer. - Refunds, chargebacks, and fraud detections can be reviewed with customer context. - Metadata and customer groups can turn customer behavior into segments. - AI Assistants and AI Voice Agents can operate with real ecommerce context. - BigQuery can measure customer behavior and outcomes over time. - RevCent can serve as the central system for ecommerce operations, automation, AI, and customer intelligence. ## Summary RevCent Customers are foundational ecommerce records that centralize customer identity and connect it to the broader RevCent ecosystem. A customer in RevCent can relate to sales, product purchases, transactions, payment methods, subscriptions, renewals, trials, shipping, refunds, chargebacks, fraud detections, salvage transactions, notes, metadata, customer groups, tracking, AI Voice Calls, AI Assistants, Email Templates, Functions, Customer Portals, and BigQuery reporting. The most important concept is that the customer is one of RevCent’s primary relationship hubs. Customers help businesses understand behavior over time, support customers with context, recover revenue, personalize engagement, segment audiences, reduce risk, power AI workflows, and measure ecommerce outcomes. Use the technical links at the top of this file to distinguish between the main ways to interface with or analyze the item: Web App, API, MCP / AI, and BigQuery / Reporting. --- Document Parent Directory * [Items](https://revcent.com/documentation/markdown/ecosystem/item/index.md) - Non-technical markdown documentation for items within the RevCent ecosystem. An item is an entity that is spawned as a result of a feature or operation conducted within the RevCent ecosystem.