DOCS/Platform Docs/Support/Contact

Contact

Use the contact form first. The email address, optional configured phone number (or callback-scheduling note), and enterprise-support note on the page are fallback paths, not equal primary workflows.

Use this guide when you need to send a tracked support request through the live contact page.

The live Yoba Systems contact form with the required request fields visible.
Use the public contact form as the primary support intake path.

Step-By-Step

  1. Open the marketing site Contact page.
  2. Fill in your name, email address, and message. Optionally add your organization, select Service_Type, and choose Priority_Level to help route the request.
  3. In the message, explain the issue, the goal, and any relevant org or environment context that would help someone reproduce or route the problem.
  4. Submit the form and wait for the page to finish transmitting the request.
  5. Confirm the success screen changes to Transmission_Received.
  6. Record the visible REF: reference ID shown on the success state.
  7. Read the response-time message shown on the confirmation screen. Without a selected priority the fallback is 24 hours; a selected priority uses its displayed ETA.

What To Expect

  • The success state is a full-page confirmation, not an inline toast.
  • The reference ID appears below the response-time message as REF: MSG-XXXXXXXX. It normally comes from the API, but the UI generates a fallback ID if a successful response omits one; the displayed ID alone is not proof of a stored submission.
  • In production, the form defaults to https://auth.yoba.systems/api/contact, or the configured VITE_AUTH_URL plus /api/contact. An explicit VITE_API_URL overrides the base (the form appends /contact); include /api when targeting the auth-worker. Development keeps the existing https://api.yoba.systems/contact default unless overridden.
  • For priority enterprise support, contact your assigned account operator or use the public contact form. Dashboard ticketing is not implemented.
  • The page shows a response-time message based on the selected priority, or a 24-hour fallback when no priority was selected. This is the UI estimate, not a separately verified support SLA.
The Transmission_Received success panel after a public contact request is submitted.
Record the visible reference ID from the success state before leaving the page.

If You Get Stuck

  • If the form shows validation errors, correct the highlighted fields and submit again.
  • If the page reports that it is unable to submit the message right now, retry once after a short pause.
  • If repeated retries fail and the request is time-sensitive, use the fallback email or phone details shown on the contact page.
  • If you have an assigned enterprise operator, use that path only when your support agreement requires it.

Next Step

Continue to Newsletter for the follow-on communication docs that cover updates, confirmations, and unsubscribe paths.