Setting Up Your Workspace

Field management (defaults and custom fields)

Field management (defaults and custom fields)

Fields are the backbone of every entity in Dalil AI. They define the type of information you capture about People, Companies, Opportunities, and other entities.

Dalil AI comes with a set of default fields to cover the essentials, but you can also customize your database by adding new fields that reflect your specific processes.

Default Fields

  • Every entity (People, Companies, Opportunities) comes with predefined fields such as Name, Job Title, Email, Phone, Company, and City.

  • These fields are standardized and cannot be edited or deleted, because they ensure consistency across all workspaces.

  • However, if you don’t want to see them, you can hide default fields from your views.

πŸ‘‰ Example: If you don’t care about City, you can hide it in the People table so your view stays clean.

Managing visibility in views

Dalil gives you full control over what fields are shown:

  • In Table or Kanban views, click the settings button (top-right of the table) to:

    • Select which fields to display

    • Hide fields you don’t need

    • Reorder fields to match your priorities

πŸ‘‰ Example: You may want to place Dalil Score next to Job Title so your team always sees priority alongside role.

Adding Custom Fields

You can add new fields in two ways:

  1. From the main dashboard, click the + button on the right side of the table.

  2. From Entity settings, select the entity and click β€œAdd Custom Field.”

When creating a new field, you’ll be asked for:

  • Type (e.g., text, number, select, stage)

  • Name (how it will appear in records)

  • Options/Settings (depending on type)

  • Description (optional, but recommended) β†’ helps your team and also improves Dalil AI’s ability to read and interpret data.

Types of Fields

Dalil offers a wide range of field types:

  • Text β†’ free text (e.g., Notes, Job Function)

  • Number β†’ numeric values (e.g., Revenue, Employee Count)

  • Currency β†’ numbers with currency formatting (e.g., Deal Value)

  • Date & Time β†’ deadlines, renewal dates, meetings

  • Email / Phone / Links β†’ structured contact fields

  • Select β†’ choose one option from a predefined list

  • Multi-select β†’ choose multiple options from a list

  • Stage β†’ define process steps (special type, explained below)

  • True/False β†’ yes/no fields (checkbox-style)

  • Rich Text β†’ formatted notes with more detail

  • Unique ID β†’ system-generated identifiers

  • Relation β†’ link this entity to another (e.g., Person β†’ Company)

  • Actor β†’ assign responsibility (e.g., Account Manager)

Select vs Multi-select vs Stage Fields

These three are often confused, so let’s break them down clearly:

Select

  • Use when each record should have one clear value.

  • Example: Lead Source = Website, LinkedIn, Referral.

  • A record can only belong to one option at a time.

Multi-select

  • Use when each record may have several values simultaneously.

  • Example: Services Interested In = CRM, Analytics, Integrations.

  • A record can carry multiple options at once.

Stage (special type in Dalil AI)

Stages are designed for process tracking and work differently from Select.

  • Stages define the journey of a record (e.g., an Opportunity or a Company in a pipeline).

  • Dalil includes three stage types:

    • Standard Stage β†’ regular step in a process (e.g., Discovery, Proposal Sent).

    • Closed Won β†’ indicates the record reached success.

    • Closed Lost β†’ indicates the record ended unsuccessfully.

  • This distinction is important because Dalil AI uses stage data to analyze success rates, forecast outcomes, and trigger AI scoring or signals.

πŸ‘‰ Example:

  • A Sales pipeline may include Discovery β†’ Proposal β†’ Negotiation β†’ Closed Won / Closed Lost.

  • By distinguishing between standard vs end stages, Dalil AI knows how to measure performance and provide insights.

Closed Lost reasons

When a record reaches Closed Lost, Dalil lets you add a reason for loss (e.g., Budget, Competitor, Timing, No Decision).

  • These reasons give you a clear understanding of why opportunities are lost.

  • Dalil AI uses this information to surface patterns, insights, and tips for improving win rates in the future.

πŸ‘‰ Example: If 60% of lost deals are due to β€œBudget,” managers can quickly see the trend and adjust pricing strategy, targeting, or messaging.

Why descriptions matter

When creating custom fields, adding a description is strongly recommended:

  • It helps your team know exactly how to use the field.

  • It gives Dalil AI additional context to interpret the data correctly, which improves AI insights, signals, and automation accuracy.

Key outcome

By managing default and custom fields effectively, you make Dalil AI truly reflect your business.

  • Default fields keep the essentials covered.

  • Custom fields let you capture unique business-specific data.

  • With Stage fields, you ensure AI understands success vs failure.

Together, this gives you a structured CRM that both humans and AI can use seamlessly.

Β© Copyright 2024. All rights reserved.