> For the complete documentation index, see [llms.txt](https://docs.snapfix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snapfix.com/how-the-apps-work/screens/help/get-in-touch.md).

# Get in touch

{% hint style="info" %}
Draft, written by an agent and not yet checked by a person ([how to read these docs](https://docs.snapfix.com/how-to-read.md)). Platforms: web, iOS and Android. [Source on GitHub](https://github.com/snapfix/docs/blob/main/spec/screens/help/get-in-touch.md).
{% endhint %}

A form that sends a message to the Snapfix support team.

![Get in touch](https://3653879137-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsVVGa79QbcEkJ7n8srxe%2Fuploads%2Fgit-blob-4a91cbdf832ab2dab94fa1806068dc52e66997dd%2Fget-in-touch.png?alt=media)

* **Where:** web `/auth/get-in-touch`, from the "Get In Touch" button on [Help with logging in](https://docs.snapfix.com/how-the-apps-work/screens/help/login-help.md) (web\_app\_v2 @ 0989b8e685, `src/app/pages/auth/auth.routes.ts:14`). iOS: the "GET IN TOUCH" tile on the [Help Hub](https://docs.snapfix.com/how-the-apps-work/screens/help/help-hub.md), and the "GET IN TOUCH" footer of the signed-out [Help with logging in](https://docs.snapfix.com/how-the-apps-work/screens/help/login-help.md). Android: the "GET IN TOUCH" button on the Help Hub (My Profile's tab and the second Help Hub screen) and on Help with logging in; there the form replaces the list on the same screen.
* **Who:** web: signed-out users only. The `/auth` routes send a signed-in user to `/fix` (`src/app/services/auth/auth-guard/auth-signin/auth-signin.guard.ts:13-16`). Signed-in web users get the side menu's "Contact support", which opens the public help center instead ([Help Hub](https://docs.snapfix.com/how-the-apps-work/screens/help/help-hub.md)) \[[ASK-195](https://github.com/snapfix/docs/blob/main/ASK.md#ask-195-should-signed-in-web-users-get-the-in-app-contact-form)]. iOS and Android: signed-in users from the Help Hub and signed-out users from the sign-in help; the app picks the endpoint by the sign-in state.
* **Feature:** [Contacting support](https://docs.snapfix.com/product/features/help/contact-support.md)

The server stores each message and emails it to the support mailbox. It creates no HubSpot ticket \[[ASK-189](https://github.com/snapfix/docs/blob/main/ASK.md#ask-189-should-contact-form-messages-create-a-hubspot-ticket)], and the email has no reply-to address, so a reply doesn't reach the person who wrote. The stored row, the email and its sender are in the [Help API](https://docs.snapfix.com/engineering-reference/api/help.md#contact-form).

## Layout

### Web

1. **Header.** A back arrow with the tooltip "Back", and the HelpHub logo.
2. **Title and text.** "Get in touch", then "Have questions, feedback, or requests? We'd love to hear from you! Use this form to reach out, and our team will get back to you soon."
3. **Email line.** "Alternatively, you can email us directly at <support@snapfix.com>." The address is a `mailto:` link \[[ASK-192](https://github.com/snapfix/docs/blob/main/ASK.md#ask-192-which-support-address-should-the-apps-show-support-or-customersupport)].
4. **Form.** "First name", "Last name", "Email", "Subject" and "Message", each with a placeholder ending in "\*". The message is a text area of three rows. No field sets a length limit.
5. **Button.** "Get In Touch" (the string "GET IN TOUCH" in title case), with an envelope icon (web\_app\_v2 @ 0989b8e685, `src/app/pages/auth/get-in-touch/get-in-touch.component.html:13-74`).

### iOS

1. **Header.** "GET IN TOUCH" with a back button.
2. **Title and text.** "Get in touch", then the web's text and "Alternatively, you can email us directly at <support@snapfix.com>.", where the address opens the mail app (ios @ aa31967ac8, `SnapFix/GetInTouchVC.swift:41-67`).
3. **Form.** "First name", "Last name", "Email address", "Subject" and "Message". The storyboard's design-time labels ("First Name", "Last Name", "Email") are replaced from the string file when the screen loads (`SnapFix/Storyboards/HelpHub.storyboard:1144`, `:1182`, `:1220`). The message box grows with its text.
4. **Button.** "Submit".

### Android

The Help Hub and the sign-in help use the same layout (android @ 86068bfeea, `app/src/main/res/layout/layout_get_in_touch_main.xml:25-201`):

1. **Title and text.** "Get in touch", the same text, and "Alternatively, you can email us directly at" with "<support@snapfix.com>", which opens the mail app.
2. **Form.** "First Name", "Last Name", "Email", "Subject" and "Message".
3. **Button.** "SUBMIT" (the string "Submit", shown in capitals).

## Inputs

All five fields are required on every platform. The send button stays disabled until the form is valid, so a missing field shows no message.

| Field      | Type            | Required | Default | Rules and messages                                                                                                                                                                                                                                                                                                                                                            |
| ---------- | --------------- | -------- | ------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| First name | Text            | Yes      | Empty   | Web: not empty; spaces alone pass. iOS: not blank after trimming. Android: not blank; up to 100 characters.                                                                                                                                                                                                                                                                   |
| Last name  | Text            | Yes      | Empty   | As First name.                                                                                                                                                                                                                                                                                                                                                                |
| Email      | Email           | Yes      | Empty   | Web: an email address; "Please enter a valid email" under the field once it has been left with a wrong address. iOS: a simple address pattern after trimming; no message. Android: the platform's address pattern; up to 100 characters; no message. The web field is an email field, iOS opens the default keyboard, and Android a text keyboard that capitalises each word. |
| Subject    | Text            | Yes      | Empty   | Web: not empty. iOS: not blank after trimming. Android: not blank; the keyboard capitalises each word.                                                                                                                                                                                                                                                                        |
| Message    | Multi-line text | Yes      | Empty   | Web and iOS: a message of spaces alone passes. Android: not blank; the keyboard capitalises each word. No platform limits the length. The server trims every field, then refuses an empty message and one over 5,000 characters ([Contact form](https://docs.snapfix.com/engineering-reference/api/help.md#contact-form)).                                                    |

The checks are in web\_app\_v2 @ 0989b8e685, `src/app/pages/auth/get-in-touch/get-in-touch.component.ts:74-82`; ios @ aa31967ac8, `SnapFix/GetInTouchVC.swift:84-101` and `Extensions/Textfield+Conditions.swift:18-24`, `:37-44`; android @ 86068bfeea, `app/src/main/java/gmail/com/snapfixapp/activity/HelpHubActivity.kt:158-171` and `layout_get_in_touch_main.xml:79`, `:104`, `:130-131`, `:156`, `:180`. iOS trims all five values before it sends them; the web and Android send them as typed (`SnapFix/GetInTouchVC.swift:115-119`).

## Actions

| Action                     | Who                                                                       | What happens                                                                                                                                                                                                                                                                                                                                                                              | API                                                                                                                                                                                                                                           |
| -------------------------- | ------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Send (web, "Get In Touch") | Signed-out users                                                          | Logs the analytics event `get_in_touch_submit` with the five typed values, before it checks the form (`get-in-touch.component.ts:48-53`). Sends the form; the button shows a spinner, then a checkmark for 1.5 seconds, and the form clears. Nothing else confirms the send. The form asks for no CAPTCHA.                                                                                | [`POST /v1/guest/help-hub`](https://docs.snapfix.com/engineering-reference/api/help.md#post-v1guesthelp-hub), with the shared guest login                                                                                                     |
| Send (iOS, "Submit")       | Signed-in users from the Help Hub; signed-out users from the sign-in help | Logs `get_in_touch_submit` with no values, checks the connection, shows "Refreshing..." and sends the trimmed values. On success: "Thank you for getting in touch! We have received your message and will get back to you shortly." with "Ok", then the screen closes (`SnapFix/GetInTouchVC.swift:104-135`).                                                                             | Signed in: [`POST /v1/app/help-hub`](https://docs.snapfix.com/engineering-reference/api/help.md#post-v1apphelp-hub). Signed out: [`POST /v1/guest/help-hub`](https://docs.snapfix.com/engineering-reference/api/help.md#post-v1guesthelp-hub) |
| Send (Android, "SUBMIT")   | As on iOS                                                                 | Checks the connection, shows "Please wait..." and sends the values as typed; no analytics event. On success: the same thank-you text, written in the code, and its button returns to the Help Hub rows or the sign-in help list. After an expired session it gets a new token and sends again (`HelpHubActivity.kt:365-405`).                                                             | As on iOS                                                                                                                                                                                                                                     |
| Support address            | Everyone on the form                                                      | Opens the mail app addressed to <support@snapfix.com> (web: a `mailto:` link) \[[ASK-192](https://github.com/snapfix/docs/blob/main/ASK.md#ask-192-which-support-address-should-the-apps-show-support-or-customersupport)]. On Android, with no mail app nothing happens, and if starting one fails the alert says "No email app founded in this device." (`HelpHubActivity.kt:173-187`). | None                                                                                                                                                                                                                                          |
| Back (web)                 | Signed-out users                                                          | Goes to the previous page, or to `/auth/help-hub-faq` when none is stored (`get-in-touch.component.ts:44-46`).                                                                                                                                                                                                                                                                            | None                                                                                                                                                                                                                                          |
| Back (iOS)                 | Everyone on the form                                                      | Closes the screen.                                                                                                                                                                                                                                                                                                                                                                        | None                                                                                                                                                                                                                                          |
| Back (Android)             | Everyone on the form                                                      | Hides the form: back to the Help Hub rows, or to the sign-in help list (`MyProfileActivity.kt:2798-2806`, `app/src/main/java/gmail/com/snapfixapp/activity/LoginHelpHubActivity.kt:213-219`).                                                                                                                                                                                             | None                                                                                                                                                                                                                                          |

## States

* **Loading:** web: a spinner on the disabled button. iOS: a "Refreshing..." overlay. Android: a "Please wait..." dialog.
* **Success:** see the send actions above.
* **Error:**
  * Web: the shared alert shows the API's message, or "Internal server error" when there is none, and the form keeps its values (web\_app\_v2 @ 0989b8e685, `src/app/services/http/http.service.ts:51-58`, `:243-251`). A refused guest login (`401`) shows no alert: the web treats it as an expired session, signs the visitor out and opens the sign-in page, so the message is lost.
  * iOS: an alert with the API's message, such as the first failed rule of a `422`; "Something went wrong. Please try again." when the answer has no message or never arrives (ios @ aa31967ac8, `SnapFix/GetInTouchVC.swift:125-141`, `APIManagers/APIManager.swift:2551-2591`, `:3056-3085`).
  * Android: the API's message for a `422` or for an answer marked as failed; "Something went wrong. Please try again." for other errors; an alert with no text when the request gets no answer (android @ 86068bfeea, `app/src/main/java/gmail/com/snapfixapp/network/ParsingManager.java:381-440`).
  * Server-side failures, such as a server without the HubSpot token answering every send with `500`, are listed in the [Help API](https://docs.snapfix.com/engineering-reference/api/help.md#post-v1apphelp-hub).
* **No permission:** none in the apps. On the web a signed-in user never reaches the page.
* **Offline (mobile):** iOS shows "No Connection" with "You must be connected to the Internet to carry out this task. Please connect and try again."; Android shows the same message without a title. Nothing is sent. The web has no connection check: the send fails and the shared alert says "Internal server error".

## Dialogs and sheets

Alerts only: the success and error alerts above.

## Platform differences

| Topic                       | Web                                                                                                                                                 | iOS                                        | Android                            |
| --------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------ | ---------------------------------- |
| Who can send                | Signed-out users only \[[ASK-195](https://github.com/snapfix/docs/blob/main/ASK.md#ask-195-should-signed-in-web-users-get-the-in-app-contact-form)] | Signed-in and signed-out users             | Signed-in and signed-out users     |
| Button                      | "Get In Touch"                                                                                                                                      | "Submit"                                   | "SUBMIT"                           |
| After a successful send     | A checkmark for 1.5 seconds, then the form clears                                                                                                   | Thank-you alert, then back                 | Thank-you alert, then back         |
| Field labels                | "First name", "Last name", "Email"                                                                                                                  | "First name", "Last name", "Email address" | "First Name", "Last Name", "Email" |
| Trimming before send        | No                                                                                                                                                  | Yes                                        | No                                 |
| Spaces alone in the message | Passes                                                                                                                                              | Passes                                     | Refused                            |
| Length limits on screen     | None                                                                                                                                                | None                                       | 100 on the names and the email     |
| Analytics on send           | The five values, before the check                                                                                                                   | The event without values                   | None                               |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.snapfix.com/how-the-apps-work/screens/help/get-in-touch.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
