All topics
Get started8Account, team & permissions44Units & fields70Records, views & tasks39WhatsApp & Cortex Chat68Email & social27Lead ads & distribution38Automations52Documents & quotes32Dashboards40Cortex AI18Developers & API12
Help Center·448 guidesAll topicsContact support

How a chat becomes a client record

Every new client who messages you can become a record automatically in the unit linked to the session, and every record shows all its chats from every channel. That keeps the client’s history in one place.

6 min
Before you start · 2 things · for everyone
A session linked to a unit, an identifier field such as the mobile number
  • Link the session to a Cortex Unit from the channel’s settings, such as WhatsApp Web.
  • The unit must have the identifier field: the mobile number, for WhatsApp.

Automatic creation

When a chat that isn’t linked arrives from a session linked to a unit, Corteksa looks for a record with the same identifier. If it finds one, it links the chat to it; otherwise it creates a new record.

Channel
Identifier
Source value
WhatsApp Web
Mobile number
whatsapp_web
WhatsApp Cloud
Mobile number
whatsapp_cloud
Facebook
The user’s Facebook ID
facebook, or facebook_comment for comments
Instagram
The user’s Instagram ID
instagram or instagram_comment
TikTok
The user’s TikTok ID
tiktok or tiktok_comment

When no record is created

No record is created if: the chat is a WhatsApp group, the session has no linked unit, the unit has no identifier field, the chat is a test chat from testing an automation, or the chat is already linked to a record.

Duplicates

If a number that’s already in another record messages you, Deduplication Control decides what happens: Off (the default: find or create), Separate + Flag (a separate record flagged as a duplicate), Unify (one record), Mirror (the chat shows on every record in the duplicate group), or Comment. A chat shows a mark if the same number is in another chat.

Chats inside the record

The record’s chats tab shows all the client’s chats from every session, including the ones mirrored to it by Deduplication Control.

Moving a record to another unit

When you move a record, its chats move with it. If the client messages you later from the old unit’s session, the chat is linked to the moved record and no duplicate record is created.

More tools

Start a chat from the record to link it straight away. To link many older chats at once, contact support.

If something goes wrong

What you see
Why
What to do
Chats without records
The session has no linked unit, or the unit has no identifier field.
Link a unit in the session’s settings. For older chats, start a chat from the record, or contact support to link many at once.
Two records for the same client
Deduplication Control is off, or the client messaged from two channels with different identifiers.
“The chat belongs to another record”
The chat is linked to another client.

A real example

Namaa Academy
The situation

The same student messages from Instagram and then from WhatsApp, and two records show with their name.

What they did
  1. They turned on Deduplication Control on the “Leads” unit, matching on the mobile number, in Unify mode.
  2. The system now links the new chat to the existing record.
The result

Every student has one record that holds all their chats.

A made-up company, to show the idea. The numbers are rounded.

Good to know

A chat is linked to only one record at a time.
WhatsApp groups never create records.
Test chats from automations don’t create records.
Did this guide solve it?
If not, we’ll ask what was missing.
Open in Corteksa
Did this guide solve it?

We read every answer. To get a reply, use Contact support.