Contact us
We'd love to hear from you. Choose a category below to get in touch.
How to send useful feedback
Utility Tally is built around practical tools and clear supporting guides. The most helpful messages include the page you were using, what you expected to happen, what actually happened, and whether the issue appeared on desktop, mobile, or a specific browser. If the issue involves a generated invoice, QR code, JSON conversion, image resize, timestamp, or color result, include a non-sensitive example so we can reproduce the behavior.
Please avoid sending passwords, private keys, customer records, payment details, health information, or other sensitive data by email. If you need to describe a private workflow, replace real values with placeholders. We can usually investigate formatting and usability issues without seeing confidential information.
Have a general question about our tools or website? Drop us a line.
Found something that isn't working right? Let us know so we can fix it.
Have an idea for a new tool or an improvement to an existing one?
Questions about how we handle data or our privacy policy?
What we review
We review bug reports, article corrections, tool suggestions, confusing instructions, broken links, accessibility concerns, mobile layout problems, and examples where a result needs clearer explanation. We also welcome ideas for new utility guides that would help visitors understand how to use browser tools safely and accurately.
Utility Tally cannot provide personalized legal, tax, accounting, security, or compliance advice. For those topics, use the tools as general helpers and confirm the final decision with a qualified professional or approved internal process.
Response expectations
Utility Tally is a free resource, so response times may vary. Messages with a clear page URL, device type, browser, and short reproduction steps are easier to review than broad requests. If you are reporting content that may be outdated, include the exact sentence or section and, when possible, a reliable source we can check.
We prioritize issues that affect tool accuracy, privacy expectations, mobile usability, accessibility, broken navigation, incorrect internal links, sitemap coverage, and confusing instructions. Suggestions for new guides are also useful when they connect directly to an existing Utility Tally workflow.
Before contacting us
If a tool result looks wrong, try the same task once with a small example that contains no private information. This helps separate a tool issue from a browser setting, pasted formatting problem, unsupported file, or unusual source data. For conversion tools, check whether the input is valid before conversion. For QR codes, scan the code from the screen and confirm the final destination. For invoices and estimates, review tax, discount, and line item settings before reporting a totals issue.
If you are suggesting a new article, include the question a visitor would be trying to answer and which existing tool it should support. The best guide topics help someone understand what to do before using a tool, what the result means, and what they should check afterward.