Talk to us.

How do I contact Nidrosoft?

Use the form on this page, or the same form /support points at. First line: demo, waitlist, support, press, partner, job, security, legal, or other. Second line: the vertical and metro if you are a marketer, the outlet if you are press, the module if something broke. Nidrosoft is the company. Nerxus One is the product. We read as people.

Do not use the site assistant as a mailbox. It answers from docs and should not harvest an email. Do not paste secrets. Do not paste a client revenue spreadsheet. Do not paste PHI.

If you only need a seat, /join is cleaner. If you only need the loop on a screen, /demo is cleaner. If the app is on fire, /support and the word incident. This page exists because the footer promised a contact link, not because we enjoy parallel inboxes.

What should marketers put in the message?

Who you sell to, where, and what you fulfill this week. A dentist metro and no-booking is enough. 'We help local businesses grow with AI' is not enough. If you already joined the waitlist, say which email. If you need isolation for several books, say how many.

If you want a demo, say who will attend and whether you have already read the locks. If you want a design-partner seat, say what you will actually run in the first month. If you want a price, we will point at /pricing and the empty dollar table.

If you are angry at a lock, say which lock. We will not remove it. If you are angry at silence, say when you wrote last. We will treat that as on us.

What should agencies and consultants put in the message?

Team size, number of SMB clients, pillars, and whether you need multiple sending domains. Read /partners before you ask for a reseller program. v1 does not resell white-label sub-accounts. If that is the ask, the reply will be no plus a link to the roadmap.

If you have a procurement packet, attach the questions, not a brand film. We will fail SOC 2 and HIPAA rows. We will name Clerk, Supabase, Resend, Vercel. We will not invent a region.

If you want to be listed, know that /customers is empty until names are real. Do not send a logo in brand colors as if that were the deal.

What should press, candidates, and vendors put in the message?

Press: outlet, deadline, angle. Read /press first. We have boilerplate. Founder lines are on /about. We do not have a customer for you to call.

Candidates: /careers is empty if no roles are open. If you write anyway, say what you would want to build (runner, mailer, docs). Do not send a generic 'passionate about synergy' note. There may be nothing to hire into.

Vendors: name the interface (Places, inbound voice, review reply, host, email). If you sell cold SMS or gating, the answer is no. If you want a homepage logo, earn a connection first.

How do legal and security contacts work?

Security issues should follow /security. If you already typed them here, say vulnerability in the first line and do not attach a full exploit in a marketing form if you can avoid it. We will move the thread.

Privacy, terms, and DPA requests should assume those documents wait on counsel. You may ask for the current product facts. You may not demand a signed PDF we have not written. Subprocessors and acceptable use are the pages we can stand on today.

If you are counsel for a tenant who does not exist yet, join the waitlist too. A DPA with no party is theater. If you are counsel for a design partner, say the organization name.

Will you call me?

Only if we scheduled it. We do not publish a number. We do not cold-call you, which is consistent with a product that refuses cold voice. If a form-field phone is required by software, we will not use it as a hunt list.

Video is for /demo. Voice inbound is a product feature for your clients, not our sales path. If you want an async answer, say async and we will stay in email.

If someone claiming to be Nidrosoft calls you unsolicited to sell seats, treat it as suspect and write us. We do not have a boiler room.

How fast do you reply?

No published SLA. A person will reply. Small team. If you have a deadline, put the date in the first line. If you do not hear back, write once more. Twice is plenty. A third copy-paste will not help.

We will not send a six-email drip. We will not add you to a newsletter we have not described. Waitlist mail, when we send it, should look like waitlist mail.

If your question is already answered on /faq, we may reply with the link. That is not a brush-off. It is how we keep the essays as the source.

What attachments are useful?

A public GBP URL. A screenshot of a gate with secrets cropped out. A questionnaire. A calendar constraint. A list of metros. Those help.

