Customer Enablement · Voice of Customer · AI Solutions

On paper, I look like three different people. In practice, that is the advantage.

I'm Ana Santana. One operating system that has run in three environments: a clinical foundation, eight years on enterprise customer teams, and the systems that turn customer voice into decisions. One person who learns fast, ships real things, and can back up every line on this page. Different on purpose. Here is why that works in your favor.

Customer Enablement · Voice of Customer · Onboarding & Community Boston, MA · Remote · Will relocate for the right team
Read the 20-second brief →
Ana Santana

The through-line

The connective tissue.

what's true on the groundthe decision

I've always been the point in the middle. Named or not.

01 · The brief

The short version. Every line backed below.

Role fit
Customer enablement, Voice of Customer, onboarding and community. And if the role doesn't exist yet, I'll build it.
Superpower
Thrives in the unknown, and makes complex workflows feel easy.
AI
Made to work in my favor. Not clever prompting or cute outputs, but context, real study of the models, and judgment about what they can do when used right.
Track record
30% faster onboarding · rigor that opened a new team-lead role at Autodesk · a scalability award · 93%+ CSAT against a 90% goal.
Foundation
A clinical foundation: evidence-first, precise under real stakes. Built on with operations and AI solutions.
Languages
Fluent English · Native Spanish
Status
Boston, MA · Remote · Will relocate for the right team
Verdict
Worth the call.

02 · How I think

Diagnosis before treatment. The symptom is never the problem.

Case 01

When the number was green and still wrong

As a team lead, everyone read the resolution numbers and relaxed. They looked healthy, and they were misleading. A rep scoring below average on CSAT was not failing, they were taking the hardest cases. Running community later, the same trap: the loudest contributor is rarely the most valuable, and the member who posts least but reads most can matter just as much. A metric that treats every context as the same context hides the truth. The fix was never a better dashboard. It was measuring what the number actually meant.

Case 02

The problem was never collection

Everyone wanted to automate, add AI, open new channels, collect more. Collection was never the bottleneck. The real problem sat on either side of it: the intake, and the commitment to close the loop after the report went out. More channels would only bury the signal deeper. The work was curating what was already there and elevating the voices that popularity had quietly silenced, the ones that mattered without shouting. Less, done better, beat more.

Case 03

The field was new. The skills were not.

Moving into a new domain looked like starting over. It never was. The work rewarded instincts I already had, they just needed retranslating. Clinical triage became prioritization. Reading a patient became reading an account. The move was never learning from zero, it was recognizing what already transferred and refusing to mistake a new vocabulary for a new beginning.

There are more of these, and the endings land better in person. Ask me anything →

03 · AI as a trusted partner

The tool is not the value. The judgment is.

AI was never the problem. Using it without expertise is.

Expertise without AI is a head start you refuse to use. The value is in the hands that know the difference.

Anyone can prompt a model. I study how they actually work, so I can tell what is true, which is the part that stays human. I run AI through four moves that each take expertise:

Delegate.

Hand the grunt to the model.

Describe.

The output is only as good as the spec. Knowing exactly what to ask for is the skill.

Discern.

Tell the true from the merely plausible. This is where taste lives, and where the model cannot help you.

Decide.

Own the call. AI drafts, I sign.

Story · the foundation

I think in systems because I first learned them in the body.

Before customer teams, I trained in a clinical world where being wrong had real consequences. That is where the habits come from: diagnose the root cause before you treat the symptom, respect the evidence, stay precise when the stakes are real.

A slow metric is a symptom, and the cause is usually upstream. A feedback loop is a feedback loop, whether it runs through an organ or an org. I carried that discipline out of medicine and into customer operations and AI, and it is still the through-line.

Still curious

Ask me what I'm working on.

I am always in the middle of a few questions. Right now: how far AI can reach into customer work before judgment has to step back in, and where that line actually sits. If you are chasing something thorny in customer enablement, Voice of Customer, or applied AI, bring it. I would rather think through a real problem with you than talk about myself.

Send me something to think about →

Yes, I have a LinkedIn. I am not the most active there, but if that's where you are, come say hi. I want to be part of the conversation. Find me there →

Worth a conversation?

Let's talk about where this fits.