Skip to content
Start a project
Start a project hello@nijora.ai

Use cases

Agents for the work between your systems.

Invoices, tickets, orders, access requests, and renewals. For each: what starts it, what the agent does, where a person decides, and which systems it touches.

Decisions take minutes. The work around them takes days.

Follow a slow case through your operation and the decision is rarely what holds it up: the time goes to finding the record, checking it against another system, re-keying it, and waiting for a reply. That's the work our agents take on, and your people keep the decisions. The workflows below are starting points, not products. Every agent is built against your systems, your rules, and your approval chain, and tested on your cases before it acts.

01 Finance operations

Invoice matching and exceptions

Clean invoices are entered without anyone re-keying them. Exceptions reach the AP lead with the PO, the receipt, the contract clause, and a proposed fix already attached.

Systems
  • NetSuite or SAP
  • Microsoft 365 or Google Workspace
  • Slack or Microsoft Teams
Sample run
Invoice exception · Finance ops

  1. Trigger

    Supplier invoice arrives in the AP inbox or a portal

  2. The agent does

    1. Reads invoices from the AP inbox and supplier portals, including scanned PDFs
    2. Matches each line to the purchase order and goods receipt
    3. Checks price and quantity variances against your tolerances, and searches contracts for approved price changes
    4. Flags suspected duplicates before they reach the payment run
    5. Enters matched bills in the ERP, ready for your normal payment run
    6. Drafts supplier queries for anything that doesn't reconcile

  3. Where a person decides

    Variances over tolerance, suspected duplicates, and any change to supplier bank details go to the AP lead with the evidence attached. The agent never releases a payment.

  4. Write-back

    • NetSuite or SAP

Sample run

  1. Read Steps: Read, Tool. It reads only what the task needs.
  2. Decide Steps: Think. The model proposes. Code checks.
  3. Check Steps: Human. When it isn't sure, it stops and asks.
  4. Write Steps: Write, Done. It writes back and leaves a record.

Select a stage to light up its steps in the run.

Invoice exception · Finance ops

Illustrative run · sample data, not a client deployment

Trigger: ap@ inbox · INV-20817 from vendor V-3307 · $48,212.00

  1. Read, 00:04.6: extract(INV-20817.pdf) → 14 lines · total $48,212.00. Schema-validated · no missing fields.
  2. Tool, 00:08.0: netsuite.get_po(PO-77310) · netsuite.get_receipts(PO-77310). Read-only scope · PO total $46,980.00 · 14 of 14 lines received.
  3. Think, 00:16.2: Line 9: 560 units at $18.40 vs PO $16.20 → +$1,232.00 · policy AP-03 limit $500 · exceeds. The other 13 lines match the PO and the receipt.
  4. Tool, 00:21.3: contracts.search(vendor=V-3307, “price amendment”). Amendment 2, signed 2026-09-01, sets this SKU at $18.40 · cited: §2.1.
  5. Think, 00:30.2: Invoice price is contractual; the PO is stale. Proposal: post the bill, request a PO update. Over-limit variance → approval required by policy, whatever the model's confidence.
  6. Human, 00:31.6: Approval requested in #ap-approvals → AP lead. Attached: PO, receipts, Amendment 2 §2.1, variance calculation.
  7. Human, 04:12.6: Approved by AP lead · 3m 41s. Approver and decision written to the trace.
  8. Write, 04:18.4: netsuite.create_bill(INV-20817) · netsuite.request_po_update(PO-77310). Scoped writes · idempotency key inv-20817 · undo: void bill until period close.
  9. Done, 04:19.0: Done · 9 steps · 38s agent time · 3m 41s waiting on approval · $0.06 model cost. trace tr_7f3a9c · ap-agent v1.4.2 · test suite passing.

Outcome: Bill posted at the contract price and a PO update requested, with the full trace on record. The AP lead made one decision, with the evidence already attached.

02 Customer operations

Ticket triage and resolution

Tickets land in the right queue with a category, the linked known issue, and a cited draft reply. Your team spends its time on customers, not on sorting.

Systems
  • Zendesk or ServiceNow
  • Salesforce
  • Jira
  • Stripe
  • Slack or Microsoft Teams
