What should you try before contacting support?

Search first, because they ask you to

systeme.io puts the same instruction on two separate pages, and marks it Important on one of them: search the help pages before writing, because most questions have already been answered there.

A third route sits next to it and gets less attention. systeme.io publishes tutorial videos covering a basic walkthrough of every main feature, offered as the first of its three ways to get help.

The three things the form wants

The contact form names them before the message box, so having them ready turns one round trip into none.

• The email address on your systeme.io account. It is the first thing the form asks for, so check which address the account actually uses.
• The URL of the page involved, where a page is involved at all.
• Anything else that helps resolve it. This is where what has already been tried belongs, so the first reply is not a link that has already been read.

The form also carries a file attachment control, which is where a screenshot of the error goes.

The page lives on systeme.io's public site under /support rather than in the dashboard. Its own line above the fields asks you to write only if the answer was not on the help pages, which is the same order both help articles set.

Pick the right door

Several things that look like support tickets are handled somewhere else entirely, and two of them are standing offers rather than problems to report.

The rule that catches people out

Posting a technical problem in the Facebook group instead of writing to support. systeme.io states that doing so will cause significant delays in resolving the issue, and the group rules list reporting technical problems as a rule violation rather than a preference.

Two more rules from the same page apply before posting there. Tagging the admins, and the founder in particular, is not allowed. Neither is asking for a feature in the comments under a post announcing one.

The group is for marketing strategies and how to use the platform. Anything else belongs in an email.

If it is a walkthrough rather than a fault

Some questions are too broad for a ticket, and systeme.io has two documented calls for exactly that. A one hour kickstart session at no charge on any annual plan or the Unlimited monthly plan, and a two hour technical call at $57 that anybody can buy. Both are arranged by emailing support.

Weigh that up before writing a long message that is really a request for a tour.

What a good first message contains

Nothing exotic, and all of it comes off the form's own prompts.

1. The account email, stated even where it matches the sender.
2. The exact URL of the page or funnel step involved.
3. What was expected, and what happened instead.
4. What has already been tried, including the help article that did not solve it.
5. A screenshot attached, where there is something on screen to see.