Platform

Start here

Platform overview

Guide, Pulse and Act

Guide Pulse Act
Solutions
Resources
Company

From request to done, across your systems and channels.

Act takes requests from inside an application, Microsoft Teams or WhatsApp, with AI agents and automations carrying out the approved actions on the user’s behalf.

  • One request across several systems
  • Connected securely through your APIs
  • Every action within existing permissions
A purchase order asked for in one sentence, run across the systems, and seen in the ERP.

A single task can touch several applications.

  • Look up a record in one.

  • Update another.

  • Send a confirmation from a third.

AI agents that do the work.

Agents answer questions, look up information and carry out approved business actions in connected applications.

One request, many systems.

Work that spans several applications runs as a single flow, without switching screens.

Start work from any channel.

Trigger a workflow from the Resource Center, a Microsoft Teams chat or a WhatsApp message. The agent keeps the conversation’s context from one message to the next.

From the Resource Center in Microsoft 365, someone asks for access to the Finance shared drive, and it is approved and granted.

In the Resource Center

In a Microsoft Teams chat, the agent remembers who the laptop is for and when they start.

Automations on demand.

Users see the automations available to them and start them with a click or a message.

Built for your processes.

ArkaFlows helps you identify the right workflows to automate, and agents are set up for your own workflows and applications during implementation.

Connected through your APIs.

A secure integration layer connects ArkaFlows to your enterprise applications, with credentials and authentication managed centrally.

ArkaFlows

Agents and automations

Secure integration layer

Credentials and authentication, managed centrally

Your enterprise applications, through their APIs

  • SAP
  • Dynamics 365
  • Salesforce
  • Workday
  • ServiceNow
  • Oracle
  • Core banking

Built for enterprise load.

Rate limiting, throttling and error handling keep integrations stable and predictable.

Within the rules.

Every agent and automation respects user access in every channel, and only approved actions are carried out.

  • Create PO-⁠2041 for $4,000 Allowed: you can raise purchase orders
  • Approve PO-⁠2041 Not carried out: approval stays with your line manager

The same rules apply in the app, in Microsoft Teams and on WhatsApp.

Built around your processes.

Agents are set up for your specific workflows and applications during implementation.

Take the repetitive work out of everyday processes.

What the agents take on in each system your teams use.

SAP

Routine SAP work, done on request.

  • Raise a purchase requisition from a plain-language request in Microsoft Teams. The agent fills in material, quantity and cost centre and submits it into your approval workflow.
  • Check the status of a purchase order, goods receipt or invoice without logging in to SAP.
  • Turn master data requests into complete vendor, customer or material records, with your data team approving before anything is created.
  • Move information between SAP and your other systems through SAP’s APIs, within existing authorisations.
Workflows in SAP

Salesforce

Less admin, cleaner data.

  • Log a call, update a next step or move an opportunity stage from a short request in Microsoft Teams, written back to Salesforce through its APIs.
  • Check the status of a case, quote or order without searching through records.
  • Pull related information from connected systems, such as billing, ERP or support, into one answer about an account.
  • Route requests, such as discount or quote approvals, into your existing Salesforce approval processes.
Workflows in Salesforce

Workday

HR requests, handled in one conversation.

  • Check a leave balance and request time off in one exchange, written into Workday through its APIs.
  • Start common requests, such as updating an address or requesting an employment letter, from Microsoft Teams.
  • Remind managers of pending approvals and let them act on simple ones without searching their Workday inbox.
  • Carry onboarding tasks across Workday and other systems, such as IT access requests in your service desk.
Workflows in Workday

Dynamics 365

Work that moves between Dynamics 365, Microsoft Teams and your other systems.

  • Create and update Dynamics 365 records, such as leads, cases or purchase requisitions, from a request in Microsoft Teams, through Dynamics 365’s APIs.
  • Check the status of an order, case or vendor invoice without opening the application.
  • Carry a process across Dynamics 365 and other systems, such as passing an approved order to a logistics partner’s platform.
  • Every action within the user’s existing Dynamics 365 security roles.
Workflows in Dynamics 365

ServiceNow

Requests raised, tracked and fulfilled from a conversation.

  • Raise an incident or service request from a plain-language message in Microsoft Teams. The agent picks the right catalogue item and fills in the details through ServiceNow’s APIs.
  • Check “where is my request?” and get the current status and assignee in seconds.
  • Complete routine requests end to end, such as access or password requests, where your fulfilment process allows it.
  • Pass information between ServiceNow and other systems, such as HR events from Workday that start onboarding tasks.
Workflows in ServiceNow

Oracle

Status, requests and follow-⁠up, handled for you.

  • Raise requisitions and expense requests from a plain-language request, created in Oracle through its APIs and sent into your approval hierarchy.
  • Answer “where is my requisition?” or “why is this invoice on hold?” with live status from Oracle.
  • Chase pending approvals and close-task owners with reminders, so period close keeps to its calendar.
  • Move information between Oracle and your other systems, within existing roles and approval rules.
Workflows in Oracle

Core banking

Routine banking operations, handled on request.

  • E-⁠KYC: customer details captured and checked, required documents confirmed, and the record prepared for approval in your core banking system.
  • Customer and account look-ups, such as balances, account status or loan details, for authorised staff without navigating several screens.
  • Bank statement reconciliation: statement lines matched to ledger entries, with exceptions listed for review.
  • Service requests, such as card blocks, cheque book requests or standing order changes, raised and tracked across your core banking and service systems through their APIs.
Workflows in core banking

Use casesWorkflow automation

FAQs about Act

Not answered here?

Ask us directly
What can the agents do?
Agents answer questions, look up information and carry out approved business actions in connected applications.
Where can people start a workflow?
From the Resource Center, a Microsoft Teams chat or a WhatsApp message. The agent keeps the conversation’s context from one message to the next.
Can one request cover several applications?
Yes. Work that spans several applications runs as a single flow, without switching screens.
How does it connect to our applications?
Through your APIs. A secure integration layer connects ArkaFlows to your enterprise applications, with credentials and authentication managed centrally.
Will it cope with enterprise volumes?
Yes. Rate limiting, throttling and error handling keep integrations stable and predictable.
Can an agent do something a user is not allowed to do?
No. Every agent and automation respects user access in every channel, and only approved actions are carried out.
Are the agents set up for our own processes?
Yes. Agents are set up for your specific workflows and applications during implementation.

See ArkaFlows on the systems you already use

Book a demo on your own applications, or ask for a quote for your organisation.