# How Billing Works Source: https://docs.riloworks.com/account/billing Rilo uses a prepaid wallet — you fund a balance, and completed work draws it down. No subscription, no per-seat fees. ## Rilo uses a prepaid wallet Your organization funds a **prepaid wallet**, and the cost of work Rilo completes is deducted from that balance. Rilo is **not** a subscription and is **not** billed per seat — you pay for the work you actually use, drawn down from a balance you've funded in advance. There is nothing to cancel or downgrade: if you stop sending work, your balance simply stops being drawn down. For current rates, see the [Rilo pricing page](https://www.riloworks.com/pricing). ## Topping up adds funds to your wallet When your balance runs low, you add funds with a **Top up** from **Manage Billing** in the customer portal. A top-up adds funds to your prepaid balance, and subsequent work draws down from the new total. ## Completed work draws down your balance Rilo deducts from your prepaid balance as it completes work for you. Longer, multi-step tasks that involve research and browsing across tools consume more of your balance than quick questions. Your organization needs a positive balance to send Rilo new work. When your balance reaches zero, Rilo **pauses taking on new work** and tells you so, with a link to top up — it doesn't silently drop your request. Work already in progress is allowed to finish. To resume, add funds from **Manage Billing**, and Rilo picks up new requests again. ## Your first 2 hours of work are on us Every new organization starts with **2 hours of Rilo's work, free** — added automatically, so you can give Rilo a real task and see the finished work before funding anything yourself. It draws down as Rilo completes work, just like any balance. When it runs low, add more hours any time to keep your associate working. ## Rilo will not make billing changes for you Rilo can **explain** how billing works and **summarize** your own billing data when you ask, but it will not **perform** billing actions on your behalf — it cannot process payments, issue refunds, or change your plan, account security, or access. Those requests are escalated to [support@riloworks.com](mailto:support@riloworks.com). See [What Rilo Can't Do](/working-with-rilo/what-rilo-cant-do) for the full boundary. | Request | What Rilo does | | --------------------------------------------- | ------------------------------------------------------------------------------------------------------------------ | | "Summarize our invoices from last quarter." | Completes it — this is information work. | | "How does Rilo billing work?" | Answers from this documentation. | | "Refund this customer." | Escalates to [support@riloworks.com](mailto:support@riloworks.com) — Rilo does not process refunds. | | "Top up our balance." / "Change our billing." | Escalates to [support@riloworks.com](mailto:support@riloworks.com) — make changes yourself in the customer portal. | ## Questions about billing For invoices, receipts, or anything about your account that you can't resolve in the customer portal, email [support@riloworks.com](mailto:support@riloworks.com). # Connecting Tools Source: https://docs.riloworks.com/getting-started/connecting-tools How to give Rilo access to the tools it needs to work. Rilo accesses tools through browser automation — the same way a person would. To do that, it needs an account in each tool you want it to use. This page covers how to set that up. ## Slack Slack is the primary way to communicate with Rilo. An admin from your organization installs the Rilo Slack app from the customer portal, then authorizes it for your workspace. Once installed, invite Rilo to any channel where you want to assign tasks: ``` /invite @Rilo ``` Rilo only reads messages in channels where it has been explicitly invited. It does not have access to other channels. ## Email Your organization is assigned a dedicated Rilo email address: ``` rilo@.mail.riloworks.com ``` No additional setup is needed — email is ready to use as soon as your account is created. Send tasks to this address and Rilo will reply in the same thread. ## Browser-Based Tools For tools Rilo accesses via browser, you'll need to give Rilo an account. There are three ways to do this depending on the tool: **Best for:** Tools that support email invites — Slack workspaces, GitHub organizations, most SaaS tools. 1. From the tool's admin settings, send an invite to Rilo's email address: `rilo@.mail.riloworks.com` 2. Rilo receives the invite, accepts it, and registers into your workspace 3. No credentials need to be shared — Rilo manages its own account This is the simplest path and works for most team-based tools. **Best for:** Tools where you need to create an account before invites are available, or where you want direct control over the account. 1. Create an account in the tool using Rilo's email: `rilo@.mail.riloworks.com` 2. Go to the **Credentials** section in your customer portal 3. Select the tool and fill in the required fields (username/password, API key, etc.) 4. Credentials are encrypted on submission — Rilo's team never sees the plaintext values Never share credentials via Slack or email. Always use the secure credential portal. **Best for:** Platforms where account creation and org membership are separate steps — GitHub, for example. 1. Rilo self-registers an account using your organization's Rilo email address 2. You invite that account into your organization from the tool's admin settings 3. Rilo's account is then available for tasks within your org context ## What's Next See which tools Rilo has validated workflows for. How to describe tasks so Rilo delivers what you need. # How Rilo Works Source: https://docs.riloworks.com/getting-started/how-rilo-works Rilo answers quick questions instantly and queues real work to plan and execute across your tools. Understanding the difference helps you get the most out of it. Rilo is a managed AI service that completes knowledge work end-to-end. You delegate to it in plain language, and it decides how to handle each message. Knowing how Rilo handles a message — and how it does the work — helps you delegate effectively. ## Quick answers vs. queued work When you message Rilo, it first decides what kind of response your message needs: * **Quick answers.** Greetings, simple questions, and things Rilo can answer from context come back immediately, in the same conversation. * **Queued work.** Anything that needs Rilo to use your tools, gather information, or take several steps becomes a task that Rilo plans and executes. You'll get progress updates and a result when it's done — see [Following Up](/working-with-rilo/following-up). You don't have to label which is which; Rilo routes your message for you. Writing a clear request helps Rilo plan the right work — see [Writing Requests](/working-with-rilo/writing-requests). ## How Rilo does the work For queued work, Rilo plans a sequence of steps, then carries them out using its [skills](/working-with-rilo/what-rilo-can-do) across your [connected tools](/getting-started/connecting-tools). It observes what happens at each step and adjusts — if something doesn't work, it re-plans rather than blindly retrying. Outputs are grounded in the task's actual context and sources, not guessed. ## Rilo learns as it goes Rilo [remembers your organization's preferences, context, and what worked](/working-with-rilo/memory-and-learning) and applies that to later tasks. The same task tends to get faster and more aligned the more Rilo does it. This memory is shared across your organization and across every channel you use to reach Rilo. ## You stay in control * Rilo works with **least privilege** — standard user-level access through secure connections, not broad admin rights. See [Security & Privacy](/security/overview). * Some requests are **out of bounds on purpose** — Rilo won't make account, billing, or security changes, and tells you where to go instead. See [What Rilo Can't Do](/working-with-rilo/what-rilo-cant-do). * Everything is **partitioned by organization** — your data, memory, and connected tools are never shared across organizations. ## Where to go next * [Quickstart](/getting-started/quickstart) — get going in a few minutes. * [Connecting Tools](/getting-started/connecting-tools) — give Rilo access to your tools. * [Writing Requests](/working-with-rilo/writing-requests) — get better results from every request. # Quickstart Source: https://docs.riloworks.com/getting-started/quickstart Send your first task to Rilo and get results in minutes. ## Prerequisites * A Rilo account with an active workspace * Rilo added to your Slack workspace, or an email address configured for your organization ## Step 1: Open a Channel with Rilo **In Slack:** Invite Rilo to any channel where you want to work with it: 1. Open the channel 2. Type `/invite @Rilo` 3. Rilo confirms it's joined and ready You can also message Rilo directly in a DM. **Via email:** Your organization has a dedicated Rilo email address: `rilo@.mail.riloworks.com`. Send tasks there and Rilo will reply in the same thread. ## Step 2: Send a Task Mention Rilo in Slack and describe what you need in plain language: ``` @Rilo What time is it in Tokyo right now? ``` ``` @Rilo Look up Acme Corp — find their website, recent news, and who the key decision-makers are. Put together a short briefing. ``` ``` @Rilo I have a call with Sarah Chen at Meridian Health on Thursday. Can you pull together background on the company and anything public about her role there? ``` There's no special syntax. Describe the task the way you'd describe it to a person. ## Step 3: Watch It Work Rilo will: 1. Acknowledge the task in your channel 2. Work through the steps — browsing, reading, cross-referencing tools as needed 3. Deliver results back in the same channel or thread For simple questions, Rilo responds immediately. For tasks that involve research or multiple tools, it will check back in when it has results. ## Step 4: Follow Up If Needed While a task is running, you can send follow-up messages in the same channel: * **Add context:** `@Rilo also check if they have any open positions listed` * **Change direction:** `@Rilo actually, focus on their enterprise pricing, not the company overview` * **Stop the task:** `@Rilo stop` or `@Rilo never mind` * **Check status:** `@Rilo how's it going?` Rilo understands plain language — no commands to memorize. ## What's Next Give Rilo access to the tools it will need to work. How to describe tasks clearly so Rilo delivers what you need. How Rilo learns your preferences over time. # Integrations Source: https://docs.riloworks.com/integrations/overview Rilo works with any tool that has a web UI. Here's how it connects. Rilo connects to your tools through browser automation — if your team uses a tool in a browser, Rilo can use it too. There's no fixed list of supported integrations and no developer setup required. Native desktop apps (Figma desktop, VS Code, Office desktop) are not supported — Rilo works through web interfaces only. ## How Rilo Accesses Tools ### Browser Automation Rilo operates any web-based tool using a sandboxed browser. It navigates, clicks, fills forms, reads pages, and extracts data — the same way a person would. This works for the vast majority of tools your team uses day-to-day. ### Email Rilo sends and receives email as a first-class channel. This covers tools and workflows that are email-based — approvals, document exchange, notifications, and communication with external parties. ## Validated Tools These are tools where Rilo has demonstrated workflows. This list isn't exhaustive — if a tool has a web interface, Rilo can work with it. ### Communication | Tool | Notes | | ---------------- | ---------------------------------------------------- | | Slack | Receive tasks, deliver results, communicate mid-task | | Email | Send and receive emails, process attachments | | Google Workspace | Gmail, Google Docs, Sheets, Calendar, Drive | | Calendly | Schedule and manage meetings | ### CRM | Tool | Notes | | ---------- | --------------------------------------------------- | | HubSpot | Contact management, deal tracking, reporting | | Salesforce | Account research, opportunity management, reporting | | Apollo | Prospecting, contact enrichment, outreach sequences | ### Project Management | Tool | Notes | | ---------- | ----------------------------------------------- | | Jira | Issue tracking, sprint management, reporting | | Linear | Issue tracking, project management | | Confluence | Documentation lookup, page creation and editing | ### HR | Tool | Notes | | ---------- | ---------------------------------------- | | Greenhouse | Candidate review, application processing | ### Finance | Tool | Notes | | ------ | ----------------------------------- | | Stripe | Payment and subscription management | ### Developer Tools | Tool | Notes | | ------ | ------------------------------------------------ | | GitHub | Repository browsing, issue management, PR review | ## Adding a New Tool Two steps: give Rilo access to the tool (see [Connecting Tools](/getting-started/connecting-tools)), then describe the task. No developer involvement, no integration setup. For tools not on this list, contact [support@riloworks.com](mailto:support@riloworks.com) if you run into any issues — most web-based tools work out of the box. # Introduction Source: https://docs.riloworks.com/introduction Rilo is an AI knowledge worker you assign to tasks the same way you'd delegate to a person. Rilo works like a capable new team member who can use any tool with a web interface, knows your preferences and processes, and gets better the more you work together. Message Rilo in Slack or email with what you need. It figures out the approach, logs into your tools, does the work, and reports back. ## What Rilo Can Do There's no fixed list of supported task types. If it's knowledge work a person could do at a computer — reading, researching, writing, organizing, cross-referencing, scheduling, summarizing — Rilo can take a run at it. Some examples of what teams assign to Rilo: **Research & analysis** — Research a company before a sales call. Find recent news, key people, product changes, and funding history. **Data work** — Cross-reference invoices against records and flag discrepancies. Pull data from one system and update another. **Writing & drafting** — Draft outreach based on what you know about a prospect. Summarize a long document into a briefing. Write up meeting notes. **Coordination** — Review job applications and prepare a shortlist. Schedule across multiple calendars. Follow up on open items. **Monitoring & reporting** — Compile a weekly status report from your project management tool. Monitor a competitor's site for changes. This isn't a menu — it's a starting point. The more clearly you describe what you need, the more reliably Rilo can deliver it. ## How It Works 1. **Send a task** — message Rilo in Slack or email with what you need 2. **Rilo plans** — Rilo works out the steps: which tools to use, in what order, what to look for 3. **Rilo executes** — steps run across your connected tools 4. **Rilo reports back** — results are delivered in the same channel or thread where you asked 5. **Rilo learns** — Rilo remembers what worked: your preferences, your tools, your processes — and applies that knowledge to future tasks ## Where to Start Send your first task and see results in minutes. Give Rilo access to the tools it needs to work. How to describe tasks so Rilo delivers exactly what you need. How Rilo learns your preferences and working patterns over time. # Security & Privacy Source: https://docs.riloworks.com/security/overview How Rilo handles your data, credentials, and keeps your organization's information private. ## Your Data Stays Yours Rilo processes tasks within your organization's isolated context. Your data is never shared with other organizations, never used to train models, and never retained beyond what's needed to do the work and learn your preferences. ## Credential Handling When you connect a tool to Rilo, your credentials are submitted through a secure portal — not shared in Slack or email. Credentials are encrypted immediately on submission and stored in a way that Rilo's team cannot read them in plaintext. Rilo uses your credentials only to perform the tasks you assign. It doesn't store session state between tasks in a way that persists login sessions beyond task execution. **We never ask for credentials via Slack or email.** If you receive a message that appears to be Rilo requesting a password or API key through a chat channel, contact [support@riloworks.com](mailto:support@riloworks.com). ## Organization Isolation Each organization that uses Rilo is completely isolated from every other. This applies to: * **Task history** — your tasks and results are only visible within your organization * **Memory** — Rilo's learned knowledge about your preferences and processes is per-organization * **Browser sessions** — when Rilo uses a browser to work in your tools, that session is fully sandboxed and never shared with or reused by another organization * **Credentials** — stored and accessed only within your organization's context ## What Rilo Logs Rilo keeps structured records of task activity for your organization: * What tasks were run and when * Which tools were used * Whether a task completed, failed, or was cancelled These records are partitioned to your organization. They're available for your team's audit and review purposes. ## Browser Sessions When Rilo operates a browser-based tool on your behalf, the session runs in an isolated, sandboxed environment. Sessions are not reused across tasks or across organizations. Rilo uses only the tools and accounts you've explicitly connected. ## Compliance For our current compliance posture, security questionnaires, or architecture review materials, email [security@riloworks.com](mailto:security@riloworks.com). # Following Up Mid-Task Source: https://docs.riloworks.com/working-with-rilo/following-up How to add context, change direction, check status, or stop a task while Rilo is working. Once Rilo starts a task, you don't have to wait in silence. You can send follow-up messages at any point — in the same Slack channel or thread — and Rilo will pick them up. ## Adding Context If you remember something relevant after the task starts, just say it: ``` @Rilo also check if they have any open roles listed — hiring patterns would be useful context ``` ``` @Rilo one more thing: they recently rebranded from "Hargrove Partners" to "Hargrove Associates", so search under both names ``` Rilo incorporates the new information without restarting. The additional context flows into the work that's still in progress. ## Changing Direction If you want to shift what Rilo is focusing on: ``` @Rilo actually, skip the competitor section — focus on their pricing page instead ``` ``` @Rilo change of plan: don't draft the email yet, just give me the research first and I'll decide whether to proceed ``` Rilo will acknowledge the change and adjust. ## Checking Status If you want to know where things stand: ``` @Rilo how's it going? ``` ``` @Rilo what are you working on right now? ``` ``` @Rilo status? ``` Rilo will give you a quick update on what it's done so far and what's left. ## Stopping a Task If you no longer need the task completed, tell Rilo to stop: ``` @Rilo stop ``` ``` @Rilo never mind, I don't need this anymore ``` ``` @Rilo cancel that ``` Rilo will stop as soon as it reaches a safe stopping point. Depending on where the task is, this may take a moment — it won't stop mid-action in a way that could leave something in a broken state. ## A Note on Timing Rilo checks for your messages at natural pause points in its work, not continuously mid-action. If it's in the middle of a multi-step operation, your message will be picked up at the next break. For most tasks this happens quickly — typically within seconds to a minute. # How to Reach Rilo Source: https://docs.riloworks.com/working-with-rilo/how-to-reach-rilo Rilo works where you already work — Slack, Discord, email, and the web workspace. Message it like a teammate; no new app to learn. Rilo is a managed service you talk to in plain language, in the tools you already use. There is no separate app to install or dashboard to learn. You reach Rilo through four channels — **Slack**, **Discord**, **email**, and the **web workspace** — and you interact with it the same way in each: describe what you want, and Rilo plans the work, does it across your connected tools, and reports back. ## Slack Slack is the most common way teams work with Rilo. * **Direct message:** open a DM with the Rilo app and send your request. * **Mention in a channel:** type `@Rilo` followed by your request in any channel Rilo is in. * **Invite Rilo to a channel:** use `/invite @Rilo` to add Rilo to a channel, then mention it there. Rilo replies **in a thread** on your message. Threaded replies are intentional: each task gets its own thread, so you can run several requests at once without the responses colliding in the main channel. Follow-ups on a task stay in that task's thread. ## Discord Rilo works in Discord servers (guilds) your organization has connected. Once your server is set up, you reach Rilo the same way you would a teammate: * **Mention Rilo in a channel:** `@Rilo` followed by your request, in any channel the bot is in. * **Direct message:** DM the Rilo bot directly. Rilo reads your message and replies in the conversation. ## Email Every organization gets a dedicated Rilo email address in the form `rilo@.mail.riloworks.com`. Email Rilo the way you would delegate to a colleague: send a request (and any attachments or forwarded context), and Rilo replies in the same thread when the work is done. This is also how many third-party tools reach Rilo — for example, when you invite Rilo to a tool, the invitation goes to this address. ## Web workspace Inside the Rilo customer portal, every workspace has a built-in chat. You can talk to Rilo there directly — ask a question, kick off a task, or have Rilo build out the workspace itself. Messages you send from a workspace are treated as work for Rilo to pick up. See [Workspaces](/working-with-rilo/workspaces) for what you can do with the workspace surface. ## The same Rilo everywhere Whichever channel you use, it's the same Rilo, working for the same organization, with the same [memory](/working-with-rilo/memory-and-learning) and the same [connected tools](/getting-started/connecting-tools). What Rilo learns from a task in Slack is available when you email it later. Pick whichever channel fits the moment. # Memory & Learning Source: https://docs.riloworks.com/working-with-rilo/memory-and-learning How Rilo remembers your preferences, processes, and working patterns over time. Rilo gets more useful the longer you work with it. After each task, Rilo retains what it learned about how you like things done — and applies that to future tasks automatically. ## What Rilo Remembers **Your preferences** How you like results formatted, what level of detail you want, which tools you prefer for what kinds of tasks. **Your processes** If Rilo figures out the right sequence of steps to accomplish a recurring task, it remembers that approach and applies it next time. **Context about your organization** Who your key accounts are, what tools your team uses, terminology specific to your industry or company. **What worked** If a particular approach produced good results, Rilo notes it. If a task needed correction, Rilo factors that in going forward. ## How Memory is Shared Memory is shared across your organization — not per person. If your colleague works with Rilo and establishes that the team prefers reports in a particular format, Rilo will apply that for you too. This means Rilo gets better for your whole team over time, not just the individuals who use it most. ## Setting Preferences Explicitly You don't need to wait for Rilo to infer a preference. You can state them directly in any message: ``` @Rilo My preference going forward: when you write outreach emails, keep them under 80 words and never mention pricing in a first touch. ``` ``` @Rilo For any research task, I always want a LinkedIn URL included for the key contacts, not just their names. ``` ``` @Rilo Going forward, format all summary deliverables as bullet points, not paragraphs. I read them faster that way. ``` Rilo will confirm it's noted and apply the preference to future work. ## Correcting Rilo If Rilo does something the wrong way, tell it — and tell it what you'd have preferred: ``` @Rilo This is too long. In the future, keep research summaries to half a page maximum unless I ask for more. ``` ``` @Rilo I didn't want you to email them directly — I just wanted a draft for me to review. Going forward, always check before sending anything externally. ``` Corrections work the same way as preferences: Rilo notes them and adjusts. ## Memory Within a Task Rilo also carries context within a single task session. If you add context mid-task or redirect Rilo partway through, it incorporates that and continues — it doesn't restart from scratch. See [Following Up Mid-Task](/working-with-rilo/following-up) for how to add context, change direction, or stop a task while it's running. # What Rilo Can Do Source: https://docs.riloworks.com/working-with-rilo/what-rilo-can-do Rilo completes knowledge work end-to-end across your connected tools — browsing, research, email, data work, documents, and more — by composing general-purpose skills, not fixed features. Rilo is a general-purpose AI knowledge worker. You don't pick from a menu of features — you describe the outcome you want, and Rilo plans the steps and uses whatever skills the job needs. The skills below are the building blocks Rilo composes; most real tasks use several at once. For the small set of things Rilo deliberately won't do, see [What Rilo Can't Do](/working-with-rilo/what-rilo-cant-do). ## Work in your web tools Rilo can use websites and web apps the way a person does — opening pages, clicking, typing, reading what's on screen, and moving between tabs. This is how Rilo operates the long tail of tools that don't have a clean API: it drives the actual web interface. If your team uses a tool through a browser, Rilo can generally work in it too. ## Research and search the web Rilo can search the internet for current information and pull together what it finds — competitive research, prospect briefings, market context, answers to open questions — and ground its output in the sources it used. ## Call APIs and integrations When a tool offers an API, Rilo can make requests to it (with your connected credentials), including reading and writing data, and it handles paginated results and API errors as part of the work. See [Connecting Tools](/getting-started/connecting-tools) for how access is set up. ## Handle email Rilo can draft and send email from your organization's Rilo address, wait for replies, and use email to complete flows that depend on it (for example, registering for a service that sends a confirmation). See [How to Reach Rilo](/working-with-rilo/how-to-reach-rilo) for the address format. ## Work with documents and data Rilo can create and edit documents, build and maintain tables and structured data, and process data programmatically — calculations, transformations, and analysis — running code in an isolated sandbox when a task calls for it. Results land in your [workspace](/working-with-rilo/workspaces) or the tool you asked Rilo to use. ## Build and maintain workspaces Rilo can turn an empty [workspace](/working-with-rilo/workspaces) into a working surface for a project — a dashboard, a tracker, a list of accounts — and keep it updated as work progresses. Workspaces are general-purpose: Rilo builds the structure from what you ask for. ## Remember and improve Rilo [learns your organization's preferences, context, and effective approaches](/working-with-rilo/memory-and-learning) and applies them to later tasks, so repeated work gets faster and more aligned over time. ## Schedule and follow through Rilo can schedule work to run later or on a recurring basis, track multi-step tasks to completion, and [keep you updated as a task progresses](/working-with-rilo/following-up). ## How to think about it Because Rilo composes general skills rather than running fixed features, the best way to use it is to **describe the result you want, with the context Rilo needs** — not to look for a specific button. [Writing good requests](/working-with-rilo/writing-requests) covers how to do that well. If a task is outside what Rilo can do, it tells you rather than guessing. # What Rilo Can't Do Source: https://docs.riloworks.com/working-with-rilo/what-rilo-cant-do Rilo handles knowledge work, not your account. It won't make billing, payment, or account-security changes — it points you to the right place instead. 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](mailto: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. | Request | What Rilo does | | ------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------- | | "Summarize our invoices from last quarter." | Completes it — reading and summarizing is information work. | | "Summarize the payment terms in this vendor contract." | Completes it — reading and summarizing is information work. | | "Find the invoice for order 1182." | Completes it — searching your tools is fine. | | "Change our billing details." | Escalates to [support@riloworks.com](mailto:support@riloworks.com) — Rilo doesn't make billing or plan changes. | | "Refund this customer." | Escalates to [support@riloworks.com](mailto:support@riloworks.com) — Rilo doesn't process refunds. | | "Reset my password." / "Add this person as an admin." | Escalates to [support@riloworks.com](mailto:support@riloworks.com) — Rilo doesn't change account security or access. | ## 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](mailto:support@riloworks.com) or use your customer portal. # Workspaces Source: https://docs.riloworks.com/working-with-rilo/workspaces Workspaces are general-purpose surfaces where you and Rilo work together. They start blank — Rilo builds the structure from what you ask for, and keeps it updated as work progresses. A workspace is a shared surface in the Rilo customer portal where you and Rilo work together on a project. Workspaces are **general-purpose**: they don't come as pre-built apps for a specific use case. A workspace starts blank, and Rilo builds the structure it needs from what you ask for — a dashboard for a launch, a tracker for outreach, a list of accounts to research. You can also build and edit it yourself. ## What's in a workspace A workspace holds one or more documents, and each document is made of **widgets** — general building blocks Rilo arranges to fit the work, such as: * tables and grids * kanban boards and checklists * rich-text and markdown documents * forms, calendars, timelines, and galleries * a live activity feed of what Rilo is doing The same set of building blocks covers every kind of work. There are no per-industry layouts — the *structure* is general, and the *content* is whatever your task needs. ## Working with Rilo in a workspace Every workspace has a built-in chat. From there you can: * **Ask Rilo to build the workspace** — "Set up a workspace to track our Q3 partner outreach," and Rilo creates the documents and widgets to match. * **Kick off work** — give Rilo a task and watch it progress in the workspace's activity feed. * **Edit alongside Rilo** — add or change content yourself; Rilo and your teammates see the same state. Because the workspace chat is just another way to [reach Rilo](/working-with-rilo/how-to-reach-rilo), anything Rilo learns there feeds the same [memory](/working-with-rilo/memory-and-learning) as your other channels. ## Sharing and access Workspaces are **organization-wide**: every member of your organization can see your organization's workspaces, with access following their organization role (owner, editor, or viewer). There are no per-workspace invite lists to manage — if someone is in your organization, they can work in its workspaces. Everything is partitioned by organization, so workspaces are never shared across organizations. ## Your home workspace Each member gets a personal **home workspace** that hosts the portal-wide chat with Rilo — a standing place to talk to Rilo even when you're not in a specific project workspace. # Writing Good Requests Source: https://docs.riloworks.com/working-with-rilo/writing-requests How to describe tasks so Rilo understands what you need and delivers exactly that. Rilo doesn't need special syntax or commands. It understands plain language — but the quality of what it delivers depends heavily on how clearly you describe what you need. ## The core principle: be specific about the outcome Rilo will make reasonable choices wherever you leave things unspecified. That's useful when the details don't matter to you, but if they do matter, spell them out. **Weak:** ``` @Rilo research Acme Corp ``` Rilo will produce something, but you'll get a general overview when you might have wanted something much more specific. **Better:** ``` @Rilo I have a renewal call with Acme Corp next week. Can you pull together: - Their current headcount and recent growth signals - Any news about them in the last 3 months - Who their main decision-makers are (LinkedIn is fine) - Whether they've posted any job openings that suggest expansion or contraction Format as a short briefing I can read in 2 minutes. ``` Naming the context ("renewal call"), specifying the sources ("LinkedIn is fine"), and describing the format ("short briefing, 2 minutes") all sharpen the result. **Weak:** ``` @Rilo check our invoices ``` **Better:** ``` @Rilo In Stripe, pull all invoices from January that are marked paid. Cross-reference them against the deals closed in HubSpot in the same period. Flag any where the invoice amount doesn't match the deal value, and list the discrepancies in a table with the deal name, invoice ID, deal amount, and invoice amount. ``` Naming the tools (Stripe, HubSpot), the time period (January), the specific action (cross-reference), and the output format (table with specific columns) leaves little room for misinterpretation. **Weak:** ``` @Rilo draft outreach for this lead ``` **Better:** ``` @Rilo Draft a cold outreach email to Marcus Webb, VP of Operations at Thornfield Logistics. Keep it under 100 words. The angle is that we help ops teams cut manual reporting work — lead with that. Don't mention pricing. Sign it as me (Jamie). ``` Tone, length, angle, constraints, and sign-off — these are all things a person writing for you would need to know, and Rilo is no different. ## Provide context Rilo can't see Rilo can access your connected tools, but it doesn't know things that live only in your head. If the task involves a specific situation, relationship, or background — include it: ``` @Rilo We've been negotiating with Hargrove & Associates for three months. They've been dragging their feet on contract review. Can you look them up and find any recent news that might explain the delay — leadership changes, budget cycles, anything like that. ``` ``` @Rilo I need to prep for a difficult conversation. The candidate we're rejecting for the senior engineer role has been in the process for 6 weeks. Can you draft a rejection email that's warm but clear, and mentions we'll keep their details on file for future roles? ``` Background context turns a generic output into something useful. ## Specify format when it matters If you're going to paste results into a doc, send them to someone, or present them — say so: * `summarize as 5 bullet points` * `put it in a table with columns for: name, title, email, LinkedIn` * `format as a Slack message, keep it conversational` * `write it up as a proper report with headings` * `give me just the numbers, no explanation needed` ## Tell Rilo what tools to use (or avoid) If you have a preference for which tool Rilo should use for a task, say so: ``` @Rilo Find their contact info — check Apollo first, then LinkedIn if Apollo doesn't have it. ``` ``` @Rilo Don't use their website for this — it's outdated. Pull from LinkedIn and Crunchbase only. ``` ## Ask for clarification up front If you're not sure whether you've given Rilo enough to go on, you can ask it to check before starting: ``` @Rilo Before you start — do you have everything you need for this, or do you want me to clarify anything? ``` ## What Rilo will do when a task is ambiguous If the task is too ambiguous to make a reasonable interpretation, Rilo will ask a clarifying question before proceeding. It won't guess when getting it wrong would waste significant work. For shorter tasks, Rilo may make a reasonable assumption and proceed, then note what it assumed in the result.