> For the complete documentation index, see [llms.txt](https://docs.slapfive.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.slapfive.com/getting-started/slapfive-best-practices/building-a-customer-program/who-to-invite.md).
# Who to invite
* Previously Engaged, Nominations, and Net New
Prime the pump with known nominations from sales/CS and also when you did your homework seeing who had already raised their hand, do they want to be given additional opportunities to share their voice? That should give you a good starting point.
The goal should be to enable and empower sales to use the customer program as that differentiator when selling - when new customers come on board they will be a member and get the opportunity to network, share their voice and provide and receive advice and insights right after signing on with you.
I have seen huge success with this.
---
# 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.slapfive.com/getting-started/slapfive-best-practices/building-a-customer-program/who-to-invite.md?ask=&goal=
```
`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.