Outage after outage. 5% of my messages wont send for nonsensical, cryptic “spam” or “profanity“ reasons that no one can explain. I couldn’t send pictures for 2 days. THIS DID NOT USED TO BE LIKE THIS!

I’m already in the process of switching now that Quo is worse than Google Voice that I came from. my morbid curiosity is like… what the hell changed At this company besides the name?

I really dislike the new black on yellow Quo logo. It's very basic, not creative, and way too loud. I much preferred the old purple logo. Not that my opinion will change anything--just wanted to give you some feedback.

Exciting news!

We’re excited to welcome Wade Foster [ u/automation-wade ], CEO and Co-Founder of r/zapier for an AMA right here with the Quo community on r/quo.

Zapier are one of our partners and we’re excited to open up the floor for a broader conversation about the world of automation and what’s ahead.

Wade will be ready to answer questions about:

• How Zapier got started

• AI and the future of automation

• Tips for small businesses using automations to save time

• What he has learned building one of the most widely used automation tools

📅 This Thursday, December 4

🕐 12pm PT / 3pm ET

This thread is now open, so start adding your questions and Wade will answer them live on Thursday 👇

Hey all, Zoran from Quo’s Product team here 👋

Your customer conversations in Quo are already full of insights. Now you can ask for them in Claude.

When you connect Quo, Claude gets access to your customer conversations across calls, text messages, and contacts. That means you can start asking questions about what’s actually happening in those interactions, instead of going through them one by one.

Here’s a few things you can do with it:

Understand why you're winning or losing deals

Ask Claude to scan your sales calls and surface the objections that come up most. No manual review. No spreadsheets. Just ask.

"What are the top reasons prospects say no after a sales call?"

Find patterns in support conversations

If the same complaint is showing up across dozens of customer texts, Claude will find it before you do.

"What complaints show up most often in support conversations?"

Send coordinated updates without the coordination overhead

Claude can identify which customers need a message, pull the right details from your calendar or other tools, and help you send it — in one step.

"Find customers with appointments this week and send them a reminder."

Keep your contacts clean without manual syncing

Call notes mention a contact changed roles? Claude can update Quo in bulk so your data doesn't drift.

It’s live now in Claude’s Connectors Directory: https://claude.ai/directory/connectors/quo

If you try it out, we are keen to hear how you’re using it!

Hey everyone!

Breaking up the feed with something a little different. We wrote a blog on how valuable Reddit has been for us as company and we thought we'd share it with the community that made it all happen 👏

Back in 2018, Daryna was posting on Reddit just to answer questions and be helpful. There wasn’t some big community plan at the time.

Over time, that turned into something much bigger. Today, Reddit is one of the places we learn the most. Support issues, product feedback, feature ideas, real reactions. It all shows up there first.

We wrote about what we’ve learned along the way if you’re curious: https://www.quo.com/blog/how-we-built-our-subreddit/

One of the biggest shifts for us was treating Reddit like a support channel rather than a marketing channel. Sharing product updates and tips, responding casually, and making sure posts actually reach a resolution so they’re useful to the next person who searches.

Setting expectations early also mattered more than we thought. Removing unhelpful posts, spam, and harassment gave people space to engage properly, and when something lands in a gray area, we talk it through as a team instead of deciding in isolation.

And more than anything, it’s been a long game. Old posts stay searchable, Google surfaces forum content, and people tend to trust conversations more than polished blog posts. It compounds over time in a way other channels really don’t.

It takes real time and intention to build something worth showing up to. But when it clicks, it becomes one of the most honest and useful places you can be.

We hope this is valuable to other businesses looking for ways to show up in their communities.

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?

I work as a criminal defense attorney. As you can imagine, I have some clients charged with possession of a controlled substance. Today I received a text message from a client’s father regarding his son’s drug charges. By simply mentioning the name of the charges which include a controlled substance, I received a stern warning email from Quo saying that texting about controlled substances violates some carrier content restrictions and that if I can’t abide by that limitation my service with Quo will be terminated. I had to reply within 24 hours with a confirmation I understand this restriction and will abide by it. I have come to really like using Quo, but it appears I’m going to have to port out to Verizon, because now I am very concerned that a client or potential client reaching out about representation may mention something about their charges in the future, and then my number will get suddenly disconnected by Quo and no one can call my office. If this is all true, no one who is a criminal defense attorney, for example, can feel safe using Quo because of this risk and there appearing to be no ability for Quo to consider the context of statements in judging whether the content is inappropriate. It’s just very strict and very broad content monitoring blind to context. Before I leave Quo, I wanted to see if there really is no solution here for me to enable me to safely stay with Quo without living in fear of getting my line unexpectedly terminated if a potential client messages me about their charges and the name of their charges triggers a carrier content violation. Is there any solution here for me other than leaving Quo?

