> For the complete documentation index, see [llms.txt](https://help.rankability.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rankability.com/serena/using-advisor.md).

# Using Serena chat

Open Ask Serena for a client to ask questions, use its context, attach supported material, and move useful work into Rankability.

Serena is most useful when the correct client is selected and its sources and integrations are current. Use **Ask Serena** for work scoped to that brand; do not use a generic support surface when the answer requires live rankings, GSC, GA4, projects, or client memory.

## Open Serena

1. Select the client, then choose **Ask Serena** in the sidebar.
2. Ask a question or describe the result you want.

Serena uses the selected client’s sources, settings, connected data, memory, and available Rankability tools. Starting a new chat does not change the selected client.

Earlier conversations live on the Serena page itself rather than in the sidebar. Open **History** to search past conversations and reopen one.

Begin with the outcome, scope, and constraints: for example, name the page, keyword, country, date range, or report you want Serena to inspect. Serena can read available client context and propose or perform supported Rankability actions, but it should not invent facts that are absent from the client.

## Attach screenshots

You can attach up to four screenshots to one message. Use screenshots when the visible page, chart, layout, or error message is important to your question.

## Actions and usage

Serena chat and supported full-platform tools are included. Before a consequential or high-impact action, Serena shows the scope and usage impact. Actions that change external systems require approval where the product presents an approval step.

Read the structured action details before approval. They are the source for scope, inputs, and usage impact. A chat response promising a later result is not evidence that background work exists; use the visible progress and terminal result in the conversation or the relevant project/task status.

## Complete a Serena workflow

1. Select the client and open **Ask Serena**.
2. State one concrete objective and include the relevant page, keyword, market, or evidence.
3. Answer a necessary clarifying question or attach up to four relevant screenshots.
4. Review any proposed action, usage impact, and destination before approving it.
5. Keep the chat open or return later and use the persisted progress/result rather than starting a duplicate.
6. Open the created project, report, list, or task to verify the output and continue the work.

## Limits and recovery

* Serena can be wrong. Verify high-impact recommendations against captured data and authoritative client sources.
* A screenshot shows only the visible state; include the URL, date, filters, and error text when they matter.
* Connected services can be stale or unauthorized. Check [Serena sources and connections](/serena/advisor-knowledge-base-and-data-connections.md) before treating missing data as zero.
* A tool can fail after approval. Preserve the error and action details, then retry only when the original run is no longer active.
* External publication, messaging, or destructive changes may require explicit approval and cannot be inferred from a general request.

## Get a better answer

* Name the page, keyword, market, or date range you mean.
* Connect the relevant data service in client settings.
* Add authoritative client sources instead of asking Serena to infer private facts.
* Open a separate chat when you switch to a different goal.

## Related articles

* [Serena sources and connections](/serena/advisor-knowledge-base-and-data-connections.md)
* [Using Activity](/activity/tasks-board.md)
* [Using Serena with connected apps](/serena/serena-integrations.md)
* [Troubleshooting common issues](/troubleshooting/troubleshooting-common-issues.md)