Keel Rules

Change a plan rule by typing.

Eligibility, incentives, contribution rules. Write what you want in plain English and it takes effect. No ticket, no specialist, no waiting on IT.

Configure the plan year by typing.

Write a plain-English sentence and Amanda compiles it into real plan logic. No ticket queue, no specialist, same day.

app.keel.com/rules
Rule composer
Wellness incentive
Active
rule.keelcompiled · 0.4s
you>
compiled to plan logic
Pick a rule on the left, or flip the toggle. Each one is a sentence Amanda compiled.
Illustrative. Example rules and counts, not a live plan configuration.
Why it's different

Plan config without the ticket queue.

The old way

File a request and wait for a specialist.

Every change is a ticket to the ben-admin's config team.
Days of turnaround for a one-line eligibility tweak.
Logic lives in a system only the specialist can read.
You find out it was wrong when an employee gets the wrong plan.
With Keel

Type the sentence. It is live.

Write the rule in plain English, Amanda compiles it instantly.
See exactly what it will do before you switch it on.
Every rule reads back as the sentence you wrote, not opaque code.
Flip it off the second something looks off. No ticket to reverse it.
By the numbers

A sentence in. Real logic out.

Same day
From idea to live rule
0
Tickets to the config team
Plain English
No syntax to learn
1 click
To switch a rule off
Better together

The rules drive the whole platform.

A rule is not a note in a doc. It actually runs, everywhere the suite touches an employee.

Questions

The details.

Do I have to write it perfectly?
No. Write it the way you would say it to a colleague. Amanda compiles your sentence into structured logic and shows you exactly what she understood, in chips you can read. If it is not quite right, you rephrase or adjust a chip, and it recompiles. Nothing goes live until you approve.
What kinds of rules can it handle?
Eligibility (waiting periods, class definitions, dependent rules), incentives (wellness credits, surcharges), contribution and cost-share logic, plan visibility, and enrollment windows. If it is a decision the plan year makes, you can usually express it as a sentence here.
Is it safe to let a rule go live?
Every rule is checked against compliance guardrails before it activates, and you see a preview of who it affects. You can run it in a dry-run first, switch it off in one click, and every change is logged with who made it and when. It is faster than the old way and easier to undo.
What does this do for the broker?
You configure plan years for every client without a config specialist or a ticketing dependency on the ben-admin. Mid-year changes that used to cost you days now take a sentence. It lets a lean team manage a big book of business, and respond to clients the same day they ask.
Keel Rules

Say it once.
It runs all year.

See a plain sentence become real plan logic, and take effect, in one tap.