Technical Support Representative

Small businesses represent 99.9% of all companies, yet they're still forced to choose between clunky, outdated enterprise phone systems or their personal phones. This multi-billion dollar market has been overlooked for decades, left to cobble together solutions that slow them down instead of helping them grow.

Quo is changing that. We bring calls, texts, and customer information together into one easy-to-use, AI-powered platform. We're not just building a phone system. We're setting a new standard for how businesses connect with their customers.

Driven by our values, we move fast, build with determination, and obsess over delivering value to the businesses that have been underserved for far too long.

Today, Quo is trusted by more than 120,000 companies and rated #1 in customer satisfaction on G2. We're backed by Y Combinator, Tiger Global, Craft Ventures, Slow Ventures, and other top-tier investors. It's safe to say we're onto something big.

About the role

Do you love figuring out why something isn't working?

At Quo, Technical Support goes deeper than answering product questions. Our customers connect Quo to the other tools they run their businesses on, and when something breaks, the answer is not always sitting in a settings menu.

You might be investigating why an API request is returning an error, why a webhook is not reaching its destination, why an integration is syncing some records but not others, or why calls behave differently for one user, device, or network.

We're looking for someone who is curious, methodical, and comfortable following a problem across multiple systems until they understand where it is actually breaking.

As a Technical Support Representative, you'll work directly with customers across email, live chat, phone, and text to troubleshoot complex product and technical issues. You'll investigate problems, gather the right evidence, test hypotheses, and resolve what you can independently. When an issue requires Engineering, you'll make sure the escalation is clear, reproducible, and actionable.

You'll also help us identify patterns in customer issues and turn what you're learning into better documentation, tooling, processes, and product experiences.

Some of the things you’ll do:

• Troubleshoot complex customer issues across Quo's web, desktop, and mobile experiences, including calling, messaging, account configuration, integrations, and connected systems.

• Investigate API and integration issues involving REST APIs, authentication, request and response payloads, HTTP status codes, permissions, configuration, and data syncing.

• Troubleshoot webhooks and event driven workflows by validating configuration, reviewing event payloads and delivery behavior, and isolating where a workflow is breaking between systems.

• Diagnose issues across multiple layers of a customer environment, including Quo configuration, third party applications, devices, browsers, networks, and carrier or telephony behavior.

• Gather logs, timestamps, request details, account configuration, reproduction steps, and other diagnostic information needed to investigate and resolve technical issues.

• Test hypotheses systematically rather than relying on guesswork, and clearly explain both the problem and the resolution to customers with different levels of technical experience.

• Recognize when an issue requires escalation and provide Engineering with a concise, reproducible report that includes impact, evidence, troubleshooting completed, and expected versus actual behavior.

• Partner with Engineering, Product, and CX Operations to identify recurring defects, confusing product behavior, integration gaps, and opportunities to improve the customer experience.

• Identify patterns across support cases and improve internal troubleshooting guides, documentation, workflows, and tooling.

• Maintain clear ownership of customer issues to the point of resolution through each of your responses, including setting expectations and communicating progress when an investigation spans multiple teams or points of contact.

About you

• Technical troubleshooting experience: You have 1 to 3 years of experience in technical support, SaaS support, implementation support, or another customer facing technical role where you were responsible for diagnosing issues rather than simply following predefined scripts.

• Systems thinking: You are comfortable troubleshooting problems that involve more than one application or service. You naturally think about where data originates, where it is supposed to go, and what could interrupt that flow.

• API fundamentals: You understand the basics of REST APIs, HTTP methods and status codes, authentication, endpoints, parameters, and JSON requests and responses. You do not need to be a software engineer, but an API error should feel like something to investigate rather than something to immediately escalate.

• Integration knowledge: You understand common concepts behind SaaS integrations, webhooks, permissions, field or contact syncing, and event driven workflows. Experience troubleshooting CRM or automation platforms such as HubSpot, Salesforce, Zapier, or similar tools is a plus.

• Diagnostic thinking: You know how to turn an unclear report into a testable problem. You ask targeted questions, gather evidence, isolate variables, and work through likely causes in a deliberate order.

• Technical communication: You can explain technical concepts clearly to customers without overwhelming them, while providing enough detail for technical customers to understand what is happening. You’re also able to connect events that transpire to engineering language for quick remediation.

• Resourcefulness: You are comfortable using documentation, internal tools, logs, testing environments, and teammates to find answers when the solution is not immediately obvious.

• Ownership and judgment: You know when to keep investigating, when to escalate, and what information another team will need to continue the investigation without starting over.

• Customer empathy: You understand that a technical problem usually has a business impact behind it. You acknowledge that impact, communicate clearly, and keep the customer informed while you work toward resolution.

• Adaptability: You enjoy working in a fast moving environment where products, tooling, and processes continue to evolve.

• Schedule flexibility: We're flexible on your time zone within North America, but most roles start around 7 to 9 AM Pacific and run for approximately eight hours. We're looking for someone who is open to working weekends depending on the needs of the team.

Nice to have:

Experience with any of the following is helpful, though we don't expect candidates to know everything on day one:

• API testing tools such as Postman

• Reading and interpreting JSON, APIs, webhooks or event driven integrations

• CRM integrations, particularly HubSpot or Salesforce and Jobber

• VoIP, telecommunications, or network troubleshooting

• Log investigation and bug reproduction

• Writing technical documentation or Engineering escalations

Who we are

We're a remote-first company with a culture of trust, autonomy, and action. As we rapidly grow, we're intentionally building communities in a handful of hub cities while continuing to hire great talent wherever they happen to live. If you're looking for a place to do your best work, we'd love to hear from you.

And remember, there's no such thing as a 'perfect' candidate. We're looking for optimists with grit and determination, who are excited to face the challenges of a growing startup. Quo is the type of company where you can grow, and we encourage you to apply for this role even if you don't think you meet all the requirements.

We are committed to creating an inclusive and diverse work environment. It is important that you are able to bring your authentic self to work every day. We do not discriminate on the basis of race, religion, color, national origin, gender, sexual orientation, age, marital status, veteran status, or disability status. #LI-Remote #PostLI