> For the complete documentation index, see [llms.txt](https://docs.fyxer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fyxer.com/workflows/fyxer-in-practice/workflows-by-use-case/know-where-every-account-stands.md).

# Know where every account stands

Know what’s happening with each client, even when someone else is handling it.

### Who it's for <a href="#who-its-for" id="who-its-for"></a>

Account leads and team leads who are responsible for clients, but aren't cc'd on every email or in every call.

***

### Sound familiar? <a href="#in-your-words" id="in-your-words"></a>

> "Our account manager had been working with a client on an important piece of work we were delivering. When he was out sick unexpectedly, we struggled to see what had been promised and by when. It would have been so useful to have an overview of the project's status based on recent emails and meetings."

***

### Why a Space fits <a href="#why-a-space-fits" id="why-a-space-fits"></a>

The story of a client is spread across your team's inboxes and calendars. Piecing it together means asking around, and hoping nobody forgot anything.

A Space gathers it for you. Emails, meetings, and actions due with that company are added as they happen, from everyone in the Space. You can read the timeline, check what's outstanding, or ask the Space a question.

{% hint style="info" %}
You might not see Spaces yet. We're rolling this feature out gradually as we test and refine it, so availability will vary. We'll keep this page updated as things evolve.
{% endhint %}

***

### Set it up <a href="#set-it-up" id="set-it-up"></a>

1. Go to [Dashboard](https://app.fyxer.com) → Spaces and select **Create new**
2. Name the Space after the client, add the client's domain name as a source, then select **Create Space**
3. Open the Space and select **Share** and turn on automatic invites, so anyone who emails or meets with that client joins the Space
4. Choose whether new members join as **Viewers** or **Contributors** (Viewers can see the Space; Contributors automatically contribute content)

***

### Questions to copy <a href="#questions-to-copy" id="questions-to-copy"></a>

Open the Space and ask:

* "What's changed with \[client company] this week?"
* "What have we promised \[client name], who owns each item, and is anything overdue?"
* "Is there anything \[client name] has asked for that nobody has replied to?"
* "Summarize our last three calls with \[client company] in five bullets."

You can also ask Fyxer about a Space from within Slack or Microsoft Teams, so you don't have to leave the conversation. Connect Slack or Teams under [Dashboard](https://app.fyxer.com) → Settings → Integrations and then ask @fyxer from the chat.

Learn more:

* [**Connect Fyxer to Slack**](https://support.fyxer.com/article/connect-fyxer-to-slack)
* [**Connect Fyxer to MS Teams**](https://support.fyxer.com/article/connect-fyxer-to-microsoft-teams)

***

### Make it a habit <a href="#make-it-a-habit" id="make-it-a-habit"></a>

Pair the Space with a Flow, so the update comes to you.

Go to [Dashboard](https://app.fyxer.com) → Flows → **Create Flow**. In the prompt box, add "Every Friday at 3pm, send me what changed this week in each of my client Spaces."

Learn more: [**Set up Fyxer Flows.**](https://support.fyxer.com/article/set-up-fyxer-flows)

***

### Learn more

[**Get started with Fyxer Spaces**](https://support.fyxer.com/article/get-started-with-fyxer-spaces) in the Help Center or watch this short video:

{% embed url="<https://vimeo.com/1232322915>" %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.fyxer.com/workflows/fyxer-in-practice/workflows-by-use-case/know-where-every-account-stands.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
