We review it
Your request goes to the right team based on the topic you chose.
What happens after you send your message
The WQ3 team reviews your message and replies by email as soon as possible on business days.
We get in touch
We reply by email or phone to understand your needs and agree the next step.
We propose a fit
A quote, a walkthrough session or an integration plan, depending on your request.
Helpful details to include
The kind of documents you sign, roughly how many users, the systems you want to connect, and any legal or security requirements your organisation has.
Start with one complete workflow
Choose one agreement workflow as your starting point and map it from preparation to storage of the signed record. Identify who prepares the document, who reviews its final wording, who signs, and who needs access after completion; this separates signing needs from internal approval procedures.
Define what your organisation should validate before wider adoption, such as a recipient completing the signing journey, a reviewer inspecting the audit trail, and someone checking the final file. A sanitised example can make the discussion concrete without exposing confidential contract details in your initial inquiry.
Translate policy into signer requirements
Turn your contracting policy into requirements for each signer rather than assuming everyone needs the same level. WQ3 allows different levels for different signers within one document, using exactly three levels: electronic signature, remote signing and token signing.
Use the enterprise discussion to distinguish everyday agreements suited to electronic signature from formal or high-value contracts requiring remote or token signing. The eKYC add-on verifies the account holder and can accompany any level; it is not a fourth signing level. Your legal team should confirm the requirements applicable to each use case.
Frame integration and deployment questions
Beyond naming systems, describe the information and documents that need to move between them: where the final draft starts, when it becomes ready for signing, and where the completed record and evidence should be kept. Separate launch essentials from improvements that could be considered later.
Capture the questions your IT team needs resolved about access, permissions and deployment boundaries. These are requirements to evaluate, not assumptions that a particular connector or hosting model is available. Before committing to a project scope, ask which needs are supported, which require further review, and which remain your organisation’s responsibility.
Prepare an evidence and privacy review
Involve security, privacy and records stakeholders early, identifying the evidence each needs to assess the signing workflow. WQ3 provides tamper-evident final documents, an audit trail and a completion certificate, so your review can examine how these support your own record-keeping procedures.
Include the public verification page in that review: it enables authenticity checks without an account and displays signer names, signature levels and timestamps. Discuss how this fits your privacy requirements, and raise questions about data processing under Egypt’s Law 151/2020. Alignment with legislation does not replace an assessment of your organisation’s specific obligations.
Explore more
Related pages
Request a demo
See WQ3 with your own documents and workflow.
Learn moreContact sales
Plans, quotes and Enterprise, API or Dedicated pricing.
Learn moreAPI inquiry
Access to the WQ3 API and embedded signing.
Learn morePartner inquiry
Resell, implement or integrate WQ3.
Learn moreGeneral contact
Any other question.
Learn moreStart your first signing journey today.
Create your WQ3 account, or talk to us about your organization’s requirements.
Frequently asked questions
Do we need a complete rollout plan before contacting you?+
Your inquiry need not be a finished plan. Start with a proposed workflow and clearly identify the decisions that remain open.
Should we include a real contract initially?+
A workflow description or sanitised example can explain the need. Avoid including personal or confidential information unnecessary to the inquiry.
Who should participate internally?+
Consider the workflow owner, legal, IT, security and privacy representatives. Include records management when retention and review requirements affect the scope.
Can we assume our requested integration is available?+
No. Describe the required information flow and request confirmation of the supported scope before planning implementation around it.
Does legal alignment establish validity for every agreement?+
No. Egypt’s Law 15/2004 grants legal validity when its conditions are met; review document and signer requirements for your particular use case.