AI agents

Agents do the follow-up. Your team makes the decisions.

Most of the work between a fault and a closed ticket is following up: asking for ETAs, chasing replies, logging what vendors said, guiding the fix. Fieldor's agents do that part, inside the rules you set, and hand people the decisions that need them.

98%of detection done automatically
89%of ETA chasing done automatically
96%of proof checks done automatically
Meet the agents

Each one takes a job off your coordinators.

CHASEPILOT

Gets the ETA, and keeps getting it.

The job that fills a coordinator's day: ringing engineers, vendors and officers for updates.

WHAT IT DOES
Asks the assigned person for an ETA on WhatsApp the moment a ticket is assigned, logs the reply, and chases again when an ETA slips.
WHEN IT ESCALATES
When there's no reply, it climbs the ladder you configure: retry, SMS, a voice call to the secondary custodian, then a supervisor or zone head.
EXAMPLE
Dispenser fault at ATM-07731 assigned at 02:11. ETA asked on WhatsApp; S. Rao replied in 34 seconds with 02:24.INC-118204 · ETA CONFIRMED 02:12
PLANNER

Tomorrow's plan, drafted tonight.

Hours of spreadsheet work every evening, turned into a review.

WHAT IT DOES
Drafts every engineer's day, weighing SLA, fault type, site importance, spares on hand and travel time.
WHO DECIDES
Coordinators review and adjust the draft in minutes instead of building it for hours. Campaigns push one job to hundreds of sites at once.
EXAMPLE
Tomorrow's day plans for a whole zone, built around open incidents, SLA clocks, site access hours and the spares in each van.PLAN · DRAFTED THE EVENING BEFORE
FIXMATE

A guide for the repair, on site.

First-time fixes that don't depend on who happens to be nearest.

WHAT IT DOES
Walks the engineer through the fix for that fault on that model, step by step, with the checklist and required photos built in.
EXAMPLE
S. Rao arrived 18 m from the ATM, verified by geofence. FixMate walked him through the pick-module swap; the ticket closed with four stamped photos and a test withdrawal.RESTORED 02:48 · 4 PHOTOS · SEALED
EMAILPILOT

Vendor replies, logged where they belong.

No more copying emails into tickets, or losing them.

WHAT IT DOES
Reads replies from vendors, partners and clients and records them against the right ticket, so the history stays complete.
EXAMPLE
A water leak found in a branch audit: AMC confirmed active, ticket routed to the HVAC vendor with the photo and a 24-hour SLA. EmailPilot logged the vendor's reply.INC-118377 · AUTO-ROUTED 10:13
One fault, on the record

What the agents did while everyone slept.

An ATM dispenser fails at 2 a.m. Here is the ticket's trail, with the agents' work and the person's work side by side.

02:11FIELDOR

Dispenser fatal on the switch feed. Incident raised automatically with the device, site and 4-hour SLA. No call needed.

02:11PLANNER

Assigned to S. Rao: trained on this dispenser, spare in his van, 12 minutes away.

02:12CHASEPILOT

ETA asked on WhatsApp. Reply in 34 seconds: 02:24.

02:24S. RAO

On site, verified by geofence 18 m from the ATM.

02:24FIXMATE

Guides the pick-module swap; spare scanned out against the ticket.

02:48S. RAO

Restored. Four stamped photos, test withdrawal passed, failed part tagged for return.

02:48FIELDOR

Proof checked and sealed. Bank notified with 3 h 12 m of SLA to spare.

Follow-through

Share of each step done automatically.

Last 30 days. People still make the calls that need judgement; the agents do the rest.

Detect98%
Assign94%
Chase ETA89%
Escalate83%
Verify proof96%
Report100%
You stay in control

Automation you can see, and switch.

YOUR RULES

Choose what runs on its own

For each step, choose automatic, ask first, or off, per client, zone and fault type.

ESCALATIONS

Your ladder, your people

You decide who is chased, through which channel, after how long, and who hears about it next.

AUDIT TRAIL

Every action on the record

What an agent did, when, and why sits in the ticket's audit log, next to every person's action. Nothing happens off the record.

CHANNELS

Where your people already are

WhatsApp, SMS, voice and email, with every reply logged against the ticket.

ACCESS

Role- and site-based access

Every user, partner and client login sees only their own sites, whatever the agents are doing.

DEPLOYMENT

Wherever Fieldor runs

In our cloud (India and EU regions), your private cloud, or on-premises in your data centre.

Questions

What operations heads ask about the agents.

Do the agents act without asking us?

Only inside the rules you set. You choose which steps run automatically, which need approval, and who gets escalations.

Can we start with some agents and add others later?

Yes. Each step can be automatic, ask first, or off, per client, zone and fault type, so you can start with ETA chasing and switch on more as your team gets comfortable.

How do our engineers and vendors interact with them?

Through the channels they already use: WhatsApp, SMS, voice calls and email. Their replies are logged against the ticket automatically.

Will we be able to see what an agent did and why?

Yes. Every agent action is written to the ticket's audit trail alongside the people's actions, and kept for the life of the contract.