Partnerships and feedback are not support

Contact on www.oernoe.com lists partnerships@oernoe.com and feedback@oernoe.com as their own desks. It also lists support@oernoe.com for bugs, account access, and service problems. Those are not three labels on one queue. Partnerships is business mail. Feedback is product notes and suggestions. Support is operational failure. This essay is company writing about that three-way split, grounded in the live Contact page, with About’s operator lines kept in view. It does not restate every inbox on Contact as if the whole map were new.

## What Contact assigns to each desk

Support’s card is narrow: bugs, account access, and service problems. Include browser, device, and steps if you can. The address is support@oernoe.com.

Partnerships’ card is one line of job language: business and partnership mail. The address is partnerships@oernoe.com.

Feedback’s card is equally short: product notes and suggestions. The address is feedback@oernoe.com.

Contact does not say partnerships is “support for partners.” It does not say feedback is “support with a friendlier name.” It publishes different jobs. The page also says who you are writing to: Oernoe is operated by Anoepal and founded by Angel Mejia Rodriguez, and the public publisher site is www.oernoe.com. There is no contact form behind an account, no chatbot in front of the addresses, and no overnight desk. A complete message with a URL, a hostname, and a browser is worth more than a vague complaint.

Reply timing, when Contact answers the ordinary FAQ, is usually one to three working days. If a message needs a change in the product before it can be answered properly, the team will say so rather than send a holding reply. That honesty is about a small team. It is also a reason not to bury a password outage inside a partnership pitch, or a product idea inside a bug thread that needs reproduction steps.

## Support’s job is reproduction, not BD

Support exists for when a live service fails a person who already uses it, or cannot get into the account that opens those services. Contact’s FAQ steers forgotten-password cases to Forgot Password on the login page first, then to support@ if the reset mail never arrives. Account creation, per the same FAQ, is immediate on Search, Health, Chat, or AI with email and password; email verification is not required for basic access. Hostname confusion has its own answer because people land on leftover www routes and think the product is broken: articles and company pages are on www.oernoe.com; Search is search.oernoe.com; Login is account.oernoe.com; other live products have their own hosts; /login or /mail on www are leftover routes and are not the index.

That is operational triage. It needs hostname, browser, and steps. It does not need a deck. It does not need a monetization proposal. It does not need a feature wishlist with no failing URL.

About’s Anoepal line points company and operations contact at info@oernoe.com or support@oernoe.com. That is holding-company and service mail, not a reason to treat partnerships@ as a silent alias of support@. Privacy Policy section 10 and Contact’s closing process lines keep privacy@, legal@, and support@ as the recurring process trio. Partnerships and feedback sit beside that trio for ordinary company product and business mail that a rights policy should not have to staff.

## Partnerships is business mail, and it is not a sponsored-post door

Contact’s partnerships card is business and partnership mail. The FAQ on the same page answers the money question people still aim at the wrong desk: does Oernoe take advertising or sponsored posts? No. Selected long-form pages carry Google AdSense through an ad network with no contact with editorial work. The company does not sell articles, links, or reviews, and pitches for sponsored content are declined without reply.

That FAQ belongs next to partnerships@ because partnership mail is where sponsored-post fantasies arrive. Declining them without reply is a company rule, not a support outage. About’s funding section says the same refusal in publisher voice: the company does not sell account or search data, and does not sell journal articles, links, or reviews; pitches for sponsored posts are declined. Ads that do appear sit on selected finished www pages, not on Search, Health, Chat, AI, Docs, Drive, Tracker, or Account, and not on Home, About, legal pages, or the journal listing.

So partnerships@ can receive real business conversation. It cannot be used as a back door into the journal. Support@ cannot clear a pitch by “escalating” it into editorial. Hello@ and editorial standards handle factual errors on publisher pages. Partnerships handles business mail that is not a bug and not a rights request. Mixing those jobs produces unread pitches in a queue staffed for reproduction steps, or unread outages in a queue staffed for business triage.

## Feedback is product notes, not a severity field

Feedback@oernoe.com is for product notes and suggestions. That is future-facing product talk: something that works today but could work better, or something missing that a user wants named. Contact does not promise that every suggestion ships. It does promise a desk that is not pretending to be incident response.

Support needs a failing hostname and steps. Feedback needs a clear product note. If the Health workspace should keep an extra field, that can be feedback. If health.oernoe.com will not load in a named browser, that is support. If Search ranking feels wrong on one query, support may still be the first desk when the page errors; product ranking philosophy is not the same as “the host returned an error,” and Contact’s Search-removal FAQ already separates wanting a third-party page removed from Oernoe Search results from ordinary website contact. Removal needs the exact result URL and the reason. Copyright claims go through DMCA. Feedback is not a substitute for that process either.

