Why do accounts get restricted, and how do you avoid it?

What restriction actually is

The account is still there, and the restriction does not delete its content. systeme.io switches off opt-ins and payments, new sales, adding contacts or students, new automation triggers, newsletters, campaigns, and students' access to the account's courses. The full list is in the table further down.

The main risk is loss of function, not immediate loss of content.

The two causes

systeme.io's article on restriction names two situations, and no others.

• Passing the contact limit set by the current plan.
• Passing a feature limit after a change of plan. That covers cancelling a paid subscription and reverting to the free plan, and moving down from a higher tier to a lower one.

Both are about size against the plan. Neither is a judgement on the business.

One gap in the article itself. It lists a move from a higher tier to a lower one as a cause, but its restriction process restricts free-plan accounts and upgrades paid ones, and it does not say which applies when the lower tier is a paid plan.

systeme.io's restriction article and its support team's emailed reply of 4 September 2026 tie the second cause only to a downgrade or a cancellation. None of the sources behind this answer says whether an account that has not changed plan can build past a feature limit in the first place, a fourth funnel on the free plan, for instance.

The warning comes first

Nothing happens the moment a limit is passed. A pre-restriction period runs instead: three warning emails, one a day, and an alert on the dashboard.

If no action is taken by the fourth day, the restriction is applied automatically.

What stops working

On the free plan a final warning email confirms that the account has been restricted, and a permanent alert is displayed on the dashboard.

What keeps working

Automations and workflows that were already running continue. Students keep their enrolments, purchases and progress, but cannot open the courses while the restriction lasts. Funnels, courses and other content are not deleted by the restriction.

That middle point has changed. The earlier copy of systeme.io's article that this answer relied on said students kept the lectures they had already unlocked, and this answer said the same. The article now says they lose access to those too.

Not deleted is not the same as still working, and the table above is the difference between the two.

The rule that catches people out

Time does not pause. Drip days keep counting during a restriction, so a delay set between lectures still runs down while the emails are held. Once the restriction ends, only the last email for the last unlocked lecture is sent.

Scheduled newsletters are worse. A send date that falls inside a restriction is removed for good rather than delayed, and an in-app notification is left for each newsletter affected. systeme.io does this deliberately, so that out of date emails do not go out on their own once the account is working again.

How to avoid it

• Watch Settings, then My plan. Items over the limit are shown in red there.
• Upgrade to a plan that fits, which raises both the contact limit and the feature limits.
• Remove enough funnels, courses, contacts or other counted assets to fit the plan before a downgrade.
• Deactivate any funnel that is not in use. In an emailed reply, not a page you can open, systeme.io support said a deactivated funnel is not counted against the plan limits, and that it can be reactivated later if the plan allows it.
• Clean the contact list when the limit that is close is the contact one.

On a paid plan it works differently

A paid account that goes over its limits is not restricted. The subscription is upgraded automatically to the next tier so that service continues without a break.

That turns a limits problem into a billing one. Coming back down means clearing the excess first, then asking support for the downgrade.

What happens to a free account left unused

Restriction does not delete content. Inactivity can. systeme.io's article on restriction ends with a separate note: if no login or activity occurs for 6 months, content may be permanently removed.

In an emailed reply dated 13 September 2026, its support team was more specific about why accounts end up suspended and have to be unlocked by support. The block is not described in the restriction article, so what this section says about the block comes from that reply rather than from a page you can open.

Support named a long period of inactivity as one of the major reasons for account suspension. A free account that has not been used for 6 months is blocked automatically, and later deleted by systeme.io's system. To get it unblocked, the account owner has to contact support.

The two sources do not describe it in quite the same way. The article speaks of content that may be removed and does not say which plans that applies to. Support's reply is about free accounts, and puts the block before the deletion. It does not say how long after the block the deletion follows.

What gets an account working again differs too. By support's emailed reply of 4 September 2026, a restriction lasts until the account is back within its plan's limits. By its 13 September reply, the inactivity block is lifted by contacting support.