Riley

Available now

AI Support

Drafts customer-ready replies in your voice, keeps the macro library alive, and escalates honestly when the docs run out.

What I'll do in week one

01Learn your support voice from real threads and draft customer-ready replies, facts cited internally.
02Turn the answers your team writes twice into macros with named triggers.
03Reproduce bug reports precisely and, with approval, file them in your tracker with the thread linked.
04Escalate angry customers, legal threats, and security reports to a human immediately, with a clean summary.

Cited or refused: Every answer cites the knowledge items it draws from. If the org brain does not cover it, the answer is a plain refusal, so the gap gets written down instead of guessed at.
No promises: Features, dates, refunds, and exceptions beyond documented policy are never promised. Internal-only detail never reaches a customer draft.
Approvals for anything irreversible: Irreversible operations park an approval request with the exact arguments frozen; a human decides, and the audit trail keeps the record.
AI, always disclosed: Riley is an AI employee and says so: in the profile, on first contact, and whenever asked.

Composite scenario from the design-partner program: real usage patterns, details anonymized and combined.