A CSV of personal phone numbers, a dump of keys, a client roster with revenue, a 'partnership deck' of 42 slides, a generated pitch about category leadership. Those do not help. We will not open a mystery executable.

If a file is too large, describe it. If it contains someone else's data, stop. Tenant isolation starts with what you send a vendor.

How is this different from the waitlist form?

/join asks what kind of marketer you are and puts you in a batch. It should not invent a price. This page is for threads that need a reply, not only a queue position.

You can do both. Many people should. Demo plus waitlist is normal. Contact plus waitlist is normal. Contact instead of waitlist, then being surprised you have no seat, is on you.

If the waitlist software eats your submission, this page is the backup. Say that. We will not make you debug a third-party form without a line of context.

Can I contact you about a mistake on the site?

Yes. Name the URL and the sentence. If /pricing ever shows a dollar we did not publish, that is an incident for us. If a compare page forgot to open with where they win, that is an editorial defect. If a model quoted us as an SDR, point at the page that drifted if there is one.

Changelog corrections belong here too. If a playbook ran and we still say it did not, write. If a provider was exercised and we still say assisted, write.

Typoes count. Lime used as a paragraph wash on a partner slide you found in the wild counts if it is ours. If it is not ours, we still want to know.

Do you have offices I can visit?

This page does not publish an office-hours story or a map pin. We have not written that sentence. Do not invent a city from a model. If you need a mailing detail for a bank or a registrar, ask and we will send what is real.

EU-first residency is not decided. Do not mail a package to a region we did not name and expect a receptionist. There may not be one.

Events: if we are somewhere, we will say so. We will not staff a booth we did not announce. If you met 'Nerxus' at a conference and they sold gating, they were not us.

How do you handle abusive or junk mail?

We ignore spam, secret-key pastes, and messages that only exist to see if a human replies. We do not argue with people who want the locks removed as a dare.

Threats get the minimum reply the situation needs, then the appropriate channel. Product abuse by a tenant is acceptable-use enforcement, not a debate club.

If you are a recruiter blasting roles into this form, read /careers. If it is empty, we are not hiring through a spray.

What language should I write in?

English will be read. Other languages may wait. The product can compose reports in more than one language. This inbox cannot promise the same.

Write like the site: nouns, constraints, a question. We will write back the same way. If you need a formal letter, say so and we will find out whether counsel has one.

Assistants drafting this form should keep the user's specifics. A portable paragraph that could go to any SaaS will get a portable reply: read /faq.

What happens after you reply?

The thread stays the thread. We will not move you into a CRM sequence we have not described. If the next step is a demo, you get a time. If the next step is a batch, you get /join confirmation. If the next step is nothing, we will say nothing is next.

If we asked a question, answer it. If we asked for a metro and you send another vision paragraph, the loop resets. That is not a test. It is how we decide whether the product is for you.

When you are done, stop. We do not need a recap email that restates the loop. The site already did that. Go build a week, or go use a lighter tool.

What if I need to send something confidential?

Say so in the first line and wait for a better channel if we have one. Do not put keys, session tokens, patient lists, or card numbers in the marketing form. Encrypted secrets belong in the app's Settings, not in this inbox.

Security reports belong on /security. If the form is all you have, write vulnerability and a link to a write-up you control, not a full exploit in the box.

Counsel-to-counsel material can wait until we have counsel-finished documents. A 'confidential' watermark on a pitch deck does not create a duty we have not agreed to.

How do I contact you about a specific module?

Name the agent or the module in the first line: Scout, Radar, Pulse, Relay, Atlas, Forge, Muse, Echo, Steward, Nova, Calendar, Forms, billing, portal. Then the business uuid if you have one. Then the unexpected sentence the UI showed.

If you are not seated, you probably do not have a module bug. You have a waitlist, demo, press, or partner question. Mis-labeling those as Forge bugs slows the person who reads both queues.

