Tranthor is an AI retention team and autonomous CRM for ecommerce. This page describes what happens between connecting a store and a message reaching a customer: the data Tranthor reads, how a campaign gets drafted, where you approve it, which checks run before anything sends, and how the result is reported.
It describes what ships today. Connectors and features that are planned are labelled as planned, and the integrations page shows the live status of every connector.
1. Data in: what Tranthor reads
Tranthor reads the data layer your store already uses. It does not replace your store or move your customers into a new system of record.
- Shopify is the live commerce source: orders, products and customers.
- Segment brings customer events into Tranthor.
- Catalog sync keeps your product catalog alongside customer data.
- An API lets you send customer data to Tranthor directly.
- WooCommerce and Salla are marked coming soon and cannot be set up yet. There is no Klaviyo import.
2. Signals: how Tranthor finds the moment
From order history Tranthor watches repeat-purchase timing, lapse risk and customer value. Lapse risk is a score specific to each merchant rather than one fixed number of days for every store.
Each signal maps to a playbook, the job a retention agent does for one moment in the customer lifecycle.
- Second purchase: new-customer activation after the first order.
- Lapse recovery: customers whose lapse risk score is rising.
- Reactivation: lifecycle win-back for customers who have gone quiet.
- VIP: saving high-value customers who show risk.
3. Drafting: what a playbook produces
When a playbook fires, Tranthor drafts the audience, the message, the timing and any offer. Copy follows your brand kit: brand tone guides the writing, and colors and fonts apply where the message format supports them.
Email templates carry per-language variants, and right-to-left locales such as Arabic render right to left.
4. Approval: how autonomy is switched on
Every playbook starts in review. The first run is always drafted for your approval, and you can approve it, request changes or reject it.
Auto-send is off by default and is switched on per playbook. It unlocks only after one approved run, and it stays disabled while the playbook has blocking readiness issues. You can pause any playbook.
5. Send-time checks: the limits Tranthor enforces
Limits you approve in your operating policy are checked at send time on autonomous sends, not only when a campaign is drafted.
- Contact frequency: a cap on marketing contacts per customer per week.
- Contact spacing: a minimum number of hours between contacts.
- Daily send cap: a ceiling on workspace sends per day.
- Discount cap: declared offers are checked against the discount percentage you approve.
- Allowlists: the channels, senders and segments Tranthor may use.
- Consent: autonomous sends require a subscription group and skip anyone who has unsubscribed or not opted in. Emails carry unsubscribe headers.
6. Channels and data out
Tranthor sends on email, SMS and WhatsApp where each is connected and configured, and autonomous sends cover all three. Journeys can also call webhooks.
HubSpot is a destination: Tranthor sends segments and engagement logs to it. It is not an inbound data source.
7. Measurement: how results are reported
Each campaign reports attributed revenue per recipient for the conversion events you configure, over an observation window. Every result is marked unavailable when data is missing, preliminary while the window is open, or mature once it closes. Missing data is never shown as zero revenue.
Attributed revenue is not proof of cause. Lift needs a holdout: where you configure one, a random group is held back and compared with the group that received the campaign. Lift is a plain difference, without a significance test, and appears once both groups have at least 100 customers. Holdouts are opt-in, so lift is not measured on every send.
How to set up Tranthor
From connecting a store to the first approved campaign.
- 1
Connect Shopify
Connect your Shopify store so Tranthor can read orders, products and customers. Add Segment if you want customer events too.
- 2
Connect channels
Connect and configure the email, SMS or WhatsApp senders you want Tranthor to use.
- 3
Approve your limits
Set contact frequency, spacing, the daily send cap, the discount cap and the channel, sender and segment allowlists.
- 4
Review the first draft
Each playbook drafts its first run for review. Approve it, request changes or reject it.
- 5
Choose the autonomy level
After an approved run, switch a playbook to auto-send within your limits, or keep it in review.