Introducing Conga Composer for Salesforce1

Subscribe to Our Blog

Get weekly updates
straight to your inbox

Submit your email address to subscribe.

By submitting this form you confirm that you agree to the storing and processing of your personal data by Conga as described in our Privacy Statement.

The release of Salesforce1 has opened up a broad new set of possibilities for users to access and act on critical business data from virtually anywhere.  Here at Conga, we realized that Salesforce1 presents a great opportunity to help our customers be even more successful with document automation solutions, and that’s why today I’m very pleased to be:

Introducing Conga Composer for Salesforce1

Conga Composer for Salesforce1 (CSF1) allows users to create and distribute documents, presentations and reports from their mobile devices.  It takes the power and utility of existing, browser-based Conga Composer solutions and puts them directly in the hands of mobile users.

Document-centric business processes don’t always happen from behind a desk.  Requirements like these are becoming more and more common:

– A sales rep needs to email a quote from his taxi on the way to airport

– A field service tech needs to send a completed inspection form back to dispatch

– A VP needs to quickly see live sales pipeline info in a PowerPoint before an off-site staff meeting

 

Let’s dig into the specifics of how you can become a mobile hero by delivering these kinds of solutions to your users and clients with CSF1.

1) Merging and Downloading Files to Your Device

CSF1 can be configured to create and download documents, presentations and reports directly to a user’s mobile device.  This is great for doing things like creating customer account profiles before in-person meetings and generating sales reports while on the go – situations where a mobile user needs highly-formatted, actionable data at their fingertips.

Example: Downloading an Account Brief

Much like other AppExchange apps that work with Salesforce1, CSF1 is launched from a record using a publisher action as shown below:
Account_PublisherAction

This can be added to any standard or custom object that supports publisher actions.  Upon tapping the action, CSF1 will launch and the user will see a list of the Composer solutions available to run on that particular object.

Let’s assume I’m an account manager who’s preparing to meet with a client, but I want to get a complete look at their recent transactions, support incidents, and any other meaningful touch points they’ve recently had with my company so that I’m fully prepared for the conversation.  I could launch CSF1 from an Account record in Salesforce1 to quickly download an account brief before my meeting:

 

AccountBrief_Button

Now, the fun part – running the solution to download our file.  Tapping “Download Account Brief” will initiate this solution and display a simple interface to the user:

Downloading_AcctBrief

At this point, CSF1 is generating our account brief and preparing it for download.  The user experience is significantly different than running the same type of Composer solution in the browser, mostly because a mobile user’s context is naturally much different than that of a desktop user.  With limited screen space and no mouse, all of the configuration options normally available in Composer’s browser interface aren’t quite as useful on a smartphone or tablet.  For exactly that reason, all CSF1 solutions require the use of background mode.

The beauty of such automated solutions is in the simplicity of the experience for mobile users.  There are no forms to fill out, no dropdowns to select, and limited screens to navigate.  A few quick taps on the screen and I’ve downloaded an account brief to my device in PDF format:

AccountBrief_Output

This file opened up in my mobile browser at first, but I could then choose to open or save the PDF using any of the compatible local apps on my device so I can access it later:

AccountBrief_OtherApps

2) Merging and Storing Files in Salesforce

CSF1 solutions can also be set up to merge and store a document, presentation or report in Salesforce.  This is a great way to give mobile users an option of creating a file that they don’t need right away on their mobile device, but that they need to access later when they return to their desk.  Alternatively, a mobile user might create a file and store it in Salesforce so that other users can access it immediately.

Although CSF1 is capable of merging and storing files in Salesforce as record attachments, Chatter Files, or Content records, Chatter is arguably the best option.  This is because in the current release of Salesforce1, Chatter provide the most options for accessing the file itself.

See for yourself – both Attachments and Chatter Files appear in the Notes & Attachments related list in Salesforce1, but Chatter Files can be viewed and downloaded by a mobile user.  Attachments don’t allow for much access at all.

Composite_Chatter_Image

Example: Post an Inspection Report to Chatter

