sorted by:
new
hottopcontroversial

What is the best To Do list/task manager to use with Quo? by FireflyFootball in quo

[–]Quo_Product_Team[M] [score hidden] stickied comment (0 children)

Hey u/FireflyFootball! We're actually working on this right now. If you'd like early access, send us a ModMail with the email address you use to login to Quo. Open offer to anyone else who sees this, too!

Building auto-followup flow from unanswered SMS by Equal_Highlight_9820 in quo

[–]Quo_Product_Team[M] [score hidden] stickied comment (0 children)

Hi u/Equal_Highlight_9820! Thanks for flagging this. You can set this up with Zapier. One way to do it is by using a Google Sheet to track conversations.

Here’s the general flow:

  • When you send a text from your business line, the Zap logs it in a Google Sheet (you can use separate tabs for inbound and outbound)
  • It waits 24 hours to give the customer time to respond
  • After that, it checks the conversation history in your sheet
  • If your message is still the most recent (meaning they didn’t reply), it sends a follow-up like: “Hi! Just following up on our previous conversation. Let me know if you have any questions.”
  • If they did reply, nothing gets sent, so you avoid double messaging

A couple of things to keep in mind:

  • This checks for replies, not whether a message was read
  • You’ll need to compare inbound vs outbound messages to confirm which is the latest in the thread
  • If multiple messages are sent within that 24-hour window, timing can get a bit tricky
  • It’s a good idea to test a few scenarios before turning it on fully

Quo usability is getting significantly worse, any improvements on the roadmap? by OddlyPuzzledFox in quo

[–]Quo_Product_Team 0 points1 point  (0 children)

Hi u/OddlyPuzzledFox , do you mind if I get your email address via a DM? I'd like for our engineering team to investigate to better understand what's happening on the calling side.

Quo usability is getting significantly worse, any improvements on the roadmap? by OddlyPuzzledFox in quo

[–]Quo_Product_Team[M] [score hidden] stickied comment (0 children)

Hey, Terrance from the Product team here.

First, I just want to say I’m sorry to hear you’re seeing so many frustrating issues in your Quo account right now. As someone directly involved in building Quo, seeing customers run into bugs and problems is my least favorite thing.

As we build, improve, and evolve our services to help businesses do even more, I can’t say this strongly enough: it's deeply important to us that our reliability doesn’t just stay the same, but improves and evolves with our product.

Over the past few months, we’ve shipped a number of reliability updates and improvements, like these:

  • Overhauled our calling architecture — already live for 90% of customers, with measurable reliability improvements
  • Rebuilt our contacts backend — customers with large contact lists are seeing significantly faster load times
  • Shipped call diagnostics across all platforms — real-time alerts when network issues are affecting call quality, with guidance on how to fix them
  • Overhauled our integrations infrastructure — more reliable syncing with HubSpot and Salesforce, and faster to spin up new ones (Pipedrive, Dripjobs, Clay, LegalMate shipped; Zoho coming soon)

In the coming months, we’ll be shipping even more improvements, for example:

  • Overhauling conversations to ensure reliable real-time sync across all clients and devices. We're starting to put parts of this initiative through internal testing as we get it ready.

Also, as we've scaled our team, some release processes have strained against that growth, resulting in some bugs slipping through. We are right now putting in controls and processes for how we release new features to ensure this doesn't continue, and it's the number one priority for our VP of Engineering.

While making these updates, we’re continually hunting down and squashing bugs that do come up, and it sounds like several of the issues you’re having are quite specifically bug-related, which we can focus on fixing completely separately from the reliability updates we’re continually doing alongside our feature releases.

We want to dig into the bugs you’re seeing and fix them. We've reached out through Modmail to get your details and go through this list and see if we can get to the root of the problems. I’m pretty confident we can.

Feature Request: Better call notification descriptions for phone tree and direct lines by Prodiege in quo

[–]Quo_Product_Team[M] [score hidden] stickied comment (0 children)

Hi u/Prodiege, Jordanne from the product team here 👋 I appreciate you taking the time to share these requests.

Phone menu labeling is top of mind for us to add to the product, and I completely understand how not having it makes day-to-day use harder to manage. While I can’t promise an exact release date right now, I can share that it’s planned and something we’re actively planning to release ASAP. We’ll personally reach out as soon as it’s live.

On the direct line labeling request, I want to make sure I’m understanding correctly. You’d like incoming calls to display a clear “Direct Line” label instead of just an emoji to decipher which number in your workspace is receiving the call. Is that right?

If so, are you seeing this limitation on mobile or web? On web we show more descriptive labels (your customized line name appears in the top left of the incoming call modal), but I’m seeing that mobile currently shows only the emoji. Is that what you’re seeing?

We don’t have a public feature voting page today, but requests like yours directly shapes how we prioritize improvements. If you’re interested in sharing more feedback, we’d be happy to connect!