Free
Introduction
This detailed overview explains the "Order Received" trigger within an automation system, focusing on how it activates and how to utilize it effectively.
The trigger is essential for automating responses and actions after a customer completes a purchase.
Understanding its mechanics enables businesses to streamline communication, gather valuable data, and enhance customer experience. This summary covers the trigger's activation points, data access, customization options, and future functionalities related to payment collection.
In-Depth Explanation of the "Order Received" Trigger
What is the "Order Received" Trigger?
The "Order Received" trigger activates when a customer completes a purchase on your platform. Specifically, it fires at the moment when:
The customer views the product.
The customer adds the product to the cart.
The customer clicks the submit button to finalize the order.
The customer leaves a message (if applicable) during checkout.
The customer submits the order, which sends data back to your chat or automation system.
This trigger is designed to capture the moment an order is confirmed, allowing you to automate follow-up actions such as sending confirmation messages, updating records, or initiating payment processes.
How to Identify When the Trigger Fires
The trigger activates upon the submission of an order, which involves several user actions:
User Action | Trigger Activation | Description |
---|---|---|
Viewing product | No | Just viewing does not trigger it. |
Adding product to cart | No | Only when the order is finalized. |
Clicking the submit button | Yes | When the customer submits the order, the trigger fires. |
Leaving a message during checkout | Yes | If a message is left, it is captured at this point. |
Submitting the order | Yes | The key event that activates the trigger. |
How to Create and Use the Trigger
To set up the "Order Received" trigger:
Navigate to the Automation section.
Create a new trigger.
Select "Order Received" as the trigger type.
Configure actions to execute once triggered, such as sending messages, updating custom fields, or initiating payment collection.
Capturing Customer Messages
Customers can leave messages during checkout, which are captured and stored within the system. These messages can be:
Saved into custom fields for later reference.
Used to personalize follow-up communications.
Analyzed for customer feedback or specific requests.
Accessing Order Data
The system provides comprehensive access to order details through system fields. These include:
Data Point | Description | Example |
---|---|---|
Order ID | Unique identifier for the order | 123456 |
Order Number | Sequential number of the order | ORD-7890 |
Total Price | Final amount paid | $150.00 |
Subtotal | Price before taxes and discounts | $130.00 |
Tax | Tax amount applied | $10.00 |
Discount | Any discounts applied | $5.00 |
Delivery Fee | Shipping costs | $5.00 |
Currency | Transaction currency | USD |
Quantity | Number of items purchased | 3 |
These details are accessible via system variables and can be integrated into messages, stored in custom fields, or used for analytics.
How to Access and Save Data
When configuring automation actions:
Select "Custom Fields".
Choose "System Fields" related to the order.
Map the data points to custom fields for future reference or personalized messaging.
For example, you can save the order message into a custom field to review customer feedback later.
Future Functionalities and Next Steps
The current system allows for capturing order data and messages effectively. Moving forward, the next focus will be on payment collection, which involves:
Calculating the total price.
Generating checkout links for various payment gateways like Stripe, PayPal, or local payment methods.
Enabling customers to pay directly through these links.
Sending immediate confirmation upon successful payment.
This upcoming feature will streamline the purchase process, reduce manual intervention, and improve customer satisfaction.
Summary Table: Key Points of the "Order Received" Trigger
Aspect | Details |
---|---|
Activation Points | Viewing product, adding to cart, submitting order, leaving message |
Data Access | Order ID, number, total, subtotal, tax, discount, delivery, currency, quantity |
Customization | Save messages and data into custom fields |
Future Enhancements | Payment collection via checkout links |
Final Thoughts
Understanding the "Order Received" trigger is vital for automating post-purchase workflows. It provides a reliable way to respond to customer actions, gather valuable data, and prepare for future functionalities like payment processing. Proper configuration ensures seamless communication, personalized customer experience, and efficient order management.
By leveraging this trigger effectively, businesses can automate routine tasks, improve operational efficiency, and foster stronger customer relationships. As the system evolves to include payment integrations, the automation capabilities will expand further, offering a comprehensive solution for online sales management.