web
You’re offline. This is a read only version of the page.
close
  • Include an auto-sort feature for font list

    Please include an auto-sort feature for the font list drop down menu, so when user add additional fonts, the font list automatically sort them in alphabetical order.

  • Implement a quote reply feature for Omnichannel chat

    Currently, the Omnichannel chat does not have the ability to quote reply, similar to the Teams chat feature. With the availability of persistent chat, a long conversation can be quite hard to narrow down the original message without a quote reply, making both parties have to scroll up and down mid conversation can be distracting.

  • Enable Batch Attendee Registration in Event API for Real-Time Marketing

    Current Limitation:

    The Event API for Real-Time Marketing does not support submitting multiple attendees in a single POST request.

    Currently, each attendee must be registered individually, requiring multiple POST calls. This creates inefficiencies and significant friction for scenarios such as paid registrations, where a registering multiple attendees for a paid event requires the submission of payment details multiple time.

     

    Requested Enhancement:

    • Allow batch submission of attendees using an array in a single POST request.
    • Maintain backward compatibility with Outbound Marketing functionality, which already supports multi-attendee registration.
    • Provide configuration options so admins can enable or disable batch submission based on organizational needs.

     

    Business Impact:

    • Improves efficiency for enterprise-scale events by reducing repetitive API calls.
    • Enhances user experience for paid registrations, avoiding multiple payment entries.
    • Aligns with customer expectations for modern API design and parity with Outbound Marketing.
    • Reduces custom development and accelerates adoption of Real-Time Marketing features.


  • Field Service - Auto fill latitude and longitude for records

    Current behavior:

    When a Functional record is set up, and Bing map integration is set up, each record will have to manually be opened and 'Geo code' command has to be clicked to fetch the longitude and latitude coordinates of the address.


    Business Impact:

    For organization with multiple locations, this requires users to have to manually go through the process to retrieve and save the coordinates to the records.


    Enhancement request:

    Since the system already has a function to fetch the coordinates, please consider adding an asynchronous trigger to fetch these coordinates, for example: on address field being updated.


    Benefit:

    This will let the data be pulled automatically, and reduce manual labor. Additionally, coordinates are often used for geo fencing service areas, so this will allow a smoother workflow for service providers.


  • Improvement to Sales application's Dynamic Marketing List

    Improvement request to how Dynamic Marketing List member list is generated and stored in database


    Current behavior:

    Dynamic Marketing List member list is generated each time we navigate to Marketing List > Members tab via a fetch query.

    This does not generate relationship between target audience records (Contact / Account / Lead) and Marketing List.

    When clicking on audience record > Related > Marketing list, the view only displays audience inclusion for Static list, not Dynamic list.


    Enhancement request:

    We'd like to have the Dynamic list generate a relationship between the records, so that we can view the audience's participant via Related view.


    Business Impact:

    This will greatly improve data readability for users.