dsrptlab/clientsflow
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix telegram contact identity context for in/out messages

Browse Source
This commit is contained in:
Ruslan Bakiev
2026-02-23 19:28:03 +07:00
parent 79f1012f41
commit 94d8d46693
2 changed files with 35 additions and 20 deletions
Download Patch File Download Diff File Expand all files Collapse all files

19
omni_chat/src/worker.ts
View File

@@ -212,19 +212,12 @@ function buildContactProfile(
normalized: OmniInboundEnvelopeV1["payloadNormalized"],
externalContactId: string,
): ContactProfile {
const firstName =
asString(normalized.contactFirstName) ??
asString(normalized.fromFirstName) ??
asString(normalized.chatFirstName);
const lastName =
asString(normalized.contactLastName) ??
asString(normalized.fromLastName) ??
asString(normalized.chatLastName);
const username =
asString(normalized.contactUsername) ??
asString(normalized.fromUsername) ??
asString(normalized.chatUsername);
const title = asString(normalized.contactTitle) ?? asString(normalized.chatTitle);
// Use only normalized contact-* fields (counterparty), avoid sender/chat fallbacks
// to prevent accidental renames to the business owner name on OUT events.
const firstName = asString(normalized.contactFirstName);
const lastName = asString(normalized.contactLastName);
const username = asString(normalized.contactUsername);
const title = asString(normalized.contactTitle);
const fullName = [firstName, lastName].filter(Boolean).join(" ");
const displayName =