The /threads endpoint also does not have an "updateSince" filter and a way to mark the thread as closed.

When we fetch threads, we end up fetching all threads from the beginning of time and then check if there are any new messages under each of the threads. This is not efficient and not helping with the API limit of 10,000 calls per hour.

Use Case 1. Daily reporting for customer service workload, agent performance, first time to response, enquiry-to-conversion ratio, etc

For this use case, our plan is to pull the data related to all the threads, messages, leads, employees once, then everyday take the delta data load once for reporting updates.

Use Case 2. Build a true Omni-channel inbox+ticketing setup for our customer agents to respond to all inbounds instead of using two or three different tools.

For this we are trying to integrate Hostfully Inbox to Zoho Desk ticketing system and connect Zoho Desk Ticketing system with Turno for instant on demand cleaning requests from guests.
We want our customer service agents to use only Zoho Desk to respond to all the messages that we get from OTAs via Hostfully Inbox.