ShipThanks Documentation
ShipThanks is a customer retention platform for direct-selling organizations. When a customer places an order, ShipThanks prompts the seller to record a short personal video thank-you. The customer receives it by text message, can reply, and the seller carries on the conversation from a shared dashboard.
The core idea: the personalized video is the product, so a human is always in the loop. ShipThanks automates the timing — catching the moment a purchase happens, when gratitude lands hardest — but never the message itself. Nothing is ever auto-sent to a customer.
Who it's for
| Role | What they do in ShipThanks |
|---|---|
| Organization | The brand or company. Owns a dedicated phone number, templates, sellers, and analytics. |
| Seller | An individual sales rep. Receives record prompts, sends video thank-yous, and manages customer conversations. |
| Customer | The end buyer. Interacts purely over SMS and the public video watch page — no account, no app, nothing to install. |
| Org admin | Manages sellers, templates, and settings, and reads retention analytics. |
The product offering at a glance
- Order-triggered seller prompts — when an order comes in, the seller gets an SMS with a one-tap link straight to the record screen. One prompt per order, no matter how many times the event is reported.
- Personal video thank-yous — the seller records in the browser and sends. The customer receives an MMS with an animated GIF preview and a link to a branded watch page.
- Two-way conversations — customer replies route to the right seller's dashboard inbox, and the seller responds from the org's number.
- Retention analytics — funnel metrics, seller leaderboards, conversation quality, and repurchase cohorts that show the lift thank-yous generate.
- API-first integration — your order management system, back office, or e-commerce platform starts a conversation with a single API call. See the API reference.
Where to go next
- How it works — the two-phase flow from order event to customer message.
- Conversations — replies, the dashboard inbox, and the watch page.
- Getting started — onboarding your organization, number registration, and starting your first conversation.
- API reference — authentication, the conversations endpoint, and customers.