You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Back and forth between leads is not very effective
It isn’t easy to hop from one deal to another. The only way is to go back to the list view and find the next deal in the queue. But even then, we lose track of the sequence because there is no way to know which deal was just opened. ERPNext used to “unbold” the names of the fields after they were just opened which was helpful.
When a deal is opened, Instead of scrolling down to the last conversation all the time, can we change the sort order to “latest first”, having the screen auto-scroll down to the last conversation is overwhelming. Similarly, when we go back from the deal view to the list view, the list view goes back on top and then auto-scrolls down, instead of a persistent list view.
Just like email management, these two improvements will help save a lot of cognitive burden. And also relevant for helpdesk @ritvik Sardana
Frappe CRM | ERPNext / Frappe Framework
-- | --
|
When a customer replies the deal’s communication status does not change to “opened”
I noticed this bug. Whenever a customer replies to an existing conversation in the deal the communication status is not automatically “opened”, and continues to stay “replied”, plus the SLA does not apply to the subsequent reply expected from the sales team. I can only imagine without this, it might be a complete nightmare for sales agents to track which deal to focus on.
Default subject line
The default subject line for any deal currently is “Name of the lead (CRM DEAL ID)”. The sales team changes this subject line every time because the default subject line does not make any sense. Also, I have seen many cases when people have forgotten to change the subject and been conversing with the same subject line. This isn’t ideal. The subject line should be configurable, maybe we can set it to “Lead’s Org name <> Frappe”
The email and contact of the deal are not visible by default (and the expand option is not intuitive), can we expand by default?
One-click easy filters to operate effectively
For Frappe CRM to be effective there should be an easy way for sales agents to work on the deals. Stripe is just one example (video below), many SaaS tools have one-click filters to make help agents work effectively. For example, an agent will first focus on all “Ready to close” deals, followed by “quotation”, followed by “negotation” and so on. This is effective for agents because the jobs to be done for leads in each stage are different. This is again relevant for helpdesk (cc: @ritvik Sardana)
Ask country code in the lead form
This is a small one but we don’t do it. :( In the phone number field of Contact-Us / Trial signup, can we please add the country code drop-down? This makes it easy to make the call directly from CRM.
Sending task reminders
I heard from the sales team that when they create a follow-up task, the notification is not received over email. Small thing, but let’s fix it.
The text was updated successfully, but these errors were encountered:
Back and forth between leads is not very effective
It isn’t easy to hop from one deal to another. The only way is to go back to the list view and find the next deal in the queue. But even then, we lose track of the sequence because there is no way to know which deal was just opened. ERPNext used to “unbold” the names of the fields after they were just opened which was helpful.
When a deal is opened, Instead of scrolling down to the last conversation all the time, can we change the sort order to “latest first”, having the screen auto-scroll down to the last conversation is overwhelming. Similarly, when we go back from the deal view to the list view, the list view goes back on top and then auto-scrolls down, instead of a persistent list view.
Just like email management, these two improvements will help save a lot of cognitive burden. And also relevant for helpdesk @ritvik Sardana
Frappe CRM | ERPNext / Frappe Framework -- | -- |When a customer replies the deal’s communication status does not change to “opened”
I noticed this bug. Whenever a customer replies to an existing conversation in the deal the communication status is not automatically “opened”, and continues to stay “replied”, plus the SLA does not apply to the subsequent reply expected from the sales team. I can only imagine without this, it might be a complete nightmare for sales agents to track which deal to focus on.
Default subject line
The default subject line for any deal currently is “Name of the lead (CRM DEAL ID)”. The sales team changes this subject line every time because the default subject line does not make any sense. Also, I have seen many cases when people have forgotten to change the subject and been conversing with the same subject line. This isn’t ideal. The subject line should be configurable, maybe we can set it to “Lead’s Org name <> Frappe”
The email and contact of the deal are not visible by default (and the expand option is not intuitive), can we expand by default?
One-click easy filters to operate effectively
For Frappe CRM to be effective there should be an easy way for sales agents to work on the deals. Stripe is just one example (video below), many SaaS tools have one-click filters to make help agents work effectively. For example, an agent will first focus on all “Ready to close” deals, followed by “quotation”, followed by “negotation” and so on. This is effective for agents because the jobs to be done for leads in each stage are different. This is again relevant for helpdesk (cc: @ritvik Sardana)
Ask country code in the lead form
This is a small one but we don’t do it. :( In the phone number field of Contact-Us / Trial signup, can we please add the country code drop-down? This makes it easy to make the call directly from CRM.
Sending task reminders
I heard from the sales team that when they create a follow-up task, the notification is not received over email. Small thing, but let’s fix it.
The text was updated successfully, but these errors were encountered: