Customer Feedback

We love feedback from you on our products and the problems in your daily work that you would like us to solve. Please describe the challenge you're encountering and your desired outcome. Be as detailed as possible.

For technical issues or bugs please head to Support or our Developer Community. You can assign up to 20 votes in total. Thank you for your feedback.

Status explanation: 'Future Consideration' = Continuing to collect further feedback, not planned at this time. 'Investigating' = Prioritized for deeper customer and feasibility investigations ahead of planning development.

ADD FEEDBACK

All feedback

Showing 1815

Sales Represtative not able to set default customer and is required to select bill to and ship to address on every log in.

When using the sales representative functionality they are no longer able to attach their user record to customers nor are they able to utilize the default customer functionality on the user record. Since our sales reps have hundreds of customers ...
over 2 years ago in Configured Commerce / CMS, Spire & Mobius 1 Investigating

The option to search a term/word used on the website that’ll pull through all the pages where it’s mentioned on the website and allow you to export the results into an excel spreadsheet.

This is critical for searching terms we can no longer mention such as a client name on the website and then we can manage where it's referenced and reduce risk for the firm.
over 2 years ago in Content Management / Reporting 0

API: Provide Readable Object IDs

Currently, the platform provides a persistent ID for label groups and labels values but those are not user-friendly, which makes troubleshooting and development complicated and prone to errors. Having the ability to define at time of creation or m...
over 2 years ago in Content Marketing / Integrations 0 Future consideration

Versions in Web Proofing

We love the new feature to upload URL, but would like to be able to upload versions of it so we don't lose comments and we'd like to be able to name the URL in case there are many in order to differentiate.
over 2 years ago in Content Marketing / Tasks, Campaigns, and Events 0 Future consideration

Form element creation behaves differently from block creation

When creating new form elements, edit UI does not ask to edit element’s fields. This is different from creating new blocks where UI also notifies about using some other name for the content than the default: “Consider renaming the content to somet...
over 2 years ago in Content Management / Forms 0

Allow for custom 404 page for missing user file paths

We are already using the OOTB 'Page not found' page. This works for root level pages. However, when trying to access a missing document located in a subdirectory, the resulting page is a standard, unstyled 404 page instead of the customized Spire ...
over 2 years ago in Configured Commerce / CMS, Spire & Mobius / Technical 1 Gathering interest

Task Creator Notifications

In our org, the task creator is responsible for driving the task to completion, but they may not be part of the workflow, and so are not considered an assignee. It would be great if we could choose a set of notifications for the task creator, as y...
over 2 years ago in Content Marketing / Notifications 0 Future consideration

Priority Workflows

In contrast to normal Workflows, Priority Workflows would automatically send daily notifications to each step’s owner so that the risk of high-priority work being late is minimized. The notification system here would override the notification sett...
over 2 years ago in Content Marketing / Tasks, Campaigns, and Events 0 Future consideration

Hover over feature on asset for the Save to Library pop-up

Our team finds it difficult to know which assets are being saved to the Library when choosing them on the content tab. It is difficult to know which asset is which. I'd like to suggest a hover over feature or scroll feature in order to see the ent...
over 2 years ago in Content Marketing / Tasks, Campaigns, and Events 0 Future consideration

Make React SDK Provider less brittle

React SDK provider should just be a context provider with its own useOptimiselyContext hook for getting and setting context. If setting the client and user id were separated either with their own functions or even when initialising context somehow...
over 2 years ago in Feature Experimentation 0 Future consideration