# Roll out Fyxer – a manager's guide {% hint style="success" %} * [Before you send the invites](#before-you-send-the-invites) * [What to tell your team](#what-to-tell-your-team) * [What to expect in week one](#what-to-expect-in-week-one) * [How to check adoption](#how-to-check-adoption) * [If people aren't engaging](#if-people-arent-engaging) * [Share these resources with your team](#share-these-resources-with-your-team) {% endhint %} You've set Fyxer up. Now comes the rollout. Here's everything you need to communicate Fyxer to your team and get them up and running. *** ### Before you send the invites There are two things worth doing before anyone else joins: 1. **Check the auto-add domain setting.** By default, Fyxer automatically adds anyone who signs up with your company email domain, which can create unexpected charges. Turn it off if you want to control who joins. Go to [Dashboard](https://app.fyxer.com/) → Admin settings → Organization and toggle off "Automatically add users for this domain" 2. **If your team uses Outlook, get IT approval first.** Without it, every Outlook user hits an "Admin approval required" error when trying to connect. This wastes trial time and creates a bad first impression. Send your IT admin the [Outlook admin setup guide](https://support.fyxer.com/en/articles/12819287-admin-setup-guide-approving-fyxer-in-microsoft-365-microsoft-entra-id) before you roll out. It takes minutes to approve *** ### What to tell your team People adopt tools faster when they can clearly see the benefits and have confidence in the product. Here's what's worth communicating upfront. **What Fyxer does:** * Organizes their inbox automatically into categories, with the most important emails in **To do** * Drafts replies for emails that need a response * Records and summarizes meetings, and drafts follow-up emails * Handles scheduling links so they stop going back-and-forth on availability **What Fyxer doesn't do:** * Send emails automatically – every draft needs their review before it goes * Reveal their account data. It's not a shared inbox, so no one else can see their emails, drafts, or meeting notes * Change how they work. Fyxer runs in the background **Template message** > Hi team, > > We've just rolled out Fyxer – an AI tool that saves time on email and meetings. You should have received an invite to join. Here's what to expect: > > Fyxer will start organizing your inbox and drafting replies automatically. You'll find drafts in your inbox, attached to emails that need a response. Review them, edit if needed, and send. Your inbox stays yours: no one else can see what's there. > > Fyxer can also join your calendar meetings to record and summarize them, and draft follow-up emails afterwards. > > To get the most out of Fyxer, spend 5–10 minutes in the [Dashboard](https://app.fyxer.com) customizing your settings. You'll find this [Dashboard tour](https://docs.fyxer.com/get-started/get-started/dashboard-tour) helpful. > > Any questions, let me know. Feel free to adapt the tone to fit how your team communicates. *** ### What to expect in week one Fyxer works from day one, but it gets better over time as it learns each person's style. Here's what's normal in the first week: * **Inbox organization**: categories appear straight away. Some emails may be miscategorized initially; Fyxer learns from how people interact with them over time * **Drafts**: draft replies appear for emails in "To do". They may not sound exactly right at first. Encourage your team to edit drafts lightly rather than rewrite them from scratch – that's how Fyxer learns their tone fastest * **Notetaker**: if enabled, Notetaker will join calendar meetings automatically. Team members can remove it from specific meetings they don't want recorded * **Scheduling**: scheduling links start appearing in draft emails. Team members can adjust their availability in the [Dashboard](https://app.fyxer.com/). {% hint style="info" %} A common first week issue is **drafts not appearing**. This is almost always caused by conversation view being turned off. Point anyone who has this problem to: [**Why didn't Fyxer draft an email?**](https://support.fyxer.com/en/articles/10948389-why-didn-t-fyxer-draft-an-email) {% endhint %} *** ### How to check adoption Go to [Dashboard](https://app.fyxer.com/) → Admin settings → People → Invites to see which invites are still pending. Once an invite is accepted, the user will move to the Members tab. If someone hasn't connected their tools yet, the most common reasons are: the invitation went to spam, they used the wrong email address, or, for Outlook users, IT approval is still pending. *** ### If people aren't engaging Adoption issues usually fall into one of three categories: **"I don't understand what it does"** Point them to the [Explore key features](/get-started/quickstart.md) page and the [Dashboard tour](/get-started/dashboard-tour.md). **"The drafts don't sound like me"** This improves over time. Encourage them to edit drafts rather than delete them, and to add tone guidance in their Dashboard under Drafts → Custom tone. **"I don't trust it"** The privacy point is often what's holding people back. Remind them that no one, including admins, can see their emails, drafts, or meeting notes. You can also refer them to: [What team members can and can't see](https://support.fyxer.com/en/articles/13185411-what-team-members-can-and-can-t-see). *** ### Share these resources with your team * [I'm new to Fyxer](https://docs.fyxer.com/get-started) * [Getting started videos](https://docs.fyxer.com/resources/resources/videos-and-events/getting-started) * [Help Center](https://support.fyxer.com) --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.fyxer.com/teams-and-admins/roll-out-fyxer-a-managers-guide.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.