One row is
one flow run
Delivery
Rewritten daily
Columns
41
Where it lands
snapshot_date= partition only, and check for _SUCCESS before you do, as
described in bucket layout.
Columns
Join key. Unique id of the flow run. Matches
response_bot_result_id on claudia_prompt_revision.Id of the flow that ran. Matches
active_flow_id on claudia_conversation.Whether the customer actually entered the flow.
false means it was triggered but never began.Whether the customer started the flow and stopped partway. Pair it with
last_group_title to find the step people give up on.Title of the last step reached. This is the column to group by when looking for where a flow loses people.
How the last step was determined:
entry from the step the customer entered, subflow from a nested flow, sem_edge when the step had no outgoing path, nao_encontrado when it could not be resolved.Conversation the run belongs to. See
key_source for which identifier this holds before joining on it.Which identifier
conversation_key holds: helpdesk for the external helpdesk id, session for the flow session, result_id when neither was available. Check this column before you join.Minutes to the first response, counting only the operation’s working hours. Use this one when comparing against an SLA.
Resolution reason of the conversation, in the same refined form as on
claudia_conversation.Whether the customer came back with the same subject after this run. A flow with a high completion rate and a high recontact rate is answering the wrong question.
frustration_score_value bucketed into a label: CALM, IRRITATED, FRUSTRATED or HIGHLY_FRUSTRATED.How the run ended, in one column:
completou finished, abandono was abandoned partway, escalou_n2 escalated, n1_com_decisao ended at N1 with a decision taken, nao_iniciou never started, em_aberto was still running, sem_conversa had no conversation attached. Labels are in Portuguese in the data.