Skip to main content

Contact Any.do Support (Chat, Contact Form, and Sending Files)

Get quick answers with chat support, then share files and details when you need deeper help.

Updated this week

Need help with Any.do? This guide explains the fastest ways to reach support, what to send, and how to capture screenshots, screen recordings, and browser logs. You do not need to be technical to contact us. The easiest place to start is Chat Support, where you can get help 24/7 from our AI assistant, and escalate to a human support agent if needed.


βœ… What is the best way to contact support?

Use the option that matches your situation.

πŸ’¬ Option 1: In-app Chat Support (recommended first)

Chat Support is the best place to start for most questions. It is available 24/7 and includes an AI assistant that can help with:

  • How-to questions and workflows

  • Feature guidance and troubleshooting steps

  • Finding the right Help Center articles (you can open articles directly from the widget)

If the issue is urgent, complex, or the AI assistant cannot solve it, you can ask to escalate to a human support agent.

A few helpful things to know:

  • If you already have a chat waiting for a human reply, you can still open a new conversation with the AI assistant to keep asking questions without waiting.

  • If multiple conversations are open, they may sometimes be merged automatically. This does not mean anything was missed. Our team reviews all messages and replies to every issue.

  • If a conversation closes after a period of inactivity, you can always reply to reopen it or start a new one.

Expected reply times (for a human agent):

  • Priority requests: usually within 1 to 2 business days

  • Standard requests: usually within 2 to 4 business days

πŸ“ Option 2: Contact Form (best for bugs, payments, and complex cases)

The contact form is the best choice when:

  • You are reporting a bug or a technical issue that needs investigation

  • You need help with billing, invoices, plan changes, or subscription questions

  • You want to attach screenshots, videos, or documents upfront

Expected reply times:

  • Priority requests: usually within 1 to 2 business days

  • Standard requests: usually within 2 to 4 business days

Submit your request here: https://www.any.do/contact_form


πŸ’¬ How to open In-app Chat Support

You can open Chat Support anytime from Any.do. The Support widget keeps your chat history in one place, and it can also recommend Help Center articles while you type.

πŸ“± Open chat support via iOS/Android

Option A:

  1. Open Any.do.

  2. Open the menu (three dots).

  3. Tap Settings.

  4. Tap Support.

  5. Open Chat Support.

Option B:

  1. Open Any.do.

  2. Open Notification Center.

  3. Tap the headset icon.

πŸ’» Open chat support via Web/Desktop

Option A:

  1. Open Any.do.

  2. Open Settings (from your profile area).

  3. Select Support.

  4. Open Chat Support.

Option B:

  • Tap the headset icon (top-right).

🌐 Open chat support via our main site/Help Center

Option A:

  1. Visit our Help Center at https://support.any.do/

  2. Click on the chat widget icon to start a conversation

Option B:

  1. Visit our website at https://www.any.do/

  2. Click on the chat widget icon to start a conversation

🧾 Where to find your previous chats and updates

  • Open the chat widget again using the steps above.

  • Choose an existing conversation to continue.


πŸ“ How to send a better support request (faster answers)

We can only help based on what you share. For privacy and security reasons, we do not have access to your device screen and cannot see your app or browser from your side.

The more specific your request is, the faster we can help.

βœ… What to include every time

Please include:

  • What you are trying to do (your goal)

  • What you expected to happen

  • What actually happened

  • The exact steps to reproduce the issue

  • Your device and OS (example: iPhone iOS 18, Android 14)

  • Your Any.do platform (Web, Desktop, iOS, Android)

πŸ“Ž What to attach when relevant

  • Screenshots for issues tied to a specific screen or error

  • Screen recordings for multi-step issues or unexpected behavior

  • Browser console logs for Web/Desktop issues

  • Invoices or receipts for billing issues


πŸ“Έ How to capture and send screenshots

Screenshots help us see exactly what you see. If you’re reporting an error or something doesn’t look right, a clear screenshot can speed up the solution.

πŸ€– Capture a screenshot on an Android device

  1. Open the screen you want to capture.

  2. On most devices, press Power + Volume Down at the same time.

  3. Make sure the screenshot shows the full screen and any error message.

  4. Attach it to your chat or contact form submission.

ο£Ώ Capture a screenshot on an iOS device

  • iPhones with Face ID: press Side button + Volume Up.

  • iPhones with Home button: press Side/Top button + Home.

Attach the screenshot to your request.

πŸ’» Capture a screenshot on a Mac device

  • Entire screen: Command (⌘) + Shift + 3

  • Selected area: Command (⌘) + Shift + 4

Attach the screenshot to your request.

πŸ–₯ Capture a screenshot on a Windows device

  • Selected area: Windows + Shift + S

  • Entire screen: PrtScn (or Fn + PrtScn on some keyboards)

