Chaindoc support for e-signatures and documents

Within 24 hours on business days. Most tickets actually get a reply the same day, especially if you submit before 3 PM CET. If you mark yours as critical, the team treats it as a priority and gets back to you faster. You'll get an email confirmation with a ticket number as soon as it's received.

Include the document or signature ID, the steps that led to the error, your browser and OS version, and a screenshot or log file if you have one. The more context you give, the fewer back-and-forth messages it takes to fix things. If you're hitting an API error, paste the response body and HTTP status code too.

The ticket form on this page is the fastest way to reach the team. You can also email support@chaindoc.com directly. For general, sales, or partnership questions, the contact page is a better fit. For billing or plan changes, check the pricing page first. All channels go to the same team, but the ticket form gives you a tracking number and status updates.

Production handles real documents and legally binding signatures. Staging is the environment where you can try API calls, signing flows, and integrations without affecting live data. Worth using before you push anything to production.

Create a ticket and select "Critical priority." Include the timestamp, error code, browser, and any document IDs involved. The team will acknowledge the report and provide status updates as the issue gets resolved. If you're blocked on signing a time-sensitive document, mention that in the subject line so it gets flagged immediately.

Yes. Select "API & integrations" as the category when you create your ticket. Describe your use case and what you've tried so far. An engineer who works on the API will pick it up. Most integration questions get answered in one reply. If you're stuck on authentication or webhook setup, mention that upfront so we can skip the basics.