Analysis Settings

​

What this feature is

is where you configure analysis fields: values your AI generates after a conversation ends. Those values can be attached to the person’s contact profile or to the conversation itself depending on how you set each field up. You describe what to extract or compute using rules (natural-language instructions). Rules can be reused across assistants so you define logic once instead of copying the same instructions into every assistant.

​

Video walkthrough

This narrated tutorial walks through Analysis Settings step by step.

​

Why it’s valuable

• One rule, many assistants: Set an org-wide default or share override logic where it makes sense, instead of duplicating long prompts on each assistant.
• Structured outputs: Fields have names, types, and update behavior so outputs stay consistent for your team and downstream tools.
• Automations and CRMs: Custom fields can flow through your Zapier integration so you can branch workflows, update records, or run post-processing outside Replify.

​

How this relates to the old Analysis Settings

Previously, Analysis Settings focused on three global custom instruction blocks for your assistant (qualification, conversation summary, and next steps). That worked, but the instructions lived per assistant and were easy to repeat or drift out of sync across a large team of assistants. The upgraded Analysis Settings keeps those ideas, you still guide how the AI interprets conversations, but expresses them as fields and rules you can reuse across assistants. Migration: Your existing Analysis Settings were migrated automatically into this new experience, the prior custom instructions carry forward as rules on the appropriate fields, so you should not need to recreate them by hand.

​

Destinations: Contact vs Conversation

Use destinations based on who or what should “hold” the value:

​

System vs custom fields

​

Assigning rules: org default vs assistant override

For system fields, your override rules sit on top of the field’s built-in default rule. For custom fields, every rule is one you author. When you create or edit a rule, you choose how widely it applies:

• Org default — One canonical prompt for that field across your organization (unless an override applies).
• Assistant override — Applies only to specific assistants you pick. Use when one assistant needs different wording or criteria than the rest.

This is how you stop duplicating the same block of instructions on every assistant: write the rule once, assign it as the default or to the assistants that need an exception.

​

Creating a new custom field (what each input means)

When you create a field, you’ll fill in details like the following. After the field exists, you add rules (prompts) and assignments as described above.

​

How to use it (day-to-day)

1. Open Settings → Analysis Settings, or go directly to .
2. Use search and filters to find fields by source (System vs Custom), destination (Contact vs Conversation), or timing (Immediate vs Standard).
3. Switch between Active and Inactive lists to manage fields you’ve turned off versus ones in use.
4. Click a field to open its detail panel. For custom fields, edit field settings and rules as needed. For system fields, the field definition is read-only—use rules to layer overrides on top of the built-in default rule.
5. Use Create field when you need a new custom field.

​

View rule output in the Inbox

The practical way to test a new or updated rule, especially a custom rule, is to run a new conversation the rule applies to, then open that thread in the Inbox. Analysis values appear under “Custom Analysis Fields”:

• In the Conversation Details section for that conversation, and
• In the Contact detail panel on the right (for values stored on the contact).

Use those spots to confirm the AI produced the output you expected before you rely on it in Zapier or downstream workflows.

​

Assistants tab

An Assistants tab may appear for future functionality that will continue to improve the experience.

​

Ideas for what to use it for

• Sales and routing — Capture qualification, urgency, or product interest once, reuse everywhere.
• Operations — Session-specific notes on the conversation vs durable traits on the contact.
• Automation — Push custom field values to Zapier for CRM updates, Slack alerts, or spreadsheet logging.

​

What else you should know

Covering common questions so nothing important is buried:

• Turning fields off — You can disable custom fields when you no longer want them filled on future conversations; historical values will remain visible where they were already saved.
• Zapier — Custom fields are the usual hook for post-processing outside Replify, e.g. if something specific happens in a conversation, then handle that conversation differently, using these custom fields to route.
• Testing rules — There isn’t a separate “preview” required in Settings: add or edit your rule, complete a test conversation, then confirm values under “Custom Analysis Fields” in the Inbox—see View rule output in the Inbox.