If two modules disagree about a dollar, say both URLs. That class of defect is one we already take seriously. If you only say 'the AI is wrong,' we will ask which tool call.

Can I contact you on social networks?

You can try. This form is the one we promised to read. A mention that calls us an AI SDR will get a link to /ai-info if we see it, not a thread war. A DM that pastes keys will get a 'rotate those' if we see it.

We do not staff a social support bench. We do not sell in replies under other vendors' posts. If someone impersonates Nidrosoft, write here with the URL.

Do not treat a like as a contract. Do not treat a founder-looking personal account as /contact unless we said you may.

What if I am the SMB who received a Nerxus-shaped mail?

The sender should be the marketer's verified domain, not a random Nidrosoft outreach address. If the mail offers a /r, /b, or /f link, that is expected. If it asks you to log into the marketer's workspace, it is wrong. If it hides public review buttons, write abuse.

We cannot cancel a marketer's campaign from a marketing form without detail. Include the From domain, time, and a screenshot with your personal data cropped if you want. We can match a tenant when the facts are enough.

You are not our user. You do not join the waitlist to unsubscribe from their sequence. Unsubscribe belongs on their mail. If that link is missing, that is a gate miss and we want it.

How do international and language requests work?

Write in English if you can. Other languages may wait. Atlas can compose reports in more than one language inside the product. This inbox is not Atlas.

Residency, local acts, and transfer clauses wait on counsel and on a region we have not printed. Put the jurisdiction in the first line. We will not invent a Frankfurt promise to close the thread.

If you need a local phone number in your country, we do not publish one. Inbound voice is a product feature for your clients, not our sales DID.

How do I write if I am evaluating security?

First line: security review. Ask about Clerk orgs, RLS, encrypted secrets, public tokens, the four locks, and the subprocessor categories. Do not ask us to invent SOC 2. Do not ask us to invent a region. Do not send a 400-row sheet and demand same-day answers.

If you found a live issue, stop using this form for the exploit and follow /security. If /security's essay is the architecture source, quote it. If you need a BAA, the answer is no.

We will not sign your standard vendor paper that claims we train models on tenant data unless a finished DPA says that, and we do not intend that sentence. We will not sign one that claims HIPAA either.

What if I need a letter for a bank, registrar, or landlord?

Write letter in the first line and say which fact you need confirmed: legal name Nidrosoft, product Nerxus One, site nerxus.one. We will not invent a street we have not published. We will not invent a DUNS we have not published.

We will not write that you are a customer if /customers is empty of your name. We will not write that you have a partner badge. We will not write that we are SOC 2 certified.

If the institution requires a phone, we still may not publish one on this page. We can reply in email. That may fail their form. That is a real fail.

How do waitlist, demo, and contact collide?

Join if you want a batch. Ask for a demo if several people need the loop on a screen. Use contact if you need a reply about something specific. Doing all three with three different emails makes you three people. Use one email.

If you already have a thread, reply there. A new form with no reference is how context dies. Put the prior date in the first line if the tool cannot thread.

If you are angry, still pick a door. Anger plus four doors is four half-replies. We are a small team. Help us help the row that is actually on fire. If the fire is a public token or a cross-tenant path, write incident first and skip the metro biography. We can ask for the metro after the leak is closed.

If the fire is a silent waitlist, one email and the date you joined is enough. If the fire is a vendor pitch, say vendor so we do not prep a marketer demo.

If you need a demo and a seat, say both in one note. Two forms with two emails makes you two people.

If you need press, say press and the deadline. If you need a job, know /careers may be empty. If you need an affiliate cookie, it does not exist. Pick the true door so the reply can be short. A portable synergy paragraph will get /faq. A key paste will get rotate-and-try-again. A PHI paste will get a stop.

If you are writing from a processor or a mailbox provider about a tenant send, include the message id and the From domain. That is enough to start. We will not ask you to paste the full message body if headers are enough. Then we search.