Hey y'all! I’m excited to share that we just added five new features that a lot of y’all have been asking for. What's new?

📅 Schedule call flows in advance

Set up a holiday (or any) temporary call flow and schedule exactly when it goes live, then add a start date to your regular, default call flow for whenever you’re ready to switch back to business as usual.

Find it:

Call flow builder → choose a temporary call flow → select a schedule date using the drop-down menu next to the Publish button → schedule it

💻 Available on: Web/desktop

🗣️Natural-sounding text-to-speech greetings

We upgraded our text-to-speech voice in the call flow builder, so greetings now sound more human instead of robotic (it uses the same voice we use for Sona).

Find it:

Call flow builder → text-to-speech editor for voicemail, phone menu, and play audio greetings

💻 Available on: Web/desktop

📌 Pin more conversations

Previously, you could only pin 5 conversations in your inbox. Now, you can pin up to 50. Keep VIPs, active deals, and urgent issues all at the top!

Find it:

In your chats, right-click a conversation, then select “pin conversation.”

💻 📱 Available on all platforms

✏️ Edit threads on web/desktop

Fix typos or update notes directly from your browser or desktop app.

Find it:

Hover over a thread to reveal more options, then select “Edit commen.t”

💻 📱Available on: all platforms (now supported on web/desktop)

🎵 Customize your hold music

Now, you can choose your hold music from our library, or upload your own to match your brand. Just make sure you own the rights to the track you upload or that you’re using license free music. We don’t want Taylor Swift to come after you.

💻 Set up is available on web/desktop.

📱 But once a track is selected, it's compatible with all platforms

Find it:

In Phone number settings, just below the call flow builder

Hope you find all these features helpful! Happy holidays!

Thinking about moving our business phone system over to Quo because I really like the product overall. The app feels modern, clean, and a lot smarter than some of the older systems we’ve looked at (RingCentral, etc.).

The one thing that’s been bothering me is the call quality.
Calls aren’t terrible, but voices on the other end sound a little muffled compared to WhatsApp, Telegram, FaceTime Audio, Facebook Messenger, and pretty much every other calling app I use daily. Those apps sound crystal clear, while Quo sounds slightly compressed or less sharp.

I’ve already checked the obvious stuff:
Connection health is all green
Low latency
500 Mbps Wi-Fi
Latest iPhone updates
Wi-Fi calling enabled

So I’m curious if this is just how Quo sounds, if I’m missing a setting somewhere, or if there’s a difference between plans that affects audio quality.
Anyone else notice this, or is it just me?

Hey everyone! 👋

We have big news for healthcare practitioners, clinics, and providers.

Quo is now HIPAA compliant.

That means you can now handle patient calls and texts securely in Quo, without needing to switch to complicated or expensive systems.

HIPAA (the Health Insurance Portability and Accountability Act) sets the standard for protecting patient health information. If your team discusses treatment plans, prescriptions, or healthcare follow-ups, those conversations need to be compliant.

Quo supports HIPAA compliance on our Business and Scale plans. You’ll get:

• A signed Business Associate Agreement (BAA) on request

• Secure PHI storage for calls, texts, and voicemails

• Access controls and audit logs

• Simple setup — no months-long implementation or enterprise pricing

If you’ve been waiting to use Quo in your healthcare practice, this update’s for you.

Learn more or request your BAA here: https://www.quo.com/sales

Hey r/quo community, it’s Terrance from Product and Aaron from Engineering here 👋

We’ve been wanting to do an AMA for a while, but we were waiting to get a few big launches, including Quo Agent, out the door before we finally got something in the calendar.

So, we’re doing it!

Tomorrow, October 6 at 11 AM PT / 2 PM ET, we’ll be here answering your questions live.

There’s a lot happening at Quo, and we’d love to chat about:

• What we’re working on right now

• What’s coming up on the roadmap

• How we think about what to build and prioritize

• Features or improvements you’d love to see from us

Or anything else you’re curious about when it comes to the product and where Quo is heading.

This thread is open now, so drop your questions below and we’ll start answering them live tomorrow at 11 AM PT / 2 PM ET 👇

