Catch up on a conversation
Ask for the message history Quo exposes to your connected account, filtered to the contact, inbox, or time period relevant to the rental question.
Quo integration · formerly OpenPhone
Bring Quo into your property management workflow
Connect your own Quo account to Rentium's built-in assistant with OAuth. Ask about calls and texts beside the rental records that give them context, while an exact approval checkpoint stands between a draft and anything Quo changes.
No copied API key Personal per collaborator Writes fail closed
Quo
Personal OAuth connection
one assistant turn
Catch me up on the messages about the renewal at 14 Oak.
Explicit read-only tool
The tenant asked about the new term and move-out notice window. No Quo record changed.
Exact action · approval required
Send one Quo message
- To
- Selected tenant conversation
- Body
- The complete proposed reply
The direct answer
One assistant for the record and the conversation
Rentium acts as a client of Quo's remote MCP server. It discovers the tools available to your personal grant at the start of a turn instead of maintaining a stale, provider-specific copy. Quo remains the source of truth for communication access; Rentium remains the source of truth for rental records and authorization.
Review calls that need follow-through
Retrieve available call or voicemail transcripts, then use Rentium records to understand which property, lease, or follow-up the conversation concerns.
Prepare a precise response
Draft a reply with the right rental context. If the assistant proposes sending it or changing anything in Quo, Rentium shows the exact action before Quo is called.
Connect once
From OAuth to an approved follow-up
- 1
Connect your own Quo access
Open Assistant → Connections and choose Connect Quo. Rentium registers the OAuth client dynamically, sends you to Quo to sign in, and stores the returned grant encrypted. No API key or shared workspace credential is copied into Rentium.
- 2
Ask from Rentium's built-in assistant
Rentium discovers the current tools Quo exposes to your grant for that turn. Ask it to find a conversation, summarize messages, review an available call transcript, or prepare a follow-up alongside your authorized rental records.
- 3
Approve the exact action when needed
A tool runs directly only when Quo explicitly and unambiguously marks it read-only. Every other tool stops at a Rentium-owned card showing the exact arguments; Approve claims and runs that stored action once, while Reject consumes it without calling Quo.
Deliberate boundaries
Useful by design, bounded by design
The integration does not turn a personal phone grant into a shared workspace secret, expose it to external AI clients, or quietly create background automation. Those separations are part of the product contract, not prompt suggestions.
- Connection owner
- Personal to one collaborator and workspace membership
- This Rentium grant
- Available only to Rentium's built-in assistant
- Runs directly
- Only tools explicitly marked read-only by Quo
- Everything else
- Exact Approve/Reject card, claimed at most once
- Direct ChatGPT or Claude
- Use Quo's separate connector in that product
- Conversation data
- Requested results may enter model context and saved chat history
Read path
Ask, retrieve, answer
An unambiguously read-only Quo tool can return requested context directly. The result is still untrusted tool data, scoped to the connected person's Quo access.
“Summarize the messages about the renewal this week.”
“What did the caller say about the maintenance visit?”
Action path
Propose, inspect, decide
A send, contact change, or anything not explicitly read-only becomes a durable one-shot proposal. The card—not a phrase typed into chat—is the authorization.
“Draft a reply with the inspection time and ask me before sending.”
“Add the new contact details after I review the exact fields.”
Plain-language answers
Quo integration questions
- Is Quo the same product as OpenPhone?
Yes. OpenPhone rebranded to Quo in September 2025. Existing Quo documentation and parts of the market may still use the former OpenPhone name, so Rentium names both on this page.
- What can the Rentium Quo integration do?
It lets Rentium's built-in assistant use the current MCP tools available to one staff member's Quo grant. Quo currently documents message-history and call-transcript reads, text sending, and contact creation or updates. The live catalog remains Quo-owned and can change without Rentium freezing a separate list.
- Does one Quo connection belong to the whole Rentium workspace?
No. Every Quo connection is personal to one Rentium collaborator and one active workspace membership. Teammates connect their own Quo access, and Quo remains authoritative for the phone workspace, inboxes, and numbers each person can reach.
- Can ChatGPT or Claude use my Quo connection through Rentium?
Not through Rentium. Rentium keeps your personal Quo grant inside its built-in assistant and does not re-export it through Rentium's public MCP server. Quo separately offers official connectors for ChatGPT and Claude, so connect Quo directly in either product if that is where you want to use it.
- Which Quo actions require approval?
Only a tool Quo explicitly marks read-only can run directly. Sending a message, creating or changing a contact, and any tool with false, missing, or malformed read-only metadata must stop for exact Approve or Reject controls. Approval is one-shot and a typed chat reply cannot substitute for it.
- Where do requested Quo results go?
Requested Quo results can enter the model context for that assistant turn and the stored Rentium chat history. Rentium sends model requests with no-collection and zero-data-retention routing settings; Quo and the selected inference provider remain separate services with their own terms. Disconnecting removes the saved grant from future turns but does not rewrite prior chats or delete Quo's own records.
Keep the conversation beside the work
Connect Quo personally, then let Rentium's assistant help you catch up and prepare the next step—without sharing the grant or skipping the approval boundary.
Open Assistant Connections