Showing posts with label Time To Upvote -Series. Show all posts
Showing posts with label Time To Upvote -Series. Show all posts

Saturday, 26 August 2017

[#Blogged] Time To Upvote -Series (Part 2)

Here we have some idea's which need to be upvoted :
IDEA 1 - 
Enable drag & drop functionality for lightning Calendar
Salesforce classic calendar supports drag and  drop off events.
Lightning has a much more dynamic user interface, but it still lacks this basic functionality which keeps many customers from managing their calendars entirely in Salesforce.
Upvote

IDEA 2 -
Allow new chats to load in the background, without monopolizing agent focus
Current behavior: When a new chat is accepted, the new chat monopolizes the agent focus, and the agent is not able to continue chatting or performing after-chat work. It brings the agent to the new chat tab, even though it takes ~ 5 seconds to load all 3 chat sub-tabs (chat, contact, case). Even once the 3 chat sub-tabs load, the user often takes a while (sometimes up to a couple minutes), to type out their question, so staying on the new chat tab is not usually the best use of agent time.
Desired behavior: When a new chat is accepted, the new chat should load in the background, allowing the agent to continue working on the other chat(s) they have open. The new chat should *not* force the agent to sit there and watch the 3 chat sub-tabs load. After working a little more on the open chats, the agent can check back on the new chat, and see how far along the customer is in composing their question. This is less disrupting to the agent workflow and maximizes agent control and efficiency.
Note: We've been told by the Live Agent PM that this is desired/expected behavior of the product. However, having observed agents in the field using Live Agent over the course of 1 week, I am confident that this is not desired behavior, and it is much preferred that the new chat *not* monopolize focus, and force the agent to sit there and watch the 3 sub-tabs load.
IDEA 3 - 
Allow Direct link to a Process Builder Process
When working with clients and/or other admins I need to be able to reference the specific process builder that I would like them to look at.  Right now the link available to me is the link that displays all of the processes.
Ideally, we should be able to send a link that opens up to the specific process. This could be something similar to what is available in the Service 

IDEA 4 - 
Pardot Merge Prospects via API
Hi All,
I've gone through the pardot API documentation, but have not found anything related to merging/deduplicating pardot prospects through the pardot API. We have a scenario where we are getting a lot of duplicates in our pardot instance. And also we have defined criteria of considering which of these prospects are duplicates.Since this number is huge, we wouldn't want to spend hours manually merging all of these duplicate prospects. Would be glad if Pardot rolls out an additional method within its APIs.
Please vote up this idea if you're facing the same issue.

Saturday, 13 May 2017

[#Blogged]Time To Upvote -Series (Part 1)

Here we have some idea's which need to be upvoted :

Idea 1 
Make the Manage External User button available in lightning

Currently the Manage External User button and the nested buttons it hosts are not available in the lightning user interface, as a result users have to switch between lightning and salesforce classic to access the functionality, another drawback to lightning as having to toggle back and forth between two different interfaces undermines the value of lightning.  Please make the manage external user button and the nested buttons it hosts available in lightning


Upvote 

Idea 2

Choose Who To Send Flow Fault emails and Process Builder Error Emails to
The notifications currently go to the user who built the flow or process builder.
I am currently in a situation where the original user who created the flows in Sandbox and deployed them is no longer active. I therefore must change his email in order to receive the error messages on existing flows.


Idea 3 
Increase the limit on the number of reports a user can subscribe to
The new report subscription feature is really nice, but only being able to subscribe to 5 reports is not helpful.  Most users who want to subscribe to reports want to do this for at least 10 - 15 reports.  I'm not sure why the limit is hard-coded to be 5 but having a higher limit (like 25?) would be much appreciated.

Upvote 

Idea 4 
Process Builder: Error messages
Process Builder works great, but when there is a validation error or any other error, it doesn't provide the much information to user and user will never know how to resolve that issue.
Admin gets an email for this exception with the proper message, but if we can improve the error messages for the end user also, that would be great.