Index
Sending a contract for signature does not mean that the sale is formalized. The integration needs to track the submitted version, its participants, and the outcome of the process before updating the opportunity.
How to evaluate this decision
Map available states in the provider and their translation into the CRM. Differentiate sent, viewed, completed, declined, and canceled when these events exist. A new version must maintain a link with the previous one without allowing a delayed event to reactivate a superseded document. The provider's capabilities and conditions need to be confirmed during scoping.
Criteria for comparing proposals
- Link: relate document, version, opportunity and external identifier in a stable way.
- Events: handle duplicity, delays and unexpected orders without advancing the funnel unduly.
- Evidence: define which files and information are available and who can consult them.
A scenario to discuss with the supplier
Hypothetical example: the salesperson cancels a document and sends a revision. A later event from the old version cannot mark the new proposal as complete.
What to validate upon delivery
Test completion, refusal, cancellation and document replacement. Check the result both in the provider and in the CRM. Receiving a webhook does not waive validation of authenticity and link.
Prepare the conversation about the project
Take the CRM, the provider and the commercial advancement rules to Quantum9. The proposal must separate technical integration from any legal interpretation of the documents used.
Systems integration · Map the company's priority