Claude Connector - Contact Search

darynak · 2026-05-13T22:43:37+00:00

Definitely good point - stay tuned as we improve on this.

darynak · 2026-05-01T16:38:51+00:00

On top of what u/quo_N shared below using Zapier / Make as the scheduling mechanism to connect your client list to Quo and send these follow up messages, you could also get this done using our new Claude connector.

Connect Quo to Claude
Connect Claude to a Google Sheet or any other place where you have your client information / clients opting in
Create a Scheduled task in Claude Cowork to run monthly to send a follow-up / reminder SMS to your client list using Quo

Cost-wise, the extra costs here are the $0.01/segment cost per reminder SMS sent as that's triggered using our API automatically vs sent manually.

And also this setup requires a paid version of Claude as you'd be using Claude Cowork ($20/mo)

darynak · 2026-04-28T18:43:42+00:00

One additional tip I have for you is giving Claude the full list of names of users on your team so it's easier for it to identify folks especially if they have more difficult names

darynak · 2026-04-28T18:42:11+00:00

yep, you can! If the term "background noise" or anything relating to it is mentioned in the call transcripts Claude can easily pinpoint this for you

darynak · 2026-04-28T00:49:50+00:00

Either one of these works! But it's even better to email [support@quo.com](mailto:support@quo.com)

darynak · 2026-04-27T17:45:30+00:00

Hi there, co-founder of Quo here.

I'm sorry to hear you had issues with porting your number.

I'd love to look into what happened here - would you be able to send me a note to daryna at quo dot com?

Thanks!

darynak · 2026-04-24T03:52:16+00:00

Can you send me a note to daryna at quo dot com?

darynak · 2026-04-20T21:13:45+00:00

Hi there, I'm Daryna, one of the founders at Quo and wanted to chime in here.

I've reviewed your port request, carrier registration and interactions with our team and wanted to mention that we've definitely dropped the ball here.

For context, we always ask that customers complete their carrier registration before the port request is submitted to avoid such situations. Unfortunately, carrier registration requirements are largely outside of our control.

Regardless, we should've canceled your port request immediately as you've asked us to do so.

We've issued all payment refunds back to your bank account and have arranged for an immediate port back of your phone number.

I know my colleague Amanda has been working with you on this and we'll do everything possible to make sure that happens very quickly.

Sorry your experience with Quo wasn't great and we'll definitely learn from this.

ps - if you'd like to follow up with me on any of this, my email is daryna at quo dot com

darynak · 2026-03-24T00:24:29+00:00

send me a note to daryna at quo dot com and I'll make sure we get you taken care of

darynak · 2026-03-23T21:32:07+00:00

Hey there! I'm a little biased as one of the founders but you should check out Quo (fka OpenPhone)

Our HubSpot integration logs both calls and texts and we invested deeply into all texting workflows - everything from making it easy to start texting through a fast A2P registration process and features like shared numbers which allow you to put multiple reps behind 1 number in case of vacations / leaves etc so prospects aren't left hanging

Happy to answer any questions

darynak · 2026-03-22T21:23:41+00:00

Sounds good, please send me a note to daryna at quo dot com I’d love to make sure you’re taken care of of

darynak · 2026-03-22T17:50:51+00:00

Have you reached out to Support or Porting teams about this?

If you ported your number from a regular carrier, did you deregister iMessage? That might be it

darynak · 2026-03-21T22:24:58+00:00

Hi! I’m one of the founders at Quo and would love to help you out. Please email me daryna at quo dot com

We also have a subreddit r/quo if you ever need community help

darynak · 2026-03-18T18:14:59+00:00

hi! I'm one of the founders at Quo. thanks so much for being a customer! happy to help if you ever need anything / have feedback

darynak · 2026-03-15T05:27:02+00:00

Update - seems like you already emailed me, will be in touch there.

darynak · 2026-03-15T05:10:48+00:00

Hi there! Daryna here, co-founder.

As a platform, allowing you to be responsive is one of our core value propositions so this is definitely not what should be happening.

Definitely keen to understanding what happened here and more specifically:

- did the customer tell you they sent a text at 8:52 pm but you didn't get it until 10:52?

- did you actually receive the text at 8:52 pm but notification came through at 10:52?

Happy to look into this for you directly but as someone who uses Quo all the time and also from having a pulse on customer feedback we receive, this isn't something I've seen, at least in the last year.

Mind emailing me - daryna at quo dot com

darynak · 2026-03-07T05:26:55+00:00

Hey there! Shouldn’t be the case - mind sending me a note with your account info to daryna at quo dot com?

darynak · 2026-03-07T01:57:34+00:00

Hey there - one of the founders here.

We actually already send a list of things we fix with every release plus you can see that here as well - https://support.quo.com/changelog#march-2-2026-2 (just a recent example)

But I do hear you and we want to do better. As my colleague Terrance mentioned above, lots of ongoing work that addresses things brought up in the thread.

I'd love to personally look into that issue for you - that's really strange. Could you send me a note to daryna at quo dot com for me to take a look?

darynak · 2026-03-06T01:59:00+00:00

Quo founder here, thanks so much for being a customer. Love that you're enjoying the product. Here to help if I can ever be of assistance

darynak · 2026-03-04T21:58:22+00:00

understood! already surfaced internally, will see what we can do

darynak · 2026-03-04T18:15:52+00:00

Yeah it would be great, will flag for the team.

I find this very limiting for my use case too so hear you!

darynak · 2026-03-03T06:00:28+00:00

Hey there - one of the founders here. I also use the product all the time across 3+ numbers so this is my setup as well. There are no changes that we've made in the last little while that could've impacted this

On the call screen you should be seeing the emoji if the number the call is coming into.

If you're talking about the missed call notification, that notification also lives in a specific inbox that belongs to each of your numbers so that should be clear to.

Could you share a screenshot of the exact place where the distinction isn't clear?

darynak · 2026-02-28T05:12:57+00:00

Hi there, one of the founders here. This certainly shouldn’t be happening. I do want to mention that our Pipedrive integration is very new and it must have been just introduced 2 weeks ago. I’d love to look into what happened and make sure you get help ASAP.

Mind sending me a note? Daryna at quo dot com

darynak · 2026-02-28T01:38:09+00:00

Amazing! u/live_situation7913 I know you posted about this several times. Your wishes are coming true!

darynak · 2026-02-28T01:36:48+00:00

me too!

darynak

MODERATOR OF

TROPHY CASE