LEAD_SCORE logic needs to be made org-specific

Currently we use single LEAD_SCORE logic for all orgs which isnt right. Lets create custom LEAD_SCORE logic starting with elefant and della resorts. 1. Analyze chats and leads dashboard for elefant and della resorts. Think in terms of escalation: if a user complaints about receiving broken toys then its a serious issue for elefant and the LEAD_SCORE needs to be HIGH. For della: if user provides details of coorporate enquiry form then again HIGH. Share a sheet of your findings before proceeding to next steps. Expecting the sheet to have: "chat link", "why the lead_score isnt right" column. 2. Define a org-specific config variable that will handle instructions being used in /generate_leads_bio API. This way we will establish a base for defining custom logic of LEAD_SCORing for elefant. 3. For elefant and della resorts: update instructions for LEAD_SCORE. A few bad cases: - LEAD_SCORE should not be low: https://beyond-chats.netlify.app/della-resorts-68c353073b0f4/116012?right_drawer_ta