Thanks for a thought on this, but this isn't the CRM we are looking for. Even though we might be in touch only with one person from client, our clients are companies. The information must perfectly persist when contact person changes, same way when eventually our support team changes.
The key is to (a) be able to define standard services and tasks, (b) attach to client (as an organisation), (c) share this information pool within our team.
Although this smells like in-house custom extension to our SaaS product, the en-visioned functionality must be already done somewhere. Our dev team is really busy with core product.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hi Andžs,
We added custom fields to Markd (relationship management tool) recently - it sounds like this might be a step closer to what you need?
We don't have collaborations yet though - working hard on getting these key features in soon :)
Thanks for sharing your insight into this issue. Totally agree that CRMs are not just for sales!
Cheers,
Brandon
Hi Brandon,
Thanks for a thought on this, but this isn't the CRM we are looking for. Even though we might be in touch only with one person from client, our clients are companies. The information must perfectly persist when contact person changes, same way when eventually our support team changes.
The key is to (a) be able to define standard services and tasks, (b) attach to client (as an organisation), (c) share this information pool within our team.
Although this smells like in-house custom extension to our SaaS product, the en-visioned functionality must be already done somewhere. Our dev team is really busy with core product.