Skip to main content
Contact support when a Mythos problem continues after you follow the relevant troubleshooting steps. Use one channel and keep the conversation there so the details stay together.

​
Choose a support channel

  • In-app form — open Help in Mythos and send the request from your account.
  • Email — write to support@mythos.new.
  • Telegram — message @mythos_support.
The three channels cover the same product support. Choose the one that is easiest for you to follow.

​
Send a useful report

1

Name the affected project

Include the project URL or project ID. If the issue is account-wide, say which page you were on.
2

Describe the action

Tell us what you clicked or asked Mythos to do immediately before the problem appeared.
3

Show the result

Include the exact visible message and explain what you expected instead. A screenshot is useful when the issue is visual.
4

List what you already tried

Mention a refresh, a focused retry, or another step from Troubleshooting. This prevents repeated work.
Never send a password, sign-in code, private key, access token, or full database credential. Support does not need secret values to investigate a Mythos issue.

​
What support can help with

Support can investigate the Mythos product and the actions it manages, including:
  • sign-in and account access;
  • the dashboard, workspace, editor, chat, and preview;
  • builds or edits that repeatedly fail or produce an unexpected product error;
  • connecting a supported service through the Mythos interface;
  • publishing and opening the public result;
  • an unexpected usage balance after a failed Mythos action.

​
What remains under your control

Some problems happen outside the Mythos product. Support can help identify the boundary, but you remain responsible for:
  • data, permissions, policies, and settings inside a service you connected;
  • third-party outages or account restrictions;
  • code, hosting, or tools you operate outside Mythos;
  • general implementation work that is unrelated to a Mythos product failure.
Mythos can still build integration behavior inside the workspace. This boundary only means support cannot administer or repair an external account on your behalf.

​
Follow up safely

Reply in the same channel if you discover a new message or reliable reproduction step. If support asks for more context, share the smallest screenshot or identifier that demonstrates the issue and remove unrelated personal or customer data first.