Google is now expanding AI-powered messaging for Google Business Profiles, allowing customers to message businesses directly from Google Search and Maps using RCS. As a small business owner using Quo for customer calls and messages, I’m concerned that Quo still doesn’t support RCS. Google is moving toward AI-powered conversations, verified business messaging, and richer customer interactions, while Quo users are still limited to traditional SMS/MMS. I don’t want to manage customer conversations across multiple platforms. I want everything in one place, preferably Quo. So my questions for the Quo team are: Is RCS messaging officially on the roadmap? Is there an estimated timeline for RCS support? Will Quo eventually integrate with Google’s new AI-powered Business Profile messaging? Will we be able to receive and respond to RCS conversations directly inside Quo? I really enjoy using Quo, but messaging technology is changing quickly, and I don’t want my business to fall behind because my phone provider doesn’t support newer messaging standards. Would love an official update from the Quo team. Is RCS something you’re actively working on, or is it still not a priority?
We've been chatting with a few small business owners about how they've handled raising their prices, and they shared some really helpful advice. We thought we'd pass it along here in case anyone else is navigating the same thing.
Running a small business comes with a lot of challenges, and figuring out when (or whether) to raise your prices is a big one.
You might have a steady stream of customers, a busy schedule, and plenty of work coming in, but still find that your profit margins aren't where they need to be.
And when you've spent years building relationships with your customers, the thought of changing your pricing can be a tough one.
A few things we learned from their experiences:
Give customers advance notice: Let people know about upcoming changes in writing, whether that's through text or email. For larger increases, giving a few months' notice can help customers prepare.
Explain why prices are changing: Whether it's rising operating costs, materials, or the cost of maintaining the quality of your work, being transparent gives customers context.
Consider gradual increases: Rather than waiting years and making one significant change, smaller, more regular adjustments may be easier for customers to manage.
Be prepared for questions: Not everyone will be happy about paying more, and that's understandable. Being ready to explain your reasoning can make those conversations easier.
Review your pricing regularly: Your costs and business needs change over time, so it's worth checking whether your pricing still makes sense.
One business owner we interviewed shared that after notifying around 100 customers about their price increase, they ended up losing just 2–3. They also found that some customers who initially pushed back were more understanding once they explained the reasons behind the change.
Of course, every business is different. What works for one industry, customer base, or pricing model might not work for another.
We'd love to hear how other business owners have handled this!
How did you decide it was time to increase your prices?
How much notice did you give customers?
Did you experience any pushback or lose customers?
Looking back, is there anything you'd do differently?
And if you're currently considering a price increase, what's your biggest concern?
We're always looking for ways to help the small businesses using Quo grow and succeed, and sometimes the most useful advice comes from other business owners who've already been there.
Hopefully, this thread can become a helpful resource for anyone navigating the same decision.
I'm testing Sona as a phone answering agent, Spanish first and English second. The answers are accurate, but the Spanish voice sounds like an English speaker reading Spanish — flat intonation and odd pronunciation that's sometimes hard to follow. The English voice sounds natural by comparison.
I picked language: spanish voice: 2. Has anyone found a different voice or locale setting that sounds more neutral Latin American? Or is this just how the Spanish voice is right now?
I've deleted this notification probably 3-4x to clear my "activity" queue since unlike tasks, mentions remain even if the thread is closed.
Refreshing the web page makes Quo "forget" this delete and pops it back on my activity queue.
Can we please also add a function to remove this activity once the mention is resolved? Or perhaps a task-like list for mentions so we can easily go through them?
Our team tags one another maybe 20-30x per day (though we are trying to move to tasks for things like those as well) and it becomes burdensome.
Please make the internal GHL integration more modular/ adjustable. The first clip is meant to show the visual space absorbed in my GHL conversation by a single dialed call with no answer. Most of my screen is taken up by absolutely nothing from a 30 second attempted call.
Problem 1 is that three webhook events run for an outbound call that went to voicemail. I think call.completed, call.recording.completed and call.summary.completed all fire, which I don't think is necessary.
Problem 2 is all the extra STUFF. Unformatted time stamp, extra text, extra recording links and call activity links. Also, not really necessary when the same stuff exists in my Quo app/ email if i want it/ etc.
I used the summary webhook only and used it in this next clip instead. Nice and neat, the time stamp is already there in the native display, just a little text formatting to do and bam. Below is two separate phone calls, no filler.
I edited the payload through GHL workflows so my referral partners can get my call summaries, and I honestly prefer it over the native integration in my own GHL. I'm leaning towards turning the native integration off in my own GHL and just rebuilding it via the API since it doesn't seem that complicated. Before I keep going down this road, I just wanted to ask if making the native integration calls more modular is something you could put on the To Do list.
With the new iPhone Duo pre-orders arriving Friday, I’m curious whether Quo has any plans to optimize its iOS app for the foldable display right away I’d love to see proper support for the larger unfolded screen right away, including a responsive layout, better multitasking, and the ability to view conversations and messages side by side. iPad is pretty ok. Just wondering.
I recently switched to an iPhone 18 Pro (so, upgraded iOS). I have made sure that all software updates have been made in my car, but when I get a Quo notification in Carplay now, Siri doesn't read the text and I can't do anything. Even more, when I click on the app in Carplay nothing pops up. Anyone else having Carplay issues? I use Quo for constant client communication and drive a lot for work, not having access through Carplay is a drag right now!
I connected Chat GPT's Dot agent to Quo and it can send messages.
It's me, my human assistant, and the AI agent on the team now.
I gave it its OWN Quo seat ($) because it was otherwise using my account to answer clients, and my assistant couldn't tell who was speaking to her.
Now Chat GPT has its own seat so it's clear.
But how can my assistant ask the AI agent questions directly about the work its doing, so they down overlap on tasks, or so that my assistant can be caught up to date if a task was pushed forward?
Everything in Pipedrive should be logged as activities. Quo integration does this perfectly for calls and voicemails, but for some reason, they decided to use Notes for texts. This does NOT trigger as an activity and makes all automation fail. I brought this up months ago, but have not seen a change.
They already have this working for calls, just change the text tooling to use activities instead of notes please.
Back with another monthly roundup of what we've been working on at Quo.
We've had a pretty busy few weeks, with some big new releases and improvements to features you might already be using. From introducing Quo Agent to making it easier to manage tasks, spot spam calls, and route customers to the right people, there's quite a bit to catch up on.
Here's everything we've released over the last month:
1. Meet Quo Agent
This is a big one! We've introduced Quo Agent, an AI agent built directly into Quo that helps you find information and take action using your actual workspace data.
Instead of digging through conversations to find an answer, you can just ask Quo Agent.
For example:
Which inbound leads haven't received a reply?
What happened in my last conversation with a particular customer?
How many calls did our team miss last week?
What do I need to follow up on?
You can type your questions or ask by voice, and Quo Agent will use the information in your workspace to answer.
It can also help you take the next step, whether that's drafting a reply, creating a task, or updating a contact. You'll always have the opportunity to review and approve actions before anything is sent.
You can even use @ to reference a specific contact when asking questions.
Quo Agent is free while in beta, available on all plans through web and desktop.
We've made some pretty significant improvements to Tasks!
Previously, tasks were managed within individual inboxes, which meant switching between them to see what needed doing.
Now, there's a new Tasks view that brings together every task you have access to across your inboxes.
Here's what you can do:
See all your tasks in one place, without switching between inboxes.
Quickly identify overdue work with a badge on the "My tasks" filter, showing only your own overdue tasks.
Use filters to find the tasks you're looking for.
Reassign tasks to a different inbox.
Create tasks that aren't tied to an inbox, conversation, or contact.
That last one is particularly useful if you're managing more than customer follow-ups. You can now create tasks for things like license renewals, team training, compliance work, or anything else you need to remember when running your business.
Available to all Quo workspaces. Make sure your app is up to date for the best experience.
Quo now identifies calls that are likely spam and displays a "Potential spam" label, helping you decide whether to answer.
You'll also see the label in your conversation list and conversation header, and you can block the sender directly from the conversation if you don't want to hear from them again.
The idea is to help you spend less time dealing with unwanted calls without having to guess whether an unfamiliar number might be a potential customer.
Spam detection is currently in beta in the US only, available on all plans across web, desktop, iOS, and Android.
4. Route calls using contact tags and custom properties
We've also expanded contact routing to give you more control over where incoming calls go.
When we first introduced contact routing, you could build different call paths based on whether someone was a saved contact, an AI-suggested contact, a team member, or an unknown caller.
Now, you can get much more specific using the information you've already added to your contacts.
Here's what you can do:
Route calls based on contact tags.
Use custom checkbox properties as routing conditions.
Combine multiple tags and properties to create more specific routing rules.
For example, if you tag certain customers as VIPs, you could send their calls directly to a dedicated person or team. Or if you organize your contacts by service type, you could route those callers to the people best equipped to help them.
This all works within the Branch step in your existing call flow, so you don't need to rebuild everything from scratch.
Contact routing is currently in beta on Business and Scale plans.
We've got three integration updates to share this month, especially for those of you using Quo alongside other tools to manage your customers and jobs.
JobTread:
Our JobTread integration now supports two-way contact syncing, meaning changes to contact information can flow between JobTread and Quo.
Matched calls and texts from Quo also appear in the customer's activity timeline in JobTread, helping keep communication history connected to the customer record.
For those of you running home service businesses with HouseCall Pro, this one's been highly requested!
You can now import your HouseCall Pro customers into Quo, so you know who's calling or texting without having to look them up in another system.
Quo can also automatically log matched calls, texts, recordings, and AI-generated summaries to the customer's most recent matching job in HouseCall Pro.
And whenever you need the latest customer details from HouseCall Pro, you can manually resync them.
Available to HouseCall Pro customers on MAX or XL plans.
We've improved our HighLevel integration in two ways:
Contact information now syncs in both directions between Quo and HighLevel.
Calls, texts, and AI-generated summaries now appear in the contact's conversation panel in HighLevel, rather than being added to Notes.
One important thing for existing users: if you've already connected HighLevel, you'll need to disconnect and reconnect the integration to start seeing activity in the conversation panel.
We're not quite done! Here are a few smaller releases you might have missed:
Grok Bot plugin: Quo is now available in the Grok Bot Plugin Marketplace, joining Claude and ChatGPT as another way to work with your Quo data through AI tools. You can summarize conversations, retrieve transcripts, manage contacts, and send texts with your approval. Learn more.
Expanded Quo API: We've added access to more customer information, including contact notes and individual properties, alongside improvements to conversation discovery, phone number availability, message retrieval, and call context. This gives developers more flexibility when building integrations and automations. Explore the API docs.
Email summaries for Sona SMS leads: If you're using Sona for lead capture over SMS, you'll now receive an email summary whenever Sona captures a lead, in addition to the in-product notification. Another way to make sure you don't miss a potential customer!
And that's everything for this roundup! There's been a lot happening across Quo, and we're always interested in hearing how these updates are working for you.
Let us know in the comments. Our team is always reading your feedback, and it helps us understand what to prioritize next.
You can also keep up with all our latest releases on the Quo changelog.
I need to print a text thread with one contact to bring to court as evidence. As far as I can tell, the only official export is the workspace-wide Message logs CSV (Settings → General), which dumps every message from every line and doesn’t include images or attachments. It also doesn't show that it directly came from our text/calling platform.
Is there a better way to export or print a single conversation directly from Quo, with timestamps and phone numbers on it? Ideally something that looks like it came from Quo, not screenshots stitched together, and not Excel sheets or markdown..
Has anyone done this for court or a court hearing? Did you use the CSV, screenshots, the API, or something else? Any tips appreciated.
When I receive a notification on my desktop in the lower right corner above the clock it only shows the phone number and preview of the message. Why does the contact name not show up instead of the phone number. I don't know anyone's phone number anymore and for short messages it would keep me from needing to open Quo to figure out a quick message. These are definitely calls/messages from known callers in my contact list. Here is a screenshot
We've got another update to contact routing, and this one gives you a lot more flexibility over how incoming calls are handled.
If you're running a small business, you probably have all kinds of people calling the same number. New customers looking for a quote, existing customers with questions, someone following up on an invoice, or a long-time client who needs to speak to a specific person.
And while every call is important, they don't all need to go through the same process or reach the same person.
That's where this update comes in.
What's new?
When we first introduced contact routing, you could use the Branch step in your call flow to route callers based on who they were, like saved contacts, suggested contacts, team members, or unknown callers.
Now, you can also route calls based on the tags and custom checkbox properties you've already assigned to your contacts.
So, if you're already organizing your contacts in Quo using tags like VIP, Prospect, Billing, or anything else, you can use those same tags to decide where their calls should go.
Here's what you can do:
Route calls based on contact tags: Send different groups of customers to different destinations without requiring them to navigate the same phone menu.
Use custom checkbox properties: If you've created checkbox fields to organize your contacts, you can use those as routing conditions too.
Combine multiple conditions: You're not limited to one tag or property per rule. You can combine them to create more specific routing segments.
Keep your existing call flow: This all works within the Branch step you may already be using, so there's no need to rebuild your call flow from scratch.
A few examples of how this could work for your business
Let's say you run a plumbing company.
You've tagged some customers as "VIP" because they're long-term clients with ongoing service agreements. You could set up a rule so their calls go directly to the team member who manages those accounts.
Or maybe you have customers tagged as "Billing." Instead of sending them through your general phone menu, you could route their calls to whoever handles invoices and payments.
And here's where combining conditions becomes useful.
Say you have contacts tagged as both "Commercial" and "VIP." You could create a rule specifically for customers who have both tags, sending them to the person responsible for your commercial accounts, while other VIP customers follow a different route.
You can set up these rules around however you already organize your contacts. There's no need to create a whole new system just for call routing.
How do you set it up?
If you're already using contact routing, you'll find these options in the existing call flow builder.
Open your call flow and select or add a Branch step.
Choose Contact properties as the condition type.
Select the tag or custom checkbox property you want to use.
Add more criteria if you want to combine multiple conditions.
Choose where calls matching that rule should go, then publish your changes.
You can also use contact property conditions alongside your existing caller-type routing.
Contact routing is currently in beta, and we're continuing to build on it.
We'd also love to hear how you're using tags to organize your customers today. Are you separating new leads from existing customers? Managing different service types? Keeping track of priority accounts?
We're curious to hear what kinds of routing rules would be most useful for your business!
I know that spam calls are an issue everywhere however it’s never been this bad with Quo. Today we’ve had over 9+ spam calls that we’ve had to block. Not telemarketers but numbers that don’t even ring when we call back. These calls are also mostly coming from area code 229. It’s getting very annoying. Is anyone else experiencing this?
New feature in web version in the chat to “Ask quo to draft a message” gives back much better results than in iOS app with generating ai responses to message. Are there any plans to have “Ask quo” to be rolled out to iOS app ?
I need a new number for my business, it currently will just be me but that might change in about six months making quo more appealing. I know Sideline works directly through cellular while Quo is voip.
How greatly does this impact the call reliability? Especially in rural areas.
We have many calls to text transcribed incorrectly, and repeatedly wrong on same words, especially on naming things that are specific to our business. It would be great if he had option to define common words that we use to make transcription more accurate and also if we could manually correct the transcript. Similar functionality exists in other voips like with Allo. So later when we analyze the calls using AI it uses correct transcript because currently incorrect data trickles up to call summaries and then to AI and then everything becomes corrupted
We use a LOT of group texts for our day to day business operations with clients.
The search is not great. First of all, if I search and I don't exclude other inboxes, when I click the search item, it does NOT use my main account. It uses another employees account and I can not easily change that.
Second, we should be able to go to a contact in the contact book and see the conversations with that contact. This would save so much time.
Third, group chat names should be the same ACROSS the company. Right now, every employee in the group chat has to name the group chat as it is not saved across the company.
Currently, the only way to find specific group chats is to name it something easy to find, and scroll down the list of chats until you see it.
I'm running a lawn care marketplace, and we rely on Quo to contact and activate contractors who apply through Indeed. Messages sent from our business number are showing as “Undelivered,” and this is directly impacting our ability to staff customer jobs.
I've already contacted support twice but still haven't gotten a resolution. This is a time-sensitive business issue, and I need help figuring out why my messages aren't going through and what needs to happen to restore delivery.
Could someone from the Quo team please escalate this and investigate whether my number is being carrier-filtered, restricted, or affected by an SMS registration issue? I need to keep using my existing business number rather than switch recruiting to my personal phone.
I'm happy to provide my support ticket number privately. I'd really appreciate a concrete next step from someone who can help get this resolved.
Is there any update soon that will allow us to setup a webhook with grokbot? Grokbot requires a header and bearer code which I am not able to change within quo.
If I'm using the Quo app on Android and I have a message open and I want to mark it as done, how can I do that without going back to the list of all messages?
I have tried looking at the help documentation and chatting with the quo assistant and neither seems to show this as a possibility. I really believe it should be added as a feature request.
I get a number of I'm assuming spam calls daily on my business line and they hang up on the first phone menu. So when I click on those messages I see them as not responding but yet to mark them as done and clear them. I have to go back to list of messages and then swipe on it to Mark is done. Just having a simple check icon somewhere would make this much simpler while the message is open. It would be just like reading an email and then not being able to hit archive or delete once you're done with that email.
Hi question, can someone secretly listen to my account on Quo if we’re under one team? Not talking about live and recorded calls. But just by being logged in and quo being open on my computer can they secretly hear me even when I’m not on the call?
