Conga Composer is a document generation and automation tool designed to simplify and streamline the process of creating and distributing customized documents, presentations, and reports.
Yeah, Conga is something that the client has selected. We asked them the same question — they believe they’re a long-time user of Conga and they have trust in that product. So that’s the reason.
Only reason was its integration with salesforce. In those apps, we had to manually copy paste the data to generate document and get signed but with conga composer’s salesforce integration, it fetches all the data from salesforce and generate the document for us and once …
We have used PandaDoc and with our personal experience, we can say that Composer is way better as it lets us pull data from multiple Salesforce objects, apply conditional logic, and generate highly customized documents.
Conga Composer helps us in document generation part and once the document has been generated from Conga Composer it can be sent out to the customers. Here we can also use Conga Email Template to send out the message and the attachments. DocuSign here works so well and we can …
S-Docs is also great with Salesforce; however, it offers broader integration, scalable automation, and a deeper support ecosystem. Conga Composer delivers more powerful and flexible document generation.
I've used PandaDoc before; it is nowhere near as good as Conga Composer in terms of usability and end-user experience. Conga is much more valuable and business-oriented.
We used the out of the box Salesforce functionality but realized when our order forms used multiple currencies and had some customization we realized we needed a tool like Conga Composer
S-Docs allows for much more dynamic flexibility. Additionally, S-Docs template maintenance is substantially easier than Conga Composer. Conga requires about 6 steps to make an update to your template. S-Docs has a simple template builder that makes the process substantially …
We used Microsoft Excel to manipulate all the data from different objects, now we can click a button and the report is generated, Excel provides a powerful tool, but Conga Composer is better than Excel to generate the data in the format that the customer wants, you don't need …
CPQ is more customizable and native to Salesforce, but it's extremely difficult to set up and maintain. The Conga Composer configuration is much simpler and quicker to implement.
From my experience, Conga Composer is particularly well-suited for generating documents, such as quotes and contracts, directly from Salesforce. It saves us a great deal of time, which is remarkably beneficial for companies with sales teams. Not suitable for companies lacking significant Salesforce expertise or administrative support.
Though I love how easily Conga Composer ties into Salesforce and its given analytics, it takes a lot of data entry to get up and running. I don't love that sometimes queries can take a long time to pull. I like keeping our marketing templates consistent via templates in the system. Pulling multiple objects into one report is fantastic too.
It's a fairly simple tool to integrate into your current business structure. When we've had issues, we were able to resolve them extremely quickly. The users click a button and it can bring in all the quote lines, and our credit application seamlessly into our tool. I'd definitely recommend it to other colleagues
It's been hit and miss depending on the issue. We use javascript to generate the urls which has confused many techs even though it generates a clean url - they are overwhelmed by the concept of code and can't understand that the url is all that matters.
I think Nintex is the primary competitor for Conga Composer, but I have not personally used it. I was not present for the decision to purchase Conga but I would recommend it in future document automation vendor selection processes because I have seen how well it works! We are especially fond of complementary features in Conga Composer, including Conga Email Templates and Conga Global Merge.
Could really use better error handling on the product when the document doesn't generate. Zero notifications are provided right now and have no idea where in a 20 page template the error is. Need to keep cutting the template into pieces to find the error.
The report generates 90% of the time so far.
Getting easier to generate templates when knowing how the JSON will be structured to add to merged fields.
Use Work Plan Template Entries and Work Steps to dynamically generate many deliverables.