Contact

How can we help?

Choose the inquiry that fits and we'll route it to the right team.

Start free Contact us

Request a demo

See WQ3 with your own documents and workflow.

Contact sales

Plans, quotes and Enterprise, API or Dedicated pricing.

Enterprise inquiry

Organization-wide rollout, integration and deployment.

API inquiry

Access to the WQ3 API and embedded signing.

Partner inquiry

Resell, implement or integrate WQ3.

General contact

Any other question.

Start with the workflow you want to improve

Make your inquiry concrete by describing one document’s journey from preparation to final storage. Include the document type, who participates, whether signers are inside or outside your organization, and where the process currently becomes difficult. This gives the discussion a practical focus beyond a general request for electronic signing.

If available, add your expected usage, the departments involved, and your intended launch date. Separate essential requirements from items you can explore later, particularly when procurement, legal, or IT colleagues will contribute to the evaluation. If you are still exploring, share what you know and identify the questions that remain open.

Frame requirements for each signer

For questions about signature strength, explain the document’s purpose and any requirements set by your organization or the receiving party. Mention whether you are considering electronic signature, remote signing, or token signing, or need to understand the differences. Requirements can vary by participant: WQ3 allows different levels for signers within the same document.

Describe identity-verification needs separately from signature-level requirements. eKYC is an account-verification add-on, not a fourth signing level, and can be required with any level. For cross-border use or formal legal review, identify the relevant countries and the questions your legal adviser needs to assess rather than assuming one level suits every situation.

Turn technical questions into a clear scenario

For a technical inquiry, describe where signing should begin in your existing system and what should happen after completion. Identify the system, who initiates the process, and where completed documents need to go. Present these as requirements to assess, rather than assuming a ready-made integration exists for the system you name.

List any operational, deployment, or permissions requirements as topics that need confirmation. For security review, identify the evidence you want to examine, such as connection protection, access control, document fingerprints, the audit trail, and the completion certificate. Highlight your IT team’s priority questions to keep the discussion focused on the evaluation decision.

Use helpful examples without exposing sensitive data

A brief workflow description is often enough for an initial inquiry; a complete contract is not necessary to explain a signing problem. If an example would help, prepare a redacted version that removes personal or confidential information unrelated to the discussion. Do not include passwords, private keys, login credentials, or API access tokens in your message.

Finish by stating the outcome you need: clarifying a requirement, evaluating a signing workflow, or preparing questions for internal review. If your concern is proving a document’s authenticity later, explain who will need to check it and what they must confirm. This connects the discussion to your intended use of the audit trail, completion certificate, and public check page.