> 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/using-fyxer/get-more-from-your-fyxer-agent.md). # Get more from your Fyxer agent Advanced ways to use your Fyxer agent, wherever you reach it. {% hint style="success" %} * [One agent, wherever you are](#one-agent-wherever-you-are) * [Two habits that help everywhere](#two-habits-that-help-everywhere) * [Your Fyxer agent at work](#your-fyxer-agent-at-work) {% endhint %} This page builds on [Meet your Fyxer agent.](/get-started/meet-your-fyxer-agent.md) If you haven’t asked Fyxer anything yet, start there. Here we go one step further, with prompts to copy and workflows to try. ### One agent, wherever you are Chat, your inbox, Slack, Teams, Flows, and Spaces are all ways to reach the same Fyxer agent, working from the same context. Start in whichever place suits the moment, and pick up later somewhere else. #### See it in action Before a meeting, Mike asks Chat for a summary of his last call with Acme and any outstanding actions. Later, Sarah mentions in Slack that Acme wants an updated invoice. Mike replies in the thread: > @Fyxer add an action to the Acme Space for Sarah to send the updated invoice by Friday. The action lands in the Acme Space, alongside the ones from his meetings. Next time Mike asks Chat what’s outstanding with Acme, the invoice is on the list, and so is everyone else’s actions from the Space. {% hint style="info" %} You might not see Flows or Spaces yet. We're rolling out these features gradually as we test and refine them, so availability will vary. We'll keep this article updated as things evolve. {% endhint %} *** ### Two habits that help everywhere 1. **Be specific.** Fyxer works from your real emails, meetings, and messages, so names, dates, and topics help it find the right thing. | Instead of | Try | | ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------ | | “What about the budget?” | “What did Tom say about the Q4 budget on Monday’s call?” | | “Write a follow-up” | “Draft a follow-up to Priya at Fernley Group confirming the start date we agreed today. Keep it short, with bullets for next steps.” | | “Any updates?” | “What’s changed with Acme since last Friday, and is anything waiting on me?” | 2. **Ask for the whole job.** Fyxer can find, sort, and draft in one go. You don’t need to break it into steps: > Find what Acme has asked for in the last two weeks that we haven’t answered, and draft one reply to Tom covering it all. If something’s missing, just say so in the same conversation, and Fyxer will update the draft. *** ### Your Fyxer agent at work #### Fyxer Chat Chat is the best place for longer work: drafting from scratch, comparing several threads, or thinking something through. Try: * “Compare what Acme and Fernley Group have each asked for this month, and tell me where they overlap” * “Draft a proposal email to Tom using what we discussed on the last two calls” * Use voice mode to talk through your day on the way in, and ask Fyxer to draft as you go * Get support using Fyxer by asking how-to questions, like "How do I create a Space?" Fyxer will answer, then link you to the full Help Center article #### Your inbox You don’t need to open the Dashboard to reach your agent. Reply to any email Fyxer sends you, or forward an email to Fyxer, . Try: * Forward a long thread and ask: “What’s being asked of me here, and by when?” * Reply to your Fyxer Briefing: “Draft an email for the first action on this list” #### Slack and Microsoft Teams Message @Fyxer in Slack or Teams and you’re talking to the same agent you use in Chat, with the same access to your emails, meetings, and calendar. Use it to search, draft, and book meetings without leaving the conversation you’re in. Start a direct message with Fyxer, or mention it in a channel, and try: * “@Fyxer what did we agree on yesterday’s call with Acme, and who’s doing what?” * “@Fyxer what have people asked me to do today?” * “@Fyxer move my 3pm with Tom to tomorrow morning” * "@Fyxer create a Flow to update the team on Acme outstanding actions every morning" **More you can do in Slack:** Fyxer can also search Slack channels, link you to a specific message, and draft messages to your Slack drafts. **Workflow to try:** [Find anything, wherever it was said](https://docs.fyxer.com/workflows/fyxer-in-practice/workflows-by-use-case/find-anything-wherever-it-was-said). #### Flows A Flow is your Fyxer agent working on a schedule. If you ask it the same thing more than twice, make it a Flow. Go to [Dashboard](https://app.fyxer.com) → Flows → **Create Flow** and describe what you want. Fyxer sets the trigger and instructions for you. Flows can run on a schedule or be triggered by an event, like a meeting or when an email gets a certain label. They can send results to Slack, Teams, email, or the Dashboard. Try: * “Before each meeting with someone outside my company, send me a short brief on our last conversation, in Teams” * “When an email is labeled To respond and it’s from Acme, alert me in Slack straight away” * “Every Friday at 4pm, send me a list of client emails I haven’t replied to by email” **Workflow to try:** [Get your briefing pushed to you](https://docs.fyxer.com/workflows/fyxer-in-practice/workflows-by-use-case/get-your-briefing-pushed-to-you) #### Spaces A Space gives you shared context on one client, deal, or project. Ask the Space directly, and it answers from everything your team has said and heard. Try: * “What have we promised Acme, who owns each item, and is anything overdue?” * “Is there anything Acme has asked for that nobody has replied to?” * “Write a one-paragraph status update on Acme I can paste into our weekly report.” **Workflow to try:** [Know where every account stands](https://docs.fyxer.com/workflows/fyxer-in-practice/workflows-by-use-case/know-where-every-account-stands) #### Claude and ChatGPT If you're a Claude or ChatGPT user, connect Fyxer so they work from your real emails and meetings. Try: * “Using my Fyxer emails and meeting notes, write a one-page summary of the Acme account ahead of next week’s renewal call” * “Using my Fyxer meeting notes from this quarter, list the most common objections we’ve heard from prospects” Learn more: [**Connect Fyxer to Claude**](https://support.fyxer.com/article/connect-fyxer-to-claude), [**Connect Fyxer to ChatGPT**](https://support.fyxer.com/article/connect-fyxer-to-chatgpt), or the [**Fyxer MCP**](https://support.fyxer.com/article/fyxer-mcp) for other AI tools. *** #### Next up Learn how to customize and get more from Fyxer email drafts. * Next: [**Work with drafts**](/using-fyxer/work-with-drafts.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/using-fyxer/get-more-from-your-fyxer-agent.md?ask=&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.