Rilla
Sales Enablement
Field-sales conversation intelligence: pull recorded sales conversations, markers, and rep performance into Ruby.
Ask Ruby
4 read-only tools
Ruby reads from Rilla and grounds her answers in your data. Every tool is read-only: she surfaces, summarizes, and drafts; a human always takes the action.
List conversations
List recorded in-home / field sales conversations from Rilla Voice for a date range, optionally filtered to specific rep emails. Each result carries the conversation's markers (checklist trackers: objections, competitor mentions, price pushback, script adherence), the recording rep, outcome, total sold, talk-ratio and monologue metrics, plus a Rilla deep link (rillaUrl) and the conversationId. Use rilla_get_conversation with a conversationId for the full record and transcript. Page through with `page`.
Get conversation
Get one Rilla sales conversation by its conversationId, including its markers (checklist trackers) and, by default, the full transcript (speaker turns). Rilla has no lookup-by-id endpoint, so you MUST pass the date window (from_date / to_date) the conversation falls in; this tool pages the export to find it. Get the conversationId and window from rilla_list_conversations first. Set include_transcript=false to skip the (slower) transcript fetch.
List users
List Rilla Voice users (sales reps / estimators) with their per-window performance analytics: conversations recorded, talk ratio, patience, recording compliance, scorecards given/received, appointments, ridealongs, and script compliance. Use for rep performance, coaching, and scorecard questions over a date range.
List teams
List Rilla Voice teams with their per-window aggregate analytics: conversations recorded, recording compliance, talk ratio, patience, scorecards given/received, appointments, and user counts. Use for team-level performance and coaching rollups over a date range.
Built for restoration, not bolted on.
Grounded answers
Ruby reads Rilla live and cites what she found, so answers reflect your actual data, not a stale export.
Read-only by design
Least-privilege, read-only access. Ruby surfaces and drafts; your team always takes the action.
Managed, secure auth
Connect with one click. Tokens are encrypted and scoped per company; revoke access any time.
Knows restoration
Ruby understands jobs, claims, drying logs, and AR, so Rilla data lands in the right operational context.
Connect once, then just ask.
Connect Rilla once in Ruby. Ask in the Ruby app, or bring the same secure connection into the assistant your team already uses.
Ruby
Ask in the Ruby app and get an answer grounded in Rilla and the rest of your connected stack.
Claude
Bring the same secure Rilla connection into Claude so it can answer with your live data.
ChatGPT
Use Rilla from ChatGPT with the same per-company, read-only access Ruby uses.
Frequently asked questions
Do I need developer credentials to connect Rilla?
You paste an API key from your account in Settings > Integrations. There is nothing to build; Ruby stores it encrypted and scoped to your company.
Can Ruby change anything in Rilla?
No. The Rilla connection is read-only. Ruby reads, summarizes, and drafts; a human always makes the change in Rilla.
Is my Rilla data secure?
Credentials are encrypted at rest and access is scoped per company. You can revoke the connection at any time from Settings > Integrations, which immediately cuts Ruby off.
Can I use Rilla alongside my other tools?
Yes. Ruby reasons across every tool you connect at once, so she can tie Rilla to your CRM, accounting, email, and documentation in a single answer.
