Stop on reply and sending windows

Two rules govern every send in Neuraware, and neither is configurable — because both protect your prospects' experience and your accounts at the same time.

Stop on reply, everywhere

The moment a prospect replies, their remaining sequence steps are cancelled — the invitation follow-up, the planned reminders, everything. This applies across the whole workspace: a prospect who answered one campaign is not chased by another.

Why it matters: following up with someone who already answered is the clearest spam signal there is, and the fastest way to burn goodwill. Once a prospect replies, the conversation belongs in the inbox — read, classified, with a draft prepared when a reply is worth sending.

Sending windows: business hours, human spacing

Sends go out during business hours in each account's working window. Actions are spaced irregularly through the day, minutes apart, the way a person works — never in bursts, never at fixed intervals.

At night, the agent works without sending: it qualifies new prospects, sorts the replies that arrived after hours, and prepares the messages that will go out the next day. Your outreach advances around the clock; your accounts only act at human hours.

Delays between steps

Between steps of a sequence you set delays in days — giving a prospect time to see an invitation, accept it, and read a message before the next one. Combined with stop on reply, delays are what makes a sequence feel like a person following up rather than a machine emptying a queue.

What this means for volume

These rules cost some raw throughput, deliberately. The account-level limits that complete the picture — daily quotas, hard caps, ramp-up — are documented in Accounts & safety.