# DocuSign Go-Live Process

This guide covers the steps to transition your DocuSign integration from sandbox/testing to production use in Welkin.

## Pre-go-live checklist

Before switching to production, confirm the following:

* [ ] DocuSign production account is active (separate from the demo/sandbox account used during testing)
* [ ] All document templates are created and approved in the production DocuSign account
* [ ] [DocuSign Authorization](/integrations/docusign/docusign-authorization.md) has been completed for the production account
* [ ] Admin settings updated to use the production environment
* [ ] All DocuSign components in Designer are pointing to production templates
* [ ] Field mapping verified with production template data labels
* [ ] At least one end-to-end test completed in production (sending and signing a real document)
* [ ] Care team trained on sending and tracking DocuSign documents (see [DocuSign Overview – Care](/integrations/docusign/docusign-overview-care.md))

## Switching from sandbox to production

### Update the Welkin Admin integration settings

1. Log in to the Welkin Admin portal
2. Navigate to **Integrations → DocuSign**
3. Click **Edit**
4. Change the **Environment** setting from **Demo** to **Production**
5. If a new Integration Key is needed for production, update it
6. Click **Re-authorize** and complete the OAuth flow with your production DocuSign credentials
7. Confirm the status shows **Authorized** and the account name matches your production DocuSign account

### Verify Designer template availability

After switching to production, open Designer and confirm that the DocuSign templates listed in each component correspond to your production account templates. If templates are missing, check that they are published (not draft) in your production DocuSign account.

## Go-live day

On the day you go live:

1. Send a final test document in production to confirm end-to-end functionality
2. Notify the care team that DocuSign is now live and any documents sent will be legally binding
3. Monitor the first few document sends to confirm patients are receiving emails and signing successfully
4. Check that completed documents are appearing in patient records in Welkin

## After go-live

* **Week 1:** Check DocuSign envelope activity logs for errors or high rates of unsigned/expired documents
* **Month 1:** Review which templates are being used most frequently; consider adding Quick Send options for high-volume templates
* **Ongoing:** Re-verify document templates with legal/compliance annually or when regulatory requirements change

## Rolling back to sandbox

If critical issues are found after go-live, you can temporarily revert to the sandbox environment by changing the environment setting back to **Demo** in the Admin portal. Note that any documents sent during the production period will remain in DocuSign production – rolling back only affects new sends going forward.

Contact your Welkin Customer Success Manager for assistance with any go-live issues.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.welkinhealth.com/integrations/docusign/docusign-go-live-process.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
