Skip to main content
Rilo is built to do knowledge work across your connected tools. A few kinds of requests sit outside that boundary on purpose — anything that changes your Rilo account, billing, or security. For those, Rilo doesn’t attempt the action and doesn’t pretend it did; it directs you to the right place.

​
Rilo escalates account, billing, and security actions

Rilo will not perform the following actions. If you ask for one, Rilo responds right away with a pointer to support@riloworks.com (or your customer portal) instead of attempting it:
  • Billing — resolving billing issues
  • Payments — making or changing payments
  • Refunds — issuing refunds
  • Subscription or plan changes — changing what you pay for
  • Account security — security settings or incidents on your account
  • Credentials — resetting or changing passwords, keys, or logins
  • Admin access — granting, changing, or escalating account access
When Rilo escalates, it tells you why and where to go — it never silently drops the request or claims it completed something it can’t do.

​
Rilo gates the action, not the topic

The boundary is about the action you’re asking Rilo to take, not the subject you mention. Asking Rilo to read, summarize, draft about, or analyze billing, accounts, or security information is ordinary knowledge work and Rilo will do it. Asking Rilo to change your account, billing, or security is what gets escalated.

​
Why this boundary exists

Account, billing, and security changes are high-stakes and often require a human or an authenticated action you should take yourself. Keeping Rilo out of them protects your account and keeps Rilo focused on what it’s good at — the work. For anything in the list above, contact support@riloworks.com or use your customer portal.