Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[ Feature Request ] New DocType for Call and Appointment #10825

Closed
4 tasks
giuseppelamatrice opened this issue Sep 18, 2017 · 25 comments
Closed
4 tasks

[ Feature Request ] New DocType for Call and Appointment #10825

giuseppelamatrice opened this issue Sep 18, 2017 · 25 comments

Comments

@giuseppelamatrice
Copy link

giuseppelamatrice commented Sep 18, 2017

"To do" is not best way to manage call and appointment.

I suggest to do this:

  • create "call" doctype: (
    call type: in/out;
    call purpose: demo/support/commercial
    contact name: John Smith
    releted to: campaign (Google AdWords)
    call details: current call / completed call / schedule call
    call duration: 36m 46s
    note: best interest save time to manage document

  • create "appointment" doctype:
    title: get document
    location: Corso Garibaldi 3, 20143 Milan, Italy
    from: 18/09/2017 13:00
    to: 18/09/2017 14:00
    Partecipant: Me
    releted to: lead/contact/opportunity (ex. Giuseppe Lamatrice)

  • add "call" on lead and customer app

  • add "appointment" on lead and customer app


Call example:
image


Appointment example:
image


Customer example:
image

@strixaluco strixaluco added the CRM label Sep 18, 2017
@joolsr
Copy link
Contributor

joolsr commented Sep 19, 2017

When you send an email. If you unclick, 'Send as Email' at the bottom, you will see that you can set Communication medium, and a lot of the functionality is (albeit quite hidden) here already

@giuseppelamatrice
Copy link
Author

It is more convenient read all information on lead/customer in one page.

@joolsr
Copy link
Contributor

joolsr commented Sep 20, 2017 via email

@giuseppelamatrice giuseppelamatrice changed the title [ Feature Request ] New DocType for Call and Appoinment [ Feature Request ] New DocType for Call and Appointment Sep 20, 2017
@umairsy
Copy link
Member

umairsy commented Oct 27, 2017

Just checking, would providing an option to create Timesheet from Lead/Opportunity/Quotation help for tracking appointment?

@giuseppelamatrice
Copy link
Author

giuseppelamatrice commented Oct 27, 2017

I propose to add 2 fields on "to do" and "calendar" tool:

  • partner type: lead / opportunity / customer / supplier / employee
  • partner name: John Travolta

@sbkolate
Copy link
Contributor

sbkolate commented Nov 5, 2017

@giuseppelamatrice
ToDo is working for us.
On top of ToDo we developed feature to add interaction. If you think its generic, then I can send pull request.

Please check screenshot in following pdf.

https://drive.google.com/file/d/0B7hi3l0nL56dSHJ3SllQY2oxcjA/view?usp=sharing

@giuseppelamatrice
Copy link
Author

giuseppelamatrice commented Nov 5, 2017

@sbkolate
Good. I think "to do" is generic tool.

I propose to add 2 fields on "to do" and "calendar" tool:

  • partner type: lead / opportunity / customer / supplier / employee / other...
  • partner name: John Travolta

In this way we can use "to do" for all business process, not only CRM.
In fact "CRM label" attached on this issue is not correct.

@joolsr
Copy link
Contributor

joolsr commented Nov 5, 2017

@sbkolate great piece of work. I need to look at more carefully but I think this would be a great benefit to be added to core ;-)

@joolsr
Copy link
Contributor

joolsr commented Nov 5, 2017

@sbkolate For the 'Type of Interaction', what types are available?

Also - small note - on the Message box that says 'Interaction Submited Successfully', please note that Submitted on your PDF is spelt wrongly. ie it should be submi_tt_ed not submi_t_ed

Great piece of work :-)

@sbkolate
Copy link
Contributor

sbkolate commented Nov 6, 2017

@joolsr @giuseppelamatrice
Type of interaction we added Skype, Whatsapp, WebEx, call, Visit
I will fix message.

We have added popup for interaction, its creating communication and ToDo, So ToDo will give reminder for next call/ interaction
If expense claim is added then only it create expense claim.

@giuseppelamatrice Interaction is similar to your call doc, and for reminder we are using ToDo.

For adding core, I will work on mockup and feature request.

@joolsr
Copy link
Contributor

joolsr commented Nov 6, 2017

@sbkolate I'm wondering if we should also add to the types of interaction 'Email'. Now I know this sounds counter intuitive as emails should be received into the Opportunity and history. But we have the situation occasionally that emails are received that may not be forwarded into ERPNext by a colleague and thus it could be useful to have this extra interaction type added.

That said, I appreciate this could be quite confusing for newcomers to ERPNext so if anyone has any further input on this I'd be pleased to hear it.

@basdereus84
Copy link

That said, I appreciate this could be quite confusing for newcomers to ERPNext so if anyone has any further input on this I'd be pleased to hear it.

Maybe call it "Email outside ERPNext" ?

This would be a very useful feature. I've posted a feature request a couple of months ago to be able to set a follow up for a quotation and sales order as well, just the way it currently works with leads and opportunity. This would be a very nice addition/integration for that. I hope it makes it to the core.

@sbkolate
Copy link
Contributor

sbkolate commented Feb 5, 2018

Hello,

Is this generic request?
We have one post on forum, to see all related communication.

https://discuss.erpnext.com/t/how-to-view-all-related-communication-with-a-contact-lead-customer-or-supplier/33421

If its generic, then I can send pull request to add Interaction/ Appointment/ Meeting Details
It will also enable to add expense claim for meeting and reports to see all interaction.

Thanks,
Sam

@basdereus84
Copy link

Although I don't think your solution will allow us to see all related communication as I was asking for in my forum post, I do think it would be a very nice addition to the CRM module of ERPNext.

I did some playing around with Odoo 11 and the ability to schedule and view calls, meetings etc. with contacts seems to be far better integrated into Odoo. I think your solution is good step to get this same type of integration into ERPNext.

@joolsr
Copy link
Contributor

joolsr commented Feb 5, 2018

As I mentioned before a few times there IS a somewhat hidden feature with everything you want. The ability to add phone calls, messages, etc is there but its really, really hidden. See video below:-

peek 2018-02-05 16-06

I think this functionality in terms of the underlying capabilities is fine, but its a far better method to show Phone messages and different forms of Communications. Its almost as is it was hidden on purpose ...

But the Doctype supports some of what you need so we should improve upon the GUI to start with so its far more obvious to use rather than adding to the infrastructure IMHO ..

@basdereus84
Copy link

@joolsr I agree with you that the function to log a call or visit is ridiculously hidden away in the send email window. I think that this solution presented by @giuseppelamatrice adds more than only a way to log a phone call. I see it as a way to easily log but also to schedule calls, meetings etc.
If you look at this video from Odoo 11: https://www.youtube.com/watch?v=r1Wq2ka1DMU You'll see that you can schedule events from a record.

We have the similar ability by using the "Assign to" function but it's very limited. You can only add one todo for each user. If you change the message inside the ToDo record it's not trackable from within the record from which you created the todo in the first place. It's also not possible to get an overview of the scheduled events for a certain record.

@joolsr
Copy link
Contributor

joolsr commented Feb 6, 2018

@basdereus84 Just a note to say that you obviously feel strongly about improving CRM and email facilities. Why don't you join the ERPNext Community CRM/Email group of which I'm a member so you can add your voice and help improve the application ? We will meet virtually tomorrow at 7.30am GMT

I cant remember how you join as such but you need to speak with Antonius Tara who is mainly heading things for now

@joolsr
Copy link
Contributor

joolsr commented Feb 6, 2018

If you want to join us for the meet tomorrow, let me know and I'll add you to the group

@basdereus84
Copy link

I would like to but unfortunately, I've got other obligations I have to attend.
Will the session be recorded?

@sbkolate
Copy link
Contributor

sbkolate commented Feb 7, 2018

@basdereus84 We have another doctype as interaction, it will enable so see all communication and reminders to users to take follow ups with communication.

@chdecultot
Copy link
Contributor

Hi guys,

I just pushed a PR to Frappe to provide the basis for this feature.
I have also added a new DocType called "Call" in ERPNext. Some proposed fields are still missing because I wait for Frappe's validation before going further.

Please don't hesitate to review this proposal and give some feedbacks.

Thanks!

@joolsr
Copy link
Contributor

joolsr commented Sep 21, 2018

Hi @chdecultot
Many thanks for your PR! I think this is well overdue and many thanks again for actually getting something proposed and coded. I am not developer but I am happy to test and offer suggestions.

I presume this is too late now for v11 but as it would be so useful I hope it wont have to wait another 9 months till v12? Perhaps we can get it into v11.1 in a couple of months time

@chdecultot
Copy link
Contributor

chdecultot commented Sep 21, 2018

Hi Joolsr,

Thanks for your kind words.
I am still working on it and actually based on the first feedbacks I have received, I have changed my mind regarding creating new Doctypes for Call and Appointment.

Whereas I do think that it could be better managed by having its own documents, the current design of Frappe/ERPNext would not allow a user to see all his events/calls/appointments in a single calendar. Which is a huge UX problem.

It is already an issue experienced with the ToDo/Event doctypes and I think we should be careful about introducing further siloed information.

Therefore, I am currently trying to tweak the Event doctype to allow the creation of categories (Call, Meeting,...) and improve the general experience with this doctype.

The general design of Frappe's PR frappe/frappe#6113 is still similar as what you can see in the Gifs.

If you have any comment, proposition regarding how we could enhance the UX of the integration between events/interactions in the CRM please don't hesitate !

And yes, let's hope it could be rapidly merged into the core once it is finalized.

Have a nice day!

@joolsr
Copy link
Contributor

joolsr commented Sep 21, 2018

Hi again Charles Henri @chdecultot

Yes, its obvious you've got a good handle on this. I wasn't aware of the issues of viewing different types of date related doctypes on the same calendar for one user but it did occur to me that a calendar view is kind of essential and expected.
I'll keep an eye on your updates and if you have a staging server I can access to try your branch I'm happy to.
I think you've linked to the wrong issue number above BTW I couldn't see that it was related .. ;-)

@ankush ankush added the to-validate Old issues pending validation label Dec 10, 2021
@ankush ankush removed the to-validate Old issues pending validation label Dec 18, 2021
@stale
Copy link

stale bot commented Feb 16, 2022

This issue has been automatically marked as inactive because it has not had recent activity and it wasn't validated by maintainer team. It will be closed within a week if no further activity occurs.

@stale stale bot added the inactive label Feb 16, 2022
@stale stale bot closed this as completed Feb 23, 2022
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jan 19, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

8 participants