Talk to us.

A single contact form looks tidy and routes badly. The asymmetry is concrete: a security disclosure has a 7-day window, a research-collaboration proposal needs the attention of a researcher in the relevant pillar, a press inquiry needs to clear the press protocol before any response goes out, and a partnership conversation routes to a different person on a different schedule. Mixing them in a single intake means each one waits behind the triage of all the others. We publish seven inboxes — one per category — because routing is the substance of being responsive, not its enemy.

The inboxes are watched on different cadences. The security inbox is monitored continuously and is the only channel whose response window is defined by policy rather than by capacity. The press inbox is checked at least once per business day. Research, partnerships, and careers run on a two-business-day target. General and privacy run on a one-week target. The targets are honest, not aspirational; we miss them occasionally and the correct fix is to write a follow-up rather than to assume the message was lost.

The messages we read fastest are the ones that name the ask, the deadline, and the relevant context in the first three lines. The ones that take longest are the ones whose ask is buried below a long preamble. The guidance below applies per channel.

• Research collaboration. Open with the proposed collaboration in one sentence; name the Apik pillar or project; attach (or link) one piece of relevant prior work; state whether you have a timeline. We respond on substance even when we decline. Route to research@apiksystems.com.
• Press. Open with the outlet, the angle, and the deadline. We can typically turn around an on-record response or a brief background conversation within two business days; tighter windows depend on availability. Route to press@apiksystems.com.
• Partnerships. Open with the proposed pilot or integration shape; name the surface (Senwitt, Brello AI, Surfacedd, or one of the research projects); state the commercial frame. Partnership conversations move faster when the Responsible Development Policy implications are addressed at the start. Route to partnerships@apiksystems.com.
• Security & safety. Vulnerability disclosures, incident reports, or safety concerns about deployed Apik systems. Route to security@apiksystems.com. The inbox accepts PGP-encrypted mail; key fingerprint is available on request. Disclosure follows the window documented in the Responsible Development Policy.
• Careers. Application packets per the careers page: cover letter making a specific argument, two to three pieces of prior work, references. Route to careers@apiksystems.com.
• Privacy. Data-subject requests, deletion requests, and policy-clarification questions. Route to privacy@apiksystems.com. We operate on the strict end of the data-discipline spectrum (see the products page); most data-subject requests resolve within the jurisdictional window.
• General. The catch-all. Use this when the channel above is unclear; we re-route internally and respond from the relevant inbox. Route to hello@apiksystems.com.

We read every message. We respond to most of them. Exceptions: bulk outreach that does not name a specific Apik person or pillar, vendor pitches outside our active procurement areas, and unsolicited investment inquiries — the last because Apik is not currently raising and a polite non-response is more honest than a templated one. If you have written and not heard back inside the relevant cadence window, a follow-up is welcome and is taken as a signal that the message was load-bearing rather than casual.