A: Great question—and you're totally right in how you've spotted the limitation.

At the moment, Zapier's "Add or Update Person in Encharge" action unfortunately does not support tags natively. That's why the workaround we recommend is the 3-step Zap:

• Step 1: Your trigger (e.g. new signup)
• Step 2: Add or Update Person in Encharge (map name, email, etc.)
• Step 3: Add Tag in Encharge

The reason for this extra step is because Zapier doesn’t allow us to include tags in the same action as mapping the person. And as you noted, that requires a Pro plan.

We’ve had multiple users request support for tags in step 2, and we hear you 💯. It’s something we’d love to streamline, but right now it would require changes both on our side and potentially Zapier’s. We don’t want to commit to something we might change our mind on later, but it’s on our radar.

In the meantime, your workaround—using a field like “Company” for tagging—is clever, though as you said, not ideal long-term.

If cost is the blocker with Zapier Pro, one alternative is using Pabbly Connect or Make (Integromat), which offer similar functionality with fewer pricing constraints. Both work well with Encharge.

And just to close the loop—thank you for thinking through this so clearly. We appreciate folks like you who push the tool to be better 🙌🙌

Let me know if you'd like a quick Flow mockup or help setting up a Zapier alt!