WEBVTT

1
00:00:00.200 --> 00:00:06.023
A completed agreement is most useful when your
team can find it with the correct CRM record.

2
00:00:06.203 --> 00:00:16.431
The essential steps are to confirm completion, obtain the final signed
PDF, identify the destination record, and verify the file after it is attached.

3
00:00:16.891 --> 00:00:23.845
In Klarstig.ai, open the signature request and
confirm that all required signing steps are complete.

4
00:00:24.025 --> 00:00:26.855
Check that you are working with the intended document.

5
00:00:27.035 --> 00:00:32.592
A sent request or a partially signed document
is not the same as the completed agreement.

6
00:00:33.052 --> 00:00:36.881
Use Download signed PDF and open the downloaded file.

7
00:00:37.061 --> 00:00:41.700
Review the document title, signature details, and all included pages.

8
00:00:41.880 --> 00:00:45.051
Keep any appended completion certificate with the file.

9
00:00:45.231 --> 00:00:50.255
Avoid substituting the original unsigned document or an incomplete preview.

10
00:00:50.715 --> 00:00:53.745
Find the exact destination in the CRM.

11
00:00:53.925 --> 00:00:58.097
Confirm the person or organization and the record identifier.

12
00:00:58.277 --> 00:01:00.177
Similar names are not enough.

13
00:01:00.357 --> 00:01:06.959
A volunteer agreement should be attached to the intended
volunteer's record, not simply the first search result.

14
00:01:07.419 --> 00:01:12.453
Use the CRM's supported file attachment option for a manual transfer.

15
00:01:12.633 --> 00:01:19.778
If your Klarstig.ai connector offers a validated
document-attachment action, it may support automation.

16
00:01:19.958 --> 00:01:24.300
Check that action's supported object, file format, and size limits.

17
00:01:24.480 --> 00:01:28.628
Record-write access alone does not establish attachment support.

18
00:01:29.088 --> 00:01:32.950
After attaching the file, open it from the destination record.

19
00:01:33.130 --> 00:01:39.095
Confirm that it is the correct completed PDF and
that the appropriate team members can access it.

20
00:01:39.275 --> 00:01:46.112
A successful signature status in Klarstig.ai does
not prove that the CRM received the document.

21
00:01:46.572 --> 00:01:52.182
Use a clear document name and retain the signature
request reference where your process allows.

22
00:01:52.362 --> 00:01:56.532
Follow your organization's document access and retention rules.

23
00:01:56.712 --> 00:02:03.229
A public file link may expose an agreement beyond the
intended team, so use the approved sharing method.

24
00:02:03.689 --> 00:02:10.856
Your next step is to check one completed practice agreement
from the signature request through to the CRM record.

25
00:02:11.036 --> 00:02:13.041
Confirm the file and its access.

26
00:02:13.221 --> 00:02:20.708
The written Klarstig.ai Academy guide includes these checks
for both manual handling and supported automation.