Maple eSign

Get back to sending and signing.

Maple includes straightforward email support for signers and senders, with practical steps for invitations, fields, identity checks, completion, and integrations.

Help for signersHelp for senders

Fix the signing problem without sharing the agreement.

A timestamp, browser, device, page number, and exact error usually give support what it needs.

TERMS
Question about the agreement

Ask the sender or your adviser. Maple can help with signing, not interpret the agreement.

PERSON
Wrong name or recipient

Stop and contact the sender. Your invitation is personal and should not be forwarded.

VIEW
Document will not load

Record the browser, device, time, and exact message, then try the invitation again once.

FIELD
A required field is blocked

Share the field label, page number, and visible error without sending the document contents.

SEND
Submission failed

Keep the page open, capture the visible status, and avoid repeated submissions while support checks the state.

COPYavailable
Need the completed document

Ask the sender how the sealed final package will be delivered for this agreement.

Send the details that move the issue forward.

A clear, redacted issue record is usually enough for basic email support to reproduce and resolve the problem.

  1. 01
    Name the workflow
    State whether the issue is in preparation, routing, invitation, signing, completion, API, or webhook delivery.
  2. 02
    Capture safe context
    Include the time, browser, environment, visible status, and error code, with recipient and document data redacted.
  3. 03
    Share the last good step
    Describe what worked immediately before the issue and whether one retry changed the result.
  4. 04
    Email the record
    Use your established Maple support contact and keep secrets, full links, and document contents out of the message.

Completion creates a complete final record.

After every required person finishes, Maple seals the final PDF, creates the Certificate of Completion, and attaches the audit history.

The sender can retrieve the package and deliver it through the workflow established for the agreement.

AGREEMENT · EXAMPLE
Agreement status
Preview

Signing

Complete

Every required action recorded

Final document

Sealed PDF

Certificate and SHA-256 hash included

Delivery

Sender workflow

Final package delivered as arranged

Share the issue, not the sensitive material.

Built into Maple
A redacted screenshot of the interface can help when it contains no document, recipient, or identity data.
A timestamp, browser version, workflow stage, document id, and error code are usually enough.
Important context
Do not send a full signing link.
Do not send passwords, API tokens, webhook secrets, or one-time codes.
Do not send a signature image, government ID, completed PDF, or unredacted document.
Do not put personal information into a support message unless Maple specifically asks for a safe, approved detail.

Quick answers when work stops.