Your policy, in every industry
Every industry has its own way for an agent to go wrong. Your gateway runs the same four checks on every request (verified agent, your policy, live truth and customer approval) with rules you set for your business.These are examples of rules you could set. Today the core runs in our lab with a travel test store; profiles for other industries are next.
- Retail and marketplacesAgent orders you can proveIn lab
- Travel and hospitalityNo bookings at a price nobody approvedWorking in lab
- Banking and paymentsAgents without the customer’s passwordIn lab
- InsurancePolicies sold with the fine print seenIn lab
- Healthcare and clinicsAppointments moved, records kept privateIn lab
- Subscriptions, telecom and utilitiesA fair chance before an agent cancelsIn lab
- Ticketing and eventsSeats for fans, not botsIn lab
Retail and marketplaces
In labAgent orders you can prove
What happens today. A customer disputes an order their assistant placed: “I never approved that.” The assistant’s chat isn’t yours to show, and to your payment system it looked like any online sale. You refund it, and may pay a dispute fee too.
Your policy decides
- Agent orders: customer approves on our page
- Return terms shown: policy v4, 30 days
- One order per approval, even if the agent retries
What you gain
- TransactionsA record behind every agent order
- SecurityOnly verified agents can place orders
- SalesAssistants can reorder from you directly
“Reorder my running shoes, size 10.”
- Verified agent
The assistant proves who it is
Signed with its published key, not a name it claims.
- Live truth
Price, stock and returns from you
Size 10 in stock at $109.00, with your 30-day return policy.
- Customer approval
The customer approves on your page
Exact item, price and return terms. Payment confirmed by your provider.
- Recorded
One order, fully recorded
Approval, terms and payment result on the order’s timeline.
If it’s disputed, you have the record
What the customer approved, when, at what price, and the verified payment.
3 more retail requests, and how your gateway handles them
“The assistant’s connection drops and it sends the order again.”
The retry gets the original result. One approval, one order.
“Return this jacket.”
The return window comes from your reviewed policy, and refunds follow your rules, such as staff review above $200.
“A price-tracking bot reads your stock levels every minute.”
Public pages stay open. Live stock levels go only to verified agents you allow.
Travel and hospitality
Working in labNo bookings at a price nobody approved
What happens today. Fares change by the minute. If an assistant books after the price moved, either the customer pays more than they agreed to, or you honour the old fare at your own cost.
Your policy decides
- Price or refund rule changes after approval: ask again
- Holds expire after 15 minutes
- Seat upgrades: offer once, labelled as ours
What you gain
- TransactionsNo bookings at prices nobody approved
- RelationshipAlternatives offered in the same conversation
- SalesLabelled upgrade offers at the moment of booking
“Book the refundable Friday flight to Lisbon you showed me.”
- Live truth
A live quote from your system
$548.20, refundable, held for 15 minutes.
- Customer approval
The customer approves $548.20
Bound to that fare, its refund rule and the hold.
- Live truth
At booking, the fare is $579.00
Your price changed, so the old approval no longer counts.
- Talk back
You ask the customer again
The new price, or a $552 alternative, goes back through their assistant.
The customer decides with the real price
No silent price jump, and no fare you have to absorb.
3 more travel requests, and how your gateway handles them
“The flight is rescheduled after booking.”
You send the change and the options to the customer’s assistant and get their choice back in the same task.
“Is checked baggage included?”
Answered from your reviewed baggage policy. If two of your pages disagree, the answer waits for review.
“Hold the seat a little longer.”
Holds follow your policy. The assistant cannot extend one.
Banking and payments
In labAgents without the customer’s password
What happens today. Some assistants still sign in with the customer’s saved password. To the bank, the assistant looks exactly like the customer, so it can do anything the customer can, and the bank has no way to limit it.
Your policy decides
- Agents: read balances, pay known billers up to $500
- New payees: our own approval step, every time
- Never by agents: contact details or card limits
What you gain
- SecurityNo shared passwords, and every agent action inside your limits
- TransactionsEach payment tied to the customer’s grant and approval
- RelationshipServe customers who bank through AI assistants
“Pay my bills from checking this month.”
- Verified agent
The assistant connects through your agent route
Signed with its own key. It never sees the customer’s password.
- Your policy
It gets only the access the customer granted
Read balances and pay known billers up to $500, until revoked.
- Your policy
A fake invoice asks for a new payee
Your policy sends every new payee to your own approval step.
- Customer approval
Known bills paid, the new payee held
The customer approves or rejects the payee in your app.
Bills paid, the scam stopped
Money moves only within the access you allow and the customer approves.
3 more banking requests, and how your gateway handles them
“What are the fees on your travel card?”
Answered from the terms you reviewed. No account access is needed.
“The customer wants to stop the assistant.”
One revoke ends its access. No password change needed.
“Raise my card limit.”
Your policy keeps account changes out of agents’ reach.
Insurance
In labPolicies sold with the fine print seen
What happens today. An assistant finds the cheapest home policy and buys it. Nobody showed the customer that flood damage isn’t covered. After the first claim, it becomes a complaint, and possibly a mis-selling case.
Your policy decides
- Binding a policy: customer approves with key exclusions shown
- Agents may quote and bind, never cancel existing cover
- Claims: agents gather details, the customer submits
What you gain
- TransactionsProof of what the customer saw before buying
- SalesAssistants can quote and bind with you directly
- SecurityCancelling cover stays out of agents’ reach
“Find me cheaper home insurance and switch.”
- Live truth
A quote from your rating system
Premium, deductible and exclusions from your reviewed policy wording.
- Your policy
Key exclusions are must-show terms
Your policy marks flood cover and the deductible as terms to show.
- Customer approval
The customer approves with exclusions in view
On your page, not in the assistant’s summary.
- Recorded
What was shown is recorded
The exact terms, the wording version and the time of approval.
A sale with proof the fine print was seen
Fewer complaints, and a record if one comes.
3 more insurance requests, and how your gateway handles them
“Cancel my old policy first.”
Your policy refuses agent cancellations, so a customer is never left uninsured by mistake.
“Does my policy cover hail?”
Answered from your reviewed policy wording, with its source.
“Start a claim for my windshield.”
The assistant gathers the details. Submitting the claim needs the customer.
Healthcare and clinics
In labAppointments moved, records kept private
What happens today. A patient’s assistant signs in to your patient portal with their saved password to move an appointment. Now it can see everything the patient can, including test results and prescriptions, and you can’t tell it apart from the patient.
Your policy decides
- Agents may book and move appointments the patient allowed
- Medical records and test results: never shared with agents
- Payments and prescription requests: the patient approves
What you gain
- SecurityAgents never see records they don’t need
- SalesPatients reschedule through their assistant, any time
- RelationshipReminders only when the patient agreed
“Move my check-up to next Tuesday afternoon.”
- Verified agent
The assistant proves who it is
Signed with its published key, acting on the patient’s grant. No portal password.
- Your policy
Only what the patient allowed
It may move appointments. Records and results stay out of reach.
- Live truth
Real availability from your calendar
Tuesday 2:30 pm with Dr. Patel is free, with your cancellation policy.
- Customer approval
The patient confirms the change
On your own page or app, before the slot moves.
Moved, without opening the chart
The appointment changed, and nothing medical left your systems.
3 more healthcare requests, and how your gateway handles them
“Show me my latest blood test results.”
Refused for agents by your policy. The patient is pointed to your portal instead.
“Pay my $40 copay.”
The patient pays on your payment provider’s page. The agent never sees the card.
“Refill my prescription.”
Sent to the patient to approve, then to your team as usual.
Subscriptions, telecom and utilities
In labA fair chance before an agent cancels
What happens today. An assistant cancels the plan in seconds. You never get to make an offer, and the first you hear of it is a lost customer.
Your policy decides
- Agent cancellations: allowed, after one labelled offer
- If the offer is declined: cancel immediately
- Plan changes: contract terms on the approval screen
What you gain
- SalesA fair retention offer instead of silent churn
- RelationshipThe conversation continues through the customer’s agent
- TransactionsContract terms approved before any plan change
“Cancel my streaming plan.”
- Verified agent
The assistant proves who it is
And that it acts for this account holder.
- Your policy
Your policy allows the cancellation
With one retention offer first. Cancelling is never blocked.
- Talk back
You make one labelled offer
“3 months at half price”, sent through the assistant as your offer.
- Customer approval
The customer decides
Accepting needs their approval. Declining cancels right away.
Some customers stay, and every choice is respected
You see how many agent cancellations you kept and how many you lost.
3 more subscriptions requests, and how your gateway handles them
“Move me to a cheaper phone plan.”
Contract length and exit fees appear on the approval screen, not behind a link.
“Drop the add-ons I never use.”
Each removal is listed for approval. Nothing else changes.
“Pause my plan for a month.”
Your policy decides what agents may pause, and for how long.
Ticketing and events
In labSeats for fans, not bots
What happens today. Bots pretending to be fans’ assistants grab and hold seats, then drop or resell them. Queues slow real fans down just as much as the bots.
Your policy decides
- Seat holds: verified agents only, 10 minutes
- Limit: 4 tickets per customer, agents included
- Price shown: all-in, fees included
What you gain
- SecurityImpersonating bots refused at your gateway
- SalesFans’ real assistants can buy from you
- TransactionsHolds expire on time, so no inventory is locked up
“Get two seats together for Saturday, $90 each at most.”
- Verified agent
Impersonators fail the signature check
A bot using a well-known assistant’s name can’t produce its key.
- Your policy
Verified assistants get fair limits
Up to 4 tickets per customer, and holds expire after 10 minutes.
- Live truth
Live seats and the all-in price
From your ticketing system, fees included.
- Customer approval
The fan approves the exact seats
Section, row and all-in price, then pays on your page.
Fans’ real assistants get through
Impersonators are refused, and held seats return to sale on time.
3 more ticketing requests, and how your gateway handles them
“Buy eight so I can resell some.”
Your per-customer limit applies to agents too.
“Get better seats, whatever the price.”
The fan still approves the exact seats and all-in price.
“Send one ticket to my friend.”
Transfer rules are answered from your reviewed policy.
One core, many templates
Every industry runs on the same engines. A template adds what is special about yours, so you start from rules that already fit and change only what is different.
Industry templates:In lab
Actions
Everything an agent may ask to do, from read to never, with its class
Terms that need a yes
Which details the customer must see and approve
Starting rules
A policy you can use on day one and edit in plain language
Approval pages
Pages that show the exact terms for each kind of action
System mappings
How common booking, order and account systems connect
A rules checklist
The regulations to review before real customer data
Working in another industry?
Wherever an agent can spend money, book something or change an account, your policy can decide what happens. We are choosing the next industry profiles with pilot partners.