Skip to content
Customer Login Support Partners
Industries

Every floor has its own vocabulary.

A renewal call is not a chargeback call. An AI worker that answers well in one industry is useless in the next unless it knows the systems, the words and the rules of that floor.

So we ship a pack per industry — and every one of them arrives already wired.

Eight floors, eight sets of rules.

Each pack carries the connectors, the operations and the flows for one industry — with a gate class on every action.

01
Insurance
Renewals, claim status, policy servicing and nominee changes
PolicyAdmin · Billing · Claims · CRM
Open →
02
Banking and financial services
Card disputes, balances, statements and lost-card blocks
CoreBanking · Cards · CRM
Open →
03
Telecom
Billing, provisioning, faults and grievances — four SME workers, one router
Billing · Provisioning · CRM
Open →
04
Healthcare
Appointments, report status and billing estimates — never clinical advice
HIS · Appointments · Reports · Billing
Open →
05
BPO and outsourced centres
Collections callbacks, dispositions and campaign state, per end client
Dialler · Campaign · CRM
Open →
06
Public sector and PSU
Scheme and application status, grievance intake, document queries
Case management · Grievance · Records
Open →
07
Retail and e-commerce
Order status, returns, refunds and delivery exceptions — in spikes
OMS · Payments · Logistics
Open →
08
Travel and hospitality
Bookings, changes, cancellations and disruption queues
Reservations · Payments · Loyalty
Open →

What you get, floor by floor.

Every pack imports as drafts with simulated bindings. Nothing calls a live system until your team binds and verifies it.

Pack contents by industry — connectors, operations and flows that ship on day one
Industry Core systems wired Connectors Operations Flows
Insurance PolicyAdmin · Billing · Claims · CRM 4 9 4
Banking and financial services CoreBanking · Cards · CRM 3 8 4
Healthcare HIS · Appointments · Reports · Billing 4 9 4
BPO and outsourced centres Dialler · Campaign · CRM 3 6 4
Public sector and PSU Case management · Grievance · Records · CRM 4 6 4
Telecom Billing · Provisioning · CRM · Ticketing 4 9 4
Retail and e-commerce OMS · Payments · Logistics · CRM 3 8 4
Travel and hospitality Reservations · Payments · Loyalty · CRM 4 9 4
One pack, opened up
insurance · v1.0.0 · the other seven follow the same shape

Insurance

Persistency is won on the outbound reminder and lost on the unanswered renewal call. The pack covers that conversation end to end — identify the caller, read the policy, state the premium and due date, confirm the date back — and lands every servicing write behind an approver.

Premium due and renewal Claim status Payment mode change Nominee update Policy revival Fund value and statements
What ships on day one
4
Connectors
9
Operations
4
Flows
The constraint that shapes the build
IRDAI conduct rules, and a claim conversation that must never become advice.
Connectors and operations
PolicyAdmin
getPolicy READ acts alone
changePaymentMode WRITE needs authorisation
updateNominee WRITE needs authorisation
Billing
getDueSchedule READ acts alone
sendPaymentLink WRITE needs authorisation
refund DESTRUCTIVE never alone
Claims and CRM
getClaimStatus READ acts alone
getCustomer READ acts alone
logInteraction WRITE needs authorisation
Flows that run end to end
Renewal — premium due reminder
The flow that must complete end to end. Identify, read the policy, state the amount and date, confirm it back, and land the write behind a gate.
Claim status enquiry
Read-only end to end. The acts-alone class, with no gate anywhere in it.
Renewal due — outbound with payment link
Event-triggered: the due date starts this flow, not a caller. Outbound is where persistency is won.
Premium mode change
A servicing write on the policy itself — the alteration class of work.
Where a human must stand
Changing premium frequency is material — it needs a named approver, not a confirmation tone. Refunds are never taken by the worker alone.

The same three classes, on every floor.

What differs by industry is which operation falls into which class. That map is a proposal until you ratify it.

READ
Acts alone
Lookups and summaries. The worker runs these without asking anyone, all day, at any volume.
Policy status · balance · claim status · order status
WRITE
Needs authorisation
Changes a record or contacts a customer. Prepared in full by the worker, released by a person.
Payment mode change · payment link · promise to pay
DESTRUCTIVE
Never alone
Irreversible from the customer's side. A named human authorisation, every single time.
Card block · refund · policy cancellation
Not on the list

A new pack is work, not a roadmap item.

Every pack on this page started as somebody's floor. The work is the same each time: map the call types with your operations team, agree which actions can run alone, bind the connectors to your systems, and prove it against your own calls.

Your pack is yours. It is versioned in your tenant, and your changes never flow back into ours.

Discover
Your call types, counted
Not a workshop about AI. A ranked list of what your floor actually takes.
Define
The gate map
Every operation classed, then ratified against your own delegation matrix.
Develop
Connectors and flows
Built in AI Studio against your own environment, simulated until the bindings verify.
Deploy
One queue, live
A narrow pilot inside your infrastructure, gates already in force.
Demonstrate
Your pack, versioned
Scored against your own test calls, promoted, and yours in your tenant.
Start with your own calls

Bring your three highest-volume call types.

We will show you the pack for your industry, the operations behind those three calls, and exactly where your people would still be standing.

01 Name your industry and your three biggest call types
02 See the pack, or the plan to build one
03 Read the gate classes and challenge them
04 Watch a flow run against declared fixtures