It would be great if a teammate could assign a Due Date for when a reply needs to go out for a specific conversation. We could tie in the Due Date with existing SLA rules, or issues notifications if the Due Date passes without a response from the ...
Custom fields are currently limited to just 50. We would like to increase this to store additional customer data to trigger workflows and surface relevant context to our team
Add a new custom field type: Link. It is a clickable text with a URL. Customers using dynamic objects asked for it and it can also be used for other objects like contacts and accounts.
Allow admins to design shared signatures where the image is individualised to the teammate. The image may be personal like a headshot or signature, or could be dependent on the team they belong to. This could be achieved through a new "image type"...
Some custom fields are meant to be used by rules or automations only, and not be manually edited by users. How could we allow admins to prevent certain custom fields being manually edited?
Ability to generate contact lists dynamically based on custom fields
Instead of having static contact lists, they should be dynamically updated based on contact lists. This will ensure that the right people are getting emailed every time without having to remember to manually update organizational changes. For exam...
Add custom fields for more resources: Company, Workspace Add more custom fields types: Tag List, ... This can unlock many scenarios that need a centralised record of constants: incident management with IMs, advanced rules scenarios etc.
Allow non-company admins to create and manage custom fields
Today, only a company admin has the ability to create, edit and delete custom fields. This can prevent trusted Workspace admins from setting up the Workflows they need autonomously. How could we allow more users to set up custom fields?