Sending and receiving for your outreach engine, with paced delivery and workspace opt-outs.
Your campaign tool handles sequences. InboxIt sends and receives.hello@yourbrand.example
Email that fits your app.Hi Alex,
Your emails should feel like part of your product. Send on your domain, use your own design and keep the reply connected.
Joshua
The InboxIt team
“Can we use our own domain?”
A visual example of an integration — not a built-in InboxIt campaign builder.
Define your audience, recipient controls and reply workflow before choosing outreach tooling.
Connect your campaign engine to the outreach API.
The direction is sending and receiving infrastructure for your outreach tools. Campaign sequences, contact lists and automated follow-ups are not built into InboxIt today.
Connect your campaign engine to the InboxIt sending and receiving API. Outreach sends include pacing, unsubscribe headers and suppression checks. Your application owns lead selection, sequences, scheduling and stopping follow-ups when someone replies.
Document why each contact is relevant and how their details were obtained. A publicly listed address alone does not establish that a recipient wants promotional messages.
Before choosing an outreach tool, check that it supports opt-outs, suppression, reply handling and the rules that apply to your recipients. Use the workspace suppression API and built-in or custom unsubscribe flow.
Decide who will monitor replies, how requests will be handled and when follow-ups must stop. Delivery infrastructure alone does not create a responsible outreach workflow.
Use the API from your own campaign engine. The workspace does not provide a customer sequence editor; your integration controls schedules and stop-on-reply.
Yes. Verified-domain transactional sending, incoming replies and email testing are available. Explore those solutions for supported workflows.
Use the contact page to describe your audience, sending volume and required controls. We can clarify whether the current product fits.
Start with 1,000 outbound emails and a separate 1,000 incoming emails per calendar month. Daily sending, storage and retention limits apply. See pricing and limits for the full allowance.
Welcome messages, account notifications and password resets. Put email inside your application workflow.
Explore solutionGive incoming customer messages a place to land, and let your application retrieve the conversation.
Explore solutionRun signup, verification and password-reset scenarios without putting test messages in someone’s personal inbox.
Explore solutionLet an agent retrieve emails, read verification messages and continue its workflow through the API.
Explore solutionConnect events in your product to useful emails: an account update, a completed task or a next step.
Explore solutionYour domain. Your design. Send emails and receive replies with InboxIt.
Start free1,000 emails / month · No card requiredStart sending after confirming your email. No manual approval required.