Skip to main content
Entries are written for the people who use Tied rather than the people who build it — what changed on your screen, not which internal component moved. Anything that needs action from you is marked, and says what the action is.
​
Docs
Documentation

​
These docs

Tied’s documentation moved to its own site, covering every channel, the inbox, automation and routing, contacts, the Help Center, campaigns, the flow builder, the AI agent, administration, and the full pricing model.Two things worth knowing about how they are written:
  • The pricing pages publish the discriminators, not just the definitions. Every resolution class shows the exact mechanical test that assigns it, so you can check a charge against your own receipt rather than taking our word for it.
  • Where the product does not do something, the docs say so. The known limitations page exists for that reason, and the compliance position is stated plainly on Security rather than implied.
No action needed.
​
Billing
Billing and credits

​
Outcome-based billing, with receipts

The billing model moved to per-resolution pricing with a prepaid credit balance.
  • Two numbers on every invoice, never blended: a flat orchestration fee set by the resolution’s class, and model cost passed through at exactly the provider rate. See How pricing works.
  • Every billed resolution carries a receipt showing the transcript it came from, which signal tier justified billing it, the class and its discriminator, and the itemised model cost — with a one-click dispute. See What counts as a resolution.
  • Automatic credits. A resolution that reopens within 30 days, or ever draws negative feedback, is voided and credited without you filing anything.
  • Channel fees are separate and passed through. Carrier and platform costs are billed at cost plus a stated flat platform fee, never folded into the resolution price. See Channel fees.
If you are on a prepaid balance, set up auto top-up. A balance hitting zero does not stop your agent — Tied fails open and reconciles afterwards — but it is worth not finding out. See Credits.
​
Channels
Apple Messages for Business

​
Rich Feature Messages, end to end

All eight Apple Messages for Business primitives are available in the reply composer and in the flow builder: quick replies, rich links, list pickers, time pickers, forms, Apple Pay, OAuth and iMessage apps.
  • Save any of them as a reusable template from the composer, and pick it up again from the Choose tab next time.
  • Every media slot the Apple schema allows is exposed — send-display and response-display images, per-item images, splash images on forms, and video on rich links.
  • Payloads are schema-validated before send, so a malformed message fails in the composer rather than at Apple.
See Rich Feature Messages.
Tapped quick replies return the label, not the key. If a reply drives a branch, keep your labels distinct or use a list picker, which does return a stable identifier. See Known limitations.
​
Chatbot
Flow builder

​
Versioned publishing and rollback

Publishing a flow now saves a snapshot rather than mutating what is live.
  • Version history on every flow, with one-click rollback to any previous version.
  • In-flight conversations stay on the version they started on, so a publish never changes the script mid-conversation for someone already talking to you.
  • A simulator in the builder steps through the flow against a message you type, before anything reaches a customer.
See Flow versions.

​
Staying current

Updating the dashboard

Tied tells you when a new version is available and lets you take it when you are ready — it never reloads underneath you mid-conversation.

Known limitations

What a platform does not allow, kept current alongside what we ship.