It would be great if templates could be given basic naming conventions to save manually renaming every file we create. Currently it gets: [customer name] [date] [time]. We would like to automatically name the file as: [template name] [customer name] or [template name] [job number] or (specified default value) [customer name] or something else along those lines.
PB0 followers0 questions328 posts
Sign up for free today or log in now to follow this topic, join the discussion, and always stay updated.
It would be awesome it we could add pdfs as documents from OneDrive. We have smartdocs, but with OneDrive it only allows the addition of word documents. I notice those using Google Drive have the ability to add pdfs as documents.
The main reason we want to do this is for the electronic signing capabilities of smart docs. We generate our quotes as pdfs in another application, so be great if we could import them into smartdocs and send for an electronic signature from Pipedrive.
I wish you would stick to the core of your product and focus on the Leads feature and make it fully functional.
Releasing s product that is not really working, not connected properly to insights etc.
Increase your workflow opportunities... stuff like that.
So many eSigning tool out there doing the whole sales enablement part better than you guys. And believe me - the list and request for what you have started it endless.
Can we collaborate?
Can we chat in the doc?
Can we do reviews?
Could we upload videos?
Can you build an editor...
Just stick to the... (More)
The smart docs eSignatures are a great way to streamline clients' signing on proposals and quotes.
However currently we can't get a trigger from Pipedrive (either in Workflow automation or via API / Zapier / Integromat) when a document has been signed.
Having such an automation trigger will enable to kickstart onboarding workflows automatically once a contract has been signed by all parties inside Pipedrive.
Could anyone else make use of such an automation trigger?