What we've maxed out in current build: * Voice quality – OpenAI Realtime (best in class) * Reliability – retries, timeouts, backpressure all solid * KB search gap – filled with natural filler speech * Language – English + Hindi auto-detect

whatsapp, messenger, instagram, web-engage. blocker to: all tasks that require changes to the above integrations

Anytime a new org is created on prod; it should get auto-synced to test. Syncing limited to: - org data/config - vector data

Depends on 301 to be completed first. Anytime a new bug is added to the bugs report sheet: - wait for 5 mins -> check if priority value is empty -> then use prioritisation rules to GET priority -> update the priority on the sheet Not sure

- Number of members in team - Number of chats / AI msgs each month - Ticketing - Leads Qualification - Live chats support - AI messages - Channel integrations

-> Admins can add unlimited members to the org. -> They don't know what each role does. ->

God level options for: - clear leads, chats, bulk messaging campaigns

It is possible that some missing info was added in DB but currently no one updates its status. There needs to be a logic that would: - check if missing info still doesnt exist in db (simple keyword search) - if exists now: mark as irreleva

Original ETA: 27/Mar -> Contact Siddhant for KT of existing progress -> Already implemented to some extend in Node / Flask projects -> Understand the existing implementation -> Check if it works well for drmalpani.com, ivfmatters.co.uk, apn

For example: If someone from elefant directly DMs on messenger the do not let the AI reply for 15 mins. 1. try to reproduce it 2. debug why we are not tracking: are we not receiving Scenarios: case 1: staff messages a new customer (we h

Requirements unclear; we already mark pending tickets (stale) as resolved every month.

CI pipelines of all projects will have to be updated

https://docs.google.com/spreadsheets/d/1F4y7g0n198LWmZq5oI9oWIG5w5erW4nJB56lAqiavOk/edit?gid=763382465#gid=763382465

User might join from multiple devices / channels. But DB stores only one channel per user.

Change is too big. We should make sure it is rolled out slowly. Rolling should be done at org-level. Some work is already done: https://gitlab.com/sid6i7/beyondchats-node/-/merge_requests/20 - whats solid about the previous work: intents a

Claude Analysis of the problem: pusher-connection-analysis.md Revisit: is our usage of pusher across laravel, embed and dashboard not properly optimized?

Original ETA: 25 Feb (Delayed due to other real-time tasks taking priority) Patients can upload their case documents, (DONE) Chatbot analyses the reports, and shares insights, (DONE) And allows for context-aware chat Also saves the file as

Discuss with: JayaShankar for leads dashboard Siddhant for what's already done

Check beyondchats mail

Original ETA: 10/Feb

https://gitlab.com/Shoney13/beyondchats-embed/-/commit/0e321ac62c4177a553062ae410fbc08b462f08ef/pipelines?ref=staging

End goal expectation: Nazeer knows ins and outs of all the features that we offer

1. find which projects + branches out of dev/staging/prod dont have a CI/CD 2. add CI/CD voice-service: prod

Devanshu's Sheet should get auto-synced