Gather signing details:

• Signers: Who needs to sign? (names, emails, titles)
• Signing order: Sequential or parallel?
• Internal approval: Does anyone need to approve before the counterparty signs?
• CC recipients: Who should receive a copy of the executed document?

Step 4: Route for Signature

If ~~e-signature is connected:

• Create the signature envelope/request
• Set signing fields and order
• Add any required initials or date fields
• Send for signature

If not connected:

• Generate a signing instruction document
• Provide the document formatted for wet signature or manual e-sign
• List all signers with contact information

Output

## Signature Request: [Document Title]

### Document Details
- **Type**: [MSA / NDA / SOW / Amendment / etc.]
- **Parties**: [Party A] and [Party B]
- **Pages**: [X]

### Pre-Signature Check: [PASS / ISSUES FOUND]
[List any issues that need attention before sending]

### Signing Configuration
| Order | Signer | Email | Role |
|-------|--------|-------|------|
| 1 | [Name] | [email] | [Party A Authorized Signatory] |
| 2 | [Name] | [email] | [Party B Authorized Signatory] |

### CC Recipients
- [Name] — [email]

### Status
[Sent for signature / Ready to send / Issues to resolve first]

### Next Steps
- [What to expect after sending]
- [Expected turnaround time]
- [Follow-up if not signed within X days]

Tips

1. Check entity names carefully — The most common signing error is incorrect legal entity names.
2. Verify authority — Make sure each signer is authorized to bind their organization.
3. Keep a copy — Executed copies should be filed in ~~cloud storage or ~~CLM immediately after execution.

zoom-oauth

帮助你选择并排查 Zoom OAuth 认证配置、权限范围与令牌刷新策略。

esignatures-io-automation

通过 Rube MCP 自动处理 Esignatures IO 的电子签署与文档流程。