Kraya-AI Docs
Leads

Attribute Data Types

Custom attribute types for leads: text, number, date, datetime, dropdown, boolean, email, phone, URL.

Overview

Custom Attributes now support multiple data types so your lead data is accurate and easy to work with. You can define attributes as Text, Number, Date, Datetime, or Dropdown, use typed inputs in the Chrome Extension and Dashboard, and rely on consistent behavior during imports, bulk updates, and AI-powered autofill.

You can also add an optional Description to each custom attribute to explain what the field is for. Descriptions appear in the Manage Attributes list and help the AI interpret ambiguous names when it fills attributes from conversations.

What you can do

  • Create and manage custom attributes with data types: Text, Number, Date, Datetime, Dropdown
  • Add an optional Description (up to 1000 characters) so teammates and the AI know what each attribute means
  • Edit attribute names, change types, manage dropdown options, and update descriptions independently when needed
  • Enter typed values in the Extension sidebar and Dashboard Edit Lead modal
  • Filter leads using typed controls (comparators for Number, date/datetime range pickers, dropdown multi-select)
  • Import/bulk update leads with client-side validation against your attribute schema
  • Let AI autofill typed attributes when confidently inferred, with clearer context when descriptions are set

How it works

  • Your organization has an attribute schema that defines each attribute's type and, for dropdowns, the allowed options.
  • Description is optional. If you add one, it is saved with the attribute and shown under the attribute name in the Manage Attributes list (smaller, secondary text). Hover or focus where supported to see the full text if it is long.
  • When AI runs steps that infer custom attribute values from the conversation (such as conversation summaries and qualification-related summaries), it can use your descriptions to understand what each attribute is meant to capture.
  • UIs render the correct input for each type:
    • Text → text input
    • Number → numeric input (supports decimals and negatives)
    • Date → date picker (stores YYYY-MM-DD)
    • Datetime → date+time picker with seconds (stores YYYY-MM-DD HH:mm:ss, 24h)
    • Dropdown → select from configured options; empty shows a placeholder
  • When you change an attribute's type, existing values that don't match the new type are cleared to keep data valid. You'll see a warning before saving. Updating only the description does not clear stored lead values the way a type or name change can.
  • Invalid data from previous entries/imports may appear as empty (null) after a type change; tooltips or toasts explain when values were cleared.

Step-by-step guide

Creating a custom attribute

  1. Open Manage Attributes
    • Extension: Click "Add/Manage Attributes" in the Additional Info section
    • Dashboard: Open any lead, then click "Manage Attributes"
  2. Click "+ Add New Attribute"
  3. Enter Attribute Name and choose a Format (Text, Number, Date, Datetime, Dropdown)
  4. If Dropdown, add up to the allowed number of options
  5. Optionally fill Description with a short explanation. A character counter shows how many characters you have used out of 1000.
  6. Save

Editing an attribute

  1. Open Manage Attributes and click the edit icon for an attribute
  2. Change the name, type, or (for Dropdown) edit options, and/or update Description
  3. If changing type, review the warning (non‑matching existing values will be cleared)
  4. Save

Deleting an attribute

  1. Open Manage Attributes and click the delete icon for an attribute
  2. Confirm the deletion
  3. The attribute is removed from all leads; values are no longer shown