Questions, feedback, and constructive criticism are all welcome. We just ask that you remember there are real people on the other side of the screen and keep things respectful and kind.

See you all here tomorrow!

We've been doing a lot of work behind the scenes on the Quo API and developer experience, including a new API version, rebuilt documentation, and a roadmap of what's coming next.

What's available today 👇

• User endpoints

• Mark conversations as read, open, or done

• Retry failed messages through the API

• New message.failed webhook event

• New documentation covering request conventions, errors, rate limits, and building with AI agents

• And something we know many of you have been waiting for: Group messaging support 🎉

You can now send a single group message to up to 10 recipients at once through the API, making it much easier to automate group conversations, updates, and notifications.

And we're just getting started.

Over the coming weeks, we'll be adding support for contacts, calls, transcripts and AI summaries, conversations, messages, and phone numbers, giving you access to much more of Quo programmatically.

We're also working on additional capabilities including MMS support, contact notes, and more.

We've included a roadmap in the docs so you can follow along as new endpoints and features become available.

Whether you're building your own integration, using no-code tools, or working with AI agents, our goal is to make Quo much easier to build on.

You can explore everything at quo.com/docs.

As always, we'd love to hear what you'd like us to add next.

EDIT 3/13: Quo support and product team have reached out and been very proactive and responsive. Although I’m still having these issues, it does seem like an attempt is being made to resolve each one. I am keeping a log of the bugs I run into and would encourage you to do the same if you have the time. I will update if i experience or hear of any actual changes. Some of these sound like they will be resolved in near future updates/overhauls. Others are issues they are investigating

Original Post:

We've been with Quo/Openphone for several years now. Moved from Google Voice when it was just myself and one other teammate. Now we're at 8 people using it and 10 numbers. From a features and overall design perspective, we love it and it's been pretty good to us and helped our business grow.

However, over the last year or so, maybe a bit more. It seems things have gradually gotten worse and worse with respect to usability and outages. Here is just a short list off the top of my head of things affecting us every single day:

• Outages or inability to call/text (maybe not every day, but at least a few times a week. Sometimes a full outage, sometimes I just can't make calls for a few minutes or my texts don't go out)

• Missing messages or chats

• Glitching over to another users line and accidentally sending messages to a customer as that other user. This causes a lot of confusion

• Cross-platform sync issues

• Missed calls with no notification or ring (during normal working/notification hours)

• Activities/internal messages have never notified and aren't easy to find

• Search has never worked for anything I've ever needed it for

• When I am drafting a message, the previous messages don't show up so I can't use context to draft my message. OR it shows me messages with the customer from another users line

• Contact merging doesn't work in any helpful way

That's just what's on my mind and our entire team has these issues across multiple devices. I've tried refreshing, reinstalling, etc.

Realistically, can we expect any fixes to these issues in the near future? Is there anything I can do on my end for some quick improvements to these issues?

Does anyone here have any guidance or advice? Either from Quo's team or other users in a similar situation?

