> For the complete documentation index, see [llms.txt](https://infosys.selmotech.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://infosys.selmotech.com/selmo-solution/selmo-solution-en/selmo-how-it-works/selmo-training/chapter-7-why-selmo-always-works/7.4-typical-objections-and-their-resolution.md).

# 7.4 Typical objections and their resolution

#### **"I can't model that in Selmo."**

In reality that usually means:\
"I haven't divided the process into states yet."\
As soon as you break the steps down logically, any procedure can be represented.\
Selmo does not model technology, but behavior.

#### **"My function has no feedback."**

Then it is unsafe.\
Feedback can always be added or simulated —\
for example via a measurement, a signal, an internal response.\
Without feedback, a safe process is not possible.

#### **"I prefer to work with timers."**

Timers are allowed, but they do not replace feedback.\
They can be used additionally — for example to set time limits —\
not to confirm the success of an action.

#### **"I need special logic."**

Selmo covers 95% of all control logic through the standard zones.\
For the remaining 5% there are extensible logical functions\
that operate by the same principle: Start → Action → Feedback.


---

# 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://infosys.selmotech.com/selmo-solution/selmo-solution-en/selmo-how-it-works/selmo-training/chapter-7-why-selmo-always-works/7.4-typical-objections-and-their-resolution.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.