Running Campaigns

Starting a batch takes one click once three things are in place.

1. Check the prerequisites.

• You’re signed in. The side panel should show your queue, not a sign-in screen.
• URLs are already in the queue. Import a list first if it’s empty. See importing target websites.
• Website credits are greater than zero. Top up or upgrade if your balance is at zero.

2. Pick the active agent. In the “Sending as” list, choose the agent for this batch. This one choice decides the sender identity, the pitch, the subject line, and whether AI Personalization applies to every URL in the run. See agents and profiles.

3. Click Start Batch. A confirmation dialog opens showing the URL count, the agent you selected, an AI cost estimate (when AI Personalization is on), and an estimated time to finish.

4. Click Start. Review the dialog, then confirm to launch the batch.

contactID never pre-charges or reserves credits up front, no matter how many URLs are in the batch.

1. Credits are spent one at a time. A credit is deducted only when a form is actually submitted, and only at that moment, as the batch runs.

2. Tabs open up to your concurrency limit. contactID opens tabs up to your Max Concurrent Tabs setting (default 5).

3. Each tab is filled and submitted. The content script detects the contact form on the page, fills it using your active agent’s details, and submits it.

4. The URL is marked and the queue advances. Each URL is marked Completed or Failed, the tab closes, and the next queued URL takes its place.

See the next article for what every queue status means while this is happening.

Every URL in the queue carries a status. Here’s what each one tells you.

• Queued. A form was found and the URL is waiting its turn.
• Processing. The URL is open in a background tab right now. Click it to see the current stage, and use Force close if a tab gets stuck.
• Sent. The form was submitted successfully. One credit was used.
• Failed. A form was found but the submission didn’t complete. No credit was used. Use Retry, or Reprocess with a different URL for that site.
• No form. contactID couldn’t find a usable contact form on the page. No credit was used. Use Retry, Open to check the site yourself, or Add to supply the direct contact page URL.
• Trash. The URL was removed from the queue. Click Restore to bring it back.

See monitoring results for reviewing sent and failed URLs after a batch finishes.

The Max Concurrent Tabs setting controls how many websites contactID works on at the same time. It ranges from 1 to 8, and defaults to 5.

The account-wide safety cap. Regardless of your tab setting, contactID caps sending at 60 submissions per minute per account, combined across all your devices. contactID self-regulates automatically to stay under this cap, so you never need to manage it yourself.

Pause and Cancel behave differently, and knowing which to use saves you time.

Pause. Halts new sends but lets tabs already in flight finish naturally. Click Resume to pick back up right where you left off, at no cost.

Cancel. Ends the batch entirely. Queued URLs that hadn’t started are marked Cancelled, while any tabs already in flight finish and record their real outcome. A cancelled batch can be resumed later from Import Jobs.

Credits either way. You’re only ever charged for forms that actually went out. Nothing is charged or reserved just for pausing or cancelling a batch.

Retries in contactID are entirely manual. There’s no automatic retry, no retry cap, no delay, and no circuit breaker deciding for you.

• Retry a single card. Open the URL in the queue and click Retry.
• Retry all. Filter the queue by Failed or No form and use Retry all to re-queue everything currently visible.
• Retry Completed Forms. Found in the run menu, this re-queues websites that were already sent to. It’s useful after you’ve changed your message and want a second pass.

Because retries never happen automatically, you stay in control of exactly when and what gets re-attempted.

contactID doesn’t use an automatic circuit breaker. Instead, it gives you the information and controls to catch a bad run yourself, before and during sending.

Before you start.

• The coverage card on the Agent tab scores how many of your queued forms your sender is likely to be able to fill.
• The deliverability check flags spammy wording in your pitch before it goes out.
• The pre-flight report shows sites with no detectable form or ones you’ve already contacted.

During the run. Pause, Resume, and Stop, together with a live success-rate readout, let you spot and fix a bad pattern early on your own terms.

Your credits stay safe regardless. Failed attempts and no-form sites never cost a credit, so there’s no financial downside to letting a batch run while you watch it.

It depends on your plan.

FREE plan. contactID automatically appends a plain line, Sent via contactID extension (no link), to every message at send time. Before adding it, contactID scans your pitch for existing signature-like text, so you never end up with the line twice.

Paid plans (Starter, Growth, Pro, Scale). Messages send with no signature at all.

Can I turn it off on the FREE plan? No. Detection cannot be disabled, but it only matches the specific signature phrasing itself, not incidental mentions of the word “extension” elsewhere in your own copy. See plans and pricing to compare plans.

contactID recognizes common bot-protection systems and deliberately does not attempt to solve or bypass any of them.

1. What’s recognized. Cloudflare Turnstile and challenge pages, hCaptcha, reCAPTCHA v2 and v3, FriendlyCaptcha, and general behavioral bot heuristics.

2. What happens when one is hit. The site is marked Failed with reason “Bot detection blocked submission.” No credit is used, and contactID won’t retry it further within that batch.

3. How to reduce it. Filter obviously bot-protected domains out of your list before you start, such as government, banking, healthcare, and major SaaS or e-commerce platforms. This keeps failure rates down without contactID needing to fight the protection. See troubleshooting for more on cleaning up a target list.