Tied’s commitment. A wider substrate is not added to that number.
Tied · orchestration AI agent
Finish the job. Leave the receipt.
Tied’s AI agent reads the conversation and the live state of the systems you connect, applies your policy, and acts only inside that tool scope. The class on the invoice is derived from the audit trail. The model does not get to name its own price.
Demo and product: tied.com. Docs are the authority for everything on this page.
- intent
- refund.request
- policy
- Typed amount. Validated before the customer is told.
- scope
- write, Advanced or Enterprise. Otherwise the call is not loaded.
- checks
- Authorization, then policy, then compliance instrument.
- result
- Processor transaction id, or a failed write that does not upgrade the class.
- class
- Derived after the fact. Highest successful class, billed once.
01 — Execution
Five steps, every turn.
In the docs, an agent is a person on your team. The software is the AI agent. Under it: a router, specialists, and a single composer.
01
Perceive
It reads the message, the thread so far, the contact, and the live state of connected systems — the order, the subscription, the ticket, the account.
02
Reason
A router picks the intent and calls specialists. Specialists do the domain work against your policy and your data, and return structured data, never customer-facing prose.
03
Act
It calls the same kind of registered action a person would: read an order, unlock an account, issue a refund, reschedule a delivery. Authorization runs outside the model, before the call. The receipt is written after.
04
Narrate
One composer writes the reply. It is the only component allowed to speak to the customer, so two parts of the AI agent cannot contradict each other in the thread.
05
Learn
What the AI agent could not answer, and what a person answered instead, can become a knowledge proposal. Nothing goes live until a person approves it. Proposals that contain personal details, secrets, or internal names are dropped before that queue.
One voice
Only the composer speaks.
That is a design constraint. If two components could write to the thread, they could disagree in front of the customer. The live trace names these parts because they are actually running.
Router
The cheapest model in the stack, because it runs on every turn. It reads the conversation, picks the intent, and chooses specialists.
Specialists
Each owns a tool subset, a model tier, and its own test suite. They return structured data. They never write to the customer.
Composer
The only component that writes the reply. One voice, on whichever channel the conversation is already on.
02 — Scope
What it can touch is the plan.
Buying a plan does not buy a resolution class. Granting a scope does. The class is worked out afterwards, from the trail, and is used only to price what already happened. These are scenarios, not customer stories.
Scenario · not a case study
A refund your policy already allows
The AI agent can read the order, check the amount against a typed policy, and — on Advanced or Enterprise, where write scope exists — issue the refund and say what it did. If the amount fails validation, it escalates. A failed write at the processor does not become a financial resolution. You can require a person to approve an action by type, amount, or customer segment; that approval is recorded and does not change the price.
Scenario · not a case study
“Where is my order?”
On Business, read scope can look it up and change nothing. On Starter, with no integrations, the answer can only come from the help center. Refusal categories and tool scope move together: a question that is unanswerable from documentation becomes answerable once the system of record is connected.
Scenario · not a case study
The path that must not vary
A chatbot flow is the tool when a returns script, an authentication step, or a compliance line has to happen the same way every time. The AI agent is the tool for the long tail. A flow that hits a question it does not handle can pass the turn to the AI agent instead of straight to a person.
Scenario · not a case study
Before they write in
Syncs keep order, subscription, shipment, and account state current on every plan, so a reply is not blind. The AI agent starting the conversation — a failed payment, a stalled shipment, a renewal about to miss — is separately entitled. It will not send without recorded, attributable consent on that channel. A proactive resolution is priced like any other, and only if it actually resolves.
03 — Controls
Held, and not held.
Tied’s security page asks readers to prefer it over any pitch that implies a certification is already in hand. This page does that.
In the product now
-
Scope is the gate
If a system is not connected, or is connected read-only, the write never happens. Instructions can shape tone and escalation. They cannot grant a tool the model cannot see.
-
Authorization sits outside the model
Every action passes authorization, policy, and — where the data class requires it — a compliance instrument. An authorization lookup that errors denies the action. The check does not read the transcript, so a prompt injection cannot talk the AI agent into a tool the account does not have.
-
Typed commitments
A refund amount, a date, an entitlement, or a discount is a field Tied validates against your policy before the customer sees it. A $400 proposal against a $200 cap is a validation failure and an escalation, not a quieter refund.
-
A person, when asked
If the customer asks for a person, they get one. That gate runs before retrieval, matches a phrase list rather than a model call, and cannot be switched off — not per account, inbox, or plan. It over-fires on purpose. Handoff costs nothing.
-
Signed receipts
Each read and write is recorded: system, operation, authorization, success or failure, and the provider’s transaction id where there is one. The class on the invoice is derived from that trail. The AI agent never states its own class.
-
Your model bill
No plan marks up tokens. On Tied’s key, counts are itemized and reconciled monthly against the provider invoice. On your own key — available on every plan — you pay the provider directly, and the key is encrypted at rest and not stored at the routing gateway.
-
Where data sits
Conversation and contact data follow the account region: US only on Starter and Business; US, EU, or APAC on Advanced; custom regions on Enterprise. The region is set when the workspace is provisioned, not from a settings toggle. Identity data — logins, SSO, MFA — is processed in the US on every plan, under a GDPR-compliant DPA with EU Standard Contractual Clauses.
-
Two tiers of personal data
Raw data stays scoped to your account, in your region, and is never pooled with another account. The only tier used for any cross-account purpose is anonymised and aggregated. Pseudonym tokens from one account are meaningless in another.
Do not badge these
-
SOC 2 Type II
On the roadmap. Not held. Tied’s security page says to treat that page as the source of truth if a pitch implies otherwise.
-
ISO 27001 and PCI Level 1
Enterprise roadmap items. Not current certifications.
-
HIPAA BAA
Coming soon, and it cannot be executed today. Do not send PHI on the assumption a BAA is in place.
-
Regulated writes
Actions touching PHI, cardholder data, or SOX-controlled systems are refused on every plan until the matching instrument is on the account. Tied does not hold a BAA, a PCI Level 1 attestation, or a SOX instrument today, so those actions are defined, refused, and not sold. The compliance-gated resolution class is not priced.
-
Retention is not a toggle
There is no fixed, published retention window. Data persists for the life of the account, and deleting the workspace removes it. A specific deletion schedule is a conversation with the account team.
04 — Systems and transports
Connectors are not channels.
An integration is how the AI agent reads or changes a system of record. A channel is the transport a message travels over. Connecting an app does not grant write access. Custom connectors beyond the 109 committed ones are Advanced and Enterprise. No vendor logos are shown here, because this page does not invent a catalog.
Web chat Every plan
One script tag. No carrier, DNS, or verification. Tied’s own advice is to start here while slower approvals run.
Email Every plan
Forward an existing inbox or connect one. Custom reply domains are documented separately.
WhatsApp Every plan
Embedded signup. A 24-hour customer-care window governs the channel; outbound outside it needs an approved template.
SMS and MMS Every plan
Text and media. US A2P traffic needs 10DLC registration. Carrier fees are separate from resolutions.
Instagram and Messenger Every plan
Direct messages from a professional account, or a Facebook Page, in the same inbox.
Telegram and LINE Every plan
Telegram via a bot token. LINE through a LINE Official Account — the default messenger in Japan, Taiwan, and Thailand.
API channel Every plan
Build a transport Tied does not ship. Your webhook carries the outbound leg.
Apple Messages for Business Advanced and Enterprise
Apple Pay, list and time pickers, forms, quick replies, rich links, and authentication, inside Messages. Plan on 4–6 weeks for Apple Business Register. Advanced includes 5,000 free messages a month; Enterprise volume is custom-quoted.
Google RCS Listed from Business up
Rich cards and suggested replies are specified, with a 4–6 week carrier approval. Tied’s channel guide also says an RCS inbox cannot be connected yet, and that no device-detection snippet is shipped to pair it with Apple Messages.
Voice Business and above
The plans page lists voice AI agent integrations from Business upward. Delivery pricing still sits outside the resolution fee.
Slack Team side, every plan
Not a place customers start a conversation. Threads from other channels mirror into Slack, and a reply there goes back out on the customer’s channel.
Channel fees are carrier passthrough plus a Tied platform fee, billed
separately from resolutions. A write_financial resolution
is $0.95 on Apple Messages or on web chat.
Compare channels ·
Integrations
Placeholder — not customer evidence
Reference log
Enterprise buyers ask who else runs it. This front door does not answer with fiction.
These cards are empty layout slots. They are not customers, logos, quotes, or results. Nothing has been redacted, because nothing has been approved for publication. Ask Tied for references on a demo call; do not treat this page as evidence.
Slot 01
Sector label only · Commerce operations
- Logo
- Empty slot
- Quote
- Empty slot. Not a customer statement.
- Result
- Empty slot. Not a measured outcome.
Slot 02
Sector label only · Subscriber support
- Logo
- Empty slot
- Quote
- Empty slot. Not a customer statement.
- Result
- Empty slot. Not a measured outcome.
Slot 03
Sector label only · A regulated team
- Logo
- Empty slot
- Quote
- Empty slot. Not a customer statement.
- Result
- Empty slot. Not a measured outcome.
05 — Price
Seat, then outcome.
Annual billing is 20% off the seat price on Starter, Business, and Advanced. Resolution rates do not change with the billing cycle. Enterprise is an annual contract with negotiated class rates. Included credits are pooled across the org, reset monthly, and do not roll over. One credit is ten cents, fixed.
Starter
$99
per seat / month
Minimum 2 seats
- No integrations. The AI agent answers from the knowledge base.
- Reachable class: knowledge ($0.35).
- 100 included credits per seat each month, pooled across the org.
- Default model routing, without the routing controls. Bring your own key on this plan too.
Business
$199
per seat / month
Minimum 3 seats
- Read-only tool scope on connected systems.
- Reachable classes: knowledge and read ($0.50).
- Least-cost, speed, or accuracy routing. 300 pooled credits per seat.
- RCS is listed here; voice AI agent integrations are listed here. See the channel notes — an RCS inbox is not connectable yet.
Advanced
$299
per seat / month
Minimum 4 seats
- Write scope. Refunds, account changes, tickets, and multi-system writes start here.
- Classes through orchestrated ($1.90). Pin a model from the Tied-hosted menu.
- Apple Messages for Business, including 5,000 free messages a month.
- US, EU, or APAC residency, set when the workspace is provisioned. SLAs, a CSM, and a dedicated Slack channel.
Enterprise
Custom
annual contract
Negotiated
- Write scope, plus per-class rates negotiated in the contract and never published.
- Long-horizon cases: work that runs for weeks, billed as a case, not a resolution.
- Your VPC. SSO (SAML and OIDC), SCIM, and org-enforced MFA.
- Custom regions. Forward-deployed engineers. The published self-serve rates are a starting point for the discriminators, not your price.
No successful action against an external system. Help-center retrieval does not count as one. 3.5 credits.
At least one successful lookup. No successful write. 5 credits.
A successful write, no money moved, fewer than three providers. 7 credits.
A successful write that moved money, and no higher class applies. 9.5 credits.
Successful writes across three or more distinct providers. 19 credits.
Highest class reached wins, once. A failed write does not move the
class up. compliance_gated is not sold.
long_horizon_case is Enterprise-only and billed as a
case. If the same issue reopens within 30 days, or the customer
leaves negative feedback, the orchestration fee and its model-cost
lines are credited automatically. Off-topic misuse is not a
resolution. Model tokens on Tied’s key pass through at provider rate.
How pricing works · Resolution classes · Credits · Pricing on tied.com
Bring it inside the boundary.
VPC, SSO, and the audit trail are the conversation. The product itself opens on tied.com.