Each product gets its own inbound @loop.orkap.com address. Partnership requests land in the right place — automatically. No labels, no manual triage, no replies from the wrong account.
Free forever for 1 product · 14-day full access · No credit card
IMAGE #3: Alias setup screen
Product list with each product's @loop.orkap.com alias — e.g. wp-caching-plugin@, figma-ui-kit@, notion-pro@ — and a copy button next to each.
Short answer
A product-scoped inbox is a dedicated inbound email address for one product. In Orkap, every product you create gets its own @loop.orkap.com alias, so partnership requests, affiliate questions, and review pitches self-route into that product's workspace — with its templates, pipeline, and history already attached.
When you sell five products and run partnership outreach for all of them, every inbound reply funnels into one inbox — and you become the router.
A collaboration request for your WP Caching Plugin and an affiliate pitch for your Figma UI Kit arrive in the same shared inbox. You read each email, figure out which product it’s about, and sort it by hand.
Multiply manual sorting by 40–60 inbound requests a month and you’ve built a recurring chore nobody signed up for — before a single conversation actually moves forward.
The product’s templates, pipeline stage, and prior history are in another tab, another tool, or someone’s memory. Every reply starts from scratch.
Create a product and get a dedicated address — [email protected]. Publish it anywhere partnership inquiries originate: your product page, press kit, affiliate sign-up, or WordPress.org listing.
Email to that alias lands in that product’s workspace. No labels, no manual sorting, no guessing. A pitch for your Notion Template never touches your SaaS tool’s inbox.
The product’s templates, pipeline, and prior history are right there when you open the thread — so you reply with the right pricing, the right terms, and the right history every time.
IMAGE #2: Self-routing inbound
An email sent to a product alias arriving directly in that product's workspace, with the product's templates and pipeline visible in the same view. (Static or animated.)
A pitch for your Figma UI Kit and a request for your WP Caching Plugin never touch. Zero cross-contamination — a guarantee no campaign-first tool can make, because none of them model "product" at all.
Product page
Footer + contact section
WordPress.org listing
Support & contact links
Press / media kit
Partnership contact line
Affiliate sign-up
Program questions address
Publish the alias wherever partnership inquiries originate — routing happens on arrival.
Each product carries its own deal stages — no shared mess, no manual tagging.
Explore →Route partnership email through your own domain or a branded alias, per product.
Explore →Scope teammates to specific products so nobody replies from the wrong account.
Explore →How product-scoped inboxes work before you create your first one.
Each product you create gets a dedicated alias — for example [email protected]. You publish it wherever partnership inquiries start, and every reply self-routes into that product’s workspace.
No. Routing is determined by the alias the email was sent to, so inbound lands in the correct product workspace automatically — no labels, no rules to maintain, no manual sorting.
No. Because every alias belongs to exactly one product, a request for your Figma UI Kit and a pitch for your WP Caching Plugin stay fully separated. Templates, pipeline, and history follow the product, not a shared account.
The free plan includes one product inbox forever, and paid plans add more — three on Maker, ten on Studio, and unlimited on Portfolio. You can start free and add products as your portfolio grows.
Start free with one product, one seat, 50 contacts a month — no time limit, no credit card. Bring your whole portfolio in whenever you’re ready.