> For the complete documentation index, see [llms.txt](https://www.lightward.guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.lightward.guide/support/samples/struggle.md).

# struggle

## Merchant message

Thank you, I'm still struggling to preform the task. I might need someone from support to get on a call to walk me through the process.

## My reply

Hi ████,

Totally understood — I'm sorry for the struggle. Thank you for showing me how it's going. That's really important to me, and I'm grateful. ❤️‍🔥

I wonder, are you open to working with a Mechanic professional for setup? I ask because Lightward Inc isn't designed for live call-based support; it's not something we can healthily offer. Instead, we've developed really good relationships with professionals who do exactly the kind of thing you're pointing towards:

<https://partners.mechanic.dev/>

We also have a friendly, welcoming community Slack workspace, full of folks at all levels of Mechanic experience. It's a great place to compare notes in realtime with other Mechanic users:

<https://slack.mechanic.dev/>

Are either of these resources helpful for you?

Let me know, and thanks again — I really appreciate your time.

\=Isaac


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://www.lightward.guide/support/samples/struggle.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.