About’s product direction line sits behind feedback without turning feedback into a founder hotline. Angel still sets product direction with a standing test: whether a feature gives people more control over their data, or less. If it is less, it does not ship. A feedback note that asks the company to sell search history into ads fails that test before it fails a ticket SLA. A feedback note that asks for clearer hostname labeling on a help page is ordinary product mail. Neither note is a password reset.

## Why the wrong desk wastes a small team

Contact is explicit that Oernoe is run by a small team. Usually one to three working days. No overnight support desk. No automated system that closes your ticket to keep a metric down. Under that constraint, misrouting is not a harmless CC.

A partnership pitch in support@ forces an operations reader to decide whether to ignore business mail or delay a lockout. A bug report in partnerships@ sits where nobody is reproducing browser steps. A product suggestion in support@ competes with account-access mail that has a clock attached for the person locked out. Feedback that is actually a privacy deletion request is worse: Contact and Privacy both say to write privacy@oernoe.com from the email on the account, say whether you want export, deletion, or both, and expect a confirm-once deletion that cannot be undone. Search listings and third-party pages are a different job again.

Hello@ exists if you are not sure which desk to use. About names hello@ for editorial mail. Contact’s FAQ says factual errors on this site go to hello@ with the page address, corrected with a note rather than edited quietly, with standards on the editorial standards page. Hello is a default under uncertainty. It is not proof that partnerships, feedback, and support are theater. If you know the job is business partnership, use partnerships@. If you know the job is a product suggestion, use feedback@. If you know the job is a bug or account failure, use support@.

## How to choose without a flowchart

Read the three cards.

Broken login on account.oernoe.com, a live product host that will not load, missing reset mail after Forgot Password: support@oernoe.com, with hostname, browser, and steps.

Business or partnership conversation that is not a sponsored-post sale into the journal: partnerships@oernoe.com. If the message is a sponsored-post pitch, Contact already says it is declined without reply.

A product note or suggestion about how a live service could work better: feedback@oernoe.com. If the note is actually “this URL is factually wrong on www,” use hello@ with the page address instead. If the note is “delete my account,” use privacy@.

Info@ remains for general site or company questions that do not fit. Legal notices still go to legal@. Privacy requests still go to privacy@. This essay’s point is only that partnerships and feedback are not support.

## What “complete message” means on each desk

Contact prefers a complete message. The contents differ by job.

For support@, complete means the failing hostname, the browser and device, and the steps that reproduce the problem. “It does not work” without a host forces the desk to guess whether www, search, account, or a product host failed. Leftover /login or /mail on www is a common false alarm Contact already names.

For partnerships@, complete means who you are and what business relationship you propose — and honesty about sponsored posts, which Contact declines without reply. A bug with a partner logo in the signature is still support.

For feedback@, complete means which product host you mean and what you want changed. Hard outages belong in support with steps. False guide sentences go to hello@ with the page address. Account export or deletion goes to privacy@ from the account email.

The usual one-to-three working day window is a reason to send once to the matching desk, not to triple-send.

## Editorial and legal edges that are still not support

Factual errors on www go to hello@oernoe.com with the page address. Contact says corrections get a note on the page rather than a quiet edit, and points at editorial standards. About says the same ownership: if a page is wrong, it is Angel’s problem as named publisher person. That is not partnerships. That is not feedback about a feature. That is not support for a failing API.

Legal notices go to legal@oernoe.com. Privacy requests go to privacy@oernoe.com from the account email. Support can help with login; it is not the rights desk. Partnerships cannot process a deletion. Feedback cannot acknowledge a legal notice. Keeping those edges visible stops partnerships and feedback from absorbing work they were never staffed to do.


## Company consistency across About and Contact

About keeps Angel as founder and named publisher person, Anoepal as holding company, free accounts, labeled paid features, and no sale of account or search data. Contact keeps the public inboxes and refuses to hide them behind a form. Partnerships and feedback exist because business mail and product notes are not incidents. Using support@ for all three jobs pretends at an omnichannel helpdesk the company does not staff.

Selected www pages may show Google ads. That fact lives in Privacy and About. It does not turn partnerships@ into an ads salesperson for journal placement. AdSense is network inventory on eligible documents. Editorial mail and business mail stay separate on purpose.

## The short rule

Partnerships@ is business and partnership mail. Feedback@ is product notes and suggestions. Support@ is bugs, account access, and service problems. Contact publishes that map. About and Privacy do not contradict it. Write the desk that matches the job. If you wrote the wrong one, send a short follow-up to the right one instead of blasting every address and calling it escalation. Partnerships and feedback are not support. The Contact page already said so; this essay only refuses to blur it.