# Live Chat Reporting **URL:** \ **Category:** Lead Capture Tools\ **Created:** [June 20, 2022, 10:04pm UTC](https://community.hubspot.com/t/live-chat-reporting/59407 "2022-06-20T22:04:04Z")\ **Posts on this page:** 13\ **Page:** 1
**Author:** ![GHunt5](https://avatars.discourse-cdn.com/v4/letter/g/ccd318/32.png) [@GHunt5](https://community.hubspot.com/u/GHunt5)\ **Post date:** [June 20, 2022, 10:04pm UTC](https://community.hubspot.com/t/live-chat-reporting/59407/1 "2022-06-20T22:04:04Z")
I am having a terrible time reporting on our live chat leads. Does not appear there are any object fields related to live chat that I can use to build a list. This is as close as I am getting but this is not very helpful. Can some one tell me a better way? We are using HS chat function ![GHunt5_0-1655762621836.png](https://d2qpr2jzcazej7.cloudfront.net/original/3X/0/6/068700210fa8b113fe8774a114c30ed31d153ee1.png) ---
**Author:** ![jnix284](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/jnix284/32/29_2.png) [@jnix284](https://community.hubspot.com/u/jnix284)\ **Post date:** [June 21, 2022, 1:28am UTC](https://community.hubspot.com/t/live-chat-reporting/59407/2 "2022-06-21T01:28:15Z")
Hi @GHunt5 Just a thought - you could create a workflow to turn your live chat conversations into tickets, then you would have more data to use for lists, like ticket create date, status, etc. 🤔 ---
**Author:** ![GHunt5](https://avatars.discourse-cdn.com/v4/letter/g/ccd318/32.png) [@GHunt5](https://community.hubspot.com/u/GHunt5)\ **Post date:** [June 21, 2022, 3:52pm UTC](https://community.hubspot.com/t/live-chat-reporting/59407/3 "2022-06-21T15:52:55Z")
How would I differentiate net new vs existing conatact? ---
**Author:** ![jnix284](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/jnix284/32/29_2.png) [@jnix284](https://community.hubspot.com/u/jnix284)\ **Post date:** [June 21, 2022, 6:11pm UTC](https://community.hubspot.com/t/live-chat-reporting/59407/4 "2022-06-21T18:11:20Z")
That would definitely get more challenging, you could look at creating a custom property to calculate the days between contact create date and ticket create date and then include a rule in your workflow to exclude greater than 1. This knowledge base article will [explain how to set up the calculation between dates](https://knowledge.hubspot.com/crm-setup/create-calculation-properties). ---
**Author:** ![GHunt5](https://avatars.discourse-cdn.com/v4/letter/g/ccd318/32.png) [@GHunt5](https://community.hubspot.com/u/GHunt5)\ **Post date:** [June 21, 2022, 6:35pm UTC](https://community.hubspot.com/t/live-chat-reporting/59407/5 "2022-06-21T18:35:04Z")
I dont have the ticket functionality either so there is that awesome gem ---
**Author:** ![jnix284](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/jnix284/32/29_2.png) [@jnix284](https://community.hubspot.com/u/jnix284)\ **Post date:** [June 21, 2022, 6:52pm UTC](https://community.hubspot.com/t/live-chat-reporting/59407/6 "2022-06-21T18:52:28Z")
Can you see any of these properties in your list or report? ![conversation-chat-sessions.png](https://d2qpr2jzcazej7.cloudfront.net/original/3X/1/8/18ea09aac50dc6c1e0b1e3e14b39b4ca19392af7.png) ---
**Author:** ![GHunt5](https://avatars.discourse-cdn.com/v4/letter/g/ccd318/32.png) [@GHunt5](https://community.hubspot.com/u/GHunt5)\ **Post date:** [June 22, 2022, 1:52pm UTC](https://community.hubspot.com/t/live-chat-reporting/59407/7 "2022-06-22T13:52:07Z")
No I cannot. I only have a list with the above filteres applied ---
**Author:** ![Greg-dAboville](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/greg-daboville/32/53612_2.png) [@Greg-dAboville](https://community.hubspot.com/u/Greg-dAboville)\ **Post date:** [July 29, 2022, 9:25am UTC](https://community.hubspot.com/t/live-chat-reporting/59407/8 "2022-07-29T09:25:21Z")
Would love to hear more about this @Jnix284! I haven’t found a way to use ticket create date in a calculated field 😞 ---
**Author:** ![jnix284](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/jnix284/32/29_2.png) [@jnix284](https://community.hubspot.com/u/jnix284)\ **Post date:** [July 29, 2022, 1:03pm UTC](https://community.hubspot.com/t/live-chat-reporting/59407/9 "2022-07-29T13:03:38Z")
@Greg-dAboville let me see what I can come up with, I have a few things to knock out this morning but I can play around with it this afternoon. ---
**Author:** ![Greg-dAboville](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/greg-daboville/32/53612_2.png) [@Greg-dAboville](https://community.hubspot.com/u/Greg-dAboville)\ **Post date:** [July 29, 2022, 1:23pm UTC](https://community.hubspot.com/t/live-chat-reporting/59407/10 "2022-07-29T13:23:32Z")
Thanks!! ---
**Author:** ![jnix284](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/jnix284/32/29_2.png) [@jnix284](https://community.hubspot.com/u/jnix284)\ **Post date:** [August 8, 2022, 2:24pm UTC](https://community.hubspot.com/t/live-chat-reporting/59407/11 "2022-08-08T14:24:13Z")
@Greg-dAboville sorry for the delay on this, but I think I cracked it. 1 - create a custom ticket date property for “contact created” 2 - use a workflow to copy the contact create date to this new property 3 - create a calculated ticket property for time between this new ticket date property and ticket create date ---
**Author:** ![Greg-dAboville](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/greg-daboville/32/53612_2.png) [@Greg-dAboville](https://community.hubspot.com/u/Greg-dAboville)\ **Post date:** [August 19, 2022, 8:05am UTC](https://community.hubspot.com/t/live-chat-reporting/59407/12 "2022-08-19T08:05:48Z")
Thanks Jennifer, I’m going to give it a try 🙂 ---
**Author:** ![Greg-dAboville](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/greg-daboville/32/53612_2.png) [@Greg-dAboville](https://community.hubspot.com/u/Greg-dAboville)\ **Post date:** [July 29, 2022, 2:54pm UTC](https://community.hubspot.com/t/live-chat-reporting/59407/13 "2022-07-29T14:54:09Z")
This way to flag them is actually very smart! Thanks for sharing it 🙂