We analyzed the behaviors of Solo's power users and found the patterns that made them successful. This article is your tell-all guide on how to prompt Solo like a pro.

Solo is smart, but it can't read your mind. The best questions should include context in your prompt. A good rule of thumb is "if a human wouldn't be able to understand what you're asking, then Solo probably can't either." The fewer assumptions Solo needs to make from your question, the better. Here is an example of a good and a bad prompt:

Bad prompt: Why don't projects refresh?

Good prompt: For our "projects" feature, what is the logic behind the refresh button? A customer reported that only half of her project's data has been refreshed.

You can direct Solo to query a specific source like Zendesk, Code, Notion, or Intercom by finishing your question with (sources: <source 1>, <source 2>) For example:

Valid sources are: code, zendesk, intercom, notion, linear, jira, confluence, featurebase

Solo is designed to give you a quick answer, but sometimes you want a very detailed response. To do that, you can add [deep dive] at the end of your message so Solo knows it should go into detail for you.

You can tailor your Solo experience by marking an answer as "not helpful." When you do this, make sure you add the answer you would have preferred in the thread so Solo can learn what it should have said. Solo remembers this context in future interactions.

Solo will always try its best to answer your question, but sometimes you need to talk to a real person. Clicking the "Who's an expert on this?" button will find the exact engineer who built this feature so you can continue the conversation with them.

The key to writing new documentation is to include:

While sections are a good way to outline your article, sometimes it can be helpful to add specific context you want Solo to add to that section. To do that, you can add -(additional context) below the subject to instruct Solo what you want it to add in that section.

In Edit Mode, you can verbally tell Solo where you want an edit to go, like "after section 2." Solo will use that to inform where to put the new section.

When reviewing documentation suggestions, sometimes it's helpful to see the section of the article where Solo is suggesting the change. To do that, you can click scroll to text and the right panel will highlight the suggested change.

If you're ever curious why Solo is suggesting a change to your documentation, you can click "..." -> View source and you'll see Solo explain why it's suggesting the change