Personalization Tokens in Notifications: Useful Alerts, Finally

Personalization tokens are now supported in Paminga's Notifications — use contact fields directly in the subject lines and message bodies of every in-app and email Notification you send to your team.

This is the kind of small change that quietly transforms a feature you barely use into one you depend on.

The Notifications system has been there forever — bell-icon alerts, banner messages, email summaries that tell your team something happened. But until now, those notifications were generic. "A contact submitted your form." Which contact? Which form? Click through to find out.

Tokens fix that. The notification can now tell you exactly what you need to know in the subject line.

What This Unlocks

Drop a token into a Notification's subject or message body and Paminga substitutes the actual contact value at send time.

Before:

"A contact submitted your Demo Request form."

After:

"Sarah Chen at Acme just submitted Demo Request — Enterprise tier"

Same notification mechanism. Vastly more useful payload.

Where It Works

Personalization tokens work in:

• Notification subject lines — the most important place. The subject is what your team sees in the notification center, in the banner, in the email summary.
• Notification message bodies — for context that doesn't fit in the subject

Every contact field that's mappable in the rest of Paminga is available here.

Practical Playbooks

Some obvious wins:

• Form submissions — "{{First Name}} {{Last Name}} at {{Account Name}} just submitted {{Form Name}}"
• Lead scoring threshold crossed — "{{First Name}} {{Last Name}} just crossed {{Threshold Name}} — score now {{Lead Score}}"
• CRM sync alerts — "{{Contact Name}} synced from CRM — {{Lead Stage}}"
• Task creation — "Task assigned to you for {{Contact Name}}: {{Task Subject}}"

The AE who gets the notification can decide whether to click in before clicking. That's the whole point.

❌ Don't ship generic "a contact did X" notifications that force everyone to click through to figure out who.
✅ Do put the contact's name and key context in the subject. It's almost always the difference between actionable and ignored.

A Reminder About Delivery Channels

Notifications go through up to three channels (configured per user):

• Notification Center — the bell icon in-app
• Banner — prominent in-app banners
• Email — summary email with a direct link

Personalization tokens work everywhere Notifications render. Same substitution, three surfaces.

Get Started

1. Open any feature that triggers Notifications — Workflows, Approvals, Lead Scoring Thresholds, Tasks
2. Find the Notification subject and body fields
3. Drop in personalization tokens — same syntax as you use everywhere else in Paminga
4. Send a test to make sure the substitution looks right

A small change. Huge improvement in signal-to-noise.