pbartecki
20-04-04, 02:44 AM
I just wanted to move/gather thoughts on CRM module posted to previous forum on SF. It's here in case old forum would become unavailable.
First post by Juan Carlos González - jcgonz:
1. Be able to have tasks templates. For example, if the organization's process to make a sale is to:
- First talk with customer
- Hand in the first budget
- Call the customer to verify that the budget arrived correctly
- Start project / hold project / cancel project
Let's enable the users to create those templates so each the module helps all users to follow procedures
2. Be able to create concurrent tasks until the project's end date
3. Have formats to register meetings, phone calls, emails that enable the user to register information such as:
- Goals
- Achieved goals
- People that went to the meeting
- Negotiations result
- Tasks created within this contact
4. Enable the system to send emails using user's email in order to mantain a centralized mail repository
5. Be able to get a report, any time, of all the contact that the project team have had with the customer (mails, phone, meetings)
6. Filter reports by type of contact
______
Other thoughts
Roman Locher - romanlocher:
CRM module should also have a keyword (e.g. customer, mailing2003, supplier) search / filter
I think of an editable keyword list and you can assign one or more keyword to a contact. After that it's possible to filter the contacts with and/or/not + keyword constructions. For example you have customer, private contact and marketing as keywords. Then you can filter your contacts like this: customer AND NOT private contact AND marketing, saying you can find a specific contact group (not only one contact) in the contact list. With this data, you can now create mailings and such things. With most CRM tools I know, you can also filter every contact field, e.g. city, name...
[side note] Yep. Definately. We should be able to assign a contact to different predefined marketing groups/categories/keywords and then be able to pull those groups (if you need say to call/mail/fax only specific group of your customers).[/side note]
______
About other ideas that Roman Locher sent me in an email:
- Phone calls assinging
- EMails to an specific contact (through the system)
- Export contacts to enable user merge documents
______
Perry Smit - perrysmit12:
MoreRelations between modules.
When you work behind your desk, you got todo with the following information objects:
Agenda
Companies
Contacts
E-mails
Documents (in and out)
Todo´s
Projects (products)
All of the modules should have a many to many relation between each module.
To explain:
When you search a contact, and you have find the contact, you always want to know:
- to which companies this contact is related and kind of relation it have.
- which documents are sent in the past?
- which documents are received
- which e-mail received
- e-mails sent to this contact etc..
You want this also when you searching a document, when you have the document, you want know which companies should have read the document and why.
THis means, we should have more tables to get the relations between each module.
In the interfaces we must add the possibilities to create the relations between the modules.
There is no crm program we can do all above of the wishes, while it´s just so basic.....
Perry
______
rich knowles - richk2003
If I may suggest a couple more things:
o Requirements validation tags such as PROPOSED, DISCUSSED, APPROVED, WAIVED and REJECTED.
o Traceability links to the WBS so that specific requirements can be tied back to actual tasks via the overall breakdown structure.
o Establish a workflow surrounding the requirement approval process to link up with a Configuration Management process. Perhaps a template which includes the names, routing, etc. for those individuals needed to validate and approve requirements.
o A documentation generation process that will take all the requirements and extract them into a human readable form. During the requirements definition process for large projects, the entire set of requirements may be extracted and printed many times.
o A versioning system so that several generations of requirements can be managed.
o Effectivity dates? Some requirements turn into pumpkins after a certain date, or requirements may become mandatory after a certain date (due to legal implichations for example).
o The capability to link from a document to a specific individual requirement such that when the requirement changes, the document will reflect the change.
o The capability to lock a requirement such that it cannot be changed except by certain individuals.
I'll think of more.
Just fired up dotproject and I'm impressed! A requirements management module would enhance its functionality!
[wow, pretty extensive list.. :) ]
First post by Juan Carlos González - jcgonz:
1. Be able to have tasks templates. For example, if the organization's process to make a sale is to:
- First talk with customer
- Hand in the first budget
- Call the customer to verify that the budget arrived correctly
- Start project / hold project / cancel project
Let's enable the users to create those templates so each the module helps all users to follow procedures
2. Be able to create concurrent tasks until the project's end date
3. Have formats to register meetings, phone calls, emails that enable the user to register information such as:
- Goals
- Achieved goals
- People that went to the meeting
- Negotiations result
- Tasks created within this contact
4. Enable the system to send emails using user's email in order to mantain a centralized mail repository
5. Be able to get a report, any time, of all the contact that the project team have had with the customer (mails, phone, meetings)
6. Filter reports by type of contact
______
Other thoughts
Roman Locher - romanlocher:
CRM module should also have a keyword (e.g. customer, mailing2003, supplier) search / filter
I think of an editable keyword list and you can assign one or more keyword to a contact. After that it's possible to filter the contacts with and/or/not + keyword constructions. For example you have customer, private contact and marketing as keywords. Then you can filter your contacts like this: customer AND NOT private contact AND marketing, saying you can find a specific contact group (not only one contact) in the contact list. With this data, you can now create mailings and such things. With most CRM tools I know, you can also filter every contact field, e.g. city, name...
[side note] Yep. Definately. We should be able to assign a contact to different predefined marketing groups/categories/keywords and then be able to pull those groups (if you need say to call/mail/fax only specific group of your customers).[/side note]
______
About other ideas that Roman Locher sent me in an email:
- Phone calls assinging
- EMails to an specific contact (through the system)
- Export contacts to enable user merge documents
______
Perry Smit - perrysmit12:
MoreRelations between modules.
When you work behind your desk, you got todo with the following information objects:
Agenda
Companies
Contacts
E-mails
Documents (in and out)
Todo´s
Projects (products)
All of the modules should have a many to many relation between each module.
To explain:
When you search a contact, and you have find the contact, you always want to know:
- to which companies this contact is related and kind of relation it have.
- which documents are sent in the past?
- which documents are received
- which e-mail received
- e-mails sent to this contact etc..
You want this also when you searching a document, when you have the document, you want know which companies should have read the document and why.
THis means, we should have more tables to get the relations between each module.
In the interfaces we must add the possibilities to create the relations between the modules.
There is no crm program we can do all above of the wishes, while it´s just so basic.....
Perry
______
rich knowles - richk2003
If I may suggest a couple more things:
o Requirements validation tags such as PROPOSED, DISCUSSED, APPROVED, WAIVED and REJECTED.
o Traceability links to the WBS so that specific requirements can be tied back to actual tasks via the overall breakdown structure.
o Establish a workflow surrounding the requirement approval process to link up with a Configuration Management process. Perhaps a template which includes the names, routing, etc. for those individuals needed to validate and approve requirements.
o A documentation generation process that will take all the requirements and extract them into a human readable form. During the requirements definition process for large projects, the entire set of requirements may be extracted and printed many times.
o A versioning system so that several generations of requirements can be managed.
o Effectivity dates? Some requirements turn into pumpkins after a certain date, or requirements may become mandatory after a certain date (due to legal implichations for example).
o The capability to link from a document to a specific individual requirement such that when the requirement changes, the document will reflect the change.
o The capability to lock a requirement such that it cannot be changed except by certain individuals.
I'll think of more.
Just fired up dotproject and I'm impressed! A requirements management module would enhance its functionality!
[wow, pretty extensive list.. :) ]