Read on Business. Write, with narration and rollback, on Advanced.
Tied · enterprise front door
An AI agent your review can finish.
Tied resolves customer conversations on the channels you already run, inside a tool scope, a signed action trail, and a deployment boundary security and procurement can check against the docs. The product stays at tied.com. This page is for the people who have to bring it in.
Both links leave orchestrator.com for tied.com or docs.tied.com.
Published fees from $0.35 to $1.90. Enterprise rates are negotiated.
The gate cannot be disabled. It does not depend on a model call.
SOC 2, ISO 27001, PCI Level 1, and a HIPAA BAA are not held today.
How it works
A person, and an AI agent, are different nouns.
Tied’s docs reserve “agent” for someone on your team. The software perceives, reasons, acts, narrates, and learns. When it cannot finish, the person inherits the whole thread — not a summary standing in for it — and the AI agent steps back while that person is on shift.
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.
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.
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.
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.
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.
What to ask for on the demo
- A signed action receipt, and the discriminator that turned it into a class.
- Which of the 109 committed connectors match your systems, and which would be custom work.
- Where conversation data would be provisioned, and the written exception for identity data in the US.
- SSO, SCIM, and VPC if the review requires them — they are Enterprise, not a settings toggle.
- The security page’s certification paragraph, read as written, not as a slide.
Use cases
Jobs the docs actually describe.
None of these are customer results. They are the motions the product is built to run, with the plan gate attached.
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.
Trust and security
What a review can check today.
Encryption in transit covers the dashboard, the API, and channel webhooks. Channel credentials, bring-your-own-key secrets, and MFA secrets are encrypted at rest. Passwords are hashed. Safety classifiers fail closed and escalate. The billing-balance check fails open, on purpose, so a billing outage does not take the customer’s AI agent down — the accepted cost is under-billing.
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.
Not held
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.
Not held
ISO 27001 and PCI Level 1
Enterprise roadmap items. Not current certifications.
Not held
HIPAA BAA
Coming soon, and it cannot be executed today. Do not send PHI on the assumption a BAA is in place.
Not held
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.
Not held
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.
Security · Residency and retention · SSO and SCIM · Guardrails
Integrations
109 committed connectors. Channels are a separate list.
Actions happen inside a conversation: look up an order, issue a refund, open a ticket. Syncs keep provider state current in the background. Tied commits to 109 connectors and warns against adding the broader substrate to that number. Anything outside the 109 is a custom integration on Advanced and Enterprise. Names of vendors are left to the docs and the demo — this page does not draw a logo wall.
Every plan
Web chat
One script tag. No carrier, DNS, or verification. Tied’s own advice is to start here while slower approvals run.
Every plan
Forward an existing inbox or connect one. Custom reply domains are documented separately.
Every plan
Embedded signup. A 24-hour customer-care window governs the channel; outbound outside it needs an approved template.
Every plan
SMS and MMS
Text and media. US A2P traffic needs 10DLC registration. Carrier fees are separate from resolutions.
Every plan
Instagram and Messenger
Direct messages from a professional account, or a Facebook Page, in the same inbox.
Every plan
Telegram and LINE
Telegram via a bot token. LINE through a LINE Official Account — the default messenger in Japan, Taiwan, and Thailand.
Every plan
API channel
Build a transport Tied does not ship. Your webhook carries the outbound leg.
Advanced and Enterprise
Apple Messages for Business
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.
Listed from Business up
Google RCS
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.
Business and above
Voice
The plans page lists voice AI agent integrations from Business upward. Delivery pricing still sits outside the resolution fee.
Team side, every plan
Slack
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.
Placeholder — not customer evidence
Customer evidence
A security questionnaire will ask for references. The honest answer, on this site, is that the slots are empty.
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.
Pricing
Published seats. Published classes. A contract where it matters.
Minimums are 2, 3, and 4 seats on Starter, Business, and Advanced. Annual billing takes 20% off the seat price and does not change per-resolution rates. Credits pool across the organization, reset monthly, and cover AI usage; channel fees and Tied-key model costs draw on the same prepaid balance. Bring your own key and model spend never touches Tied’s invoice.
Starter
$99
per seat / month
Minimum 2 seats
Small teams launching customer messaging.
- 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
Teams that want the AI agent to look things up and change nothing.
- 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
Teams that need the AI agent to act, with narration and rollback.
- 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
Regulated teams that need sovereignty and contract terms.
- 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.
knowledge $0.35
No successful action against an external system. Help-center retrieval does not count as one. (3.5 credits)
read $0.50
At least one successful lookup. No successful write. (5 credits)
write_simple $0.70
A successful write, no money moved, fewer than three providers. (7 credits)
write_financial $0.95
A successful write that moved money, and no higher class applies. (9.5 credits)
orchestrated $1.90
Successful writes across three or more distinct providers. (19 credits)
Handoff is not a reduced charge. It is zero. A reopen inside 30 days, or negative feedback, credits the fee and its model-cost lines without a claim. Plans · Resolution pricing · tied.com/pricing
Next
Walk procurement through the docs, then the product.
Start with security status, residency, and which systems would be in scope. The demo is booked on tied.com.