For WooCommerce and WordPress agencies

Many client domains, each one ramped and capped on its own.

An agency sending for WooCommerce and WordPress clients runs a fleet: several inboxes on several domains, a list per client, and a reputation per client to protect. CraftNudge treats the domain as the unit, prices the inbox, and leaves the contacts unmetered.

One workspace per client

Each client is its own workspace with its own inboxes, campaigns, rules and bill, and one Agency page lists them all with their campaigns, the state of their inboxes, and whether each can send. Switch into a client with one click.

A domain per client, ramped on its own

Each client domain starts its own warmup ramp, 5, 10, 12, 15, 20, 25 a day by the week, shared across every inbox on it and held back when its bounce rate crosses your limit. A busy client cannot spend a quiet one’s number.

Inboxes grouped and capped

Tag inboxes by client, set caps in bulk, and see sent today against allowed today across the fleet on one screen. A domain cap is shared by its inboxes: two on one domain split it, they do not each get it.

Leads in by API, after your own checks

Your pipeline decides who gets written to. CraftNudge takes the address by one call and refuses the ones your checks missed: already in another campaign, contacted inside the re-contact window, on the blocklist. Every upload reports what it skipped and why.

Copy that reads as the client

The sending inbox’s signature and name are variables, so one sequence reads right from every client’s inbox. Merge fields with fallbacks and wording variation keep a hundred sends from sharing one skeleton.

One inbox for every reply

Replies, bounces and out-of-office from every client inbox in one place, matched to the send, filtered by campaign or inbox. Mark a lead interested in a click and answer in the thread from the inbox that received it.

What came back, per domain

Bounces by cause, deferrals per inbox, and each domain’s last fourteen days drawn against what it was allowed. A day over the line is a day the ramp was broken, and you see which client’s domain it was.

A reply while it is warm

Telegram, email or a webhook the moment a person replies, with the thread one tap away and the follow-ups already stopped.

One address, one history

Type part of an address and see every campaign it was in and everything that went to it, with the server’s answer each time. The question a client asks is always about one shop.

Priced by inbox, not by contact

Contacts and sends are unlimited on every plan. A list of ten thousand shops costs the same as a list of a hundred, so the pipeline can be generous and the checks can be strict.

The audits and the lookups that decide who to write to are your pipeline, and the API is where the two meet. Address checks can stay there too, or run in CraftNudge on your own Reoon key. Warmup is not included. Keep the one you trust, and let CraftNudge do the sending and the reporting per client domain.