allopy — execution layer
policies loaded · caps armed
ledger open ▍
Execution layer · every step on the record

Runs your operations.
Shows its work.

Allopy reads your inbox, decides under the policies you set, and executes — refunds, scheduling, retention, collections — then writes every step to a ledger you can replay.

Request access →
Follow one email ↓
▸refund $49.00 → maria@acme.co — DONE▸reschedule Tue → Thu · invite sent — DONE▸cancellation → saved with 20% — DONE▸invoice #1182 reminded · $340 — DONE▸wire change held · confidence 0.31 — HELD▸escalated → you · nothing sent — YOU▸lead qualified → routed to sales — DONE▸contact + note logged to CRM — DONE▸status #4821 answered in-thread — DONE▸invoice paid · collections closed — DONE
▸refund $49.00 → maria@acme.co — DONE▸reschedule Tue → Thu · invite sent — DONE▸cancellation → saved with 20% — DONE▸invoice #1182 reminded · $340 — DONE▸wire change held · confidence 0.31 — HELD▸escalated → you · nothing sent — YOU▸lead qualified → routed to sales — DONE▸contact + note logged to CRM — DONE▸status #4821 answered in-thread — DONE▸invoice paid · collections closed — DONE
Act I · one email, start to finish
01 / 05 — received
from: maria@acme.co09:41:07
Charged twice for May

“Hi — I think I was charged twice this month. Can someone look into it?”

refund · 0.94
DONE
policy check
✓sender owns charge ch_3Pk…
✓within 30 days
✓under $200 cap
written to the ledger
email receivedsystem
classified · refund · 0.94ai
policy check passed · 3/3ai
stripe_refund $49.00 → original cardai
resolved in 41s · reversibledone
Act II · not everything should run
from: no-reply@spoof.ru10:17:20
URGENT — change wire details

“Please update the payout account immediately. This must happen today.”

confidence 0.31
HELD
▸below your confidence floor — the machine stops
▸no reply sent · no data shared · nothing moved
▸escalated to you · waiting on your call

It knows when to stop.

The dangerous version of automation is confident and wrong. Below the floor, Allopy holds, asks you, and sends nothing — refusal is a feature, on the record like everything else.

What it runs

Whatever lands, it’s handled.

01

Refund

duplicate charge → $49 back on the original card, inside your caps — DONE
02

Reschedule

“can we do Thursday?” → slot found, invite sent — DONE
03

Retain

cancellation → saved with a 20% offer, under your limit — DONE
04

Collect

overdue invoice → reminded, reconciled, closed when paid — DONE
05

Reply

“where’s order #4821?” → answered in-thread — DONE
06

Escalate

risky wire change → held, flagged to you, nothing sent — HELD
07

Log

every step above → written to the record, replayable — ALWAYS
Trust, enforced

Every step. On the record.

policy caps

Money actions are checked against your written caps before they fire. Every time.

confidence floor

Unsure means stop. Below the floor it holds, asks you, and sends nothing.

deterministic rails

Refunds and money moves run coded paths with hard checks — not model improvisation.

kill switch

One click pauses everything, mid-flight included.

Put your operations
on the record.

Write your policies in plain English. Connect Gmail and Stripe. Watch the ledger fill.

Request access →

No card · connects Gmail, Stripe, HubSpot & Calendar in minutes

▸refund $49.00 → maria@acme.co — DONE▸reschedule Tue → Thu · invite sent — DONE▸cancellation → saved with 20% — DONE▸invoice #1182 reminded · $340 — DONE▸wire change held · confidence 0.31 — HELD▸escalated → you · nothing sent — YOU▸lead qualified → routed to sales — DONE▸contact + note logged to CRM — DONE▸status #4821 answered in-thread — DONE▸invoice paid · collections closed — DONE
▸refund $49.00 → maria@acme.co — DONE▸reschedule Tue → Thu · invite sent — DONE▸cancellation → saved with 20% — DONE▸invoice #1182 reminded · $340 — DONE▸wire change held · confidence 0.31 — HELD▸escalated → you · nothing sent — YOU▸lead qualified → routed to sales — DONE▸contact + note logged to CRM — DONE▸status #4821 answered in-thread — DONE▸invoice paid · collections closed — DONE