Please be generous with your feature requests and upvote any that would be useful for you. We receive lots of requests and prioritise largely based on user demand.
Please note that if you post your name will display to other Upmind users.
Currently the Slack webhook URL can only be configured at brand level (Settings → Automation → Notification Channels), so ALL Slack notifications — support tickets, new orders, paid invoices, client registrations, fraud alerts — post to a single Slack channel. Request: allow overriding the Slack webhook URL per automation action (or per action category), falling back to the brand-level default when not set. Use case: route ticket notifications to #support-tickets, order/invoice notifications to #orders, and fraud/provisioning alerts to #alerts. In Slack, each channel has its own incoming webhook URL, so this only requires exposing the existing webhook URL field (already present at brand level) on the automation action itself. This would make Slack notifications far more usable for any team that separates operational workflows into dedicated channels — which is standard practice in Slack.
I’d like the ability to receive copies of all system notifications (e.g., invoices, ticket replies) in both my primary and secondary email addresses simultaneously. Currently, notifications only go to the default email. This helps ensure critical updates aren’t missed if the primary inbox has delivery issues, and allows teams to monitor communications across multiple addresses (e.g., admin@ + support@). We also can provide access to our agent for checking notification without giving account login information. Thank your for your attention.
Allow users to modify the default email subject for support tickets automatically created from invoice notes
Stripe Connect is the easiest method of managing affiliate payouts and sending out necessary tax documentation if a payout threshold is met. No other billing system has figured out or has considered to prioritize a way to integrate payouts aside from using PayPal; I’d love to see Stripe Connect integrated here.
Hi team, One of the chat staff noticed that the scheduled ticket is not showing as an ‘Active Ticket’ from the client side. It will only show if they select to view all tickets. Could you help adjust the scheduled ticket as an active ticket as well? This will make sure that the client is aware and that we are waiting for their response, while we can keep following up if they’re not responding yet. I attached one of the ticket examples also the screenshot for reference DOT-OVL-753-27246
We will add new hooks for when TaxTemplates and TaxTags are modified. These hooks help track changes more easily: tax_tag_created_hook tax_tag_deleted_hook tax_tag_locations_updated_hook tax_tag_updated_hook tax_template_created_hook tax_template_deleted_hook tax_template_tags_updated_hook tax_template_updated_hook
Import external emails into the email log so that they show in the email history log.
(and which are active/not currently active) At the moment, you can go to a product and see the notifications attached to it. But you can’t do it the other way around and go to a notification and see which products use it Is this possible?
It would be very nice to have the ability to connect to a third party SMS service so that when a high priority ticket comes in, a text message is sent to the agent on duty. Maybe setup a way to check a box to enable which agent(s) are on call at the time, so you can switch which agent(s) will receive the text messages easily. (Sort of like PagerDuty)
Set up email piping to automatically forward emails to a specific user within the system This would allow a brand to have for instance [name]@brand.com pipe to the ticket system and have the ticket assigned to a specific user.
This feature ensures that the formatting of HTTP responses, including spaces, tabs, and line breaks, remains unchanged within the Webhook Event log modal. By preserving whitespace integrity, users can accurately review and interpret response data without any loss of formatting
When an email template is deleted, this update ensures that any associated triggers are also removed. This keeps your system clean and organized, preventing any unnecessary mappings or conflicts.
On PDF regeneration (because of status change for example) fire new hook - instead of PDF created - PDF regenerated
When Credit Notes are paid, they get the Invoice Payment Received email – this should be a separate trigger.