Workflow Automation Software Kenya

Approval nodes route each request to a named role or up the Reports-To chain. A TSR claim in KES escalates to the RSM at the Nairobi HO, a KAM credit limit on a Naivas chain order routes to the Sales Head, all inside one workflow up to 7 levels.

Yes. A Condition node compares the order value in KES against the outlet credit limit. If exceeded, the workflow holds the order, notifies the KAM on WhatsApp Business, and pushes an Approval node to the Sales Head before posting moves forward.

Communication nodes fire WhatsApp Business messages, email, or in-app notifications. WhatsApp Business is the default for field roles like TSR, KAM, MR, FST, and agronomist because it is the most-used comms channel across the 47 counties.

Yes. An Approval node closes the loop on a refund or distributor settlement, then a Webhook node hands the payout off to M-Pesa Till or PesaLink. Reference, amount in KES, and approver name are stamped to the audit trail automatically.

A Condition node watches the eTIMS posting status. On failure, the workflow escalates a notification to the FST and accounts team on WhatsApp Business, retries through a Webhook node, and surfaces the order in a Pending Action queue for the RSM.

Yes. The Reports-To chain follows the territory tree across the 47 counties. A MR sample stock request in Mombasa routes to the local RSM, while an upcountry van-sales order from Eldoret routes to the Western RSM, no manual reassignment.

Drafts run separate from Active. Admins edit a copy, test the new logic against a sample KES order, then publish a new version. Approvals, notifications, and KRA eTIMS handoffs already in flight finish on the old version without disruption.

Summary cards display Total, Active, Drafts, and Entity Types. The library table lists Name, Entity, Trigger, Nodes, and Priority. Admins filter by entity such as Order, Customer, or Claim and see which county-level routes are running today.