Your Allmoxy instance comes preloaded with thirty template triggers, completing various actions throughout the cabinet ordering and production processes!
- What are Triggers
- Layered Conditions
- Explanation of Trigger Conditions
- Trigger Actions
- Example Use Cases of Triggers
- Troubleshooting Triggers
What are Triggers?
Triggers are pre-built actions that can help automate multiple processes in your Allmoxy instance.
Your instance comes preloaded with thirty template triggers completing various actions throughout the order process. You can customize these or build your own! All of the template triggers are inactive until you activate them.
Layered Conditions:
Most trigger actions have the option to + Add Condition. This allows you to refine the trigger condition down to a specific product, product attribute, order tag, or specific shipping method. This ability exponentially increases the versatility of each trigger condition!
You can also use multiple layers, like a specific product AND a particular product attribute.
Here's a quick explanation of each Trigger Condition:
Order Status Changes To ➡️ Select Order Status:
This trigger will fire based on the status being changed in Allmoxy. Statuses can be changed manually, automatically through a recorded labor process, or through Allmoxy's expected workflow. You can refine this trigger by defining specific product tags to meet the trigger condition.
Remake Status Changes To ➡️Select Order Status:
This trigger follows the same rules as Order Status Changes To, except it only applies to Remake Orders. This is a great way to keep track of Remakes.
Order Process Started ➡️ Select Labor Process:
Utilizing this trigger condition will allow you to fire an action when a specific process is started. Use this to give another department an indication of where an order is in production, or delight your customers by notifying them of a particular phase in the production line.
This trigger is only available if you've built out your labor processes and are actively time-tracking through the scanning station.
Order Process Ended ➡️ Select Labor Process:
Similar to the condition above, the order process ended will fire when a process is completed.
This trigger is only available if you've built out your labor processes and are utilizing the Process Complete or Process Time Tracking functions in the scanning station.
Order Past Due ➡️Select Number of Days:
Utilize this condition to automate your collection process. You can set up multiple Order Past Due triggers with varying days to frequently remind customers of their past due balances. This trigger condition goes by the date payment is due based on what you set for "Default Status to Charge Customers" in financial settings.
This trigger does not allow for additional trigger conditions to be added.
For example, if your status to charge a customer is set to Shipped status and the payment is considered past due after that shipped date, then a trigger that is set to fire on Past Due by 1 day will send an email the day after a job is moved to Shipped status.
Payment Made:
Receive notification of customer payments, including the invoice numbers that were paid.
New Company Created:
Receive notification of new company accounts created. This is a great way to ensure new accounts get reviewed or to distribute new customers to a dedicated salesperson.
New Company Contact Created:
Receive notification of new company contacts created.
New Individual Created:
Receive notification of new individual created. Individual contacts are people who are not associated with a business.
New Product Created:
Alert your catalog owner of any new products created.
This is not recommended for announcing a new product to your customers, as it fires upon creation before the product has been properly configured.
New Supply Created:
Alert your inventory manager of any new supplies added.
New Remote Request:
Receive a notification if another Allmoxy user requests a B2B connection with you.
Note Created On ➡️Select an Item:
Receive a notification of any notes added to any of the following:
- company
- contact
- order
- product
- supply
Additional triggers will need to be created if you want notification on more than one of the above items.
Finance Charge Created:
Alert your accounting department or your customer if a finance charge invoice is created on an account.
Order Attachment Added:
Receive notification of any files attached to an order. This is especially helpful if your customers are uploading designs with their orders.
Ship Date Modified ➡️ Determine the Order Status(es) to Receive Notification:
Notify your customer or internal teams of an update to their shipped date. You can also restrict this trigger down to certain statuses, for example: email the customer if an In Progress order's ship date gets adjusted.
Credit Card Expires Soon ➡️Determine a Timeframe:
Notify customers of an upcoming credit card expiration.
Product Subscription Cancelled ➡️Failed Payment:
Alert a customer if their product subscription is canceled due to a failed (expired, unauthorized, etc) payment method.
Trigger Actions:
The trigger action is the thing that happens when a selected condition is met. Not all actions are available on every condition.- Send an email
- Send an SMS
- Add an announcement
- Add a task
- Add tags
- Remove tags
- Send a web request (webhook)
Here are a few use cases of various triggers:
- Automatically alert employees when an order is placed so they can verify it for production via email, text, or task alert.
- Notify an employee when a new customer creates an account so they can do follow-up tasks
- Automatically email customers about their order status
- Notify customers of an outstanding account balance automatically.
- Send an email automatically to the individual who placed an order.
Troubleshooting Triggers:
The company is not available as a trigger target.