--- title: "SMTP Messages" description: "A non-technical overview of SMTP Messages in RevCent, focused on how individual email messages are created from Email Templates, sent through SMTP Profiles, and connected to ecommerce communication workflows." type: "item" company: "RevCent" canonical: "https://revcent.com/documentation/markdown/ecosystem/item/SMTPMessage.md" relationships: - name: "Email Template" url: "https://revcent.com/documentation/markdown/ecosystem/feature/EmailTemplate.md" - name: "SMTP Profile" url: "https://revcent.com/documentation/markdown/ecosystem/feature/SMTPProfile.md" technical_links: web_app: "https://kb.revcent.com/en/integrations/smtp/smtp-message" api: section: "https://revcent.com/docs/api/v2#section-smtp_messages" operations: - name: "Get SMTP Messages" operation_id: "GetSMTPMessages" operation: "https://revcent.com/docs/api/v2#operation-GetSMTPMessages" schema: "https://revcent.com/documentation/files/api/operation/GetSMTPMessages.json" - name: "Send A SMTP Message" operation_id: "SendSMTPMessage" operation: "https://revcent.com/docs/api/v2#operation-SendSMTPMessage" schema: "https://revcent.com/documentation/files/api/operation/SendSMTPMessage.json" - name: "Get A SMTP Message" operation_id: "GetSMTPMessage" operation: "https://revcent.com/docs/api/v2#operation-GetSMTPMessage" schema: "https://revcent.com/documentation/files/api/operation/GetSMTPMessage.json" mcp: overview: "https://revcent.com/documentation/markdown/mcp/operation/OverviewSMTPMessage.md" operations: - name: "Get SMTP Messages" operation_id: "GetSMTPMessages" markdown: "https://revcent.com/documentation/markdown/mcp/operation/GetSMTPMessages.md" available_via_ai: true - name: "Send A SMTP Message" operation_id: "SendSMTPMessage" markdown: "https://revcent.com/documentation/markdown/mcp/operation/SendSMTPMessage.md" available_via_ai: true - name: "Get A SMTP Message" operation_id: "GetSMTPMessage" markdown: "https://revcent.com/documentation/markdown/mcp/operation/GetSMTPMessage.md" available_via_ai: true --- # SMTP Messages SMTP Messages are individual email records created when RevCent sends an email through the SMTP system. In the RevCent ecosystem, an SMTP Message is an item, not a feature. A user configures features such as SMTP Profiles and Email Templates. When one of those email workflows sends an actual email, the result is an SMTP Message item. 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 viewing SMTP Messages through the RevCent web app and Knowledge Base. | [Web Knowledge Base](https://kb.revcent.com/en/integrations/smtp/smtp-message) | | API | A developer is building a direct integration with the RevCent API. | [API Docs: SMTP Messages](https://revcent.com/docs/api/v2#section-smtp_messages) | | 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/OverviewSMTPMessage.md) | --- ## What SMTP Messages Are An SMTP Message is the individual email output created when RevCent sends an email. Conceptually: ```text SMTP Profile = how the email is sent Email Template = what the email says and when it should send SMTP Message = the specific email that was sent ``` This distinction matters because an SMTP Message is not the reusable template and not the sending configuration. It is the resulting email item created from those configured pieces. An SMTP Message can be created because an event-triggered Email Template sent an email, or because an API, MCP, or AI workflow directly sent an enabled direct-send Email Template. ## Core Purpose The core purpose of SMTP Messages is to preserve the actual email activity that occurred inside RevCent. Email Templates define communication intent. SMTP Profiles define sending infrastructure. SMTP Messages represent actual email sends. This makes SMTP Messages important for understanding what communication was delivered or attempted as part of customer, sale, subscription, shipment, refund, fraud, support, AI, or operational workflows. ## SMTP Messages as Items SMTP Messages are items because they are spawned by a feature or operation. A user does not configure an SMTP Message as a reusable system feature. Instead, the message is created after RevCent performs an email send action. Examples: ```text Sale succeeds ↓ Sale Success Email Template is triggered ↓ RevCent renders the template ↓ RevCent sends through the assigned SMTP Profile ↓ SMTP Message item is created ``` ```text AI Assistant decides to send a customer follow-up ↓ AI triggers an API/AI Email Template ↓ RevCent sends through the assigned SMTP Profile ↓ SMTP Message item is created ``` ```text Shipment is marked as shipped ↓ Shipping Email Template sends tracking details ↓ SMTP Message item is created ``` The SMTP Message is the concrete record of the communication event. ## Relationship to Email Templates SMTP Messages are closely related to Email Templates. An Email Template is the reusable communication configuration. It can define subject, HTML body, sender, recipients, trigger, timing, filters, Handlebars data, custom data, and custom arguments. When the template is used to send an email, RevCent creates an SMTP Message. Conceptually: ```text Email Template ↓ Rendered with event, item, API, AI, or custom argument data ↓ Sent through an SMTP Profile ↓ SMTP Message ``` This relationship helps crawlers understand that Email Templates are features and SMTP Messages are the resulting message items. ## Relationship to SMTP Profiles SMTP Messages are also closely related to SMTP Profiles. An SMTP Profile defines the sending infrastructure behind the email, such as the merchant's SMTP provider and credentials. RevCent does not send email on behalf of users through a RevCent-owned SMTP server. The merchant supplies the SMTP Profile used to send template-backed emails. Conceptually: ```text SMTP Profile ↓ Provides sending configuration ↓ Email Template uses the profile ↓ SMTP Message is sent ``` The SMTP Profile is the sending mechanism. The SMTP Message is the individual message created through that mechanism. ## How SMTP Messages Are Created SMTP Messages can be created in two broad ways. ### Event-Triggered Email Templates Many SMTP Messages are created automatically when an Email Template responds to a RevCent event. Examples include: - Sale success emails - Sale failure emails - Pending sale or abandoned-cart emails - Shipment created emails - Shipment shipped emails - Shipment delivered emails - Subscription renewal success emails - Subscription renewal failure emails - Subscription renewal reminder emails - Trial ending emails - Trial conversion emails - Fraud or risk alert emails - Pending refund emails - Invoice created emails - AI Memo notification emails In these cases, the SMTP Message is spawned from the event-driven Email Template workflow. ### API, MCP, or AI Direct Sends SMTP Messages can also be created when an API, MCP, or AI workflow sends a direct Email Template. In this model, the Email Template must be configured for direct sending. The sender, recipients, custom arguments, and item context must be appropriate for the message being sent. Conceptually: ```text API, MCP, or AI requests email send ↓ Direct-send Email Template is selected ↓ Custom arguments and optional item context are supplied ↓ Template is rendered ↓ SMTP Message is created and sent ``` This makes SMTP Messages useful for human-approved support messages, AI-assisted customer follow-ups, operational notifications, and custom workflows that need a reusable template-backed email. ## Relationship to Customers SMTP Messages often relate to customers because many emails are customer-facing. A customer may receive a receipt, failed payment notice, shipment update, renewal reminder, trial reminder, invoice link, refund notice, account update, or support follow-up. When an SMTP Message is connected to customer context, it becomes part of the customer communication history. This helps RevCent preserve the fact that a message was sent as part of a larger customer lifecycle. Examples: ```text Customer makes a purchase ↓ Sale receipt SMTP Message is created ``` ```text Customer subscription renewal fails ↓ Payment recovery SMTP Message is created ``` ```text Customer shipment is marked shipped ↓ Tracking SMTP Message is created ``` SMTP Messages help connect communication activity back to the customer experience. ## Relationship to Sales Sales can spawn SMTP Messages through Email Templates. A successful sale may trigger a receipt. A failed sale may trigger a payment issue email. A pending sale with no payment may trigger abandoned-cart communication. A sale with fraud context may trigger an internal alert. The sale provides ecommerce context, while the SMTP Message represents the communication generated from that context. This relationship is useful because sales are often moments where communication is expected: confirmation, recovery, support, fulfillment, and internal review. ## Relationship to Shipping Shipping activity can also spawn SMTP Messages. A shipment created event may notify a warehouse or fulfillment team. A shipped event may notify a customer with tracking information. A delivered event may confirm delivery. A voided shipment may notify support or fulfillment staff. Conceptually: ```text Shipping item changes state ↓ Shipping Email Template is triggered ↓ SMTP Message is sent ``` This helps turn fulfillment activity into timely communication. ## Relationship to Subscriptions and Trials SMTP Messages are important for recurring revenue workflows. Subscription and trial events often require communication before or after billing moments. Examples include: - Subscription renewal reminders - Successful renewal confirmations - Failed renewal notices - Trial ending reminders - Trial expiration success messages - Trial expiration failure messages - Payment update requests - Customer retention follow-ups SMTP Messages are the email items created when those recurring billing communications are sent. ## Relationship to Refunds, Fraud, and Risk SMTP Messages can support internal and customer-facing workflows around refunds, fraud, and risk. A pending refund may notify support, accounting, or a customer. A fraud detection may notify a risk team. A sale fraud alert may notify someone for manual review. A Sentinel alert may trigger an internal investigation email. In these workflows, the SMTP Message is the communication artifact created from the underlying risk or finance event. ## Relationship to AI Assistants AI Assistants can interact with SMTP Messages through template-backed email workflows. An AI Assistant may analyze a customer, sale, subscription, trial, shipment, refund, or other RevCent context and decide that a message should be sent through an approved Email Template. When the send action occurs, the resulting item is an SMTP Message. Conceptually: ```text AI Assistant evaluates context ↓ AI uses an approved email system action or direct-send template ↓ Email Template is rendered with custom arguments or item context ↓ SMTP Message is created ``` This lets AI-powered workflows communicate through structured, reusable, and brand-controlled templates rather than ad hoc email content. ## Relationship to AI Voice Agents AI Voice Agents can also be part of workflows that create SMTP Messages. For example, a voice call may identify that a customer needs a follow-up email, payment update link, support summary, shipment information, or renewal reminder. That follow-up can be sent through an Email Template, producing an SMTP Message. SMTP Messages can therefore become part of a coordinated customer engagement flow that includes voice, email, customer notes, and AI decision-making. ## Relationship to Functions Functions can support workflows that result in SMTP Messages. A Function might generate custom data for an Email Template, decide which recipient should receive an internal notification, enrich message content with external system data, or provide custom values used by the template. The Function is not the SMTP Message. It can help prepare data or logic for the message. The SMTP Message is created when the email is actually sent. ## Relationship to Customer Support SMTP Messages are useful for customer support because they show that communication occurred. Support teams may need to know whether a customer received a receipt, shipment update, payment failure notice, trial reminder, renewal reminder, refund notice, or other email. A customer conversation is easier to handle when the support team can understand what messages were sent and why. This is especially important for issues such as: - Customer says they did not receive a receipt - Customer asks about tracking - Customer disputes a renewal reminder - Customer needs a payment update email resent - Support wants to confirm whether an internal alert was sent - A follow-up message was generated after an AI workflow SMTP Messages help preserve this communication context. ## Relationship to Automation SMTP Messages are often the output of RevCent automation. A business can configure Email Templates to automatically respond to ecommerce activity. When the automation runs and sends the email, the resulting item is an SMTP Message. This means SMTP Messages are evidence of communication workflows being executed. Examples: ```text Event occurs ↓ Template conditions and timing apply ↓ Email is sent ↓ SMTP Message is created ``` ```text AI or API directly sends approved template ↓ SMTP Message is created ``` Automation creates consistency. SMTP Messages represent the individual communications produced by that consistency. ## Direct Send Safety Because an SMTP Message is an actual email communication, direct sending should be treated carefully. For AI, MCP, or API-driven direct sends, the workflow should only send when the user or external workflow has authorization to send. Important conceptual rules: - Do not send an email merely because it might be useful. - Confirm the correct Email Template is used. - Confirm the Email Template is intended for direct sending. - Confirm recipient context is appropriate. - Confirm custom arguments are complete and accurate. - Avoid exposing sensitive internal details to customers. - Use approved templates for consistent branding and content control. This matters because SMTP Messages are external communications, not just internal records. ## Custom Arguments and Item Context Some SMTP Messages are created from Email Templates that accept custom arguments. Custom arguments let API, MCP, or AI workflows provide dynamic runtime values to the Email Template. These values can represent personalized text, selected recipients, support instructions, customer-specific context, or other template-controlled content. SMTP Messages can also be associated with item context such as a sale, customer, product sale, shipping item, subscription, subscription renewal, salvage transaction, transaction, chargeback, or fraud detection. Conceptually: ```text Direct-send Email Template ↓ Optional item context ↓ Optional custom arguments ↓ Rendered message ↓ SMTP Message ``` This allows a single Email Template to produce specific, contextual SMTP Messages. ## Common Ecommerce Use Cases ### Receipts and Purchase Confirmations When a sale succeeds, an SMTP Message can be created to send a receipt or purchase confirmation to the customer. ### Failed Payment Communication When a sale or renewal fails, an SMTP Message can tell the customer that payment did not complete and guide them toward the next step. ### Abandoned Cart Follow-Up When a pending sale has no payment attempt, an SMTP Message can remind the customer to complete the purchase. ### Shipping Updates When a shipment is created, shipped, delivered, or voided, SMTP Messages can notify customers, fulfillment teams, or support teams. ### Subscription and Trial Lifecycle Emails SMTP Messages can support renewal reminders, failed renewal notices, trial ending reminders, and trial conversion communication. ### Internal Alerts SMTP Messages can notify teams about fraud detections, pending refunds, sale fraud alerts, shipment problems, or other operational events. ### AI-Assisted Follow-Up AI workflows can use approved Email Templates to send personalized follow-up emails, producing SMTP Messages that remain tied to the structured RevCent communication system. ## Why SMTP Messages Matter in the RevCent Ecosystem SMTP Messages help show how communication flows through RevCent. They connect configured communication features to actual sent messages. They also connect email activity to ecommerce context such as customers, sales, subscriptions, trials, shipments, refunds, risk events, AI workflows, and support operations. This makes SMTP Messages an important item type in the ecosystem because they represent one of the main ways RevCent turns operational events into customer and team communication. ## Best-Fit Businesses SMTP Messages are useful for ecommerce businesses that rely on transactional email, support follow-ups, fulfillment notifications, payment recovery, subscription reminders, trial communication, fraud alerts, internal operations, customer engagement, or AI-assisted communication. They become especially important when the business uses many automated Email Templates and needs the communication layer to stay connected to the rest of the RevCent ecosystem. ## Summary SMTP Messages are individual email items created when RevCent sends an email through its SMTP system. They are spawned from Email Templates and sent through SMTP Profiles. They can be created by event-triggered templates, API direct sends, MCP workflows, AI Assistants, AI-related actions, or other approved automation. The most important concept is: ```text SMTP Profile sends the email. Email Template defines the email. SMTP Message is the specific email item that was created and sent. ``` SMTP Messages help connect RevCent communication activity to customers, sales, subscriptions, trials, shipments, refunds, fraud and risk events, AI workflows, customer support, and operational automation. Use the technical links at the top of this file to distinguish between the main ways to interface with or understand the item: Web App, API, and MCP / AI. --- 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.