> For the complete documentation index, see [llms.txt](https://docs.ltvnumbers.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ltvnumbers.com/onboarding-process/success-call-expectations.md).

# Success Call Expectations

Reflect on these questions for the call:

* Overall how has it been to use the tool? Easy/hard, confusing/makes sense, etc.
* How often do you use the tool?
* Have you been doing the daily / weekly / monthly analysis that we recommend?
* Who uses the tool and how?
* Has it changed the way you operate your business?
* Have you learned anything surprising or unexpected about your business or your customer buying behavior?
* Have you seen any exciting early results?
* Is there a particular customer segment or customer journey that you will be paying special attention to?

It will come in handy to think about how you've used the tool, how you would like to use the tool, and how we can help you moving forward.


---

# 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://docs.ltvnumbers.com/onboarding-process/success-call-expectations.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.
