April 2022link
We have added a new column, source
, to the MESSAGE
table.
March 2022link
We now capture deletes for the TEAM_MEMBER
and CONVERSATION_TAG
tables.
February 2022link
We have added a new column, first_message_in_meta_to
, to the CONVERSATION
table. The column stores the message recipient’s email address.
January 2021link
We have added a new column, satisfaction_level_first_answer
, to the CONVERSATION
table.
September 2020link
You can now exclude the following tables from the sync:
CARD
COMPANY
CONVERSATION
CUSTOMER
KOBJECT
MESSAGE
NOTE
NOTIFICATION
QUEUE
SHORTCUT
SNOOZE
TAG
TEAM
TEAM_QUEUE
USER
On your connector details page, go to the Schema tab and deselect the tables you want to exclude.
August 2020link
We have added two new columns, deleted
and deleted_at
, to the USER
table. You can use the two columns to identify the users that have been deleted from the Kustomer account.
We have added a new column, _fivetran_deleted
, to the COMPANY
, NOTIFICATION
, and CARD
tables. The _fivetran_deleted
column marks data that was deleted from the Kustomer account.
We have added two new tables, QUEUE
and TEAM_QUEUE
.
We have added a new column, queue_id
, to the CONVERSATION
table. The queue_id
column stores the foreign key to the QUEUE
table.
July 2020link
We now support Kustomer applications that are hosted in the European Union (EU) region. When you create a new Kustomer connector, you can now designate EU as the region.
April 2020link
We now capture deletes for the CONVERSATION
, CUSTOMER
, and NOTE
tables.
We have added a new table, MESSAGE_ATTACHMENT
, which stores message attachment details.
January 2020link
We have added a lookup table, MESSAGE_SHORTCUT
with the following fields:
message_id
shortcut_id
December 2019link
We now sync satisfaction level to the CONVERSATION
table. Each new satisfaction level column has the prefix satisfaction_level_
(for example, satisfaction_level_rating
).
October 2019link
You can now create Kustomer connectors through the Fivetran API.
September 2019link
We have added the following new fields to the CONVERSATION
table:
first_message_in_createdAt
first_message_in_id
first_message_in_sentAt
first_response_createdAt
first_response_id
first_response_responseTime
first_response_sentAt
first_response_time