Skip to main content
Your CRM already knows which accounts matter. Why leave that context behind when you open LinkedIn? Custom fields bring your own data into TalkToHumans, so it can change what you see and who you work next. Think ICP score, CRM stage, segment, owner, intent signal, or customer status.

​
Current scope

Custom fields currently apply to contacts. They do not apply to companies or conversations. Supported types: → string for short text values.
→ text for longer text.
→ number for scores and amounts.
→ date for calendar dates.
→ boolean for yes or no state.

​
Create a field

1

Open a contact view

Choose the contact view where you want the field to appear.
2

Open the column controls

Choose the option to add a custom field. Workspace admins can create and manage field definitions.
3

Define the field

Add a name, icon, and data type. Choose the type carefully because the field type cannot be changed after values depend on it.
4

Add it to the view

Keep the new field visible as a column, then place it where it helps the workflow.

​
Set field values

Custom field values cannot currently be edited by hand in the app. Update them through the public API. This keeps TalkToHumans connected to the system that owns the data: → Your CRM writes CRM stage.
→ Clay writes ICP score.
→ An internal model writes Intent level.
→ Your data warehouse writes Customer status. After values arrive, you can show them in the sidebar, use them as columns, and filter or sort contact views around them.

​
Example workflow

Suppose your CRM stores account ownership and a fit score.
1

Create the definitions

Add Owner as a string field and ICP score as a number field.
2

Write values through the API

Match each contact and send the current owner and score.
3

Build a working view

Filter for Owner = Robin and ICP score ≥ 80, then exclude existing customers.
4

Work the queue

Review each person with the CRM context beside the LinkedIn conversation.