Attach the screenshot to your request.


πŸŽ₯ How to record and send a screen recording (screencast)

Screen recordings are the fastest way to show us what is happening, especially for bugs and multi-step workflows.

Note: If your recording-file is too big to attache to your ticket/chat, simply add it to any 3rd party cloud service and send our agents a public link for viewing.

πŸ€– Record your screen on an Android device (built-in recorder)

  1. Swipe down from the top to open Quick Settings.

  2. Tap Screen Recorder.

  3. Choose your sound setting, then tap Start.

  4. Reproduce the issue.

  5. Tap Stop.

  6. Attach the video from your Gallery.

Tip: If you do not see Screen Recorder, edit Quick Settings and add it. If you do not have a native records, please install AZ Screen Recorder via the Google Play store. After this you can simply press on the application, record the issue and attach the screen recording to your ticket/send in the chat.

ο£Ώ Record your screen on an iOS device (built-in recorder)

  1. Go to Settings β†’ Control Center.

  2. Add Screen Recording.

  3. Open Control Center.

  4. Tap Screen Recording to start.

  5. Reproduce the issue.

  6. Tap the red status bar (or recording icon) and stop.

  7. Attach the video from Photos.

πŸ’» Record your screen on a Mac device

Use QuickTime (built-in):

  1. Open QuickTime Player.

  2. Select File β†’ New Screen Recording.

  3. Record the issue.

  4. Save and attach the file.

πŸ’» Record your screen on a Windows device

Use Game Bar:

  • Start/stop recording: Windows + Alt + R

  • If needed, open Game Bar first: Windows + G


🧾 How to capture browser console logs (Web troubleshooting)

Console logs help our team debug issues on Web/Desktop. They only show technical information related to what the browser is doing.

Important:

  • Please reproduce the issue first, then capture the logs.

  • If possible, download the logs as a file, not only as a screenshot.

🌎 Capture browser console logs in Chrome

Open Console:

  • Mac: Cmd + Option + J

  • Windows: Ctrl + Shift + J

Then:

  1. Reproduce the issue.

  2. Take a screenshot of the Console.

  3. To download logs: right-click a message β†’ Save as…

🌐 Capture browser console logs in Microsoft Edge

Open Developer Tools:

  • Windows: Ctrl + Shift + I

Then:

  1. Open the Console tab.

  2. Reproduce the issue.

  3. Screenshot the Console.

  4. To download logs: right-click a message β†’ Save as…

ο£Ώ Capture browser console logs in Safari

Enable the Develop menu:

  1. Safari β†’ Settings/Preferences β†’ Advanced.

  2. Enable Show Develop menu in menu bar.

Open Console:

  1. Right-click the page β†’ Inspect Element.

  2. Open the Console tab.

  3. Reproduce the issue.

  4. To download logs: right-click a message β†’ Export as Text.

🦊 Capture browser console logs in Firefox

Open Console:

  • Mac: Cmd + Option + K

  • Windows: Ctrl + Shift + J

Then:

  1. Reproduce the issue.

  2. Screenshot the Console.

  3. To download logs: right-click a message β†’ Save as…


πŸ’³ Billing issues: what to send (invoices and proof of purchase)

For billing, refunds, plan switches, or subscription issues, we usually need a receipt or invoice so we can locate the correct transaction.

πŸ“² If you purchased through a store

Please attach your invoice from the relevant store:

  • Apple App Store

  • Google Play

  • Huawei AppGallery

πŸ’³ If you purchased directly from Any.do (Web/Desktop)

Premium invoices:

  1. Log in to the Web app: https://app.any.do

  2. Go to Settings β†’ Profile β†’ Manage Subscription.

  3. Download and share your invoice.

Workspace/Family invoices:

  1. Open Settings.

  2. Under Workspace settings, select Manage Workspace.

  3. Check the billing email and share the invoice or billing details.

For more details about invoices, please see this article.


πŸ™‹β€β™‚οΈ FAQs

πŸ€” Why do you ask for screenshots, videos, or logs?

Because we cannot see your device screen or access your browser session. For privacy and security reasons, we can only investigate what you share with us. Screenshots, recordings, and logs help us understand what you are seeing and solve issues faster.

🧐 I do not want to record my screen. Can you still help?

We are always here to help! However, for many technical issues, a screenshot, screen recording, or console logs are the fastest way to diagnose the problem. If you prefer not to record, please describe the steps clearly and include any error messages you see.

πŸ‘Ύ What should I send if I am reporting a bug?

Send:

  • Steps to reproduce

  • A screen recording (preferred)

  • Console logs (Web/Desktop)

  • The device and platform you are using

πŸ’² What should I send for a billing issue?

Send your invoice or receipt from Apple, Google Play, Huawei, or Any.do Web billing, plus a short explanation of what you need help with.

Did this answer your question?