Settings and configuration

  • Attribute name rules:

    • Attribute names may contain: letters (a–z, A–Z), numbers (0–9), spaces, hyphens (-), underscores (_), dots (.), slashes (/), and ampersands (&)
    • Special characters not in the above list (e.g., @, #, !, %, ^, (, )) are not allowed
    • If you enter a disallowed character, you'll see the error: "Attribute name can only contain letters, numbers, spaces, hyphens (-), underscores (_), dots (.), slashes (/), and ampersands (&)."
    • This validation applies when creating a new attribute (name field) and when renaming an existing attribute
  • Description (optional):

    • Label: Description
    • Multiline field with a 1000-character maximum
    • Leave empty if you do not need extra context
  • Dropdown options:

    • Add, remove, or rename options
    • Options must be unique (case-insensitive)
    • UI shows a placeholder when the value is empty
  • Schema fetch:

    • Extension and Dashboard fetch the attribute schema and cache it for the session
    • After changes, UIs refresh automatically so new types/options and descriptions appear immediately
  • Plan-based attribute limits:

    • Free plan: up to 10 custom attributes per organization. Reaching the limit shows an upgrade prompt.
    • Paid plans: up to 50 custom attributes per organization. Reaching the limit shows a "Max attributes limit reached (50)" message; contact your Kraya POC if you genuinely need more.

Role-based behavior

  • Admins:
    • Can create, edit, and delete attributes
    • See warnings and confirm type changes that may clear invalid values
  • Members:
    • Can edit attribute values in leads using typed inputs
    • May not be able to add or remove attributes depending on org policy

Limits and quotas

  • Custom attributes (free plan): up to 10 attributes per organization.
  • Custom attributes (paid plans): up to 50 attributes per organization.
  • Attribute name: allowed characters are letters, numbers, spaces, -, _, ., /, &
  • Description: up to 1000 characters per attribute
  • Dropdown options: up to 50 options in UI (larger backend limit may exist)
  • Default type: Text (existing attributes without a type are treated as Text)
  • Type changes never block saving; invalid existing values are cleared to keep data valid

Common edge cases

  • Type change clears values When you switch, any existing value that doesn't match the new type is cleared. For example, "abc" in a Number field becomes empty.
  • Description-only changes You can save after changing only the description. Stored lead values for that attribute are not cleared by that action.
  • Removing a description Clear the Description field and save; the list no longer shows secondary text for that attribute.
  • Empty or null values For Number/Date/Datetime/Dropdown, empty is shown as a placeholder until you select a value.
  • Dropdown mismatch If a value is no longer in the option list, it becomes empty. Choose a valid option to restore.
  • Timezones Date and Datetime display in your organization's timezone; stored in normalized formats.

Troubleshooting

Invalid number keeps clearing

  • Cause: Input contains non-numeric characters
  • Fix: Enter a valid integer or decimal (e.g., -12, 3.14)

Date won't save

  • Cause: Not in DD-MM-YYYY
  • Fix: Use the date picker or enter DD-MM-YYYY

Datetime format mismatch

  • Cause: Time not included or wrong format
  • Fix: Use date+time picker; stored as YYYY-MM-DD HH:mm:ss (24h)

Dropdown value missing

  • Cause: Option removed or renamed
  • Fix: Pick a current option from the list

Description does not appear in the list after save

  • Cause: Field was empty or only spaces (saved as no description)
  • Fix: Open edit again, enter text in Description, and save

Attribute name won't save — "can only contain letters, numbers..." error

  • Cause: The name contains a character that is not allowed (e.g., @, #, !, %)
  • Fix: Remove the special character. Allowed characters are: letters (a–z, A–Z), numbers (0–9), spaces, hyphens (-), underscores (_), dots (.), slashes (/), and ampersands (&)

FAQs

  • Can I change an attribute's type later? Yes. Changing type doesn't block saving. Values that don't match the new type are cleared.
  • Do imports respect types? Yes. Invalid values are rejected or coerced to empty; you'll see warnings in the UI.
  • Can AI fill these fields? Yes. AI populates attributes when confidently inferred; invalid or mismatched values become empty.
  • Do I need a description on every attribute? No. Descriptions are optional. They help when the attribute name alone might be unclear to people or to the AI.
  • Does the AI always read my description? When AI steps infer custom attributes from conversations, your description can provide extra context.
  • Which characters are allowed in attribute names? Letters (a–z, A–Z), numbers (0–9), spaces, hyphens (-), underscores (_), dots (.), slashes (/), and ampersands (&). Other special characters like @, #, ! are not allowed.

Tips and best practices

  • Use Description for business meaning that the attribute name does not carry (for example, units, what to extract from chat, or how a dropdown label should be interpreted).
  • Prefer Dropdown for small, consistent sets (e.g., Source, Region)
  • Use Number for counts, budgets, or amounts; avoid encoding units in text
  • Use Date/Datetime for scheduling and filtering; pickers prevent format errors
  • Keep option lists short and clear; merge near-duplicates
  • For attribute names, use hyphens or underscores to separate words (e.g., Lead-Source, budget_range) to keep names clean and readable

Screenshots

On this page