Email in Pega: are you positioning it right?

General
, , ,
1

Hi experts,
I’ve posted a blog about a question that comes up surprisingly often in the field:
Should an email management use case live in Pega Platform or Pega Customer Service?

If you’ve ever been in a meeting where a client is struggling to optimize email handling — and you’re quietly thinking “Platform or Customer Service?” — this one’s for you. The answer is rarely obvious, and the choice has real consequences for outcomes, architecture, and roadmap.

The article walks through a practical decision framework to cut through that ambiguity, and looks at how Agentic AI is starting to shift where that boundary sits for conversational channels like email.

:backhand_index_pointing_right: Read the blog: Email in Pega: How to Position Platform vs. Customer Service (with Agentic AI) | Pega

I’d love to hear from the community:

  • Have you faced the Email in Platform vs Customer Service decision in the field? What tipped the balance?

  • As Agentic AI changes channel orchestration, what new positioning challenges are you already seeing?

Drop your thoughts below — let’s compare notes. :backhand_index_pointing_down:

7 Likes
2

Superb article—we get this question all the time during discovery sessions, and perspectives like this really help teams land on the right choice.

One additional dimension that sometimes comes into play is whether the scenario is B2C, B2B, or B2B2C. That can materially influence how email is experienced and who the primary users are.

When the end user is a retail customer, teams often gravitate toward a Customer Service–led experience so CSRs have the context, prioritization, and tooling needed to manage ongoing customer conversations. In B2B and B2B2C scenarios, the choice can be more nuanced and depends heavily on how email fits into the overall process and operating model.

At the same time, it’s worth reinforcing one of your key points: the foundational email capabilities—especially on Constellation—are shared. The differentiation really shows up in how those capabilities are wrapped into an agent or process experience, rather than in basic email handling itself.

With LLM and agentic capabilities, email evolves from a passive input into actionable intelligence—handling multiple languages, complex scenarios, and nuanced intent. This makes email interactions more conversational, relevant, and faster to respond to. Guided by workflow predictability and controls, agentic email enables greater autonomy where appropriate, while keeping humans firmly in the loop.

3 Likes
3

Hello @gencr

Indeed a thought driven, well written article on a very important topic.

For me, email should never feel like a system-generated message. It has to be context-aware and meaningful when a customer reads it, they should feel like it actually understands their situation, not just a template response.

A quick personal experience on this:

The other day, I was trying to book a US visa slot and ran into an issue where my DS-160 wasn’t getting detected. I raised a support request through their feedback option.

After ~6 hours, I got an automated reply saying:
“We understand that you are facing an issue to add a person for creating a group request.”

And I was like… wait, what? :sweat_smile: That wasn’t even close to my problem.

What made it worse was that there was no way to reply back to that email, no chatbot, and no clear customer support contact. I even tried raising the request again… and got the exact same response.

At that point, I just gave up :raising_hands:

Why this matters here:

This is exactly where email communication fails when it’s not context-aware or conversational. It felt like a one-way, template-driven system rather than an actual support experience.

That’s why I strongly feel, especially with AI in the mix, we need to focus not just on sending emails, but on enabling meaningful conversations.

AI definitely helps for routine emails (acknowledgements, updates, etc.), but for critical or sensitive cases, I strongly feel there should be a human in the loop. AI can draft, but a person should validate before it goes out.

On Platform vs Customer Service, I usually look at one simple thing:

Is it just a notification, or an ongoing conversation?

  • Notifications → Platform works well
  • Conversations → Customer Service adds more value

With Agentic AI coming in, this line is getting thinner, but this distinction still helps in making the right call.

Regards

JC

3 Likes
4

Thank you very much for the feedback and for sharing your personal experience!

5

@gencr Nice article. Email is some thing every one wants and trust it more than any other channel when it comes to collecting data. :+1: