A reply is matched to the email it answers by its message ids, so one from an alias, a colleague or the person’s other address still counts for the person you emailed. It stops their sequence, or everyone’s at their company if you choose. Out-of-office auto-replies stop nothing.

• Gmail and Microsoft 365 read through their APIs, other mailboxes over IMAP
• Bounce reports read from the inbox and the address suppressed
• A campaign’s lead drawer shows the conversation on every plan

Switch it on and it labels each reply (interested, meeting request, objection, referral, not interested, out of office, unsubscribe), then acts: an interested reply opens a deal, makes a task and drafts your answer for approval; an unsubscribe is suppressed; an out-of-office resumes the sequence on the return date.

• Runs on your own Anthropic or OpenAI-compatible key
• Drafts wait for your approval unless you put an intent on autopilot
• The sender sends, never the model

Each endpoint is a URL with its own token. Post JSON (one lead, a list, or leads under a key you name) or a plain form; map the fields once, or let their names match. People already in the workspace are not added twice, and each new person can start a workflow.

• Up to 500 leads a request and 20 endpoints a workspace
• A hosted form per endpoint, on its own link, to share or embed with one line of code
• The last 200 requests kept, with the keys each one carried
• Rotate a URL or switch it off at any time