Views in Dalil AI define how your CRM data is displayed and organized. They allow you to create different perspectives on the same records without changing the underlying data.

Each Entity (such as People, Companies, or Opportunities) and each Pipeline can have multiple views. This allows teams to quickly access the exact information they need without manually reapplying filters or settings.

Views help transform your CRM from a static database into a flexible workspace where data can be organized based on different workflows.

What a View is

A view is a saved configuration that defines how records appear in your workspace.

Each view combines several elements:

• Layout: The visual structure used to display records.

• Visible fields: Which fields are shown and in what order.

• Filters: Conditions used to include or exclude records.

• Sorting: The order in which records are displayed.

Example:

You could create a view showing People located in Dubai with a Dalil Score above 70, displaying only the fields Name, Job Title, Company, and Dalil Score, sorted by highest score first.

Views allow teams to focus only on the information relevant to their current task.

Where to find Views

Every entity in Dalil starts with a default All view.

You can create additional views from the top-left area of the entity screen, just below to the entity name.

Entities that support views include:

• People

• Companies

• Opportunities

• Task

• Notes

• Analytics

Pipelines also support multiple views. This allows you to analyze the same pipeline using different perspectives, such as a Kanban board by stage or a list view sorted by revenue.

List view vs Kanban view

Dalil provides two main ways to display records.

List (Table) view

List view displays records in rows and columns, similar to a spreadsheet.

This layout is ideal when you want to see many details at once.

Example:

A People view showing:

Name
Company
Job Title
Last Contacted
Dalil Score

List view is typically used for analysis, filtering, and data management.

Kanban view

Kanban view displays records as cards grouped by a field, usually a stage field.

This layout is useful for visualizing progress in a process.

Example:

An Opportunities pipeline showing deals moving through stages such as:

Discovery → Proposal → Negotiation → Closed Won / Closed Lost

Kanban views are ideal for pipeline management and workflow tracking.

You can switch between List and Kanban views at any time depending on the workflow you need.

Filters and sorting

Views become powerful when combined with filters and sorting.

Filters

Filters allow you to display only records that match specific conditions.

Examples:

City = Paris
Contact Type = Prospect
Opportunity Stage = Proposal
Created in the last 30 days

You can also filter based on relationships between entities.

Example:

Show People linked to Companies in the Healthcare industry.

Sorting

Sorting controls the order in which records appear.

Examples:

Sort by Dalil Score descending to prioritize the hottest opportunities.

Sort by Last Contacted date to identify contacts that need follow-up.

Sorting ensures the most important records appear first.

Saving and organizing Views

Once configured, views can be saved for quick access.

Saved views appear as tabs at the top of the entity or pipeline.

You can:

• Rename views to make them easier to understand

• Pin as default important views

• Access favorited views directly from the Sidebar

Favorited views appear as a tree structure in the Sidebar, nested under their parent entity or pipeline.

Example:

If you favorite a view called Enterprise Prospects inside the Companies entity, it will appear under Companies in the Sidebar.

This structure makes navigation faster and keeps your workspace organized.

Examples of views in action

Sales teams often create views tailored to specific workflows.

Examples include:

People
CEOs in Europe, sorted by Dalil Score.

Companies
Prospects in the Healthcare industry displayed in Kanban by customer journey stage.

Opportunities
Deals created in the last 30 days, displayed in List view sorted by Owner.

Customer success teams may also use multiple pipeline views.

Example:

Onboarding view
Shows companies in early stages with fields such as Kick-off Date, CSM, and Next Task.

Steady-state view
Displays active customers with renewal dates and expansion potential.

Views allow different teams to use the same CRM data for different objectives.

Why Views matter

Views provide several important benefits:

Save time
Filters and settings are saved, so teams do not need to reconfigure data each time.

Stay organized
Different workflows such as sales, fundraising, or customer success can each have dedicated views.

Collaborate better
Teams can share and favorite views to align around the same data.

Enable AI insights
Clear views help Dalil’s AI analyze records more effectively and provide context-aware signals and recommendations.

Key outcome

Views allow you to organize and explore your CRM data from different perspectives.

By using views effectively, your team can quickly switch between prospecting, pipeline management, and customer success workflows while always working with the same structured data.