7 questions to think about before integrating with Signi

When integrating e-signing into an organisation, it is a good idea to briefly map the whole process in the company, i.e. ask yourself the following questions:

1. What happens BEFORE documents are signed

2. What happens DURING the signing of documents

3. What happens AFTER the documents are signed

In this way we can make sure that signing via Signi "fits" into the company process without any hitches and that something in the process does not go wrong, is too complicated for the user or signatory, etc.

In greater detail, it is about answering the following questions:

1. Where do you get the contact details of the signer from? - First name, Last name, Email, Phone number (this is not mandatory, but then the user has to enter it himself so that the SMS is sent to him and he can be authenticated).

2. What will it send? - Finished PDF/DOCX/HTML/XSLX document or parameters for a document template stored in Signi. What the document will be called, so that the name shown to the signer when communicating is both clear and ideally unambiguous for easy tracking.

3. How is the "sign" action invoked? - In the integrated application as a menu action on the relevant record, by setting some custom field to "Send for signature", etc.

4. How are signatures positioned? - This is only handled for sent documents, when using patterns in Signi the position of signatures is determined by the pattern. The simplest way to place signatures is at the end of the document on the Signature Sheet. A variation is to place them on exact coordinates (suitable for forms such as Pension Record Sheet).

5. Where is the result of the signature shown to the user? - Signing status / resulting document / audit trail - checklist.

6. How are the results transmitted back? - The preferred option is a webhook calling an actively integrated system with the signing result. Alternatively, the integrated system can be periodically queried for the signing result.

7. What will be the link between users of the integrated application and Signi users? - In the simplest scenario, there is only a single service account in Signi, which is also used for integration. The signers from the customer's company do not need to have an account in Signi, they are listed as one of the signing parties when they call Signi, they will receive an email and SMS prompting them to sign each document, just like the counterparties. Alternatively, if the signatories from the customer's company also have an account in Signi, they can then be automatically signed to documents, they can send documents for signature directly and outside the integration, etc. The integrated application only needs to say when calling Signi that these are the representatives of the proponent of the document and not the counterparties. Other scenarios are possible by agreement.

What next after the questions are answered?

Based on these questions, it is then possible to delve into a more technical level and ask:

• What is the name of the integrated system? Which of its modules/agendas are to be used? What data will flow to and from it?

• Who supplies and maintains the system for the company? It could be internal IT, an external integrator, the system vendor, anyone.

Based on this, the following can be decided.

• Who should deliver the integration? Internal IT, external integrator, system manufacturer or in some cases the Signi team.

• What support can Signi provide for this? For example, provide a description of the Signi API, an already prepared partner solution, a link to a suitable partner, or perform the integration as part of their delivery.