r/UseApolloIo

Apollo is sharing my personal cell phone number, and I cannot get a real human being at the company to help me remove it.

I’m getting dozens of cold calls ever week, at all hours of night and day, on my actual personal cell. Not a business line. Not a work phone. My personal cell phone.

I tried the opt-out form. It only lets me enter an email address, then tells me my email is not in the system but that they’ll add it to a suppression list. No additional options for phone numbers. I’ve emailed Apollo support. I’ve emailed Apollo privacy. Both times, I get AI responses telling me to use the same opt-out form that does not solve the problem.

So now I’m here, because I’m honestly out of formal options.

Apollo, please help me remove my personal cell phone number from your platform. I do not consent to having it shared, sold, enriched, distributed, or whatever the internal term is for why random salespeople now have it.

And for Apollo users: this is not a good look. Even if I were interested in what you’re selling, calling my personal cell because you paid a data platform for it makes me immediately distrust you. There is no scenario where I’m giving business to someone who reached me this way.

I’m just trying to get my personal phone number off a platform I never signed up for, and Apollo has made that weirdly impossible. ANY TIPS?

Apollo's AI credits burn at enrollment, not when an email sends, so if you add an AI variable to a sequence and enroll 500 contacts before qualifying the list, you've spent credits on 500 people before a single email goes out!

Four things that help conserve credits:

1. Qualify before you enroll. Run AI Research on a tight, targeted list first and only enroll contacts that clear your bar. Don't use AI personalization as a sorting mechanism, use it as a finishing step.

2. Test on one contact before you bulk enroll. Apollo lets you preview AI output on a single contact. If the output is generic or off-target, it's almost always a Context Center problem, not an AI problem!

3. Treat your Context Center like a prompt. If your context is thin or vague, your outputs will be too. Specific value props, real ICPs, actual "why now" language, that's what turns an okay opener into something that gets replies.

4. Watch your workflows. If a workflow is auto-enrolling contacts into an AI-powered sequence, it's burning credits every time that trigger fires. Check what's running and at what volume.

Happy to answer specifics if anyone's running into this in the comments.

Most people think of Apollo as a data platform. You go there, pull contacts, get account info, move on...but we built something a little different.
I work on the AI team at Apollo and I just finished putting together a journey-based renewal series for our account managers that uses Apollo as the actual orchestrator of the whole workflow and not just the data source.

Here's how it works:

The anchor: Salesforce

We pull contract end dates from Salesforce and use those as the anchor for everything downstream. From there, Apollo kicks off a series of timed flows that notify the AM at the right moments leading up to the renewal.

At each stage, four things happen in sequence:

1. Apollo runs AI research on the account and surfaces strategic guidance: who to reach out to, how to position the conversation, what the renewal narrative should be.
2. The right contact (the admin at the account) gets enrolled into a sequence automatically.
3. A Slack message goes out to a shared channel where the AM and their manager can both see it.
4. That Slack message includes a link to the account, what the rep needs to do, the AI guidance, and a direct link to the sequence task.

The interesting part: the Claude project

The Slack message also links to a Claude project that is connected to Snowflake data and Apollo's MCP. The rep opens it, pastes in a prompt, and Claude generates the actual artifact (executive brief, 6-month EBR, or end-of-year EBR) and handles creating the Google Slide deck.

Here is what the actual Slack notification looks like:

u/Account Manager. Contract ends on [Date]. Time to send the Executive Brief
to [Account Name].

AI strategic guidance on who to reach out to and how to position the brief:

Strategic angle: With [X] seat upside identified and a team actively ramping
new reps, this check-in is best positioned around ensuring the team has the
foundation to hit pipeline targets as the renewal approaches. Demonstrating
measurable outbound progress from the ramp investment strengthens the
renewal narrative.

Who to reach out to: Reach out to [Contact Name]. They are directly
overseeing end-user ramp sessions and have visibility into team performance
and capacity gaps that justify expanding the seat count.

Next steps:
  1. Review the contact added to the sequence via the link below
  2. Replace [email] with the correct recipient
  3. Prompt Claude with: "Executive summary for [Account ID] to [email]"

Sequence task: [link]
Claude Project: [link]

Prerequisites: Snowflake access approved, Snowflake MCP connected,
Apollo MCP connected.

The whole thing is measurable! Contacts are in sequences, tasks are logged, reps have a clear action every time they get pinged.

Happy to share the Claude project file if anyone wants to set up something similar. Drop a comment.

Noah