Let’s assume I’m a field service tech who’s just completed an inspection at my customer’s facility and I need to create a summary report.  In order for the sales team to generate a quote for equipment repair, I need to give them access to my inspection report as soon as possible.  Having entered the necessary data into a Case record on my mobile device as part of the inspection, I could easily run CSF1 to launch a solution that will create my report and post it to the Case’s Chatter Feed.

Case_Action

 

I’m then presented with the Composer solutions available to run from the Case object:

Case_Solutions

One quick tap and I’m merging my inspection report and posting it to Chatter:

Case_Merging

Finally, I’m redirected back to my Case record where I can see the results:

Case_ChatterPost

3) Merging and Emailing Files

Another common use case for CSF1 is the requirement to merge and email a file from a mobile device.  There are countless types of files that require email delivery, but this is particularly useful for customer-facing documents where speed of delivery is crucial – things like sales quotes, shipment confirmations, and receipts.

Example: Emailing a Quote to a Customer

Let’s assume I’m an inside sales rep and I’ve just wrapped up a meeting with my customer at their office.  Their inventory is critically low, and I’m eager to send them a quote for the new stock of products they’d like to purchase immediately.  From the taxi on my way to the airport, I could launch CSF1 from an Opportunity record in Salesforce1:

Oppty_Solutions

You’ll notice that my hypothetical super admin provided me access to three different Composer solutions here in CSF1 (I’ll review these eSignature solutions in the next example).  One quick tap on the Email Quote solution and I can automatically generate the latest quote and email it directly to my customer:

Email_Inbox

When emailing files with CSF1, it often makes sense to employ Composer’s activity logging parameters to save a copy of your output file or create activities in Salesforce as part of the process.  This is great for leaving a record of the transaction and archiving the file that’s been sent.

4) Merging and Delivering Files for eSignature

Integrating with eSignature providers like DocuSign, Adobe EchoSign and Sertifi is also something that CSF1 is capable of.  These kinds of integrated solutions are super useful in the browser, but almost always involve delivering a document for eSignature via email.  When you’re face-to-face with someone and need to capture a digital signature, it often makes more sense to facilitate a signing transaction right then and there with no email involved.

CSF1 supports both use cases – it can deliver a document for eSignature via email, but also leverage EchoSign and DocuSign’s hosted signing and in-person signing features, respectively.  This is a particularly cool way of reducing friction in a transaction and removing bottlenecks from a signature-driven business process.

 

Example: Hosted Contract Signing with EchoSign

Let’s assume I’m an event coordinator that needs to provide a contract for one of my vendors to sign while I’m at a trade show.  I need the signature before we can proceed with setting up their booth, so it’s critical that I get the contract signed right away.  Right from the trade show floor, I could fire up Salesforce1 and launch CSF1 from an Opportunity record:

Oppty_Solutions (1)

 

If I tap the EchoSign solution, CSF1 will display its standard merging interface as it generates my contract.  However, after it finishes, I’ll be redirected to the EchoSign Agreement that we’ve created on the fly:

ES_HostedSigning

From here, I can use the Host Signing button to initiate a hosted signing session with my vendor.  After tapping the button, I’m instructed to pass my device to my signer:

ES_Pass

Now, the vendor can easily input their signature to sign the contract:

ES_Contract

Signers can choose to type in their name so that a nicely-formatted signature is applied to the contract, or they can use free-form signing to draw their name:

ES_Signature

Upon inputting their digital signature, the status of the EchoSign Agreement will update and a copy of the fully-executed contract will be stored in EchoSign:

ES_Signed

When you consider all of the steps that can be required in getting a contract signed, the comparative speed and efficiency of an integrated eSignature solution on CSF1 is simply incredible.

 

Summary

By no means is this an exhaustive list of the things you can do with CSF1 – the use cases are virtually limitless.  CSF1 is included with Conga Composer at no extra charge, and existing Conga customers can get access by upgrading to the latest version of Composer on the Salesforce AppExchange.

For all the information needed to get started with CSF1, please review the Conga Composer for Salesforce1 Configuration Guide.

Got a great mobile use case for CSF1?  Or even an opinion on Salesforce1, in general?  We’d love to hear about it in the comments.  Thanks for reading – until next time!

0 Shares

Leave a Reply

Your email address will not be published. Required fields are marked *