> 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/onboarding/let-us-help.md).

# Let us help you

{% 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: iOS and Android. [Source on GitHub](https://github.com/snapfix/docs/blob/main/spec/screens/onboarding/let-us-help.md).
{% endhint %}

Describe the challenges Snapfix should solve, and opt in to be contacted by the Snapfix team.

* **Where:** iOS and Android: setup step 4, reached only from "I don’t know yet" on [Work types](https://docs.snapfix.com/how-the-apps-work/screens/onboarding/work-types.md). "Next" on work types and the join path skip it. Android sets its bar to 80; iOS's bar is fixed at 0.65.
* **Who:** people starting a site without work types, in the app's setup flow, which the current apps do not open ([Start or join](https://docs.snapfix.com/how-the-apps-work/screens/onboarding/start-or-join.md)).
* **Feature:** [Site setup in the app](https://docs.snapfix.com/product/features/onboarding/site-setup.md)

The note and the tick travel with the setup and are sent as `notes` and `notify_snapfix_team` with [`?action=create_parent_without_templates`](https://docs.snapfix.com/engineering-reference/api/onboarding.md#post-actioncreate_parent_without_templates) on [Configuring Snapfix](https://docs.snapfix.com/how-the-apps-work/screens/onboarding/configuring.md). That call emails the Snapfix team (`register@snapfix.com`) the person's contact details, the company name, industry, role, note and opt-in on every call, ticked or not, and the screen does not say so \[[ASK-39](https://github.com/snapfix/docs/blob/main/ASK.md#ask-39-is-the-apps-setup-flow-retired)].

## Layout

1. A back arrow at the top left, and the Snapfix logo.
2. "Let us help you", "Explain the challenges you like Snapfix to solve for your company or team." and "Our team of experts will reach out to you to discuss your use case and can help you get set up."
3. A multi-line text box. Its placeholder on iOS is " e.g. As a fast growing comany I want to ensure that each member of the team is aware of the tasks that need to be completed." (leading space and "comany" as in the app); on Android it is "e.g. As a fast growing company I want to ensure that each member of the team is aware of the tasks that need to be completed."
4. A tick box: "Snapfix can reach out to me to discuss my use case."
5. "Next", disabled until the box holds text.

## Inputs

| Field                                                 | Type            | Required | Default    | Rules and messages                                                                                                                                                                                                       |
| ----------------------------------------------------- | --------------- | -------- | ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Challenges                                            | Multi-line text | Yes      | Empty      | No message: "Next" just stays disabled. iOS ignores spaces and line breaks for this and saves the text trimmed. Android enables "Next" for any character, spaces included, and saves the text as typed. No length limit. |
| "Snapfix can reach out to me to discuss my use case." | Tick box        | No       | Not ticked | Sent as `notify_snapfix_team`: 1 or 0 on iOS, the text "1" or "0" on Android.                                                                                                                                            |

## Actions

| Action          | Who               | What happens                                                                                                                           | API  |
| --------------- | ----------------- | -------------------------------------------------------------------------------------------------------------------------------------- | ---- |
| Type in the box | Anyone            | Enables or disables "Next" by the rule above.                                                                                          | None |
| Tick the box    | Anyone            | Changes the opt-in; nothing else changes.                                                                                              | None |
| "Next"          | Anyone, with text | Keeps the text and the tick, then opens [Grid or list](https://docs.snapfix.com/how-the-apps-work/screens/onboarding/grid-or-list.md). | None |
| Back arrow      | Anyone            | Returns to [Work types](https://docs.snapfix.com/how-the-apps-work/screens/onboarding/work-types.md), with nothing picked there.       | None |

## States

* **Loading:** none.
* **Empty:** "Next" is disabled while the box is empty.
* **Error:** none; nothing is sent from this screen.
* **No permission:** none.
* **Offline (mobile):** works. The create call at the end needs a connection.

## Dialogs and sheets

None.

## Platform differences

| Topic        | iOS                   | Android            |
| ------------ | --------------------- | ------------------ |
| Placeholder  | " e.g. … comany …"    | "e.g. … company …" |
| Spaces only  | "Next" stays disabled | "Next" enables     |
| Opt-in value | Number 1 or 0         | Text "1" or "0"    |


---

# 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/onboarding/let-us-help.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.
