The rules

every operating rule the engine applies, read from its configuration

These are the rules the engine applies right now, read from its configuration. Spot one that is wrong? Propose a change right here. Nothing is edited directly on this page: the admin applies each request to the configuration itself, and this page re-reads it.

Open change requests

Everything the team has proposed from the sections below, waiting on the admin. Requests are applied to the configuration by the admin and take effect at the next engine run.

Requests unavailable: fetch failed. Requests already raised may exist but cannot be shown right now; try again once the live connection is back.

The one law

The engine drafts and organizes. It never sends. A person approves every list and every message.

This is the design of the system, not a setting anyone can switch off. Every rule below exists to serve it.

Market rules

How each market may be worked: channels, language, platforms. From the live configuration.

Market	Focus	Platforms	Channel limits	Language	Market-specific rules
UAE	T2 · deepen and defend	Amazon.ae, noon, quick commerce	No channel limits	English	-
KSA	T1 · expansion	Amazon.sa, noon, quick commerce	No channel limits	English	Cold drafts are written in English, never machine-generated Arabic The Content pitch leads with Arabic localization capability as its differentiator Arabic belongs in live conversations, handled by an Arabic-capable rep
India	T1 · retention plus acquisition	Amazon.in, Flipkart	No channel limits	English	Budget-qualify a lead before it takes up rep time Park a lead after two touches with no signal and no budget
Turkey	T3 · partner led entry	Trendyol, Hepsiburada, quick commerce	Never lead with Amazon (default; Atlas and AMC are exempt, see the product table below) Partner-led: outreach runs through the local partner	Turkish for local roles, English for senior international buyers	WhatsApp only after a call attempt or an accepted LinkedIn request, never as the first cold touch

The Amazon rule, product by product

Derived from each product's own channel limits in the live configuration, so this section always tells the truth about what is set today.

Atlas and AMC are Amazon-only products: they run on Amazon data and may name Amazon in every market, including Turkey.

Content, PiGen, and PiVerse never lead with Amazon in Turkey.

Atlas Media does not run in Turkey at all.

Product	UAE	KSA	India	Turkey	Cadence templates
Atlas	no channel limits	no channel limits	no channel limits	no channel limits	standard_amazon
Atlas Media	no channel limits	no channel limits	no channel limits	not offered	atlas_media_continuation
Content	no channel limits	no channel limits	no channel limits	no Amazon lead	content_audit
PiGen	no channel limits	no channel limits	no channel limits	no Amazon lead	pigen_geo
PiVerse	no channel limits	no channel limits	no channel limits	no Amazon lead	piverse_qcommerce
AMC	no channel limits	no channel limits	no channel limits	no channel limits	amc_media

Retail coverage

Which retail universe each product's outreach may lead with. From the live configuration's retail scope map (team feedback, Jul 23).

Atlas and AMC are Amazon by definition: they run on Amazon data, and their outreach may name Amazon in every market, including Turkey.

Content, PiGen, and PiVerse speak to every retailer in the market: Amazon, noon, Flipkart, Trendyol, quick commerce - never Amazon-only.

Atlas Media is the Amazon ads continuation: an existing Atlas relationship carried into Amazon advertising, so Amazon-scoped by nature.

Quality gates

What must be true before a message can reach a prospect. Deadlines and freshness windows come from the live configuration.

A real stat and a named competitor, or no draftA draft missing a brand's real number or a named competitor is never sent out generic. It is held, and the missing piece becomes a data-team task with a turnaround of 3 days.

Data older than 30 days is staleA brief built on a stale export is blocked until fresh data lands. Better no brief than a brief on old numbers.

A person approves every touchNothing is exported on the engine's say-so. Each message is approved, edited, or rejected by a named person, and edits replace the draft.

Export unlocks only when every touch is decidedA list with undecided messages cannot leave. The download contains only what a person approved; rejected and unreviewed messages stay out.

Sending discipline

The engine drafts; people send. These are the operating limits for the people doing the sending (pilot guidance, Jul 23).

Volume per sender mailboxAbout 30 cold emails per day during the first two warm-up weeks, 50 per day after that, and never more than 200 per week from one mailbox.

Spread sends across cadence daysSends follow the cadence day by day. A whole run is never batch-blasted in one sitting.

Only verified addresses get emailBeyond Apollo's own status, the engine runs a second check (ZeroBounce): valid addresses keep the email channel, invalid and unverifiable ones move to LinkedIn, spam-trap and do-not-mail addresses are dropped with a logged reason, and catch-all addresses (common at large MNCs) are emailed only up to a capped share of each run. Anything not yet checked lands in that run's verification_todo.csv to upload to ZeroBounce.

Hard bounces stay under 2 percentA bounced address is never retried, and HubSpot suppresses hard bounces automatically. If a mailbox's bounces spike, pause sending from it for a week.

The quiet rule stays across productsSending discipline adds to the cross-product quiet rule, it does not replace it: once any product touches a contact, every other product waits 21 days before reaching the same person.

Team decision pendingCatch-all email cap: 20% (conservative launch setting)

Big companies (Unilever, P&G, and similar) run mail servers that accept every address, so those addresses cannot be verified and bounce far more often. The engine still emails them, but only up to 20% of a run's email sends; the rest go to LinkedIn instead, never dropped. It is set low for launch on purpose. To do: discuss with the team, watch the real bounce rate in HubSpot for a few batches, then decide whether to raise it toward 30–40%. Changing it is a one-line config edit (no rebuild), and this number updates itself here.

Clients and quiet time

Who the engine will not contact, and why. From the live configuration's client repository and quiet rules.

A client is suppressed only where they are a clientSuppression is scoped: a client is off-limits for the products they already buy, in the markets where they buy them. Everywhere else they are a normal target, and the contact carries a relationship note for the account owner.

Every exclusion is logged with a written reasonNo one silently disappears from a list. Each excluded contact gets a written reason in the run's record, so any exclusion can be audited later.

21 days of quiet across productsOnce any product touches a contact, every other product waits 21 days before reaching the same person. One company, one conversation at a time.

The full client list, what each client is still targetable for, and the form for flagging a wrong entry are on the Suppression page.

Free offers

Every buyer type opens with a free offer, not a pitch. The offer for each buyer lives in the buyer catalogue on that product's hub.

Open a hub to see its buyers and their free offers:

Atlas Atlas Media Content PiGen PiVerse AMC