How to Collect Signatures
Email Signature
Korint automatically sends a secure signature link to your customer by email. The customer opens the email, clicks the link, and signs the documents online from any device. Once the signature is completed, the policy is activated and any alternative quotes are automatically closed. The entire process is fully automated, with reminder emails sent if the customer has not yet signed, making it ideal for remote or digital-first interactions.Phygital Signature
For in-person meetings, signatures can be collected directly on a tablet or device while with the customer. Korint generates the signature link without sending an email, allowing you to open it instantly on your device and have the customer sign on the spot. The policy is validated immediately after signing, combining the efficiency of digital signing with the convenience of a physical meeting—ideal for brokers, agency visits, and live events requiring immediate completion.Security Options
Standard Signature
The customer signs the documents electronically after accessing them through the secure signature link. No one-time code is required at this level — access to the link is what identifies the signer. This provides a straightforward, legally valid electronic signature suitable for most day-to-day insurance policies.- Security: Standard level
- Customer needs: Valid email address
- Best for: Most standard insurance policies
Signature with SMS Verification
An additional layer of security is provided through a verification code sent by text message. The customer receives a one-time code via SMS, which they must enter before being able to sign. This step ensures stronger authentication and confirms that the individual completing the signature is indeed the intended customer.- Security: Enhanced level
- Customer needs: Email address and mobile phone number
- Best for: High-value policies, sensitive contracts, or when regulations require stronger verification
What Documents Can Be Signed
Documents to Sign
These are documents that require your customer’s signature. You can fully configure the type of documents and the fields included. Fields can be added for completion by the customer, such as date stamps, text boxes, or checkboxes, allowing precise control over what information is captured during the signing process.Documents to View Only
These are documents presented to your customer during the signing process but do not require a signature. All aspects of these documents and their presentation are configurable, ensuring full flexibility in what is displayed and how it is delivered.What happens after a signature
You can configure the meaning of a signature per document. If a document signature is required for the project/policy to become active, you can set it up that way. Conversely, if you only need a signed document for record-keeping and it has no impact on the project lifecycle, you can configure that as well.Driving signatures through the API
Requesting a signature is one call; learning that it completed is not. Signing happens in the customer’s hands, so completion is something you observe rather than receive.string
required
EMAIL — the provider invites each signer directly. URL — you receive signer links and present
them yourself, for signing in a branch or over a shared screen.boolean
Adds SMS verification, using
phoneNumber.boolean
default:"true"
Whether to include every document required for the contract to count as signed, so the customer
signs them in one session.

