Self Serve Support Tickets

Need help with something in UserGems? You can create a support ticket directly from anywhere in the app, no email required. Tickets go straight to our support team, and every reply lands in your inbox so you can follow the conversation without logging back in.

Use this when something is broken or you suspect a bug. For strategy or program questions, your CSM is the better path (more on that at the bottom).

Where to find it

Click the support button (the ? icon) in the top right of any UserGems screen, then click Create Ticket.

Creating a ticket

The ticket form walks you through a handful of fields. The more detail you give up front, the faster we can diagnose and the less back-and-forth you'll deal with.

πŸ“ Any field marked with a * is required β€” you'll need to fill it in before the ticket will submit.

πŸ’‘ Tip: Take your screenshots before you start the ticket so they're ready to upload when you get to the Attachments field.

  1. Customer Email β€” Pre-filled with your email. All support replies go here, so double-check it's right.
  2. Summary β€” A short, descriptive one-liner for the issue or error you're seeing. Think subject line, not paragraph.
  3. Detailed Description β€” The heart of the ticket. Cover what's happening vs. what you believe should be happening, the impact (who/what it's affecting), and key details that help us find it fast: audience/campaign names, impacted signals, report IDs, prospect names and emails.
  4. Steps to Reproduce β€” List the exact steps our team can take to see the issue ourselves. Even rough steps beat none.
  5. Loom Link β€” If you can, record a quick Loom and drop the link here. Seeing the issue live is one of the fastest ways to cut down on confirmation back-and-forth.
  6. Product Component β€” Select the component most closely tied to the issue (e.g., Workflows, Signals). Pick the closest match if it's not obvious.
  7. Priority β€” Choose the level that matches the real-world impact. See the breakdown below.
  8. Attachments β€” Upload your screenshots here. These are hugely helpful for quick, accurate diagnosis. Drag and drop, or click to upload.

Picking the right priority

Priority Use it when… Example
Urgent Something is broken and it's impacting multiple audiences or campaigns Several campaigns didn't run when they should have
High Something is broken, but the impact is more contained One campaign didn't run, or you can't access certain pages in-app
Medium Something seems off, but you're not sure what Audience volume looks wrong, or campaigns didn't seem to fully run
Timely, but not urgent Things are functioning, just not fully to expectation. Most tickets belong here. Small impact, everything's still running

What happens after you submit

Once you submit, you'll see a confirmation screen letting you know the ticket went through, and you'll get a confirmation email as well.

A few things to know:

  • All support replies go to your email. You don't need to log back into the app to keep the conversation going.
  • Reply to the email directly to update your ticket. Your response threads right back into the ticket.
  • Expect a first response within 24–48 hours, depending on the scope and impact of the request. We prioritize based on impact.

When to open a ticket vs. contact your CSM

Tickets are for things that are broken or buggy. Strategy, structure, and "how should I set this up" questions are better handled by your CSM, who knows your program.

✅ Open a support ticket for… 💬 Go to your CSM for…
Something is broken or throwing an error How to structure a campaign or audience
You suspect a bug Strategy and best-practice questions
A campaign didn't run when it should have Whether a signal or workflow is the right fit for your goals
Data looks wrong (audience volume, missing records) Program planning and rollout decisions
You can't access pages or features in-app Questions about results, benchmarks, or optimization
An integration or sync isn't behaving as expected Requests to change how your program is set up
πŸ“ Not sure which bucket you're in? If something used to work and now doesn't, that's a ticket. If you're asking how something should work for your goals, that's your CSM.

‍

Was this article helpful?