Your rules. Your workflow.
No code.
Graicx runs on policies you control — not a black box. Decide how every service request is triaged, routed and actioned with transparent if-this-then-that rules, set once and overridden exactly where you need it.
If this, then that — for facilities.
A rule watches for a moment in a request’s life — created, triaged, flagged for review, or converted to a work order — checks your conditions, and takes an action. String several together and the busywork of triage runs itself, the way you decided it should.
Triggers
Fire on request created, triage complete, needs review, or converted to a work order.
Conditions
Match on 14+ fields — source, site, priority, category, safety flag, duplicate status and more — with operators like equals, in, greater-than and contains.
Actions
Route to a queue, hold for review, request info, auto-create a work order, auto-assign, add a tag, or reject with a reason.
Ordering
Give rules a priority and a stop-processing flag so the right one wins and the rest stand down.
Set once. Override where it matters.
Policies and rules live at three levels — account, client and site — with inheritance you can actually see. Configure a sensible default for the whole organisation, then tailor it for a demanding client or a single building without rebuilding anything.
Account
Your organisation-wide default behaviour for triage, duplicates, auto-create and auto-assign.
Client
Override the default for a specific client or contract when their requirements differ.
Site
Get specific for one building — the most local setting wins, and the source is always visible.
Automation you can trust.
Because every rule is explicit and inspectable, you are never guessing why something happened. Keep new rules in draft until you are happy, activate them when ready, and pause them instantly if priorities change.
Run fully hands-off for routine requests, keep a human sign-off on the categories that matter, and let the platform handle the routing in between.
Common
questions.
Do I need a developer to set up workflow rules?
No. Rules are built from plain dropdowns — choose a trigger, add conditions on fields like source, site, priority or category, and pick an action. There is nothing to deploy and no code to write. A coordinator or manager can create, test and activate a rule in minutes.
Can different sites or clients have different rules?
Yes. Policies and rules apply at three levels — account, client and site — with explicit inheritance. Set a sensible default once at account level, then override it for a specific client or an individual site. You can always see which level a setting comes from.
What can a rule actually do?
Rules can route a request to a queue, hold it for manual review, request more information, automatically create a work order, auto-assign it, add a tag, reject it with a reason, or stop further rules from running. Conditions can be combined across more than a dozen fields using operators like equals, in, greater-than and contains.
Will automation take humans out of the loop?
Only as far as you want it to. Every rule is transparent and can be left in draft, set to active or paused. You can run fully hands-off, require sign-off on certain categories, or anything in between — and override any automated decision.
See Graicx on your estate.
Send us your current process — a spreadsheet, a screenshot, a description of what breaks every Monday morning. We'll show you a working prototype on your data within a week. No contract required, no consultant jargon.
No obligation. We sign your NDA. Your data never leaves a UK or EU region.