Support & Feedback

Every page inside the app has a help launcher in the bottom-right corner. Use it to reach the team without leaving your work. You need to be signed in; the launcher does not appear on the marketing site or the sign-in pages.

Open it with the launcher button, close it with Escape or the same button. When the team answers something you sent, the launcher shows an unread badge until you open it. Everything you have ever sent is listed under Settings → Your submissions.

Ask a question

1. Open the launcher and choose Ask a question (or the Question tab).
2. Type your question (up to 500 characters) or pick one of the popular questions.
3. Press Send question.

You get a confirmation email right away and a reply by email, typically within 24 hours. The reply goes to the address on your account, shown under the question box.

Report a bug (with screenshots)

1. Choose Submit ticket, then the Bug Report tab.
2. Add a short title, the product area (Dashboard, Billing, Integrations, API or Other) and a description. Steps to reproduce help the most.
3. Attach screenshots in any of three ways:
   • Choose files to pick them,
   • drag and drop them onto the attachment box,
   • paste an image from your clipboard anywhere on the form. Thumbnails appear immediately; use the ✕ on a thumbnail to remove it.
4. Press Submit ticket. The confirmation screen shows your ticket number (for example TICKET #128).

Screenshot rules: PNG, JPG, WebP or GIF; up to 5 images, up to 4 MB each and 12 MB in total. Large images are shrunk in your browser before they are sent. Anything outside these limits is rejected inline with the reason, and the rest of the report is unaffected.

Your browser, operating system, current page and app version are attached automatically so you do not have to describe them.

What happens to screenshots. The ticket text is saved and sent to the team first; the screenshots follow in a second email a moment later. The confirmation screen tells you when they are sent. If sending fails, you get a Retry button; if it still fails, the ticket is safe but the images are not, and the screen asks you to email them to support quoting your ticket number. Screenshots are only ever delivered to the team's inbox; they are not stored in Architecto.

Request a feature

1. Choose Submit ticket, then the Feature request tab.
2. Describe what to build (one line), which problem it solves, the product area and how important it is to you (Nice to have, Important or Blocking me).
3. Press Submit request. You get a request number, and the request shows as Under review.

Rate the product

1. Choose Leave us feedback (or the Feedback tab).
2. Tap a face to rate your experience, pick what it is about and, optionally, tell us more.
3. Leave OK to follow up by email on if you are happy to hear back; turn it off if you do not want any email about this rating.
4. Press Send feedback.

Emails you can expect

Every reporter email comes from Architecto's transactional sender and can be replied to directly; replies reach the support inbox. If you turned follow-up off on a rating, you receive no email about it at all.

Tracking your items

Everything you send is listed under Settings → Your submissions (/app/settings/feedback). You can also reach it from Your requests on the launcher's home screen, from your avatar menu, or from the button in any of the emails above.

• Each entry shows its number, what you wrote, the current status, and every public reply from the team, newest submission first. The tabs filter by questions, bugs, features and ratings.
• Items with an update you have not seen yet are marked New update.
• The launcher badge counts those same items; opening either the panel or the submissions page clears it.
• Bug reports and feature requests move through Received, With the team, Planned, In progress, Done and Closed. Questions are answered by email and then marked Done.
• Keep the #N number from the confirmation email; quote it when you contact support about the same issue.

Limits

• Up to 20 submissions per hour per account. Above that the form shows a short message asking you to try again later.
• Text limits: title 200 characters, question 500, description 5,000.
• Screenshots: 5 per bug report, 4 MB each, 12 MB total, image formats only.