First-time account onboarding

This guide is for accounts that are not yet operational — typically: no senders (email accounts) connected. Your role is to guide your user through setup. Every Manyreach-side step below can be performed with the operations here. What stays manual are steps on other websites (the user's email provider, their DNS provider) — there, guide the user precisely: name the site, the exact setting, and what to enter. One alternative connect method lives only in the Manyreach web app: the 1-click OAuth connect (see step 1).

To survey an account before onboarding, start with account/get (which account and scope this session operates in), then user/get → sender/get → campaign/get → list/get.

How to work with your user:

• Go through the checklist top to bottom; verify progress with the operations wherever possible.
• Prefer explaining in your own words, adapted to what the user already has set up.
• Help-article links below are a last-mile device: first narrow down what your user needs (their email provider, the exact step they're stuck on), and only then offer the one relevant link — because it contains screenshots you cannot display directly. Never open with a list of links.

Checklist

1. Connect a sender

A sender is created with sender/post: the email address, a dailyLimit, and working SMTP/IMAP credentials (host, port, username, password). The credentials are prepared on the provider's own website — ask which provider the user has, then walk them through that branch:

• Gmail / Google Workspace — app password + SMTP. Three sub-steps on Google's sites, in order:

  1. Enable IMAP — in Gmail: gear icon → See all settings → Forwarding and POP/IMAP → Enable IMAP → Save. How to enable IMAP in Gmail
  2. Enable 2-Step Verification — at myaccount.google.com/security: 2-Step Verification → Get Started → verify a phone number → turn on. Allow 5–10 minutes before the next step. How to enable 2-Step Verification
  3. Create an app password — at myaccount.google.com/apppasswords: enter an app name (e.g. "Manyreach") → Create → the user must copy the 16-character code immediately (it is shown only once). Google displays it in four space-separated groups — submit it without the spaces. How to set an app password

  Then call sender/post with that app password as both the SMTP and the IMAP password (the SMTP setup article has the host/port values). On Google Workspace an admin can disable app passwords org-wide — if the user can't create one, use the OAuth alternative below.

• Microsoft 365 / Outlook. A Microsoft 365 admin must first enable IMAP and authenticated SMTP for the mailbox: admin center → Active users → the user → Mail → Manage email apps; allow ~30 minutes to propagate. Enable IMAP & authenticated SMTP Then sender/post with the mailbox's SMTP/IMAP credentials, as above.

• Any other SMTP/IMAP provider. Some providers require SMTP/IMAP access to be enabled in the account settings first; then sender/post with the provider's host/port/username/password. Connect any SMTP/IMAP provider

• Many mailboxes at once. There is no bulk-create operation — loop sender/post per mailbox. (The web app also offers a CSV import: connect senders in bulk.)

Verify after creating — creation succeeds even with wrong credentials. A 201 does not prove the credentials work; validation runs asynchronously. After sender/post, wait ~15 s, then confirm via sender/get_by_id (connection state) and sender/errors_by_id before relying on the sender. Error rows can land within seconds, but an empty list read before that wait proves nothing — re-check rather than telling the user the sender is connected.

Web-app alternative — OAuth 1-click connect. The Manyreach web app (Senders → Add senders) also offers a 1-click OAuth connection for Google Workspace and Microsoft 365 — no app password or 2-Step Verification needed (for Workspace, a super-admin first marks the app as trusted in admin.google.com). This connect method has no corresponding operation, so it happens in the web app: Google Workspace OAuth · wizard overview

2. Configure the sender

Everything here is ordinary fields — set them at creation (sender/post) or any time after (sender/patch_by_id):

• Sender details: firstName, lastName, fromName (the name recipients see), signature (HTML).
• Sending limits: dailyLimit and delayMinMinutes (minimum minutes between messages, not seconds) — conservative values protect a fresh account's reputation.
• Auto-increase: dailyLimitIncrease with dailyLimitIncreasePercent and dailyLimitIncreaseToMax — gradually ramps daily volume by a percentage up to a cap.
• Custom tracking domain (optional but recommended): the user creates a CNAME at their DNS provider (propagation can take up to 24 h), then set trackingDomain to that hostname. Tracking-domain article

Guidance on good values (with screenshots per section): How to set up the sender for an effective outreach

3. DNS authentication — SPF, DKIM, DMARC (at the user's DNS provider)

Fully explainable in text — walk the user through their DNS provider (GoDaddy, Namecheap, Cloudflare, …). Records to create (TXT):

• SPF — authorize the sending service, e.g. Google Workspace: v=spf1 include:_spf.google.com ~all · Microsoft 365: v=spf1 include:spf.protection.outlook.com ~all
• DKIM — generate in the email provider's admin console, then publish the key, e.g. google._domainkey.<domain> with v=DKIM1; k=rsa; p=<PUBLIC_KEY>
• DMARC — policy record at _dmarc.<domain>, e.g. v=DMARC1; p=none; rua=mailto:<address>; ruf=mailto:<address>; fo=1;

DNS changes can take 24–48 h to propagate. Publishing and checking these records happens entirely outside Manyreach's reach — supply the exact record text and have the user confirm at their provider. Reference: SPF, DKIM, DMARC setup

4. Enable warmup

Warmup builds sender reputation through simulated human-like exchanges before real outreach — skipping it risks burning a fresh account. Budget 2–4 weeks on a fresh mailbox before sending at full volume; build the campaign meanwhile, and keep dailyLimit low until then. Enable and tune it via sender/patch_by_id (or at creation): set warmup: true, then warmupDailyLimit (start low), warmupReplyPercent, customWarmupTag, optionally warmupSkipWeekends and a ramp (warmupDailyLimitIncrease, warmupDailyLimitIncreasePercent, warmupDailyLimitIncreaseToMax).

• Why it matters: What is sender warmup?
• Suggested values (with screenshots): How to enable sender warmup

5. Create the first campaign (your job — run the operations)

No web app needed: create the campaign via campaign, add steps via sequence, add prospects via prospect and list. Confirm with your user before anything can actually send (senders connected + warmed up + limits configured).

6. Verify and close the loop

Re-check sender/get and campaign/get — once senders exist, the onboarding notices in these docs disappear on their own. Beyond onboarding (clientspaces, custom IPs, deliverability troubleshooting): https://help.manyreach.com/en