Skip to main content
Emma’s model picker is updated as new models become available. This guide focuses on the decisions that matter: start with the model that fits the job, then move up only when the work needs more reasoning or precision.
The model names on this page are the names you see in Emma. The picker is the source of truth for the models currently available to your account.

Start with the job

Use these three questions to choose a model:
  • How much reasoning does this need? A simple lookup does not need the same model as a high-stakes strategy memo.
  • Is this one response or a large batch? A small cost difference matters much more when a workflow runs across hundreds of items.
  • Does the work have a specialist fit? X posts, image generation, coding, and long-document research each benefit from a purpose-fit model.

Ad creative and image generation

Start with: Gemini 3.1 Flash Image Use it for campaign variations, social assets, and other high-volume creative work. It is the practical default when speed and iteration matter. Use GPT Image 2 instead for a small number of hero images or other one-off assets where you want to spend more time refining a single visual.

Marketing copy, ad copy, and content writing

Start with: Claude Sonnet 5 Use Sonnet 5 for landing pages, email sequences, LinkedIn posts, and other work that needs a consistent voice and strong instruction-following. It is the everyday writing recommendation. Move to Claude Opus 5 for a high-stakes deliverable—such as investor material, an important long-form piece, or work that needs especially careful synthesis. Artificial Analysis’ evaluation and AWS’s model documentation support the distinction between Sonnet for everyday work and Opus for the hardest work.

Handwritten text extraction and document OCR

Start with: Claude Sonnet 5 For contracts, forms, multi-table pages, and technical reports, use a model that can interpret the structure around the text—not just transcribe characters. Test a few representative files before using any model for high-stakes extraction. Use GPT-5.6 Sol when you want Emma’s current premium GPT option or it is already selected for the wider workflow.

Research, competitor analysis, and long documents

Start with: Gemini 3.7 Flash Gemini 3.7 Flash is the efficient default for broad research, source gathering, and long-document triage. Google names it as the migration target for Gemini 3.5 Flash workloads, with a 1M-token context window and grounding support (Google model guide). Move to Claude Sonnet 5 or Claude Opus 5 when the job becomes a precise analysis, a difficult synthesis, or a high-stakes final deliverable. If a workflow genuinely requires more than 1M tokens of context, keep the existing long-context model instead of treating a migration as automatic.

Lead enrichment and CRM workflows

Start with: Claude Sonnet 5. Use Claude Opus 5 for high-value batches. Lead enrichment combines research, scoring, and personalized outreach. Sonnet 5 is a strong default for normal-volume work. For event guest lists, strategic accounts, or other high-value batches, use Opus 5 when stronger research and judgment are worth the additional cost.

Coding, technical implementation, and skill development

Start with: Claude Sonnet 5 Sonnet 5 is the general recommendation for coding and agentic implementation work (AWS). For high-volume routine coding, use DeepSeek V4 Pro. For the hardest agentic or coding work, use Claude Opus 5 or GPT-5.6 Sol.

X posts and tweet ranking

Start with: Grok 4.6 Use Grok for X posts and replies when the goal is strong distribution on X. It is the specialist choice for X-native conventions and ranking context. Use Claude Sonnet 5 instead for non-X long-form writing.

General-purpose and mixed-task conversations

Start with: Gemini 3.7 Flash For conversations that mix planning, research, and routine updates, Gemini 3.7 Flash is a good efficient default. Switch to Claude Sonnet 5 when the conversation turns into more demanding writing or reasoning.

Quick reference

Keep models current

When Emma adds a newer model, do not replace a working selection just because the version number is higher. Change it when the newer model is a clear fit for the job—for example, it improves quality at the same or lower cost, or keeps quality while reducing cost. Preserve a model that provides a capability the replacement lacks, such as a larger context window. For X workflows, keep Grok as the specialist choice even when a newer general-purpose model becomes available.

How to change models

In the Customer Portal:
  1. Per conversation: click the model name at the top of a chat to open the picker. Your selection persists for that conversation.
  2. Scheduled chats: select a model when you create or edit a scheduled chat. Use an efficient model for lightweight recurring work and a stronger model when the outcome is more valuable.
  3. Work plans: a work plan can have a default model. You can choose a different model at the start of the conversation when the task calls for it.

Next steps

  • Concepts — skills, work plans, scheduled chats, and templates.
  • Agent Mode — the chat interface where you select models.
  • Settings — manage connected accounts and API configuration.
Last modified on August 22, 2026