Writing Rules That Actually Work: A Practical Guide To Natural Language Email Instructions

TL;DR

Rules are natural language instructions that shape how Jace drafts your emails. They're not toggles, not automations, and not retroactive. They're judgment instructions: short, specific guidance that tells Jace how to handle certain types of threads. This post covers why toggle-based customization fails, what rules actually do, a framework for writing rules that stick, ten copy-paste-ready rules for founders, common mistakes, and how rules interact with labels and drafts.

Why Toggle Based Customization Breaks Down

Every founder knows the pattern. You answer the same types of emails over and over: investor check-ins, vendor negotiations, internal approvals, sales follow-ups. The pressure never stops, and consistency slips.

Toggle-based email tools promise to help. Set your tone to "professional." Turn on "auto-greetings." Flip a switch for "short replies."

But toggles break down fast.

They're global, so your casual tone for the team also shows up in investor updates. They're binary, so you can't say "be direct with vendors, but warmer with customers." They're shallow, so they don't know to include the project name in internal threads or to highlight payment terms in finance conversations.

Toggles assume that your needs fit into a checkbox. They don't.

Real email behavior is contextual. The same person might need a three-sentence reply to a quick question and a longer breakdown for a scope change. The same type of email might need different handling depending on who sent it, what's already in the thread, or what's at stake.

This is where natural language rules change the equation. Instead of picking from a menu, you write instructions in plain English. Jace reads them and applies judgment when drafting.

What Rules Are And Are Not

Before writing rules, it helps to understand what they actually do.

Rules shape drafting behavior. When Jace writes a draft, it reads your rules and uses them to guide tone, structure, and content. That's it. Rules are instructions for how to write, not instructions for what to do automatically.

Rules do not apply labels. If you want to label emails as "Sales" or "Urgent," that's a separate feature. Rules won't do that for you.

Rules are not retroactive. When you save a rule, it applies to messages going forward. Jace won't re-draft old emails based on new rules.

