Want e-signature inside the CRM you already use, under your own brand? Get a free automation audit

The Challenge

Sending a contract for signature sounds trivial until you count what it costs a sales team.

1. Signing happened outside the CRM. Documents were prepared, sent and chased somewhere else, so the record never matched reality. Anyone who needed to know whether a customer had signed had to go and look, or ask a colleague.
2. Someone else's brand on the customer's moment. Off-the-shelf e-signature puts a vendor's name on the email and the signing page. When your customers are clinics and distributors, the final step of a commercial agreement is not where you want to introduce a third-party logo.
3. Manual steps exactly where compliance matters. Signed PDFs filed by hand. Status updated from memory. The timestamps that make an agreement defensible sitting in a different system from the deal they belong to.

What We Built

The constraint that shaped this project: we owned half the system. Salesforce development sat with the client's own Salesforce team. Zoho Sign setup, API configuration, white-labelling and webhooks sat with us. So the work was split explicitly — 14 Salesforce-side tasks, 11 Zoho-side, 18 joint — with a signed-off field mapping document acting as the contract between two teams who had never worked together.

One button, inside Salesforce

• A custom button and Lightning Flow with an Apex trigger for "Send for Signature", on the Opportunity, Account or custom object where the deal actually lives.
• Documents generated from Salesforce merge fields, so every customer gets a document built from their own record rather than a template somebody edited by hand and forgot to change.
• Signing positions — signature, date, name, page one or two or both — passed dynamically per document type instead of hard-coded. Hard-coding those is what forces a developer to get involved every time legal changes a paragraph.

A signing journey carrying one brand

• Zoho Sign configured on Enterprise for full white-labelling: custom sending domain, branded signing page, email templates in the client's own wording.
• From notification email to completed document, the customer sees the manufacturer. No vendor branding anywhere in the journey.

Status that writes itself back

• Webhooks, not polling. The moment a document is signed or declined, Zoho Sign pushes a callback to a purpose-built Salesforce REST endpoint.
• Salesforce attaches the signed PDF to the originating record, updates status, and stores sent, viewed and signed timestamps as reportable fields.
• Error handling and retry logic for API failures, timeouts, invalid addresses and rate limits. The unglamorous part that decides whether an integration survives contact with production.

An audit trail that stands up

• Full audit trail and signed-document generation in Zoho Sign, with the same timestamps mirrored into Salesforce fields so compliance reporting runs from the CRM.
• Signed PDFs held in both systems — on the Salesforce record and retained in Zoho Sign with the complete trail.

Results

• Signing never leaves Salesforce. Sales send, track and retrieve executed documents from the record they were already in.
• The brand stays the client's. Branded email, branded signing page, branded completed document.
• Status is fact, not memory. Callbacks update status and timestamps the moment something happens, and the signed PDF lands on the record on its own.
• Four weeks, six phases, plus a 15-day support window after go-live.

Why It Worked

Two decisions, both made before any code was written.

First, the field mapping document signed off up front. When one team owns Salesforce and another owns the signature platform, an integration fails at the seam or it doesn't fail at all. The seam is a data contract, and arguing about it on paper in week one is far cheaper than discovering the disagreement in testing. The same thinking held two data centres together in our cross-border Zoho CRM and Books build.

Second, webhooks instead of polling. It is the less obvious choice and slightly more work, and it means status is correct the instant a customer acts rather than correct within fifteen minutes. When a signed document triggers fulfilment, that gap is real money.

And worth saying plainly, because it cuts against our own interest: we're a Zoho partner, and this project did not put the client on Zoho CRM. It put Zoho Sign underneath the CRM they already had. When a business has already invested in a platform that works, replacing it is usually the wrong advice — however good it would be for our invoice.

Frequently asked questions

Facing the same challenge?

If your team signs contracts outside the CRM, or a vendor's brand is sitting on your customer's signing page, we'll show you what a direct, white-labelled integration looks like for your stack. Start with a free automation audit. Get a free automation audit