Gem-E Content Setup Examples
This guide provides real-world examples of how to structure each content type in Gem-E. For detailed instructions on how to set up content, see the Gem-E Content Setup Guide.
Each example below shows the complete structure including filters, content, and instructions to help you understand best practices for your own content setup.
Sample Emails Examples
Example: Post-Event Attendee Sample Emails
Sample Emails:
Email 1:
Subject: Coffee's on us
Hi [First Name],
Thanks for stopping by the UserGems booth at [Event]!
Post-conference weeks hit hard, here's a coffee on us to power through:
[Link to event attendee gift card hyperlink with "Coffee on Us"]
Hope you got some good takeaways!
Cheers, [your name]
PS: X and Y evaluated us last year so it might be worth getting their thoughts on UG :)
Email 2:
Subject: Re: Coffee on us
Hey [First Name],
Don't forget to grab your cup of Joe.
To jog your memory in the sea of [Event] booths our lounge had the [Event details]
By the way, did you have a chance to chat with X or Y about their thoughts?
Cheers, [Your Name]
PS: So-and-so was a UserGems customer at their last company, [Co-Workers last company], might be worth asking for their thoughts too
Email 3:
Subject: AI Command Center
Hi [First Name],
We work with folks in your space like [Customer Competitor] so thought [Company] could see real value too.
Since you're [Role] I imagine [Pain]
If you're open to checking out how UserGems can work as your GTM command center - here's our calendar link [hyperlink AE calendar link]
—[Your Name]
PS: X and Y evaluated UG last year, could be helpful to hear their take
Filter: Event Signal
Instructions:
Use the sample emails provided to influence the tone, structure, and style of the emails you write to this prospect. Do not copy any of the content within the sample emails - instead use it to help craft emails that sound 'on brand' from our company.
AI Summary (Button): Enabled (aka: click the "summarize" button to have AI analyze the emails and summarize the writing style – this means Gem-E is not using the specific content inside!)
Case Studies Examples
Example: Mixpanel Case Study
Case Study (Content/Summary):
Case Study Title: How UserGems helped Mixpanel hit 14X ROI in 13 months
Publication Date: Mar 22, 2022
Customer Name: Mixpanel
Industry: Product Analytics
Company Size: Enterprise
Challenge: For Michael Witt, Marketing Ops Manager at Mixpanel, the challenge was threefold: identify the warmest paths into deals, get into deals earlier (which increases the likelihood of conversion), and find prospects who knew the value of Mixpanel and had a great experience with the product in the past. Mixpanel needed a systematic way to track when their power users changed jobs.
Solution: Mixpanel pulled in product users from their user base and implemented UserGems to track when these contacts changed jobs. They fully automated the UserGems workflow so leads would show up ready for reps to work on, integrating with Salesforce and Outreach for seamless operations.
Results: Sourced 30+ opportunities via UserGems and hit 14X ROI from these opportunities within 13 months of implementation. The solution required very little lift from the sales team and ran smoothly in the background, with UserGems Customer Success providing support as needed.
Customer Quote(s): "Make sure you have an idea of who you're targeting and how you're going to contact them. Find your power users and set up a sales motion for them. At the very least, even if they're not a direct influence, they can open/show you a way to get in the door." - Michael Witt, Marketing Ops Manager at Mixpanel
Key Stats: 30+ opportunities sourced, 14X ROI achieved, 13 months to achieve results, fully automated workflow requiring minimal manual intervention
Instructions (Example #1):
(No instructions added) – this means our team is okay with Gem-E using best judgement based on the contents of the summary above to decide when/where to mention the case study
Instructions (Example #2): Scenario: if you want to make sure Gem-E mentions a case study in the email sequence, but you don't want to specify exactly which email should include the case study…
Mention the most relevant case study (the most relevant one for the prospect based on their role, industry, company size, etc.) from the case studies you've been provided and mention it 1 time in the sequence to this prospect in a logical and seamless way that fits naturally into the context of the email and sequence.
New Features Examples
Example: Gem-E Feature Announcement
Link: https://www.usergems.com/news/meet-gem-e
Filter: Last Contacted = 3 months ago
Description:
Gem-E is UserGems' AI outbound agent designed to help sales development reps (SDRs) efficiently identify, prioritize, and engage with high-value accounts and contacts using a combination of UserGems' proprietary signals and your own CRM data. By continuously analyzing people signals (such as job changes, past champions, and buying group data) and company signals (including funding, hiring, and competitor activity), Gem-E surfaces actionable buying opportunities and automates personalized outreach at scale. The result is outreach that's not only highly relevant and timely, but also consistent with your team's voice and priorities, reducing manual data entry and research, while increasing pipeline effectiveness.
Gem-E was released in early 2025, so make sure to take the amount of time that has elapsed between early 2025 and today's date into account when mentioning the recency of Gem-E's release. Only mention the release date of Gem-E in general terms (e.g., "recently introduced", "earlier this year", or "over the past few months"), and don't mention specific timeframes.
Make sure any mention of Gem-E fits naturally into the context of any emails you mention it in and Gem-E is framed in a way that is relevant to the prospect you're reaching out to.
Links Examples
Example 1: Gifting Link
Link: Sendoso.com/UserGems-Redeem-Giftcard-NewHire
Description: This is a gifting link for New Hires and Promotions.
Instructions:
It should be naturally incorporated into the first 3 emails of the sequence. In the first email fit it in somewhere towards the end of the email that fits in naturally with the other messaging in the email. In emails 2 and 3 briefly mention it as a reminder in case they missed the gifting link in the prior emails.
- Any time the gift/gifting link is mentioned, make sure to include the hyperlinked text to the gift. There should be a hyperlink to the text in emails 1, 2, and 3 of the sequence.
- Do not show the full URL for the gifting link. Instead hyperlink it to text that fits naturally into the content of the email or hyperlink to phrases like "here", "gift", "check it out here", etc.
- Never add a P.S. when adding a gifting link because a sign-off/signature will always be manually added by the user at the end of the email after you have generated it.
- Never mention any specific timeframes when mentioning gifting links sent in previous emails (ex. Never say "Hope you caught that gift from yesterday", "Hope you saw the gift I sent last week", etc.) since you don't actually know how much time has elapsed between emails being sent.
- Make sure to explicitly state where the gifting links should be added and how they should be mentioned in the "Personalization Signal Used For Each Email" section of the data summary.
Filter: Signals (is any of) = New Hires & Promotions
Example 2: Webinar/Resource Link
Link: https://www.usergems.com/usergems-classroom-modern-outbound-for-sdr-leaders/class-1-revive-closed-lost-opportunities-us
Filter:
- Current Title (Contains) = Development
- Persona (is) = Sales - Enterprise
Description:
This is a recorded classroom session intended to be shared as a value-add resource for SDR leaders. It provides a tactical, behind-the-scenes walkthrough of how UserGems revives Closed Lost opportunities using AI-powered outbound.
This link should be woven naturally into the email body, similar to how a case study or playbook would be shared. It should support the message, not dominate it, and should feel optional and helpful rather than promotional.
This content is designed for SDR leaders who care about pipeline recovery, signal-based prioritization, and running outbound motions that actually convert. It is not an event, registration, or webinar invite. It is framed as useful, practical content they can skim or save.
The link should never appear as a P.S. and should not be positioned as the primary CTA.
The link should only be included in one e-mail of each sequence.
Link messaging instructions:
Introduce the link with casual, value-forward language such as:
- "We recently walked through exactly how we revive Closed Lost with AI. Sharing in case it's useful."
- "This breaks down the Closed Lost motion we actually run. No theory."
- "If Closed Lost is sitting untouched, this walkthrough might be helpful."
The phrase "recorded classroom session" must be hyperlinked to the content URL.
Never show the full URL. Always hyperlink the phrase "recorded classroom session."
When referencing the presenter, use: "Sara, our Director of Account Development."
- Place the link mid-email or immediately after a relevant insight, similar to how a case study would be shared.
- Do not place the link at the top of the email.
- Do not place the link after the closing CTA.
- The primary CTA should remain focused on a reply or short conversation. The link is secondary.
- Include the link only once per email.
- Do not oversell, summarize the full session, or pitch it as "must watch."
- Do not mention dates, attendance, or that it was live.
- Do not use marketing language. This should read like a peer sharing something genuinely useful.
Conditional Instructions Examples
Example 1: Language Localization
Filter: "Person > Country" IS France
Conditional Instruction:
ALL EMAILS MUST BE WRITTEN EXCLUSIVELY IN FRENCH. MAKE SURE ALL EMAIL SUBJECT LINES AND EMAIL CONTENT IS WRITTEN IN FRENCH.
In the "Personalization Signal Used For Each Email" section of the data summary make sure to explicitly state that all emails (both subject lines and bodies - including all greetings (use traditional French email greetings for all emails)) must be written in French. Also explicitly state that no content should be output in English.
Example 2: Competitor Tech Stack Signal
Filter: Signal (is any of) = Tech Stack (Competitor Name)
Description:
This prospect is known to be using (Competitor Name)as part of their GTM stack. When generating messaging, do not assume the prospect is actively evaluating alternatives or dissatisfied with their current solution.
All other Tech Stack signals should be ignored so that the messaging only focuses on (Competitor Name)tech stack signal.
When referencing (Competitor Name):
- Mention (Competitor Name) in exactly 2 emails in the sequence.
- Treat the second (Competitor Name) email as standalone. Do not reference the first 6sense email in any way.
- In each email that mentions (Competitor Name):
- Say "(Competitor Name)" only once.
- Keep all (Competitor Name)-related language to max 2 sentences total.
- Do not position UserGems as an intent-only tool.
- Do not position UserGems as a complimentary tool
- Use the mention of (Competitor Name) as a direct callout of what's broken in ABM today. Examples below:
- "Many teams tell us that ABM tools like (Competitor Name) aren't working well for them. These tools only show you which companies are in-market, but can't tell you who."
- "We often hear from teams using (Competitor Name) that they're unable to...."
- "One common frustration we hear with (Competitor Name) is that it's hard to operationalize"
- After the (Competitor Name) mention, shift the focus to UserGems' strengths, such as:
- Identifying who within an account is most relevant to contact, rather than leaving sellers to guess. Providing clear, explainable prioritization so teams understand why certain accounts or contacts matter now.
- Helping sales and marketing activate the same buyers at the same time, instead of working from disconnected lists or tools.
- Combining multiple signals to add context and timing, rather than relying on a single isolated indicator.
You should adapt the emphasis based on the prospect's role:
- For marketing leadership, focus on activation, alignment with sales, and reducing wasted effort from account-level signals that are hard to operationalize.
- For sales leadership, focus on prioritization, clarity on where reps should start, and consistency in execution.
- For frontline sellers, focus on not having to guess who matters or why outreach is timely.
Do not open the message by mentioning (Competitor Name) unless no contact-level or stronger personalization signal is available. If other signals exist, lead with those and weave the 6sense reference in later as supporting context.
If other tech stack signals are available: do not mention them or mention anything about integrating with them, only mention (Competitor Name) using the instructions provided