Hello,
I would recommend to create a custom entity that serves as a custom M:N relationship between Account and Project entity. This custom entity (lets call it "ProjectFeedback]") would have fields like:
ID, Project (1:N lookup), Account (1:N Lookup), Comments (Textbox), Status (OptionSet), Created Date, …
Then you create subgrids (or rely on the Related Views / associated views) for the Project Feedback on both Account and Project while showing the respective related project feedback items. You may create respective views that show the Project / Account in the respective other entities project feedback grid.
Next you can think on how to utilize this information:
- If you are using Dynamics 365 for Marketing, you can add this Project Feedback to the customer insights sync and start building segments against project feedbackand filter by project, Status and identify the primary contact of the respective accounts.
- Or you build dynamic marketing lists to select accounts or respective contacts for follow up communication
In Dynamics 365 for Marketing you could then run automated Customer Journeys that pull dynamic information from the respective Project Feedback items:
"Dear [xyz], you have provided the following feedback to our proposal for Project [abc]:
[comment]
We love to talk more "
In order to efficiently capture the feedback when staff is working with the prospects, a Power App might help that is tuned for entering new project feedback items on the go on a tablet device.
Lots of opportunities...
