Launch Terri.ai on a live workspace
Configuration order, extension dependencies, staging checks, and the minimum setup for a production rollout.
Resources
Docs, rollout notes, and operator playbooks for a real support launch.
This page is built like a true SaaS resource hub. It now frames Terri.ai as a configurable platform with optional extensions, operator controls, and rollout guardrails.
Inbox automation and spam cleanup rules
How Terri.ai decides what is support, what is ops noise, and what should be archived or routed for human review.
Refund caps, address validation, and safe actions
Why order actions are bounded, what still requires confirmation, and how to avoid letting AI overreach.
Launch guide
Moving from staging to a live storefront support rollout.
Enable only the extensions you need, then add the connector credentials, OpenAI settings, and Google Maps key in the app dashboard.
Terri’s safe write actions and verification flows depend on the store connection being correct first.
Verify status questions, order detail replay, address edits, cancellations, and refund caps before rollout.
Make sure Terri’s inbox polling rules match your mailbox and that auto-reply is only enabled where appropriate.
Inbox automation
What Terri should do with incoming email.
Keep
- Order status questions with an order number
- Out-of-stock and restock questions
- Product questions tied to catalog items
- Threads that need human review
Archive or label out of the inbox
- Store ops notifications like new orders and failed orders
- Unsolicited marketing mail
- Unsupported-language contact spam for the US-only store flow
- General non-support conversations
Guardrails
The AI is useful because the action layer is constrained.
Terri works when the support model is explicit about what can and cannot happen automatically.
Refunds stop at the remaining balance
Customers cannot prompt the system to refund more than the order actually has available.
Address changes need validation
Google Maps checks are used before Terri stages a shipping edit for confirmation.
Email does not mutate orders directly
High-risk requests from email are pushed back into the verified Terri session instead of being applied from the inbox alone.
Update log