cloud_chat_messages.
One row is
one message
Delivery
Daily delta on
etl_updated_atColumns
19
Where it lands
etl_date= partition to reconstruct the table. One of them is
etl_date=__initial__, the first load, holding everything that preceded the
earliest daily partition. Check for _SUCCESS before reading a partition, as
described in bucket layout.
Columns
Join key. Conversation the message belongs to. Matches
cloudchat_id on claudia_conversation.Who sent the message:
USER for the customer, AGENT for the agent or the person who took over.When the message was sent. Order by this column within a conversation to reconstruct the transcript.
Whether the message was an internal note rather than something the customer saw. Exclude these when you rebuild a transcript.
How the message was produced:
STATIC for a fixed text, FLOW for a step in a controlled flow, OTHER for everything else.The customer question this message answers, as the agent understood it. This is the interpreted query, not necessarily the customer’s literal words.
Which response strategy produced the message. The value is a fully-qualified internal class name and its exact string is not part of the delivery contract: read the trailing segment, for example
LowConfidenceResponse, ClarificationResponse or N2SectionResponse.Medium of the message, in the same fully-qualified form as
originated_from_class. The trailing segment is the useful part: TextMessage, ImageMessage, AudioMessage or FileMessage.When the datamart last wrote this row. This is the cursor for the daily delta: a partition holds the rows whose
etl_updated_at fell on that day, so a message edited later reappears in a later partition.