Apollo

Your assistant can search Apollo's people database by title, seniority and organization, pull the full company record behind a match, and enrich up to ten people or ten company domains in one pass. Apollo's own guidance is to start broad and narrow, because stacking strict filters on title, seniority and organization together often returns nothing. Every one of these reads, and none of them writes into your Apollo account.

What you end up with. A named shortlist of people at the account, with title, seniority and whatever contact detail Apollo holds on each.

Start with it bringing you the information and you deciding.

Never without. Watch the credit meter. Apollo charges credits per domain and per person enriched, and organization search consumes credits on every call, so an assistant that re-runs a query it already ran is spending money you did not budget. Ask for the query once and keep the result.

Built on: Apollo people search / Search organizations in Apollo / Get Organization by ID / Bulk people enrichment / Bulk organization enrichment

It can search news articles about a company in Apollo's database, list that company's open job postings, and read the account record you already hold. Hiring for three support roles and an announcement in the same month is a specific opening, and it is the kind of thing nobody has time to check by hand across forty accounts. Reading only.

What you end up with. A short brief per account naming the recent news and the roles being hired for, with dates.

Start with it bringing you the information and you deciding.

Never without. Read a job posting as a signal, not as a fact about the buyer. Postings sit open for months after a role is filled, and quoting one back to somebody who hired in March makes you sound like you are working from a list.

Built on: Search news articles / Get Organization Job Postings / Get Organization by ID / Search Apollo Accounts / Get Account by ID

Before anyone touches an account again it can assemble the history in one place: the account record, the tasks logged against it, the calls with their outcomes and durations, the sequence emails your team sent, and the deal if there is one. This is the check that stops two people from your side arriving in the same inbox a week apart.

What you end up with. A dated account history covering calls, tasks, sequence emails and current deal stage, in one written summary.

Start with it bringing you the information and you deciding.

Never without. Treat this as what was logged, not as what happened. Calls placed outside Apollo and conversations that never got written down are invisible here, so an empty history means nothing was recorded rather than that nobody has spoken to them.

Built on: Get Account by ID / Get Apollo Contact / Search tasks / Search for Calls / Search outreach emails / Get Apollo deal

It can list the sequences in the account, search the outreach emails your team sent through them, and read the email accounts those went out from. That supports the comparison worth making, which is not open rate in isolation but which sequence, sent from which mailbox, produced replies worth having. Apollo caps the email search at 50,000 records and requires a master API key for it.

What you end up with. A comparison of your live sequences by volume sent and replies received, with the sending mailbox named.

Start with it bringing you the information and you deciding.

Never without. Do not let a rate decide anything on its own. A sequence with forty sends and one meeting is not beating one with four hundred sends and eight, and the assistant will happily rank them for you if you let it.

Built on: Search sequences / Search outreach emails / List email accounts

It can search your existing contacts, find the sequence and the sending mailbox by their real IDs, and add the contacts to that sequence. The IDs matter here: the sequence, the campaign and the sending email account all have to be looked up first, because Apollo will not take a name in place of an ID. Adding someone starts real email going to a real person, so this is a step to watch rather than one to hand over.

What you end up with. The named contacts enrolled in the sequence you chose, sending from the mailbox you chose, with the enrolled list written back to you.

Start with it doing the work and checking with you.

Never without. Read the enrollment list person by person before it runs, and confirm which mailbox is sending. This puts email in front of real people under a colleague's name, and an existing customer who lands in a cold outbound sequence is a phone call you will have to make yourself.

Built on: Search Apollo contacts / Apollo people search / Search sequences / List email accounts / Add Contacts to Sequence

It can find the sequence, read the contact, and change that contact's status within it so the remaining steps stop. One thing is worth knowing before you run it: Apollo's connector cannot set a sequence status back to active. Every other status is reachable, so the move out is easy and the move back is not.

What you end up with. The contact stopped in that sequence, with the sequence, the contact and the new status named in writing.

Start with it doing the work and checking with you.

Never without. Never let it change sequence status for a set described only as a rule, such as everyone who replied this week. Have it list the exact contacts and sequences first and approve that list, because this connector cannot set a status back to active and reversing it means rebuilding the enrollment by hand.

Built on: Search sequences / Get Apollo Contact / Search Apollo contacts / Update contact status in sequence

It can read the contact stages and account stages your team actually configured, search the records that are sitting in the wrong one, and move them, one contact stage at a time or a batch of accounts at once. Reading the stage list first is not optional, since Apollo takes stage IDs and rejects the names people use out loud.

What you end up with. Contacts and accounts sitting in a stage that matches reality, plus a list of every record moved and what it moved from.

Start with it doing the work and checking with you.

Never without. Never run a stage change over a set you have not read back first. Stage is what your forecast and your sequence rules key off, so a batch that catches thirty accounts you did not mean quietly changes what your pipeline says next Monday.

Built on: List apollo contact stages / List Apollo account stages / Search Apollo contacts / Search Apollo Accounts / Update contact stage / Bulk update account stage

It can list the teammates on the Apollo account to get the numeric user IDs the reassignment needs, search that person's accounts and contacts, and move ownership of both to whoever is picking them up. Names and email addresses are not accepted in place of the user ID, which is the usual reason this fails on the first try.

What you end up with. The departing owner's accounts and contacts transferred to the named teammate, with a written list of what moved.

Start with it doing the work and checking with you.

Never without. Confirm the receiving user by name against the ID before it runs, and agree the split with the people picking the accounts up. Ownership drives routing and notifications, so a bulk transfer to the wrong teammate hands somebody a territory nobody told them about.

Built on: List Apollo Users / Search Apollo Accounts / Search Apollo contacts / Update account ownership / Update contact ownership