Read-only by design
Zeke queries data; it does not modify it.
- Its tools are read-only lookups of your workspace's data
- A rule draft only fills in the form: nothing exists until a person saves it
- Approval and payment remain with people
Zeke, the AI agent
An AI commission agent with defined limits
Zeke assists administrators in configuring rules and obtaining answers faster. It never acts on a payment: people review, approve and pay.
Zeke
Evenq agent
Administrator: Why does Mariusz have an outstanding balance from September?
Zeke:
Mariusz Nowak has an outstanding balance of €1,240.00 from September. The payout is approved and will be included in the next pay run:
| Commission · sale INV-2112 | €1,480.00 |
| Clawback withheld · lost sale INV-2077 | −€240.00 |
| Net owed | €1,240.00 |
|---|
Open the payout
Administrator: What commission would a €30,000 sale generate for Anna under the EMEA Sales Plan?
Zeke:
Under the EMEA Sales Plan rules, the sale would generate a commission of €2,400.00:
| Attainment before the sale | 90% |
| Bracket applied | Up to 100% · 8% |
| €30,000 × 8% | €2,400.00 |
| Commission | €2,400.00 |
|---|
Simulation only: no data was saved
AI commission assistant
Zeke drafts the rules. The engine runs every calculation.
Administrators describe a rule in plain language and Zeke completes the rule form for review. Questions about the data are answered from read-only lookups, and “what would this pay?” simulations run on the same engine as the pay runs.
- Answers from your live data, with read-only access
- Never cites a record it has not read
- Asks for clarification on ambiguous requests instead of guessing
No change is saved until a person reviews it. Available to administrators.
Rule preview
Example sale€17,700.00
€10,000.00 × 5% = €500.00
€7,700.00 × 7% = €539.00
Would pay€1,039.00
Nothing is saved
The engine performs the calculation
The figures in Zeke's answers come from lookups of your data, and simulations run on the same engine as your pay runs.
- “What would this pay?” runs the real calculation, not an estimate by the model
- Balances and amounts are read from your data, per currency
No AI model can be guaranteed infallible. For that reason, nothing Zeke says can change a payment on its own.
Guards in code, not only in instructions
The limits are enforced by the product, not left to the model's discretion.
- A rule draft that relies on an invented number or an unstated assumption is refused and turned into a question
- An answer that references an ID no lookup returned is blocked
- Access is limited to administrators, and usage is metered per billing period
Boundaries
What Zeke does, and what it does not do
Clearly defined limits are what make an assistant appropriate for financial data.
Zeke does
- Draft a rule from your description, into the rule form, for you to review
- Request clarification when a request is ambiguous, instead of guessing
- Answer about salespeople, plans, commissions, payouts and balances with read-only lookups
- Run “what would this pay?” on the real calculation engine
Zeke does not
- Save, approve or pay anything: a person does
- Write to your data: its access is read-only
- Cite a record it has not read: such answers are blocked
- Retain a draft that depends on a figure you did not provide: it asks instead
- Serve salespeople yet: it is available to administrators only
Design partner programme