How To Use Gem-E 2 Messaging

Hey there, It's Taylor from UserGems here.

And in this video I'm going to guide you through how to chat with Gemmy2 and best practices to use when chatting to shape your outbound messaging.

So I'm, currently inside of the editor right here on the workflow level.

And that means all of the edits and chats that I have with Jammy are only going to impact the messaging in this specific campaign.

Right.

We can of course chat with Gemmi on the global level.

if you just go to here, I'll go ahead and show you this Gemmi tab right here.

Any edits and chats that you make to Jemi on this level are going to apply across all of your campaigns.

So let's head back to the sample so I can show you.

We're going to hop into Jemi, generate AI messages v2, and here we are.

I'm going to preview what the messaging originally sounded like and then that way you can see what kind of changed.

Right.

so here we are.

The original message was about two words for subject line.

And the messaging itself is very cheery and warm.

Right.

I wanted to show you some extreme examples.

This isn't something that I would do in our own outbound messaging, but just to show you those extreme examples, I've asked Jemmy to use a more formal and detached tone instead of a friendly and warm one.

I also asked, this is not best practices for an extremely long subject line.

Five worded subject lines.

Right.

So let's actually see what happened and you can actually watch this change.

for this, prospect right here on the right hand side, I'm going to continue from draft.

And there it is, right.

Forward subject lines.

and then the tone itself, exclamation points are removed.

It does sound more formal and detached here.

Right.

If I wanted to undo anything that I just did, I can go ahead and just hit undo last message.

Maybe I wanted three to four worded subject lines or two to four words.

Right.

I can either undo here.

I can create a new message and say two to four worded subject lines, or I can actually hop over to the instructions tab where Gemmi is storing all of those instructions.

And here, this is where we recommend adding, very specific or making tiny little tweaks and edits that are specific.

Here's the five word long subject line.

If I wanted to come in here and change it to three, that's where I'd be able to do it.

But for the sake of this example, I'm just Going to discard my change.

And let's keep editing this.

Actually here we can see, how Jemmy talks about pain growth marketing leaders face increasing pressure to deliver qualified pipeline.

This is assumptive.

we can change the way Jemmy talks about this by saying, when talking about pain points, always use hedging language.

Let's feed some examples.

too.

for example, maybe not sure.

maybe not sure if it's the same or it seems like.

But this is more.

Less assumptive.

And let's go ahead and feed another instruction as well.

Here I can see we're asking one question per email.

Let's say ask two questions per email.

And the CTA should be no more than.

let's do four words.

Very specific.

I'll hit send here.

And Jemmy starts to work its magic.

It's going to start generating the new instructions and then feeding it into this instructions tab.

So here it says it added a new section to use hedging language when referring to pain points.

And we can actually see this in the instructions here.

it also added the questions and call to action.

Right?

Two distinctive questions in every email.

And the call to action itself should be no more than four words.

Let's go ahead and wait for Jemmy to update the messaging here all right, so it looks like Jemmy followed our instructions here.

It's using not sure language instead of assumptive language when we're talking about the pain points.

I also see two questions are now added for every single email.

and then I also see that it's following the CTA should be no more than four words.

Right?

That shrunk a lot compared to the old version that we were previously looking at now.

worth noting here that if you wanted to undo this.

if I liked two out of the three ways that Jemmy changed this email, but I wanted to remove the other, it's a little bit tough.

So for that reason we don't recommend chunking a whole bunch of different instructions, like a whole list all in one go, but maybe worth just breaking it up chat for chat, so it's easier to undo.

but of course we can edit this directly in the instructions too if we wanted to change anything here.

So from here I would also like to talk about best practices what you can and can't ask Jemmy to do.

I will say I'm going to share these do's and don'ts here with you.

Right.

The rule of thumb is to avoid mentioning sample level prospects.

So what we mean by that is don't get super laser focused into a specific prospect that you're looking at inside of the previews and, instead go more broad.

Right?

So instead of asking something like change John Doe's CTA in the first email to xyz, we can accomplish the same thing by simply saying in the first email, use XYZ as the cta.

Right.

next rule of thumb here is to steer away from hard coded phrases unless they can be applied broadly.

And let me give you an example of that.

In sentence 3 of email 1, always use this exact phrase.

Since your team is growing, are you focused on ramp?

Right.

that might make sense in the context of one email that you're looking at at a sample level.

But remember that Jemmy2's emails are all dynamic.

So while this might work for one prospect or a specific subset of prospects, these hard coded sentences might not always apply.

So what we could do instead and accomplish something very similar is to say in sentence three of email one, always ask the prospect about relevant initiatives based on the best available signal.

So there's another example here for you.

Now, this last one is just a don't.

There's no do here.

But avoid asking Jemmy for data that it doesn't have access to.

And then also avoid asking Jemmy to do things that it can't.

Right, so if you say update my audience or change my workflow, that's something that Jemi can't do.

we will attach a help article to this video here just to give you some more ideas of things that you can do with Jemi.

This is a limited list.

Jemmy can do quite a lot.

But the last tip that I'm going to leave you here with is if you give Jemmy a specific instruction, always try your best to feed in some examples.

Right?

Like when I said to use hedging language up here, I gave it specific examples.

I used the words maybe.

Not sure if it's the same.

It seems like giving Jemmy examples of what good looks like versus what bad looks like really helps Jemmy with updating the messaging here to sound, in the same way that you're hoping to shape it too.

Right.

So, quick crash course here on best practices do's and don'ts with Jenny but if you have any other questions, check out that help article or reach out to our team and we'd be happy to help you with this.