Rules are judgment instructions, not workflow automations. They don't trigger actions. They don't send emails automatically (unless you've opted into auto-send separately). They shape how drafts look before you review them.

Think of rules as a briefing document for a sharp assistant. You're not telling them exactly what to say. You're giving them context and preferences so they can draft something you'd actually send.

A Simple Rule Writing Framework

Good rules share a few traits. They're specific. They define context. They describe output. And they leave room for judgment.

Here's a framework to follow:

1. Specific beats vague

"Be professional" is almost useless. Jace already tries to be professional. What does professional mean to you? Short sentences? No emojis? Formal sign-offs?

Instead: "Use a direct, senior tone. Avoid casual language. Close with 'Best,' not 'Cheers.'"

2. Define the trigger context

Rules work best when they describe what kind of email or thread they apply to. Without context, Jace has to guess.

Instead: "For emails from vendors about pricing or invoices..."

3. Describe the output format

What should the draft include? What structure makes sense? What must not be missing?

Instead: "Include a one-line summary of the request and a clear next step."

4. Add safety checks

Sometimes you want Jace to flag things for your review rather than just drafting a reply. Rules can include this.

Instead: "If the email mentions contract changes, highlight the specific clause and note it for review."

5. Set tone and length constraints

If you want short replies, say so. If you want a warmer tone for certain senders, specify.

Instead: "Keep replies under five sentences. Match the sender's energy."

Here are some examples of weak rules rewritten:

Ten Starter Rules For Founders

These rules are ready to copy and paste. Adjust for your context.

Sales Threads

1. Inbound interest: "For inbound emails asking about pricing or demos, acknowledge their interest, confirm what product they mentioned, and suggest a 15-minute intro call this week."
2. Objection handling: "When a prospect raises concerns about pricing or fit, acknowledge the concern directly, restate the core value, and offer a follow-up conversation rather than a written defense."

Vendor and Finance Threads

3. Invoice disputes: "For emails about invoices or billing, include the invoice number and date in the reply. If there's a discrepancy, flag it clearly for my review before drafting a resolution."
4. Vendor negotiations: "When replying to vendors negotiating terms, keep the tone firm but collaborative. Reference any prior agreements mentioned in the thread."

Internal Approvals and Alignment

5. Budget requests: "For internal emails requesting budget approval, summarize the ask in one sentence, state whether it's within policy, and include a clear approve/reject line for me to confirm."
6. Cross-team updates: "When drafting replies to cross-functional threads, keep the reply short, restate the team's current status, and tag any open blockers."
7. Exec escalations: "For escalations from direct reports, acknowledge receipt, confirm the priority level, and outline next steps in bullet form."

Investor Updates

8. Monthly updates: "For monthly investor update threads, use a structured format: highlights, lowlights, key metrics, and asks. Keep the tone confident but transparent."
9. Quick investor questions: "When investors reply with short questions, match their brevity. Answer directly. Avoid over-explaining."

Follow-Ups on Waiting

10. Waiting threads: "For threads marked Waiting with no reply after three days, draft a polite nudge referencing the original request and asking for a quick update."

Common Mistakes And How To Fix Them

1. Rules that fight each other. If one rule says "keep replies under three sentences" and another says "include full context on every thread," Jace has to choose. The result is inconsistent.

Instead: Make rules specific to context. Short replies for quick internal asks. Detailed replies for onboarding threads.

2. Rules that try to apply labels. Rules don't label emails. If you write "label all investor emails as VIP," nothing will happen.

Instead: Use Jace's labeling features separately. Rules shape drafts; labels organize your inbox.

3. Rules that are too vague. "Be helpful" is not a rule. It's a vibe. Jace is already trying to be helpful. Vague rules get ignored or misapplied.

Instead: Define what helpful looks like. "Include a clear next step in every reply."

4. Rules that overconstrain tone. If every rule specifies tone, your drafts start sounding robotic or inconsistent. Tone rules should be exceptions, not defaults.

Instead: Set one general tone rule for external emails. Add tone overrides only for specific contexts, like "warmer tone for customer success threads."

5. Rules that forget recipients and CC sensitivity. Not every reply should treat CC'd parties the same. A rule that ignores who's on the thread can create awkward drafts.

Instead: "If legal is CC'd, avoid speculative language. Stick to confirmed facts."

6. Rules that create long drafts. If your rules keep adding requirements, drafts get bloated. Most emails should be short.

Instead: Start with a length constraint. "Default to five sentences or fewer. Expand only when the thread requires detail."

7. Rules that assume perfect accuracy. Jace is smart, but not omniscient. Rules that say "always include the exact contract value" assume Jace can always find it.

Instead: Frame rules as guidance. "If the contract value is mentioned in the thread, include it. Otherwise, flag for my review."

8. Rules that try to trigger automations. Rules don't trigger actions. They don't move emails, send automatically, or start workflows.

Instead: Use label triggers for drafting actions. Rules shape what those drafts say.

How Rules Work With Labels And Drafts

Labels and rules work together, but they're not the same thing.

Labels can trigger drafting behavior. When an email lands in a label like "Needs Reply" or "Call Jace automatically," Jace knows to draft a response. If a thread is in "Waiting" and hasn't had a reply for three days, Jace can draft a follow-up.

But labels don't decide what the draft says. That's where rules come in.

Rules shape how those drafts are written. A label might say "this email needs a reply," and a rule might say "for sales threads, keep the reply short and suggest a call."

The review-first approval boundary stays the same. Even with labels and rules set up, drafts land in your review queue unless you've explicitly opted into auto-send for a label. You're always in control before anything goes out.

Think of labels as the trigger and rules as the style guide.

FAQ

How do I write natural language rules for an AI email assistant? Write in plain English. Be specific about the context (what kind of email), the output (what the draft should include), and any constraints (tone, length, safety flags). Avoid vague instructions like "be helpful."

Why do my AI email instructions not stick? Usually because they're too vague or they conflict with other rules. Review your rules for overlap and make sure each one targets a specific type of email or thread.

Can rules apply labels automatically? No. Rules shape drafting behavior only. Labeling is handled separately through Jace's labeling features.

Do rules change drafts for old emails? No. Rules apply to messages after the rule is saved. They're not retroactive.

How do I avoid conflicting rules? Make each rule specific to a context. Don't write global rules for tone or length; tie them to email types. If two rules could apply to the same thread, check that they give compatible guidance.

How do I use rules for different email types? Start each rule by defining the context: "For emails from investors..." or "When replying to support tickets..." This helps Jace match the rule to the right thread.

How many rules can I create? There's no strict limit, but fewer well-written rules work better than many overlapping ones. Start with five to ten and refine from there.

Can Jace suggest rules for me? Yes. Jace can propose rules based on your behavior. You approve which ones to save.

CTA

If you're ready to move beyond toggles and write rules that shape your drafts the way you actually think, try Jace. Review-first drafting on top of Gmail or Outlook, powered by natural language instructions.