Choose the correct support path
Use EZFormz technical support for problems with ezformz.net itself, including account access, site errors, broken tools, upload failures, and reproducible bugs.
Questions about a particular seller's form, product, payment, order, refund, shipping, pickup, event, or policy belong with that form owner. EZFormz support does not control the seller's transaction. For suspected fraud, impersonation, harassment, malicious content, or other abuse, use Report an issue, not a technical support ticket.
The support form warns that non-website requests may be deleted without a reply. EZFormz cannot identify an unknown seller from a payment handle alone, reverse an external payment, change a seller's refund policy, or fulfill an order.
Check System status first when several pages or services appear unavailable.
The status page performs live browser checks of the public API, authentication configuration, and a static asset, shows the observed HTTP state and response time, and repeats about once per minute. It is a current reachability snapshot, not an incident history or a guarantee that every signed-in workflow is healthy.
Submit a useful ticket
The initial support form requires a category, email, subject, detailed description, related page or link, and at least one screenshot or image. You can attach up to five images.
Include:
- what you expected and what happened;
- exact error text;
- steps that reproduce the issue;
- the browser and device type;
- the approximate time of the failure; and
- the affected page URL after removing tokens, codes, and other private query values.
The initial image should show the relevant state, but crop or redact unrelated names, buyer details, addresses, payment evidence, and account information in a trusted editor before upload. Remove location and other image metadata too; uploaded originals are not re-encoded merely to strip metadata. A ticket submission returns a short reference. Ticket creation does not send an acknowledgement email, so save the reference or use My Support Tickets when available.
Protect private information
Never include login or authenticator codes, recovery codes, passkey prompts, API or provider keys, OAuth tokens, private crypto keys or seed phrases, full payment credentials, or one-time access links. Support can investigate a missing login email using the account email and request time; it does not need the code.
If you choose EZFormz feature request, a sanitized version of the subject and details may be posted automatically to the configured community feature thread. Common emails, links, handles, phone numbers, UUID-style IDs, and requester identity values are removed, but automated redaction is not a reason to include confidential information. Write feature requests as if the product idea may be discussed publicly.
For a dashboard metric or card idea, the Want a different widget? form is a shorter feedback route. Include the metric and the decision it should support. A widget request is not a support ticket, and a submission does not promise implementation.
Follow a support reply safely
Signed-in requesters can view requester-visible messages and images in My Support Tickets. A public admin reply may also send an email notice with an expiring ticket-access link; the reply body is not placed in that email.
Treat the ticket-access link as a bearer credential. Anyone who receives a valid copy may be able to view and reply to that ticket's requester-visible thread and images. Do not forward it, paste it into another ticket, or leave it visible in screenshots, analytics, or shared chat. Use My Support Tickets instead when you can sign in.
Replying to a waiting or resolved ticket reopens it. A closed ticket cannot accept another requester reply; submit a new technical support ticket if more help is needed.
Report abuse through the dedicated workflow
Report an issue collects the reporter email, reported party, category, summary, details, and optional evidence. It creates an evidence-preserving moderation case rather than a website troubleshooting ticket. Include the relevant order or form context and transaction evidence you can safely share, but never upload account factors, private keys, or unrelated buyer data.
A confirmed abuse action can restrict the reported account or email from login, connected-app access, and new order submission. Historical orders, reports, and evidence may remain available for investigation; a report is not a promise of a specific outcome.
Support EZFormz separately
Support EZFormz is the voluntary contribution page, not technical support. It presents Cash App, Venmo, Ethereum, and Solana methods and marks methods unavailable when they are paused. Follow the live availability and exact network warning on that page before sending; EZFormz cannot reverse a transfer sent to the wrong handle, address, asset, or network.
After sending outside EZFormz, you may optionally report the amount, reference, and identifying contact details so the contribution can be reconciled. Reporting does not move the money. Donations are not required for account access, are not processed by EZFormz, and do not produce a tax receipt.
Check these current product answers first
- The current public plan is $0 and lists unlimited forms, products, and orders with no credit card required.
- EZFormz is an order-form tool, not a payment processor. Sellers provide their own payment instructions and verify and refund payments through the service that moved the funds.
- Public forms currently use
ezformz.net/f/{slug}. Custom domains are listed as a future/coming-later feature, not a current setup option. - Current public forms do not offer Save Progress or Save & Continue. Do not rely on an old seven-day resume claim or treat an old resume link as a submitted order.