<!-- https://nuforce360.com/help/getting-started/contact-us-public -->
# Contact Us (Public)

How to use the public Contact Us form to send a message to the NuForce team without signing in.

# Contact Us (Public)

This screen lets you send a message straight to the NuForce team without needing to sign in first. Use it when you have a question about NuForce, need help before you have an account, or want someone from the team to follow up with you directly.

## What you can do here

- Enter your name, email address, and phone number so the team knows who is reaching out and how to reply.
- Write a message describing your question, issue, or request.
- Submit the form to send it directly to NuForce support.
- See an on-screen confirmation once your message goes through, addressed to you by first name, letting you know NuForce has received it and will get back to you.

## Steps

1. Enter your full name.
2. Enter an email address you check regularly.
3. Enter a phone number where you can be reached.
4. Type your message, explaining what you need help with or want to ask.
5. Submit the form.
6. Watch for the on-screen confirmation. It tells you your message was received and that the team will follow up soon.

## Related

- /help/signup
- /help/talk-to-support

<!-- REVIEW NOTES (drafting agent could not verify):
  1. No frontend page for route /contact-us was found in the web-app repository (no app/contact-us/page.tsx, no built /out output, no rewrite). The route only exists as a catalog entry in lib/data/navigation-items.ts (name: "Contact Us (Public)"). All field names, validation, and the confirmation message are grounded in the backend action HelloHandler::onContactUs() and the matching OpenAPI operation "contactUS" (fields: name, email, phone, message, all required), not in observed on-screen UI text, so exact button labels/wording on the real page are unconfirmed.
  2. The 'Related' article paths (/help/signup, /help/talk-to-support) are inferred from adjacent entries in the same navigation catalog (Signup and Talk to Support), not confirmed to exist as actual help-center articles.
  3. Whether the phone field is genuinely required in the rendered form (vs. only in the backend validator) is unconfirmed since the form's client-side code was not found.
-->