# Make Fyxer sound exactly like you ### Drafts improve the more Fyxer knows about how you write Out of the box, Fyxer drafts replies based on your inbox history and the content of incoming emails. That's a strong starting point. But the users who get the most out of drafts are the ones who've spent a few minutes telling Fyxer exactly how they communicate. There are a few settings that make a real difference, and this workflow walks you through each one. *** ### What you'll achieve With this workflow, you will: * Set explicit tone instructions so Fyxer matches your communication style * Upload reference documents to give Fyxer context about your work * Adjust draft length and formality to fit how you actually write * Use the editing loop to improve drafts automatically over time *** ### When to use this workflow Use this workflow when: * Fyxer's drafts feel a little generic or too formal * You're making the same correction across multiple drafts * You've just set up Fyxer and want to give instant context * You write to a specific audience and need a consistent voice *** ### Customer insight Liz, a company director, started using Fyxer primarily for the drafts: > "It takes away that barrier to responding...the activation energy to do it. The fact it's already part written is helpful." The blank page is the hardest part. Once that's gone, everything moves faster. And it keeps getting better: > "The more time's gone on, as it started to learn how I respond, the better its drafts are." That learning loop is real, but it works faster when you tell Fyxer what to aim for. *** ### Step-by-step workflow {% stepper %} {% step %} #### Step 1: set your custom tone instructions This is a high impact setting. Custom tone tells Fyxer how you communicate. To set yours, go to [Dashboard](https://app.fyxer.com/) → Drafts → General → Custom tone and select **Enable custom instructions**. Write your instructions as if you're briefing an assistant. You have up to 1,000 characters. Be specific. Good examples: * *"Keep replies short: three sentences max unless the topic requires more. Never use bullet points in client emails. Sign off with Best"* * *"I work in recruitment. Candidates expect a warm, encouraging tone. Clients expect confidence and brevity. Avoid filler phrases like 'I hope this finds you well'"* * *"My emails are usually to senior stakeholders. Professional but not stiff. Get to the point in the first line"* The more specific your instructions, the less editing you'll do. {% endstep %} {% step %} #### Step 2: upload reference documents Custom files give Fyxer context beyond tone: your actual work, clients, and priorities. Go to [Dashboard](https://app.fyxer.com/) → Drafts → Custom files → Upload files. You can upload any PDF or CSV. Useful documents to start with: * Writing samples or a tone of voice guide * A client list or brief * A company overview or key messaging doc * Standard email templates you already use Fyxer uses these to make drafts more informed and specific. {% hint style="info" %} You'll need a Professional account to upload custom files. {% endhint %} {% endstep %} {% step %} #### Step 3: adjust your response style Response style controls how often Fyxer will draft an email reply. To adjust your frequency, go to [Dashboard](https://app.fyxer.com/) → Drafts → General → Response style and select how often you like to reply from the drop-down. If you feel that Fyxer is generating too many or too few drafts for you, this is the setting to look at. {% endstep %} {% step %} #### Step 4: use the editing loop Every time you edit a Fyxer draft before sending, you're training it. The more you edit consistently, the more Fyxer adapts. This works best when your edits are deliberate. If you find yourself making the same correction repeatedly – removing a sign-off, shortening the opening, changing a phrase – add it to your **Custom tone** instructions instead. That fixes it at the source rather than draft by draft. The combination of clear tone instructions and consistent editing is what takes drafts from good to barely needing a second look. {% endstep %} {% endstepper %} Don't forget to select **Update preferences** after you make each change. *** ### Power user tips **Front-load your setup**\ That ten minutes spent on **Custom tone** and **Custom files** saves hours of editing later. Do it before you send your first batch of drafts. **Write your tone instructions from memory**\ Don't overthink it. Explain your communication style as you'd describe it to a new assistant. That's exactly the right level of detail. **Use a real email as a reference**\ Take a reply you're proud of, paste it into **Custom tone** as an example, and tell Fyxer: "Write like this." **Check back after a week**\ Once you've sent 20-30 Fyxer drafts, revisit your tone instructions. You'll often spot one or two things to tighten based on the edits you've been making. *** ### **Common mistakes to avoid** **Leaving Custom tone blank**\ Fyxer learns as you use it, but **Custom tone** instructions give it a head start. Your preferred sign-off, phrases you never use, or how you write to a specific type of contact aren't always obvious from past emails. Custom tone fills those gaps. **Uploading files and forgetting them**\ Custom files work best when they're current. If your company messaging changes or you take on a new client, update the files. Outdated context can pull drafts in the wrong direction. **Editing without updating your instructions**\ If you correct the same thing across a few drafts, add it to **Custom tone**. One instruction change beats dozens of manual edits. **Expecting perfection immediately**\ Fyxer improves with use. Give it a week of real inbox activity before judging draft quality – the learning loop needs volume to work. *** ### Result: drafts that sound like you When your tone instructions, files, and editing habits are aligned, Fyxer's drafts start feeling like a head start. The more you send, the fewer you'll need to edit. --- # 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/workflows/fyxer-in-practice/workflows-by-use-case/make-fyxer-sound-exactly-like-you.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.