> For the complete documentation index, see [llms.txt](https://docs.slatecx.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.slatecx.com/concepts/unanswered-questions.md).

# Unanswered Questions

A key advantage of a persistent workspace is that the prospect can return to it again and again. &#x20;

This means if they ask a question that the Slate agent does not know the answer to, the Slate agent can actually trigger an internal alert, get an answer from a human, and then post that answer to the slate and let the propect know it has an answer.

This pattern is often referred to as 'human-in-the-loop'.

In practice this means that the Slate agent can be very honest in what it does know and does not know.

Here is how that works in practice:

* Prospect asks a question of the Slate agent.
* Slate agent queries its available knowledge, determines it does not know the answer and offers to find the answer for the prospect.
* The prospect agrees, saves their slate via the popup dialog and then either continues with their conversatiion or leaves the slate.
* The Slate agent raises an 'Open question' which is posted to HubSpot or Slack or both.
* A human staff member sees the alert (in slack) or is assigned a task via a workflow (in HubSpot)
* They click the supplied link to review the question in the context of prospects slate.
* They answer the question.
* The prospect is notified the question is answered and receives a link to the slate to see the answer.

This is what an Open Question looks like in Slack.

<figure><img src="https://2844884401-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5AhClAmEf81WtHS8kM9H%2Fuploads%2FyIq4mqmgU52gZOZf68gm%2Fimage.png?alt=media&amp;token=7c901122-d04f-45ec-bdb4-ba6b05c36304" alt=""><figcaption></figcaption></figure>

They human staff member can click 'View Question' to answer the question directly.