Sample run
Ticket triage · Customer ops

  1. Trigger

    New ticket arrives in the support queue

  2. The agent does

    1. Reads each new ticket, its attachments, and the customer's recent history
    2. Checks the order, the account, and billing records to find the cause
    3. Classifies by intent, product area, and severity, and routes by plan, SLA, and language
    4. Links known bugs in Jira, or files a new one with reproduction steps
    5. Drafts replies from your help center and past resolutions, citing each source

  3. Where a person decides

    A support lead approves customer-facing replies until a reply type has passed its tests and you choose to let it send. Refunds over your limit, legal threats, and security reports always go to a person.

  4. Write-back

    • Zendesk or ServiceNow
    • Jira

Sample run

  1. Read Steps: Read, Tool. It reads only what the task needs.
  2. Decide Steps: Think. The model proposes. Code checks.
  3. Check Steps: Human. When it isn't sure, it stops and asks.
  4. Write Steps: Write, Done. It writes back and leaves a record.

Select a stage to light up its steps in the run.

Ticket triage · Customer ops

Illustrative run · sample data, not a client deployment

Trigger: zendesk · ticket #58213 · “CSV export times out on large workspaces” · Enterprise plan

  1. Read, 00:00.9: zendesk.get_ticket(58213) + org history: 3 tickets in 90 days. Plan: Enterprise · first-response SLA 4h · language: en.
  2. Tool, 00:02.3: jira.search(“export timeout”) · kb.search(“large CSV export”). Top match: PLAT-4127 “Export exceeds gateway timeout” · in progress · workaround in KB-0342.
  3. Think, 00:03.9: Known issue PLAT-4127 · severity S2 · no security, legal, or refund signals. Guardrail: any of those signals skips automation and goes straight to a person.
  4. Write, 00:04.6: zendesk.update(58213) → tags [bug, export] · group Tier 2 · linked PLAT-4127. Scoped writes: tags, group, internal notes. Sending replies is outside this agent's permissions.
  5. Think, 00:06.5: Draft reply: async export workaround · cites KB-0342, PLAT-4127. Source check passed: every claim maps to a cited source.
  6. Human, 00:06.8: Draft queued for support lead review · autonomy level: suggest. In this deployment, a person sends every customer-facing reply.
  7. Human, 41:00.0: Sent by the support lead · 1 edit · 41m after the ticket opened. Edit saved as a candidate test case for engineer review.
  8. Write, 41:00.2: jira.comment(PLAT-4127) → affected orgs 7 → 8. Engineering sees current customer impact on the issue.
  9. Done, 41:00.3: Done · 9 steps · 7.1s agent time · reply sent at 41m · $0.011 model cost. trace tr_c41d02 · triage-agent v2.0.3 · test suite passing.

Outcome: Routed, linked to the known bug, and answered with a cited workaround 41 minutes after the ticket opened, inside the 4h SLA. Engineering sees one more affected customer on the issue.

03 Order operations

Order intake and order changes

Orders that arrive as emails and PDFs become sales orders without re-keying. Credit, stock, and pricing problems surface at intake, not at the loading dock.

Systems
  • SAP or NetSuite
  • Salesforce
  • Postgres
  • Microsoft 365 or Google Workspace
  • Slack or Microsoft Teams

  1. Trigger

    Buyer sends a purchase order or a change request

  2. The agent does

    1. Reads purchase orders and change requests from email, PDF, and portal exports
    2. Matches customers, ship-to addresses, SKUs, and prices to your master data
    3. Runs availability and credit checks
    4. Creates the sales order and confirms dates to the buyer
    5. Applies changes within your cut-offs, and alerts the warehouse before pick

  3. Where a person decides

    Credit holds, price overrides, and changes to orders already picked or shipped go to the credit manager or the order desk lead.

  4. Write-back

    • SAP or NetSuite

04 IT & people operations

Access, onboarding, and offboarding

Joiners start with the access their role needs, and leavers lose it when they go. Every grant is on record, with the role template or the person that approved it.

