Contacts & lead data

Contact fields across the inbox and AI

Keep contact forms, the conversation panel, variables and agent write permissions aligned.

Before you start

Use a test channel or sample conversation first. Confirm the visible result in ValueChat before applying the setup to production traffic.

How it works

  1. 01

    Definitions

    Definitions. Standard fields cover identity, contact information, location, biography, company and supported social profiles. Create extra typed Contact attributes from Settings; Conversation attributes are a different scope.

  2. 02

    One record

    One record. Contacts and the customer panel in a conversation display the same contact record. Configured fields can be shown even when empty; zero and false are real values, not missing data.

  3. 03

    Agent permissions

    Agent permissions. A field existing in the workspace does not automatically grant every agent permission to read or update it. Add the intended typed field/value references and update instructions in the agent skill.

  4. 04

    Variables and mentions

    Variables and mentions. Use $ for available contact values and variables, and @ for linked assignment, knowledge and other supported references. A displayed label is not an authorization rule; the saved reference identifies its target.

  5. 05

    Columns

    Columns. Customize the Contacts table columns and order for the account/user view. A hidden table column does not delete its field or saved value. Relevant field changes can invalidate qualification until reassessment.

What to verify

✓The expected channel, conversation, contact or execution is visible.

✓The assigned person or agent matches the routing rule.

✓No customer-facing message claims an action that failed.

✓Activity or execution history contains enough context to investigate.

Need help?

Collect the workspace, channel, conversation and execution identifiers, then contact support@valuechat.app. Never send API keys or passwords.