Feature Request: Update WooCommerce Order Status When a FluentSupport Ticket Is Closed
Our customer uses FluentCRM and FluentSupport together to manage WooCommerce orders. They handle order customizations through FluentSupport β when a new order comes in, a support ticket is automatically created.
Problem:
There is currently no way to automatically update the WooCommerce order status when the associated FluentSupport ticket is closed. The workflow is one-directional: an order can trigger a ticket, but closing the ticket cannot update the order back.
Requested Feature:
Add an automation action (or trigger-based option) in FluentCRM that allows updating a WooCommerce order status when a FluentSupport ticket status changes β specifically when a ticket is closed or resolved.
Example Workflow:
- New WooCommerce order β FluentSupport ticket is created automatically
- Team works on the order customization via the ticket
- Ticket is closed β WooCommerce order status automatically updates (e.g., to βPrintingβ or a custom status)
This would close the loop between FluentSupport and WooCommerce, making the integration significantly more useful for teams that manage order fulfillment through support tickets.
You can do this with the custom hooks and filters that are available. Requires a tiny bit of custom code, but will be easier to setup and manage.
Hi Taylor Drayson,
Thanks for your reply. We're a design agency and don't have any experience on PHP coding. This might be easy for who knows PHP but it's hard to handle for us.
Tolga AltasΒ I understand that, AI could probably get you pretty close.
I generated these 2 snippets with AI, and haven't tested, but it's along the right lines.
This is triggered on ticket close and updates the latest order from the user. https://snippets.tdrayson.com/ovwb9q/
This triggers on ticket close and also tries to find an order ID in the ticket title, something like "#1234" or "order 1234"
Not sure or your setup, but it's pretty niche and even with the automation feature, you would still run into the same issue where FluentCRM doesn't know what order it should be updating etc