Custom attributes for contacts

Oct 20, 2026 को अपडेट किया गया5 मिनट में पढ़ें
हिन्दी
इस पेज पर

Custom attributes let you store extra structured data on contacts or conversations beyond the default fields. Examples: a contact's plan tier, lifetime value, NPS score; a conversation's product area or escalation reason. Pick a type (text, number, list, date, checkbox, link), give it a name, and the field shows up on every contact or conversation panel. Automation rules can check them, and your own systems can set them over the API.

Custom attributes let you store additional data on contacts beyond the default fields. Whether you need to track a customer's subscription tier, preferred language, or account ID, custom attributes give your team the flexibility to capture the information that matters most to your workflow. Custom attributes are available on the Business and Enterprise plans, and administrators create them.

Why use custom attributes?

Every business collects different data points about its customers. The default contact fields,name, email, phone number,cover the basics, but they rarely tell the whole story. Custom attributes let you:

  • Personalize conversations by surfacing relevant details (e.g., plan type or company size) directly in the contact sidebar.
  • Automate with automation rules that check attribute values as conditions.
  • Maintain a single source of truth so agents don't have to switch between tools to find key information.

Creating custom attributes

Follow these steps to add a new custom attribute:

  1. Navigate to Settings > Custom Attributes.
  2. Click New Attribute.
  3. Under Applies To, choose whether the attribute is for a Contact or a Conversation.
  4. Enter a descriptive Display Name (e.g., Subscription plan). The key (e.g., subscription_plan) is built from it and can't be changed later.
  5. Select the Type (Text, Number, Link, Date, List or Checkbox). For a List, type each option into Options and press Enter.
  6. Click Create Attribute. The new attribute immediately appears in the right panel of every conversation and, for contacts, on the contact's Attributes tab.

Best practices

  • Use clear, consistent naming. Stick to a naming convention,such as lowercase with underscores,so attributes are easy to identify at a glance.
  • Choose the right data type. Selecting "list" for a field with a fixed set of options (e.g., plan tiers) prevents typos and keeps data clean.
  • Avoid duplicating default fields. Before creating an attribute, check whether the information is already captured by a built-in field.
  • Review periodically. Delete attributes that are no longer in use to keep the interface uncluttered for your agents.

Common pitfalls & troubleshooting

  • Attribute not showing up? Make sure you selected the correct model (Contact vs. Conversation) when creating it.
  • Inconsistent data entries? Consider switching from a free-text type to a list type to standardize values across your team.
  • Accidentally created a duplicate? Delete the extra attribute from Settings > Custom Attributes before agents begin populating it, to avoid data fragmentation.

Frequently asked questions

Can I edit or rename a custom attribute after creating it?
Yes. Navigate to Settings > Custom Attributes, locate the attribute, and update its display name, description, type or list options. The key and Applies To can't be changed. Existing data stored under that attribute will be preserved.
What types of fields can I create?
Six: text (free entry), number (integer/decimal), list (predefined options dropdown), date, checkbox (boolean), and link (URL that renders clickable).
Should I use a list or text type for a value with few options?
List. Always list when the value is constrained. Text invites typos ('Premium' vs 'premium' vs 'PREM') that break automation rule conditions. Lists keep your data normalized.
Can I create custom attributes on conversations too?
Yes. Choose Conversation under Applies To when creating the attribute. Useful for ticket-specific tags like 'escalation reason' or 'product area' that don't apply to the customer in general.
How do I bulk-update custom attribute values?
Via the API (API tokens need the Enterprise plan) or a CSV import: an administrator opens Settings > Import & Migration, picks the CSV import and maps the column to Custom Attribute. The value is saved under the column header, so name the column like the attribute's key (e.g. subscription_plan). Existing contacts with the same email get the values applied as updates.
Can the AI bot read custom attributes?
Copilot does: it reads the contact with its custom attributes when it helps you with a conversation. Fynn's bot instructions have no placeholders for attribute values such as {{contact.attributes.plan}}. Fynn uses a contact's attributes only in a live chat with a visitor your website verified, only when Contacts is on under Data Access in the bot settings, and only the attributes your website signed (see the widget developer docs). Fynn can then tell the customer what those attributes say. Attributes sent without a signature, or set in the dashboard or through the API, never reach Fynn and stay with your team.
Are custom attribute values visible to customers?
No. They're internal-only metadata. Customers never see them directly, though Fynn may tell a verified visitor what your website's signed attributes say (see the question about the AI bot above). If you want to surface them to customers, build the display yourself in your widget or transactional emails.
Can I rename an attribute after data already exists?
Yes. Only the display name changes; the key and the stored values stay as they are. Useful when you realize your initial naming convention was off.
What happens when I delete an attribute that has data?
Only the attribute itself is deleted, and that can't be undone. Values already saved stay on the contacts and conversations and show read only below the other attributes.
Is there a hard cap on number of attributes?
No hard cap. Past roughly 30 to 50 attributes, the contact sidebar gets cluttered. Review them yearly and delete what you don't use. A List attribute can have up to 100 options.
Can I use custom attributes in automation rules?
Yes. Rules can match on attribute values ('if contact.plan = Enterprise → assign to enterprise team'). One of the most useful patterns for plan-tier-aware routing. Rules and macros can't set or change attribute values.
Are attribute changes tracked in the audit log?
Partly. On Enterprise, the audit log records that a conversation's attributes were changed, with who and when, but not the old and new values. Changes to contact attributes are not logged.
Can I display attributes on the public chat widget?
No, attributes stay agent-side. Your website can set contact attributes through the widget with window.deskwoot.identify, but only with Identity Verification set up for the inbox.

क्या यह गाइड मददगार थी?

आगे पढ़ें

इस गाइड के बारे में Fynn से पूछें

इस गाइड और बाकी सहायता केंद्र से छोटा जवाब पाएं।

अब भी मदद चाहिए?

Fynn चैट में इन गाइड से जवाब देता है, और वहीं आप टीम से भी बात कर सकते हैं।

हमें ईमेल करें