What is your primary use case for Conga Composer?

One of the main use cases for Conga Composer would be to generate quote documents. We had different types of quote documents in our business process, so we used different kinds of Conga Composer templates for those. Basically, there was one template for the initial quote to give them an idea of how the price structure is going to work. Once they finalize, we have a different template, so when the deal is finalized and everything is in place, they would be able to see how much they would be paying, including the tax. That was the main use case around it. But as I mentioned earlier, we also used it for other custom objects that we had, such as POV, and to generate and print basically the invoices as well. We used Conga Composer mainly for generating the documents, but we did not use Conga Composer Sign functionality. Instead, we opted for the DocuSign functionality. Once the document generation process was completed by Conga Composer, we integrated DocuSign into our system. Once the document is generated, it moves to a DocuSign envelope. We are able to send the document to different contacts mentioned there. DocuSign was mainly for sending the document to get it signed, and once it comes back signed, we also had an automation in DocuSign that updates some fields at the quote level. It lets us know that the document has been signed and things around that.

One of our clients is looking to build case summaries or quote summaries where we list all the products they have purchased. They have a complex quote summary requirement. We use Conga Composer to build the entire quote summary, displaying all quote details, products purchased, and related information. The implementation varies according to countries, so we apply many conditions on the same templates. We use Conga Composer for document generation purposes. We remain consistent with Conga Composer because it satisfies many business use cases. We have used it several times across multiple projects to build similar document solutions.

I don't use Conga Composer anymore daily; we have our setup, and it's working fine, so I don't have to touch it. We have something external for contract management. I think we use DiliTrust for the contract management, but mostly our French colleague uses that. In the past, my clients would generate documents using a template through a button or automation, and they could send them afterward using Conga or DocuSign because we can plug them together. Today, we're basically doing the same thing. We use a Conga Composer template, and through a button, because some of my colleagues prefer verifying the data and changing a few things before sending the document, while others don't care. We have a button or we have automated the generation and sending of the document using mostly DocuSign. We want our partners to sign the document we are sending them. So we use Conga Composer to generate the document and we use DocuSign combined with Conga Composer to send it and to capture the signature back. That's the use case we have today.

I primarily use Conga Composer for sales proposals and quotes. Whenever I need to auto-generate proposals using opportunity data and determine whether to include pricing discounts and product details, I use Conga Composer. The process begins when the opportunity is ready and a sales rep is working on an opportunity in Salesforce that contains the account information, products, total value (ACV), and a stage designation of proposal, price, or quote. All this data is already stored in Salesforce. The sales rep then clicks a custom button labeled generate proposal, which is configured to trigger Conga Composer and passes the opportunity ID and related data. Conga Composer fetches data automatically, pulling account details, opportunity details, and product line items. The system then performs template merging using a pre-built template in MS Word that includes company branding, dynamic fields, static fields, and tables for product line items. Finally, the document generation process produces a PDF or Word proposal instantly, followed by auto delivery and the e-signature process.

We are using Conga Composer in our Salesforce environment to dynamically generate documents. For example, if we have a customer and need to finalize a business deal, we capture deal data. Suppose you're selling a car; you need to prepare a quote. Conga Composer helps in preparing that quote by mapping fields such as customer information and car details onto a template.

In the project, we were generating a PDF based on the insurance, creating the contract form and agreements, and sending that PDF to the customer by merging all the information from Salesforce. We installed all the packages of Conga Composer into Salesforce and integrated them to pull all the information from Salesforce to the PDF and then sent those PDFs to the customers.

We used Conga Composer for bill generating. They were having transactions on a click of a button, and we had to collect those fields automatically based on the criteria, and we had to map them dynamically.

I use Conga Composer to build different templates, mainly for proposals. I create the templates and incorporate conditions to make it user-friendly for professionals to handle.

I work for a Salesforce consulting composer, and I'm mostly a developer, sometimes an admin. Sometimes the clients require us to set up things in Conga, either Conga Composer, Conga Sign, or any other similar application. So most of the times, the request is just to update existing templates or create new templates for them to use on Conga.

I have a project where I generate a document and send it via client email when an opportunity arises in Salesforce. When the opportunity is won, an invoice is automatically sent to the recipient. I also use it to generate documents and send them for signatures using Conga eSign.

I use Conga Composer to generate invoice and code templates. It's useful for creating templates on Salesforce object records, but I haven't used it for contract management.

We utilize it for contracts, account statements, and summary reports.

We use Conga Composer for document generation. For instance, our clients need reports showcasing opportunities they've secured recently, categorized by employee ownership. Additionally, in the healthcare sector, we generate reports detailing the number of patients treated and their conditions. So, most use cases are around document generation, as I work in the health sector.

I primarily use Conga Composer to generate documents for customers and partners. While we have the capability to generate complex documents, our main focus is on generating simple documents. Sometimes, these documents are associated with the signature feature, allowing recipients to sign them if necessary. Primarily, however, we use Conga Composer to generate documents without signatures.