Skip to main content

​
Ask Ana

Ana knows what she can and can’t do. If something isn’t working the way you expect, try asking her directly in your chat on app.textql.com — you can ask questions like “why did this query fail?” or “can you do X?” and she’ll walk you through what’s going on. It’s the fastest way to debug.

​
Check the FAQ

Most common questions are already answered in our Frequently Asked Questions. Start there — it’s the fastest way to get unblocked.

​
Submit a Ticket In-App

Click the ? button in the bottom-right corner of app.textql.com. Describe your issue and submit — our engineering team gets notified immediately. You can attach screenshots and a .har file in the same form.
Bugs reported with a HAR file get resolved faster. A network trace shows the exact request that failed — its status, timing, headers, and payload — so our engineers can pinpoint the failure instead of inferring it from a description and trying to reproduce it blind. For loading, timeout, and network errors it is often the difference between a fix and a round of follow-up questions.See how to record and send one. Uploading through the in-app ? form strips the standard credential headers and parsed cookie arrays — but not tokens in non-standard headers, URLs, request bodies, or response bodies. Review the file before you upload it.

​
Ask in Slack

If your team has a shared Slack channel with TextQL, drop your question there. You can also tag @Ana Support to open a support ticket directly from the channel.
Don’t have a shared Slack channel yet? Reach out to your TextQL account manager or email support@textql.com to get one set up.

​
Email Us

Reach out anytime at support@textql.com.

​
Send Us a HAR File

For anything that looks like a loading, timeout, or network failure, a HAR file — a recording of every network request your browser made — usually tells us exactly which request broke and why. See Send Us a HAR File for how to record one, how to strip credentials out of it first, and where to send it.

​
Tips for Faster Resolution

  • Clearly describe the issue when opening a ticket.
  • Include screenshots or error messages when available.
  • Provide the chat URL where the error occurred, if applicable.
  • Attach a HAR file for anything that looks like a loading, timeout, or network failure.