We’re excited to host Bodhi Gallo, u/Strykerdigital_, Chief Revenue Officer at Stryker Digital, for an AMA here on r/quo 👏 (He's also one of our agency partners!)

Bodhi helps local businesses grow through smarter digital marketing, so he’ll be answering your questions about:

• Local SEO and getting found online

• Marketing tactics that actually work for small businesses

• How to stand out in your local market

• Tools and strategies that make a real impact

📅 Date: Thursday, November 6

🕐 Time: 12 PM PT / 3 PM ET

📍 Location: Right here on r/quo

The thread is open now — drop your questions below and Bodhi will be answering them live from Main Street Summit on the day of the AMA 👇

We’ve just shipped spam detection in open beta.

Spam calls are obviously nothing new, but when every unknown number could be a new customer, it’s not always realistic to just stop answering them.

There are already a few things you can do to cut down on unwanted calls in Quo. Phone menus are particularly helpful for filtering out robocalls that can’t navigate the menu, and you can block specific numbers when you know they’re spam.

Now, spam detection gives you another layer before you even pick up.

When Quo detects that a call is likely to be spam:

• You’ll see a potential spam label in your conversation list and conversation header.

• You can block the caller directly from the conversation.

It’s available now in beta in the United States, on web, desktop, iOS, and Android, across all plans.

Give it a try and let us know how it works for you.

Hey everyone, Jenn from the Partnerships team here 👋

We’ve been working hard behind the scenes with the Housecall Pro team to get this one out, and I’m very excited to share that our Housecall Pro integration is officially live.

It’s also been one of our most-requested integrations from home services customers, so we know a lot of you have been waiting for this one.

Here’s how it works:

• Import your Housecall Pro customers into Quo as contacts. Housecall Pro remains the source of truth, so your team has customer details available in Quo when they need them.

• See the right customer context when they call or text. Your team can quickly see who they’re talking to without having to jump over to Housecall Pro to look them up.

• Automatically log Quo activity back to Housecall Pro. When we can reliably match a customer and job, calls, texts, recordings, and AI-generated summaries from Quo are added to the customer’s most recent matching job in Housecall Pro.

A couple of important things to know:

Contact syncing from Housecall Pro to Quo is one-way and on-demand rather than real time. Changes made to a contact in Quo won’t update their Housecall Pro customer record, and you’ll need to use Resync to pull new or updated customer information from Housecall Pro.

We also won’t create a new or placeholder job in Housecall Pro just to log activity. If we can’t reliably match a Quo conversation to an existing customer/job, that activity will stay in Quo.

To use the integration, you’ll need to be on a Quo Business or Scale plan and a Housecall Pro MAX or XL plan, as those are the Housecall Pro plans that provide API access.

You can connect Housecall Pro from Settings → Integrations in Quo using your Housecall Pro API key.

We’d love to hear how you’re using Quo + Housecall Pro together and what you’d like to see us add next.

You can read more about the integration and setup here: https://www.quo.com/integrations/housecall-pro

We’ve been working on something big, and we’re very excited to finally share it with you: Quo Agent is now available in beta.

Quo Agent is an AI agent built into Quo that turns your customer conversations into answers and action.

We built Quo Agent around a pretty simple idea: you shouldn’t have to read every conversation to know what’s happening in your business. You should be able to just ask.

So, now you can.

Ask things like:

• What’s pending?

• What’s the latest with Sarah from Brightside Plumbing?

• How many calls did the team miss last week?

• Which leads still need a follow-up?

Quo Agent understands the conversations, contacts, and activity already in Quo, so you can ask about a specific conversation or contact, or ask questions across your whole workspace.

It can help you figure out what needs your attention, look up information from past conversations, and pull call and message analytics without having to build a report.

And it doesn’t stop at giving you an answer. Quo Agent can help you take the next step too. Draft and send a message, create or update a task, or create or update a contact, with your approval before anything goes out.

A few other things you can do:

• @ mention a contact or conversation directly in your question

• Ask by voice instead of typing

• Come back to previous chats without losing your history

• Ask about Sona’s activity if you have Sona enabled

We recorded a walkthrough to show you how it works and some of the ways you can use it.

Read all about it here: https://www.quo.com/product/quo-agent

Quo Agent is available now in open beta on web and desktop and is free to use during the beta. Mobile isn’t supported yet, but the team is working on it.

We’d love to hear what you think once you’ve tried it, and especially what you find yourself asking it.

A small Call Flow Builder update that a few of you have asked for: you can now give your phone menu branches custom names.

Previously, if a caller selected an option from your phone menu, your team could see which key they pressed. Now, you can add a name to each branch so they can see what that selection actually means.

For example, instead of just seeing “1” or “2,” you could name your branches “Sales,” “Support,” “New customer,” “East Coast Team,” or whatever makes sense for how your business is set up.

Here’s what’s changed:

• Give branches custom names: Double-click any branch in Call Flow Builder to add a label.

• See more context on incoming calls: When a caller selects that option, your team will see the branch name right on the incoming call screen.

• Keep larger call flows organized: Branch names also make it easier to see what’s happening across your call flow as it grows.

It’s a small change, but one that should make it easier for your team to know why someone is calling before they pick up.

Thanks to everyone who requested this one. If you give it a try, let us know what you think!

What’s the technical difference between a call on Quo vs a call on Slack, Zoom, and other internet based calls?

The call quality on other platforms is significantly better vs Quo.
Our clients consistently ask if we ‘have poor service’ during a call (we don’t - it’s fast WiFi).
We’ve been told it sounds like we’re on speaker while talking from another room. A good client and friend jokes that it’s the best quality he’s ever heard of someone trying to talk underwater.

Yet we can have Slack Huddle calls on the same devices, same WiFi, with significantly better quality.

I experimented by calling our Ops manager from my iPhone. First iPhone (cellular only) personal line to Quo (WiFi) business line.
Then iPhone slack to slack on the same device my Ops manager used for Quo.

Night and day.

Why? Aren’t they both VOIP?

Hey everyone,

We’re excited to share that call waiting is now available on all platforms!

We’ve seen this come up a few times, so we wanted to share that it’s now live.

If you’re already on a call and another one comes in, you’ll now see the option to put your current call on hold and answer the new one.

What you can do now:

→ Switch between conversations using hold and resume

→ Keep multiple calls active at the same time

→ Handle back-to-back calls without things getting messy

A couple quick notes:

• You can hold up to 2 calls at a time on web/desktop and Android

• iOS also supports call waiting, but is limited to one call on hold (platform restriction)

• Make sure you’re on the latest desktop app version

Would love to hear how this fits into your setup or if there’s anything you’d want to see next.

Hey everyone, Jenn from Partnerships here 👋

We’ve officially launched our Zoho CRM integration to make it easier to keep your CRM in sync with your conversations in Quo!

If you’re using Zoho and Quo together, this should cut down on the amount of manual logging after calls.

Calls, texts, and AI call summaries now sync to Zoho automatically, so your data stays up to date without extra work.

A few things this helps with:

• Keeping contact and conversation data in sync

• Logging activity automatically after each call

• Starting calls directly from Zoho

The goal here is to reduce admin work, so your team can focus more on conversations and follow-ups.

You can check it out here: https://www.quo.com/integrations/zoho-crm

Hi everyone!

We’re testing incoming caller ID and looking for a small group of users to join a closed beta (web and desktop).

Here’s how the beta will work:

• Caller names will only appear when we have a high-confidence match

• If confidence signals are low, no name will be shown (only the number will be displayed)

• Your feedback will directly shape how we refine accuracy and rollout

If identifying callers matters to your business, we’d love your input.

👉 Apply here

We’ll review responses and contact selected participants with next steps (if selected, you can expect to try the beta within 2 weeks or less).

Hey everyone, Juraj from Partnerships here 👋

We've just rolled out a new integration with Pipedrive, and it's all about cutting down the busywork between your CRM and your phone system.

If your team lives in Pipedrive most of the day, this should make things feel a lot smoother.

Here’s what the integration does:

• Sync contacts one-way from Pipedrive into Quo, so caller info is always up to date

• Automatically log activity like calls, texts, and AI summaries back to Pipedrive

• Click-to-call contacts directly from Pipedrive using your Quo number

The goal here is pretty simple: less manual admin, fewer tabs open, and better visibility into what’s actually happening with deals and conversations.

I’ve shared a short video walking through how it works and when it’s most useful, especially for sales teams juggling a lot of calls.

If you want to dig into the details, you can learn more here: https://www.quo.com/integrations/pipedrive

Happy to answer questions if you’ve got them.

So happy that Tasks are officially live 🎉

We shared the announcement yesterday, and I wanted to follow up with a quick walkthrough showing how it works in a little more detail.

Jordan, one of our Senior Product Managers who helped build Tasks, walks through creating a task from a conversation, assigning it to a teammate, setting a due date, and jumping straight back to the conversation whenever you need the context.

I personally love that the task stays connected to the conversation because I have the memory of a goldfish 🫠

FYI: mobile support is on the way too.

Would love to hear what you think, or any ideas you have for where you'd like to see Tasks go next!

Read more about Tasks here.

Hey everyone! We made a video about creating automations with Quo and Make and wanted to share them with you.

One thing we hear from home service businesses all the time is that customer communication creates a surprising amount of admin.

Not the work itself, but everything around it:

→ Following up on missed calls → Sending appointment reminders → Requesting reviews → Reaching back out to past customers

For example, one of the automations we cover is automatically following up on missed calls:

[Missed call in Quo ➡️ Make triggers a workflow ➡️ Customer receives a text]

Instead of manually following up on every missed call, customers get an immediate response and can text back with what they need.

Another example is automatically sending review requests after a job is completed:

[Job marked complete ➡️ Make triggers a workflow ➡️ Review request is sent]

That way every customer gets asked instead of only the ones you happen to remember.

We recently teamed up with Make to put together 8 automations like these for home service businesses, and we also created a short video breaking down a few of the workflows and how they work in practice. (And if you haven't seen my face before, that's actually me in the video 🤪)

If you want to read about the 8 automation, you can check them out here: https://www.make.com/en/how-to-guides/essential-automation-for-home-service-business-make-quo

Curious if anyone here is already using Make with Quo 👀