> 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/get-started/quickstart.md).

# Explore key features

How Fyxer's features share context and get better together.

{% hint style="success" %}

* [How Fyxer's features work together](#how-fyxers-features-work-together)
* [See them in action](#see-them-in-action)
* [What each feature adds](#what-each-feature-adds)
  {% endhint %}

### How Fyxer's features work together

Every Fyxer feature draws on the same picture of your work: your emails, your calendar, your meetings, and the tools you connect. What Fyxer learns in one place helps everywhere else.

A meeting summary makes your next draft more accurate. A draft you edit teaches Fyxer your tone. So the more of Fyxer you use, the better each part gets.

***

### See them in action

Here's how that could play out.

You have a call with a new client. **Notetaker** records it and writes up a summary. One of the action items is your promise to send a proposal by Friday.

The next morning, that promise is in your **Top priorities** in the Dashboard. You didn't have to note it down. It came straight from the meeting.

The client emails with a question about pricing. Fyxer's **draft reply** already knows what was discussed on the call, so you only need a light edit to the email before you send it.

The client asks to meet again. Fyxer drafts a reply with times from your calendar, plus your **scheduling link**, so the client can book a meeting without any back and forth from you.

Later that week, you can't remember exactly what was agreed. You ask **Fyxer Chat**, "What did I promise the client on our last call?" The answer comes from the meeting notes.

That's how Fyxer helps you never miss what matters.

***

### What each feature adds

**Inbox organization** tells Fyxer which emails need you. That decides which emails get drafts, and which ones are pulled into the Dashboard as priorities.

**Drafts** learn from your sent emails, your edits, and your meetings. Each edit you make teaches Fyxer more about how you write.

**Notetaker** adds what was said across meetings. Without it, Fyxer only knows what's in writing.

**Your calendar** tells Fyxer who you're meeting and when you're free, for scheduling replies and meeting prep.

**Chat** can draw on all of this at once, so you can ask about an email, a meeting, or a file in one place.

**Files you upload**, like briefs or price lists, fill in details that might never come up in an email.

**Fyxer in Slack and Teams** brings that same assistant into your team conversations. Mention @fyxer in a thread to pull in context from your emails and meetings, without switching tools.

**Flows** put that context to work on a schedule. Set up a routine task once, like a morning briefing or a weekly update, and Fyxer runs it using what it already knows about your work.

**Spaces** share that picture with your team. Create a space for a deal, project, or client, and everyone in it sees the same emails, meetings, and files, and who owes the next step.

***

### Next up <a href="#next-up" id="next-up"></a>

Now you know what each feature does and how they connect. Next, meet the agent that brings them together, wherever you work.

* Next: [**Meet your Fyxer agent**](https://docs.fyxer.com/get-started/meet-your-fyxer-assistant.md)


---

# 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/get-started/quickstart.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.