Systems
  • Workday
  • Okta or Microsoft Entra ID
  • Microsoft 365 or Google Workspace
  • ServiceNow or Jira Service Management
  • Slack

  1. Trigger

    Joiner, mover, or leaver event, or an access request

  2. The agent does

    1. Picks up joiner, mover, and leaver events from your HR system
    2. Creates accounts and group memberships from role templates your IT team owns
    3. Checks each access request against your access policy and the requester's role
    4. Proposes the narrowest role that covers the task, with a scheduled revocation date
    5. Revokes access at offboarding, transfers file ownership, and confirms each revocation

  3. Where a person decides

    Template grants are pre-approved by the template's owner. Anything outside the template waits for the manager and the resource owner. Admin and production roles sit outside the agent's permissions entirely: it can only route those requests.

  4. Write-back

    • Okta or Microsoft Entra ID
    • Microsoft 365 or Google Workspace

05 Revenue operations

Renewals and subscription changes

Each renewal reaches its owner with a brief and a draft quote well before the date. Seat changes and co-terms are drafted correctly, with CRM and billing in agreement.

Systems
  • Salesforce or HubSpot
  • Stripe or NetSuite
  • Zendesk
  • Snowflake or Databricks
Sample run
Seat change · Revenue ops

  1. Trigger

    Renewal date nears, or a subscription change is requested

  2. The agent does

    1. Builds a renewal brief ahead of each renewal date: usage, open tickets, invoices, and contract terms
    2. Flags risk early: falling usage, overdue invoices, open escalations
    3. Drafts renewal quotes and subscription changes from your price book and discount rules
    4. Asks the account owner when a request is ambiguous, instead of guessing
    5. Checks that CRM, billing, and contract records match after every change

  3. Where a person decides

    The account owner approves every quote before it reaches a customer. Discounts outside your rules and non-standard terms go to the deal desk.

  4. Write-back

    • Salesforce or HubSpot
    • Stripe or NetSuite

Sample run

  1. Read Steps: Read, Tool. It reads only what the task needs.
  2. Decide Steps: Think. The model proposes. Code checks.
  3. Check Steps: Human. When it isn't sure, it stops and asks.
  4. Write Steps: Write, Done. It writes back and leaves a record.

Select a stage to light up its steps in the run.

Seat change · Revenue ops

Illustrative run · sample data, not a client deployment

Trigger: orders@ inbox · “Please add 25 seats from next month” · account ACC-3391

  1. Read, 00:02.8: salesforce.get_account(ACC-3391) → 2 active subscriptions: Core (120 seats), Analytics (40 seats). Both renew 2027-03-31.
  2. Think, 00:08.2: The request names no subscription, and the account has two. Not guessing. Rule: never infer the target of a billing change.
  3. Human, 00:09.3: Asked the account owner in Slack: “Core or Analytics?” · run paused. Nothing is written while a run is paused.
  4. Human, 06:09.3: Account owner: “Core, co-termed with the current contract.” · 6m. Answer recorded on the trace.
  5. Tool, 06:15.5: pricing.quote(Core, +25, start=2026-12-01, coterm=true) → $4,500.00. $45 per seat per month × 25 seats × 4 months · list price · within deal-desk rules.
  6. Write, 06:20.4: salesforce.create_quote(ACC-3391) → Q-10482 · status: draft. Scope: draft quotes only. Activation stays with the account owner.
  7. Tool, 06:28.2: stripe.preview_invoice(Core, +25 seats) → $4,500.00. Billing preview matches the quote to the cent.
  8. Done, 06:29.0: Done · 8 steps · 29s agent time · 6m waiting on the account owner · $0.03 model cost. trace tr_91be44 · orders-agent v1.1.0 · test suite passing.

Outcome: One clarifying question instead of a wrong guess. A correct co-termed quote, with CRM and billing in agreement before anything reaches the customer.

Worksheet

Size your queue.

Your own volume and handling time, as the hours the work takes today. It shows only your numbers, never a projected saving.

Hands-on time for one case.

Hours a month
— Cases a month × minutes per case ÷ 60
Per person
— Hours a month ÷ people on the queue

Nothing you type here leaves this page.

06 Start

Don't see your workflow?

The domain matters less than the shape:

  1. steady volume
  2. several systems
  3. clear rules with exceptions
  4. a person who owns the outcome

If yours has that shape, bring it to us. If it doesn't, we'll say so, and suggest what to do instead.

Start a project

An engineer reads every note and replies within two business days.