People

Entity: People

1. Overview

The entity People is the core of Hablla's data modeling and represents any individual the organization interacts with — whether customer, prospect, lead, partner or internal contact.

In the context of MCI (Integrated Conversational Marketing), People it is the basis for centralizing and unifying interactions across multiple channels, ensuring that each conversation is contextual, personalized and data-driven.


2. Entity Objectives

  • Unify contact data from multiple channels into a single record.

  • Consolidated interaction history for a 360º view of the relationship.

  • Enable personalization in campaigns, flows and support.

  • Support compliance with LGPD and data governance.


3. Attributes and Standard Fields

Field
Description
Data Type
Example
Notes

Internal ID

Unique identifier generated by the Hablla platform

UUID

3f9c2b...

Not editable

Full Name

Individual's name

Text

João da Silva

Required

Email

Electronic address

Text / Email

Validated

Phone (WhatsApp)

Number for communication via WhatsApp

Text / Numeric

+55 11 91234-5678

E.164 Format

Instagram Identifier

Instagram profile ID

Text

17841405793187218

Obtained via API

Facebook Identifier

Facebook profile ID

Text

1000123456789

Obtained via API

Telegram ID

Unique contact ID on Telegram

Text

123456789

Obtained via Bot

Phone (voice)

Number for phone calls

Text / Numeric

+55 21 99876-5432

Interaction History

Complete record of messages, calls and activities

Record

Automatic update

Tags

Tags for segmentation

Text list

["VIP Customer", "Black Friday 2025"]

Free

Acquisition Source

Contact origin

Text

WhatsApp Ads Campaign

Consent Status

Indicates whether there is authorization for communications

Boolean

true

LGPD-compliant


4. Relationships with Other Entities

Entity
Relationship Type
Description

Organizations

N:N

A Person can be associated with multiple Organizations (and vice-versa).

Cards

1:N

A Person can be linked to several Cards (opportunities, tickets, support cases).

Tasks

1:N

A Person can have Tasks associated directly or indirectly.


5. Business Rules

  1. Multichannel Identification

    • Each channel has its unique identifier (e.g., Instagram ID, WhatsApp phone).

    • The same individual may have different IDs per channel.

  2. Record Unification

    • Merging duplicate records must follow data prioritization rules (most recent update > most complete).

  3. Immutable History

    • Recorded interactions cannot be deleted, only hidden for compliance reasons.

  4. Mandatory Consent

    • Proactive communications require consent status true.


6. Usage Examples

  • Marketing: Lead segmentation of those who interacted on Instagram in the last 30 days.

  • Sales: Identification of decision-makers linked to the same Organization.

  • CX: Retrieve a customer's complete history before a support call.


7. Best Practices

  • Update data whenever a new interaction brings more accurate information.

  • Use standardized tags to facilitate segmentation.

  • Avoid duplicates from importing untreated lists.

  • Keep consent reviewed periodically to avoid campaign blocks.


8. Security and LGPD Considerations

  • Store only data necessary for operation.

  • Ensure that data deletion requests are processed within the legal timeframe.

  • Log changes and accesses to the Person's profile.

Last updated

Was this helpful?