Omoplata - Documentation

Alerts monitor your club automatically and create actionable tasks whenever something needs attention. Instead of checking every area by hand, the system periodically scans for known issues and surfaces them to your team -- each with an assignee, a status, and a history.

Navigate to Settings > Alerts to manage your alerts.

Built-in alerts

The system ships with ready-made checks that run hourly for your club. They cover the most common operational risks:

Alert	Description
SEPA file not sent	A SEPA file was created but not uploaded after 12 hours.
Bank transactions not fetched	A SEPA file was sent but no bank transactions were processed 5 days later.
Member stuck on onboarding	A member hasn't completed onboarding after 2 days.
Member without payment method	An active member has no payment method on file.
Membership pause ending	A pause ends within the next 7 days.
Member with multiple memberships	A member has more than one active membership (superseded contracts excluded).
Contract expiring	A contract ends within a configurable window (default: 30 days).

The lifecycle of an alert

Every alert moves through a clear status so nothing slips through:

Status	Meaning
Open	Active and requires attention.
Done	Resolved by a team member.
Ignored	Dismissed as not relevant.
Auto-resolved	The system detected the condition no longer exists.

Alerts can also be reassigned to another team member and reopened when a resolved issue resurfaces. Many alerts resolve themselves -- the moment a missing payment method is added, for example, the corresponding task disappears automatically.

Automatic resolution

You don't need to close most alerts by hand. Fix the underlying cause and the hourly check picks it up and marks the alert "Auto-resolved".

Handling expiring contracts

When you resolve a "Contract expiring" alert, you get three options so you can trigger the right follow-up directly:

Option	Description
Keep as is	The alert is closed and the membership is left unchanged.
Change terms	Schedules a switch to a monthly price at the end of the contract, optionally with a custom amount. The change is applied automatically on the contract end date.
New contract	Creates a new membership starting the day after the contract ends, cancels the current one on the contract end date, and sends the member a contract-signing link.

Custom rules

Beyond the built-in checks, you can define your own custom alert rules to monitor any condition -- for example, members who haven't logged in for 30 days, or unfulfilled document requests. A rule consists of:

Field	Description
Model to monitor	what is being checked (e.g. Member, Membership).
Conditions	one or more conditions that must all be met (e.g. field `created_at` is more than 30 days ago, or no payment method exists).
Check frequency	how often the rule runs.
Template	the title and body of the resulting alert. Placeholders like `{first_name}` or `{membership.plan.name}` insert values from the record.
Default assignee	optional, to assign new alerts to a team member automatically.

Visual rule builder

The visual builder for custom rules is in development. Until then, custom rules are set up technically -- ask your Omoplata team to help.