Best practices
Outbound only works when it is wanted. These are the habits that keep replies coming and mailboxes healthy — most of them the API enforces for you; the rest are yours. Rules that are mandatory live in the Acceptable Use Policy.
Build lists you would be proud to send to
Run the loop in order: find_leads → find_intent → enrich → verify_email. Each step is cheap or free on a miss, so it costs almost nothing to be selective and a great deal to be sloppy.
- Describe the audience, not the volume. A precise audience of 200 outperforms a vague one of 2,000 — and costs a tenth as much to enrich.
- Filter on intent before you enrich. Companies hiring for the role you sell into, or that just raised, reply at multiples of the base rate. Scanning is half a credit per company; only signal hits cost real money.
- Never send to a catch-all you haven't verified. verify_email resolves most catch-alls; treat catch_all_unknown and risky as "don't send" unless the account is worth a bounce.
- Business contacts only. Personal addresses, consumer lists and anyone under 18 are out of scope — and the API's data providers will not return them.
Sending capacity: separate, warmed, modest
- Never send cold email from your primary domain. setup_sending provisions lookalike domains and mailboxes leased to your workspace; your real domain's reputation stays untouched.
- Five mailboxes per domain, no more. The quote packs them that way on purpose. Spreading volume across mailboxes and domains keeps each one under the radar.
- Respect warming. New mailboxes ramp up over two to three weeks. Sending limits are applied per mailbox by the platform and its provider; start at a modest daily volume and let the ramp do its work.
- Watch bounces like a hawk. A bounce rate above a few percent is a list problem, not a mailbox problem. Stop, re-verify, then resume. The platform pauses campaigns that are hurting deliverability.
- Keep upkeep funded. Mailboxes carry monthly upkeep charged to your balance; if it can't be covered you get a 7-day grace window before the lease is cancelled. A low balance alert is your friend.
Copy that reads like a person wrote it
- Short. Under 80 words for the first touch. One idea, one question.
- Plain text. No images, no tracking pixels, no HTML templates, no more than one link. This is what lands.
- Personalise from real signals. The intent signal or the job posting you found is the opening line. Generic "I noticed your company" openers are the fastest route to the spam folder.
- Say who you are. Real name, real company, real reply address, and a postal address where the law requires it. Deceptive subject lines and hidden senders are prohibited, and they don't work anyway.
- Make opting out effortless. A plain "reply 'stop' and I won't write again" beats an unsubscribe link in cold email — and the platform honours both, permanently.
- Two or three follow-ups, then stop. Spaced 3–5 days apart, each shorter than the last. Stop-on-reply is on for every sequence.
Replies are the product
- Poll get_replies often and act within the hour. Reply speed is the strongest predictor of a meeting.
- Trust the classification, verify the intent. interested means a human should read it now; not_interested and unsubscribe are suppressed for you; out_of_office is a free re-touch date.
- Never contact a suppressed address again, from anywhere. Suppression is workspace-wide and permanent inside GTMRouter. If you also send from other tools, carry the suppression list over.
Keep your agents on a leash
- Scope every key. A research agent doesn't need campaign:launch. Create one key per agent, with only the scopes that agent's job needs.
- Set spend caps. Every key can carry a monthly spend limit. The API refuses calls that would exceed it, so an agent stuck in a loop costs you the cap, not the balance.
- Approval means you read it. Purchases and launches wait for a human in the console. Open the preview, read the copy, then confirm.
- Always send an Idempotency-Key on mutating verbs. Retries replay the original result without re-charging; without a key, a retrying agent can duplicate work.
- Revoke fast. If an agent behaves in a way you didn't intend, revoke its key from the console. Its next call fails; nothing else changes.
Stay on the right side of the law
Cold B2B email is legal in most jurisdictions when it is honest, relevant, addressed to people in their professional capacity, and easy to stop. You are the sender and the controller of the data you retrieve; the platform is your processor. In practice that means:
- a lawful basis for each contact (legitimate interest for relevant B2B outreach, in the UK and EU);
- truthful sender identity and subject lines (CAN-SPAM, PECR, CASL);
- a working opt-out, honoured immediately — the platform does this for you;
- no special category data, no consumers, no children; and
- a privacy notice of your own that mentions prospecting, if you don't already have one.
The full rules are in the Acceptable Use Policy; the data roles are in the Data Processing Addendum.