Referral programme rules
The rules the referral programme enforces: who may take part, what does not earn a reward, how self-referral is treated, which checks run, and the limits with their real numbers. The programme is not switched on for accounts at the moment.
- Who
- Anyone sharing a referral link
- Plan
- Active paid subscription on a plan the programme covers
- Role
- Billing access to view the Referrals page
Before you start
- The referral programme switched on for your account
A referral reward moves real money: it extends a paid subscription by a month. The rules on this page are what keeps that defensible — for you, for the business you invited, and for every other customer sharing a link. The Referrals page links to the Terms of Service, which govern your use of OMAI generally.
Who may take part
- Organisations with an active subscription that is being paid for, on a plan the programme covers. The shipped setting covers Starter and Growth.
- A trial account cannot hold a link or earn a month, however far into the trial it is.
- Anyone on the account with billing access can share the link; only an Owner or an Admin can create it.
- The link belongs to the organisation, not to the person who pressed the button. It survives team changes and plan changes.
- An organisation whose account is suspended, frozen, or pending deletion cannot be issued a link, and rewards on it are held.
What does not earn a reward
None of the following is punished. They simply do not produce a reward, and the Referrals page says so honestly through the status on the row.
- Referring your own business, or a business whose signup email belongs to a member of your organisation.
- A business that signs up and only ever trials. Payment for a plan is what creates a reward.
- A business that pays on a plan the programme does not cover, or that cancels after paying and before the referral qualifies.
- A payment that is refunded inside the 14-day verification period.
- A business that already had an OMAI account. Attribution is written when an organisation is created and cannot be added later.
- A signup more than 30 days after the click, or in a browser that never carried the referral.
- Loading the link in the background — inside an image tag or a script, for instance — so visitors are counted without ever choosing to open it. Only a real page visit attributes.
Self-referral
When an account signs up through your link, the signup email is compared with the email addresses of your own organisation’s members. The comparison ignores the tricks that hide a match: capitalisation, a +tag suffix, and — for gmail.com and googlemail.com addresses — dots inside the name. So Dana.Cohen+omai@gmail.com and danacohen@gmail.com are treated as the same person.
A match does not silently drop the referral. The referral is recorded, a review flag is raised on it at that moment, and the reward stays at In progress until a person resolves the flag. That way the timeline is honest and a genuine case — a colleague opening a second, separate business, say — can be released by review rather than lost without explanation.
The checks that run
Alongside the email comparison, a small battery of checks looks for evidence that the two sides of a referral are the same actor. Every one of them raises a flag for a person to look at. None of them rejects a reward by itself, because each has legitimate explanations — shared offices, family cards, one accountant setting up two businesses.
| Check | What it compares | What it does |
|---|---|---|
| Signup email | The referred account’s signup email against the members of the referring organisation. | Raises a flag when the account is created. |
| WhatsApp business number | Whether both organisations use the same WhatsApp number. | Raises a flag. |
| Payment card | The last four digits, the card brand and the expiry date on both sides. | Raises a flag. Family and company cards can match legitimately, so this is evidence only. |
| Network address | Whether the visit that converted came from an address your organisation has signed in from recently. Addresses are compared as one-way hashes, never stored in the clear. | Raises a flag. Shared offices and mobile networks collide legitimately. |
| Signups per link | How many signups one link attracted in 24 hours. | Raises a flag above 20. |
While a flag is open the reward waits at In progress. If review finds nothing wrong, the flag is released and the reward continues along its normal path. If review confirms abuse, every reward on that referral that has not already been applied moves to Not eligible.
The limits, with their numbers
| Limit | Value |
|---|---|
| Attribution window | 30 days from the click. The same number governs the cookie and the server-side check. |
| Referrals per referred business | One, ever. |
| Rewards per referring organisation | 12 approved or applied in any rolling 365 days. |
| Verification period | 14 days from the referred business’s first plan payment. |
| Life of an approved reward | 90 days, then it expires. |
| Signups on one link before a flag | More than 20 within 24 hours. |
| Visits recorded per link per day | Up to 2,000. The link keeps working past that; further visits that day are not recorded. |
| Requests to a referral link | Up to 30 a minute from one network address. Beyond that the visitor still reaches the signup page, without attribution. |
| How long visit records are kept | 210 days, then they are deleted. Reward history is not affected. |
What is recorded, and what you can see
A click records a visit row. It holds a random identifier for the visit, the channel the link travelled through, and one-way hashes of the network address and browser identifier — the raw values are never written down. The referral itself records which carrier attributed it, and nothing about the person: no name, no email address, no phone number.
- You see counts, stages, statuses and dates. You never see the identity of a business that signed up through your link.
- Review flags are not shown to you. The reward simply stays In progress while one is open.
- Only OMAI staff reviewing a referral can see both sides of it, and those privileged actions are recorded in an audit log.
- How OMAI handles personal data generally is covered in How OMAI handles your data.
If you disagree with an outcome
Start with the Reward history table: the status on the row is the current verdict, and it is re-derived every hour rather than frozen at the moment of signup. If it still looks wrong, write to support@omai-software.com with the date you shared the link, the date the business signed up, and the status shown on the row. Support can tell you which condition is outstanding; the detail of a review flag is not something we relay.
Can I run ads for my referral link?
The programme does not police where you share the link. What it does check is the outcome: each referred business has to be a separate business that pays for a plan and keeps it through the verification period.
A flag was raised on a referral that is completely legitimate. What now?
Nothing is lost. The reward waits at In progress while a person reviews it, and if the review finds nothing wrong the reward continues as normal.
If OMAI disables a referral code, are earlier referrals cancelled?
No. Disabling a code stops future attribution only — the link no longer attaches new signups. Referrals and rewards that already exist keep their status and continue to be assessed every hour.
