> 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/hand-over-an-account.md).

# Hand over an account

Pass a client to a colleague, and the history goes with them.

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

Anyone passing an account to someone else: a deal moving from sales to account management, a colleague covering while you're away, or a new hire taking over a client.

***

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

> "We're a small team, so we don't have the resources for multiple people on the same account. All the knowledge sits with one person. When they go on vacation or, worse, leave, we're left trying to piece together where things stand."

***

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

A handover usually means a long email, a stack of forwarded threads, and a call to fill in the gaps. Something still gets missed, and the client notices.

With a Space, the history lives with the account. Whoever takes over sees what was said, what was agreed, and who owes the next step, from the first day.

{% 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. Make sure the account has a Space. If not, go to [Dashboard](https://app.fyxer.com) → Spaces → **Create new**
2. Select **Share** and check automatic invites are on, or **Invite** in a Space you didn't create
3. cc the new owner on your handover email to the client. They're added to the Space straight away
4. If they join as a Contributor, ask them to accept the invite, so their own emails and meetings with the client are added
5. Reassign any open action items to them in the Space. You can ask Fyxer to do this for you in Chat within the Space, or anywhere else that you talk to Fyxer

***

### Prompt to copy <a href="#prompt-to-copy" id="prompt-to-copy"></a>

The new owner opens the Space and asks:

> Give me a handover brief: where the relationship stands, what we've promised and by when, any open questions, and anything I should know before my first call.

They can then follow up by asking Fyxer to draft their first introductory email to the client, with the full context to hand.

***

### Learn more <a href="#learn-more" id="learn-more"></a>

[**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/hand-over-an-account.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.
