jdZddlZddlZddlZddlZddlmZmZmZddlm Z m Z ddl Z ddl m Z ddlmZddlmZddlmZmZmZmZmZmZdd lmZdd lmZmZmZdd l m!Z!m"Z"m#Z#dd l$m%Z%dd l&m'Z'ddl(m)Z*m+Z,m-Z.m/Z/ddl0m)Z1m+Z2m-Z3m4Z4ddl5m6Z6m7Z7m8Z8ddl9m:Z:ddl;md?dd@dAddBddCgidBddCgidBdidDdEgddFid@gdddddGdHdddIdddJddKdLgdddddMdNdddOdddPddQdgdddddRdSdddTddUdVddUdWdddXdYgdZd*dd[dd\gd]ddddd^d_ddd`ddUdaddUdbdddXdYgdcd*ddddddedddfddggdhdddddidjdddkdddlddmdngdddg ZCdoZDdpZEdqZFdrZGdsZHdtZIduZJdveKfdwZLdxZMeNZOddyZPddzZQdd{ZRdd|ZSd}ZTd~ZUdZVdZWedZXdeYfdZZdeYfdZ[de\fdZ]dZ^dZ_dZ`eDeEeGeHeTeIeUeVe^e_e`d ZadZby)zNative tool-calling layer: schemas + executors for actions the chat model can take. Replaces the legacy fenced signal blocks (ticket_creation_signal, etc.). N)datetime timedeltatimezone)ZoneInfoZoneInfoNotFoundError)settings)client)TICKET_CONSOLIDATION_PROMPT) create_ticket get_ticketget_ticket_by_threadinsert_feedbacksearch_vector_data update_ticket download_link)email_configuredis_valid_email send_email)get_email_settingsTICKET_CATEGORIESget_tool_settings)get_embeddings)set_intervention_status) cancel_eventcheck_availability create_eventget_google_calendar_connection)rrrget_teams_connection)match_productssemantic_productsto_card)QuotaExceededError)get_redis_client publish_event)zdon't have enough informationzdo not have enough informationfunctionsearch_knowledge_baseuSearch this business's knowledge base for facts. You have NO built-in knowledge about this business — its products, pricing, services, features, policies, hours, contact details or support processes are ONLY available through this tool. You MUST call it before answering any question about the business. If the results do not answer the question, call it again with a differently worded or more specific query before concluding you cannot answer. Returns matching content chunks, each with its source URL. Not for a question asking which product/service to get, including a goal or problem phrased with no product named ('how can I improve my brand health') -- that is recommend_products, even without shopping words in the sentence.objectquerystringzeWhat to search for. Use the user's own wording, or a rephrasing targeting the specific fact you need.)type description)r+ propertiesrequired)namer, parameters)r+r&create_or_update_ticketuCreate a support ticket, or update the session's existing ticket with a new issue. Use when the user reports an issue/complaint/bug, or wants to book a demo/meeting or contact the team/sales. ASK THE USER WHAT THE ISSUE IS before raising a ticket. Do not assemble the problem description from context or assume what went wrong — if they have only said something vague like 'it is broken', ask them what exactly is happening. The content field must be their own account of the problem, not your guess. Alongside that, collect their email address and phone number (and their name if not already known); ask for what is missing together rather than one question per turn. Never reuse an email or phone number that came from search results or a document — only what the user gives you here. You may write the short heading yourself, and set priority from how they describe the urgency. STOP ASKING once you have (a) their description of the problem and (b) their email and phone — call this tool immediately in that same turn. Do NOT then ask for a website URL, error messages, screenshots, what changed, or any other extra detail: the support team will follow up for those. One or two questions total, never an interrogation. If the session already has a ticket, do NOT re-ask contact details; just ask what the new issue is. Any team notification email is also sent in the background -- tell the user their ticket has been logged/raised, never that the team has already been emailed or has already seen it.z User's namezShort ticket headingzDetailed issue description)LowMediumHigh)r+enumzUser's email addresszUser's phone numberzOptional other contact infozkWhich team should handle this: General enquiries, Sales, or Business. Pick from the conversation's content.)r+r5r,) user_nameheadingcontentpriorityemail contact_noany_other_contact_mediumcategoryr7r8r9r=submit_feedbackuStore the user's feedback about this conversation or the service. You MUST call this tool whenever the user expresses satisfaction or dissatisfaction — whether or not you asked them for it. That includes: any rating ('5 out of 5', '4/5', 'I'd give it a 3'), any verdict on whether you helped ('that was helpful', 'this didn't help at all', 'you've been useless'), and any praise or complaint about the service. Thanking the user in text WITHOUT calling this tool loses their feedback permanently — the reply text is not stored anywhere as feedback. Set `question` to what you asked, or to a short description of what they were reacting to if they volunteered it unprompted. Do NOT call this for a plain 'thanks'/'ok' that carries no opinion about the service.zThe feedback question askedzThe user's feedback answer)questionanswerr@rArequest_human_takeoveruNotify a real human team member to join this conversation. This is the ONLY way a human is actually notified — saying so in text without calling this tool notifies no one. Call it immediately, in the same turn, whenever the user explicitly REQUESTS a human/real person/agent/someone from the team (e.g. 'can I speak to someone', 'I want to talk to a real human', 'this isn't helping, connect me with your team'), or when the request is too complex or unsafe for you to handle safely. Do NOT call this for a QUESTION merely asking about human handoff capability (e.g. 'can this be escalated to a person if needed?', 'do you support human takeover?') — answer questions like that from context instead. Keep helping the user until the human joins.reasonzWhy human help is neededruEmail information to the user. Use ONLY when the user explicitly asks for something to be emailed to them (e.g. 'email me this', 'can you send that to my inbox', 'mail me the pricing'). Before calling: you MUST have searched the knowledge base for the content, and you MUST have the user's email address and have confirmed it back to them in your previous message ('Shall I send it to x@y.com?'). Never guess or invent an address, and never email an address the user did not give in this conversation. The `body` must be written ONLY from knowledge-base search results and what was already said in this conversation — never invent facts, prices or policies to fill out the email. If the knowledge base does not contain the information, tell the user instead of sending a made-up email. NEVER offer to email, and never call this tool, when your answer is that you could not find the information — an email saying you do not know is worse than no email. Offer a ticket or a human instead. Sending happens in the background after this call returns -- tell the user you are sending it now ('I'm sending that over now'), never that it has already arrived.z3The recipient address, exactly as the user gave it.z@Short, specific subject line, e.g. 'GalaxiQ BrandForge pricing'.zPlain text body written from knowledge-base content. Use short paragraphs; '- ' at line start for bullets. Include the source URLs where relevant. No greeting placeholders like [Name].)to_emailsubjectbodyattach_resourcesuAttach the source URLs/images your answer relied on so the frontend can render them as clickable buttons or image cards. Every result returned by search_knowledge_base carries a 'source' and may carry an 'images' list. ONLY attach a source that is a real web address starting with http:// or https://. A source that is an uploaded file name such as 'Pricing Sheet.docx' or 'policy.pdf' is NOT a URL -- never pass it here, because it produces a card that leads nowhere. To give the visitor an uploaded file, use send_document instead. You MUST call this tool, in the same turn as your text answer, whenever you used a search result that has a source URL or an image to produce your answer — this is REQUIRED, not optional, any time the context you drew on has a source. Never write the raw URL or image link directly into your reply text instead of calling this tool; the link belongs in the tool call, and your reply text should read naturally without it. Only include resources that directly relate to the current answer, and keep a URL and its matching image in the same object. Skip this tool only when no search result you actually used has a source URL or image. resourcesarrayr+null)urlimagelabelrM)r+items send_documentu%Give the visitor the actual uploaded file — the brochure, price list, spec sheet or policy PDF itself — as a download link, rather than only describing what is in it. Call this when the visitor asks for the document ('do you have a brochure?', 'send me the pricing PDF', 'can I get that as a file?'), or when you have just answered from a document and handing them the original is obviously useful. Search the knowledge base FIRST: every result carries a 'source', and when that source is an uploaded file name (something ending in .pdf, .docx and so on) that is exactly what you pass as file_name. Never invent a file name — only use one you have actually seen in a search result. If the tool reports the document was not found, tell the visitor the file is not available and do not make up a link.z`Exact file name as it appeared in the 'source' field of a search result, e.g. 'pricing-2026.pdf'z#Briefly, what the visitor asked for) file_namerCrPrecommend_productsaShow the visitor actual products, plans or services as cards they can act on, with the business's own buttons. Call this when the visitor is asking WHICH thing to get rather than asking ABOUT something: 'what do you have', 'show me', 'do you sell X', 'which plan suits me', anything with a budget or a category. This also covers advice-phrased requests for a recommendation, not only literal shopping requests -- 'what shirt should I wear', 'what should I get for a beach trip', 'what do you suggest for sensitive skin' are all still asking which product to get, just phrased as a question for advice; call this tool for those too, not search_knowledge_base. The same applies to a goal or outcome phrased as a problem, with NO product named -- 'how can I improve my brand health', 'how do I get more ROI from marketing', 'how do I grow my audience' are the visitor asking which of this business's products/services solves that, exactly the same as if they had said 'what do you have for X' -- call this tool, not search_knowledge_base, even though the sentence itself contains no shopping words. Do NOT call it for a question about a product they already named -- 'what does BrandForge do', 'does it integrate with Shopify' -- that is search_knowledge_base, and answering in prose is correct there. The tool returns only products this business actually has. If it returns none, say so plainly; never name a product, quote a price, or describe a button that did not come back from this tool.z3What the visitor is looking for, in their own wordsz4Category to narrow to, only if the visitor named one)r)r=raCheck whether one specific time the user asked for is open, e.g. '9 AM tomorrow'. Use whenever the user asks to book a call/meeting/demo -- never invent or claim a time is open without calling this first. If that exact time is free, this confirms it -- go ahead and book it once you also have the visitor's email and name. If it is NOT free, this returns a small number of real nearby alternatives instead -- relay those to the user; do not invent alternatives of your own, and do not read out more than the tool gives you. This tool's result always includes a 'timezone' field -- ALWAYS state that zone explicitly when you relay any time from this result (e.g. '10:30 AM IST', not just '10:30 AM'), so the user is never left guessing which timezone a time is in. Never assume it matches the timezone the user asked in -- use the value this tool actually returned. Give the date and time exactly as a person would say them (a 1-12 hour, a minute, and AM/PM) -- do NOT convert to 24-hour time yourself; this tool does that conversion for you so you never have to. BEFORE your FIRST check_availability call in a booking conversation: if the user has not already told you what timezone or city they're in, ASK them directly (e.g. 'What timezone are you in, so I book the right time for you?') -- do not silently assume they mean the business's own timezone, and do not guess. Only proceed without asking if they say they don't know or don't care (in which case leave visitor_timezone out and it defaults to the business's own zone). Once you know the user's timezone (asked or stated), pass it as visitor_timezone (an IANA zone name, e.g. 'Asia/Kolkata', 'Europe/London', 'America/Los_Angeles') on EVERY check_availability and book_meeting call for the rest of THIS conversation -- never drop it on a later call, never switch between passing it and not passing it for what is meant to be the same request. Two calls for the same nominal time (e.g. both called '9 AM') must resolve to the exact same instant, or the user sees contradictory answers. If this returns no alternatives or an error, tell the user you could not find an open time and offer a ticket/human contact instead of inventing one.zISO 8601 date (YYYY-MM-DD) the user wants, resolved from their natural-language request yourself (e.g. 'tomorrow' -> tomorrow's date).integerzThe hour the user asked for, on a 1-12 clock, exactly as you would say it out loud (e.g. 9 for '9 AM'). Never convert this to 24-hour time.zThe minute the user asked for (0-59). Use 0 if they only gave an hour, e.g. 'tomorrow morning' -> a reasonable hour of your choosing with minute 0.AMPMzMWhether the requested time is AM or PM, exactly as you would say it out loud.zIANA timezone name (e.g. 'Asia/Kolkata') for the user's own timezone, established by asking them if they haven't already said. Once set for this conversation, pass the SAME value on every later call -- omit only if the user said they don't know/care.)datehour_12minutemeridiemvisitor_timezone)rUrVrWrX book_meetinga Book a meeting at a specific time. Only call this after check_availability has shown this exact time as open and the user has picked it -- never call this on a time you have not already confirmed is free. This books immediately; there is no separate confirmation step after this call succeeds, so only call it once the user has clearly picked a time, not while they are still considering options. You must have the visitor's email and name before calling -- ask for whichever is missing first. Give the date and time exactly as a person would say them (a 1-12 hour, a minute, and AM/PM) -- do NOT convert to 24-hour time yourself; this tool does that conversion for you so you never have to. Pass the EXACT SAME visitor_timezone value you used on the check_availability call that confirmed this slot (asked or stated earlier in this conversation) -- do NOT convert the hour yourself, and do NOT drop or change the timezone between check_availability and book_meeting for what is meant to be the same slot. Leave it out only if you never established one for this conversation. On success this returns 'confirmed_start' and 'timezone' -- when you tell the user their meeting is booked, state the time WITH that exact timezone (e.g. 'booked for 10:30 AM IST'), not a bare time -- never assume it matches whatever zone the user originally asked in. If this returns an error because the slot was taken in the meantime (someone else booked it first), tell the user and offer to check availability again -- never silently pick a different time yourself.zvISO 8601 date (YYYY-MM-DD) of the slot the user picked, matching the date on that slot as shown by check_availability.zThe hour of the slot on a 1-12 clock, exactly as you would say it out loud (e.g. 2 for '2:30 PM'). Never convert this to 24-hour time.z5The minute of the slot (0-59), e.g. 30 for '2:30 PM'.zCWhether the slot is AM or PM, exactly as you would say it out loud.zIANA timezone name (e.g. 'Asia/Kolkata') ONLY if the user explicitly named a timezone or city for this slot -- the same one passed to check_availability. Omit this field entirely otherwise.z-The visitor's email address, as they gave it.z$The visitor's name, as they gave it.)rUrVrWrXrY visitor_email visitor_name)rUrVrWrXr[r\cancel_meetingaCancel a previously booked meeting. Ask for the visitor's email, and if they don't recall the exact time, roughly when it was (e.g. 'around 2pm ' or 'sometime tomorrow') -- the lookup searches by these, not by an exact ID, so the more specific they are the more reliably it finds the right one. If this reports it could not find exactly one matching meeting, tell the user and ask for more detail (a narrower time) rather than trying again with the same information.z/The email address the meeting was booked under.z]ISO 8601 datetime near when the meeting was, if the user recalls it. Omit if they don't know.)r[approximate_timer[c8K|jdxsdj}|sgdddS t||d|jd}t|d|d }g}|xsgD]}|jdxsi}|jdxsg} g} | ddD]Z} t| tr&| jdr| j| d9t| tsJ| j| \|j|jdd|jdxs|jdxsd| d|t||sddSddS#t$rt $r*}t jd |d gdddcYd}~Sd}~wwxYww)zBRetrieval as a model-chosen action. Returns content, not a status.r)rz Empty query.)resultscountnote tenant_iduser_id)rdrelimitz#Tool search_knowledge_base failed: Texc_infozSearch failed.Nmetadata top_imagesrKr8source source_urlzInternal Knowledge Base)r8rnimageszNNo matches. Try a different wording before telling the user you cannot answer.) getstriprrr# Exceptionloggererror isinstancedictappendstrlen) argsctxr) embeddinghitsexrahitmetarp image_urlsimgs 6/var/www/html/strategist-ai/app/services/chat/tools.pyexecute_search_knowledge_basers XXg  $" + + -E >BBE"5C 4DcggV_N`a !#k"2IQGGzr  wwz"(b,'-2 "1: 'C#t$!!#e*-C%!!#&  ' wwy"-hhx(_DHH\,B_F_     Wb &*  +  E :2$?$ O3CDDEs<,F1E BF&A5FF-F F FFFcNK|d}|d}|jd}|jd} t||}|r tj|d|d|d|d}tj j jtjd|d gd }|jd jjj} | jd djddj} tj | } | jd|d| jd|dd|d|d|jdxs|jdxsdd} t)||d| } | rHt+||ddd|ddd{ t-||d}|rt/||dd!|dd"Sd#|dd"St1|}d$t3j4j6dd%j9|d<|jdxsd|d<|r||d<|r||d<t;|||&}|r4t+||dd'd(|dd{ t/||d*|dd"Sd#dd"S#t"$ra} t$j'd| |d|dd|d|d|jdxs|jdxsdd} Yd} ~ vd} ~ wwxYw7Q#t"$r+}t$j'd|dd|d Yd}~^d}~wwxYw7#t"$r*}t$j'd)|dd|d Yd}~d}~wwxYw#t<$rt"$r)}t$j'd+|d d#dd"cYd}~Sd}~wwxYww),zDCreate a new ticket, or consolidate into the session's existing one.rd thread_idr6rer7r8) old_heading old_content new_heading new_contentuser)roler8i )modelmessagesmax_completion_tokensrz```jsonr`z```z --- r9r=General enquiriesr>zConsolidation LLM call failed: z --- [Update]: N ticket_idticket_updatedzTicket z& has been consolidated with new issuesTupdatedz&Ticket update notification failed for : rir)statusrruzTICK-)rnew_ticket_createdzA new ticket has been created: zTicket notification failed for createdz%Tool create_or_update_ticket failed: )rqr r format openai_clientchat completionscreater LLM_MODELchoicesmessager8rrreplacejsonloadsrsrtrur_publish_ticket_eventr _notify_ticketrwuuiduuid4hexupperr r#)r{r|rdrr6reexisting cons_prompt cons_responserawcons update_datacons_exsuccess full_ticketr ticket_datanew_ids rexecute_create_or_update_ticketr9s,K IK I $Iggi GG6' 9=  9@@ ( 3)AT $YT)_ !. 2 2 > > E E",,'-+FG*-!F! $++A.66>>DDFkk)R088CIIKzz##xx 4 ?C#xx hy6I5J)TXYbTcSd3ef $Z 0 $ 4 g Z8P gTg  $Ix /DkRG+Ix 7LN^.5h{6K5LLr,suuu /",Y8M"NK"&y+tL#,(;:OPP%H[4IJ J4j %*4::<+;+;BQ+?+E+E+G*H#I K "&((:"6"M:M J '0K $ %,K "y+K ' ;{3KMa*I+VaJbIc(df f f py+6(k+6NO O!55Y  >wiHI#I"*9"5!66J4PY?J[\ $Z 0 $ 4 g Z8P gTg   u!/LL#I(S^J_I``bcebf!g)-!/// f  p >{;?W>XXZ[]Z^_jn oo p  6 z*execute_submit_feedback..s#(h!TUV\T]agTg9(h  Nc38K|]}|ddk(s |dyw)r assistantr8Nrrs rrz*execute_submit_feedback..s#)n1UVW]U^bmUm!I,)nr)last_user_querylast_ai_responseT)is_explicit_feedbackrated_conversationrkrsavedzTool submit_feedback failed: riru)rqnextreversedrrsrtru) r{r|rdrr6r feedback_datalast_interactionrs rexecute_submit_feedbackrsK IK I $Iggi$G#%)*%5h&/iI  #'(hx?P(hjn#o$()n@Q)npt$u  >BYi$j j! =1'"" # 4RD9D I'""#s5.CA!BC CB?9C:C?CCc K|d}|d}|jd} t||d| td|ddd d |||jd |d d d{ddiS7#t$r"}tj d|Yd}~,d}~wwxYw#t$r(}tj d|dddicYd}~Sd}~wwxYww)z@Flag the thread for human intervention and notify the dashboard.rdrreT)rerz:conversation_listrintervention_requestedz-AI has requested human assistance for thread rC)rrCrerNz1Failed to publish intervention request to redis: rflaggedz$Tool request_human_takeover failed: riru)rqrr%rsrtrru)r{r|rdrrerrs rexecute_request_human_takeoverrsK IK Iggi G # 9dGL Y')4F G +CJ9+V&/488H;MZabJ  )$$   Y NNNvhW X X Y # ;B4@4 P'""#soC B.A(A&A("B%C &A(( B1B BBB CC<C=C CC cpK|jd}t|tr t|nd}d|dSw)zJResources are collected by the chat loop; this only acknowledges the call.rHrattached)rrb)rqrvlistrz)r{r|rHrbs rexecute_attach_resourcesrs3%I(D9C NqE 5 11s46cd|d|S)Nz chat_emails::r)rdrs r_email_count_keyrs )Ai[ 11returnc K t}|jt||d{}t|xsdS7#t$r5}t j d|d|tjcYd}~Sd}~wwxYww)aHow many emails this conversation has already sent. Only consulted when a cap is configured. Fails CLOSED on a Redis outage: if we cannot prove the conversation is under the limit, we refuse rather than risk turning the chat into a mail relay. NrzCould not read email count for r) r$rqrintrsrtrurEMAIL_MAX_PER_THREAD)rdrr valuers r_emails_sent_in_threadrsu-!#jj!1)Y!GHH5:AI - 6ykB4HI,,,-sCB(AAABA B *A;5B6B;BBcKt||} t}|j|d{}|dk(r|j|dd{yy7%7#t$r%}t j d|d|Yd}~yd}~wwxYww)Ni: z Could not record sent email for r)rr$increxpirersrtru)rdrkeyr rbrs r_record_email_sentrs 9i 0CK!#kk#&& A:--%56 6 6 ' 6 K 7 {"RDIJJKsP B AAA AAB AA B!B<B BB cfd}tj|}tj||j tj |S)aSend in the background; the caller never waits on this. on_sent, if given, is an async callable run only after a confirmed successful send -- used to keep execute_send_email's per-thread rate counter accurate without blocking the tool-call round trip on it. c|K tjjfdd{}|jddk(rr;d{ytj dd|jdyy7V73#t $r'}tj dd|d Yd}~yd}~wwxYww) Nc$tS)N) first_namerd)r)rFrrErdrDsrz7_fire_and_forget_email.._send..s 8Wd.8IOrrsentzBackground email to z failed: detailz raised: Tri)anyio to_threadrun_syncrqrtrurs)resultrrFron_sentrErdrDs r_sendz%_fire_and_forget_email.._sends X ??33OPPFzz(#v-!)OO 3H:YvzzRZG[F\]^ P $ X LL/z2$GRVL W W Xs\B<)B B$B BB B<*B B<B B B9B4/B<4B99B<)asyncio create_task_background_email_tasksaddadd_done_callbackdiscard)rDrErFrdrrrtasks`````` r_fire_and_forget_emailrsK X X   uw 'D%2::; Krc|d}|rdnd}|d|jdd|d}d|d |jdd |jd d |jd xsdg}|jdr|jd|d|jdr|jd|d|jd|j|jdxsd|dj|fS)NrUpdatedNew r=z ticket: r7z Ticket ID: z Category: z Priority: r9zFrom: r6Unknownr:zEmail: r;zPhone: r`r8 )rqrxjoin)rrrverbrEliness r_ticket_team_email_contentr  sK(I9UDa  34Ik)>T=UVG i[! [__Z012 [__Z012 -:;<  E w w{73456|$ w{<89:; LL LL+1r2 DIIe$ $$rcd|d}|rd|}d|d|dd}||fSd|}d|d|dd}||fS) Nru"Your request has been updated — zEWe've added your latest message to your existing ticket. Ticket ID: z Summary: r7z+ Our team will follow up with you shortly.u We've received your request — zBThanks for reaching out. Your ticket has been logged. Ticket ID: r)rrrrErFs r_ticket_customer_email_contentrsK(I6ykB#%#I./08 9  D=5YK@#%#I./08 9 D=rc pt|jddsyt|sy|jdxsd}t|jdgDcgc]H}t |t r6|jd|k(r"|jdr|jdJ}}|r%t ||\}}|D]}t|||||jdxsd j} | r.ps @f6TZZ\ ! @sz2Refusing to email a no-answer response for thread ruThere is nothing useful to email — the knowledge base did not answer this. Tell the user you could not find the information, and offer to raise a ticket or connect them with the team instead.rNz Email limit (z) reached for thread zfEmail limit reached for this conversation. Tell the user you cannot send any more emails in this chat.cDKtjddyw)Nz Chat emailed for thread )rtinfo)rrDsr_on_sentz$execute_send_email.._on_sents  mH:\)EFs r6)rrqueued)rto)rqrrrrtrrranyREFUSAL_MARKERSrrrrrr) r{r|rErh already_sentrdr rFrrDs @@@rexecute_send_emailr&Vs $*113Hhhy!'RG 88F  !rD c+. / 3 3It D>s;?O>PQR!)* * C , -!^` ` ( #!hZ'bce e ::<!-OPP @ @@ HQ\I]H^_`!RS S  ) )EW\_`W`/K0@#kBRSSSfgL qy\U*H99::OPSPWPWXcPdOe f "?@ @K IK IG Y 2228WdI&)ggk&:HNh //+T$3s%D6G;G.s c+. :rNz'send_document: no stored file matching  for rd not_foundzNo uploaded document named z-. Tell the visitor the file is not available.zsend_document: rrrr)rqrrrrrrtr)r{r|linkrPs ` @rexecute_send_documentr-s+&,"335I !-BCC)):< .s!#k"2ECrNc&tddSr0)r r1srrz,execute_recommend_products..sN3{#3U!Drz$recommend_products: nothing matched r*rdnonezWThis business has no matching products. Tell the visitor plainly and do not invent one.)rproductsrzrecommend_products: rrfound)rr4) rqrrrrrrtrr"rz)r{r|rowsrr4r)s ` @rexecute_recommend_productsr8s XXg  $" + + -E))CE ED __-- DFF  :5)D{+,. / b;< <%))q )H) KK&s8}o\#''+BVAWXY8 44 EF*s6A C?C6,C?;C8<.C?*C:<;C?8C?:C?)hoursr{c|jdxsdj}|r t|S|S#ttt f$rY|SwxYw)aThe zone a requested time should be interpreted in: the visitor's explicitly-named zone if the model passed one and it's a real IANA name, otherwise the business's own connected-calendar zone. Callers must relay this SAME zone back in their response to the model (as the tool result's own "timezone" field) rather than always reporting the business's zone -- live testing found the tool result silently labelling a visitor-timezone request with the business's own zone name, which the model then relayed as if it matched the times it just gave, when the times were actually in a different zone entirely. rYr`)rqrrrr ValueErrorKeyError)r{ business_tzvisitor_tz_names r_resolve_effective_timezoner@s]xx 239r@@BO O, , &z8<    s 4A  A c:t||} tj|jdxsdj }t |jd}t |jd}|jdxsdj j}d|cxkrdkrny d|cxkrd krny |d vry |dz}|d k(r|dz }t|j|j|j||| S#ttf$rYy wxYw)aThe date/hour_12/minute/meridiem the model gave us, as a real datetime -- or None if any field is missing or out of range. The model gives us the time exactly as a person would say it (e.g. 9, 30, "AM") and we do the 12-hour-to-24-hour conversion ourselves, deterministically, rather than asking the model to compute and pass a 24-hour datetime. Live testing found the model unreliable at that specific conversion (a systematic AM/PM slip), even after the tool description demanded it copy a value verbatim. Built in whatever _resolve_effective_timezone resolves to -- the visitor's explicitly-named zone if given, otherwise the business's own. rUr`rVrWrXr r;)rSrTNrT)tzinfo) r@r fromisoformatrqrUrrrryearmonthday TypeErrorr<)r{r>tzrHrVrWrXhour_24s r_resolve_requested_timerLs  %T; 7B $$TXXf%5%;<AACdhhy)*TXXh'(HHZ(.B557==?W""-.,=2,=CKR^B^B, t  rMG#))SWWgvbQQ z "s$B(D7 DD =DDDrdc4t|xsi}|jdxsi}|jdsdddddfS|jdxsi}|jd}|dvrdddd dfS|d k(r t|n t|}|sdddd dfS||dfS) zThe active meeting provider's connection, or (None, None, error_dict) if the feature is off, nothing is selected, or the selected provider has no active connection. Mirrors execute_send_email's guard shape.featuresrZNruz0Meeting booking is turned off for this business.r providers)google_calendarteamsz3No meeting provider is connected for this business.rPz8The connected meeting provider is unavailable right now.)rrqrr)rd tool_settingsrNrOprovider connections r_book_meeting_connectionrUs&i06BM  ,2H << 'Tg&XZZ Z!!+.4"I}}^,H33Tg&[]] ]@HK\?\0;*95 Tg&`bb b Z %%rc ~ Ktjjfdd{\} }|r|S jdxsd} t |}t||d d d Std z tjd|}|dk(rt nt" t%j&tj}|k\rgtjj fdd{}t)fd|Dr&d|dj+ j+ddSt-|t.z t.ztjj fdd{} | D cgc]0} t1| t2s| jds&| d|k\s/| 2} } | j5fd| dt6} d|d| D cgc]w} t1| t2re| jdr| jdj+nd| jdr| jdj+nddyc} dS71#t t tf$r3tjd|dddtj}YLwxYw776cc} wcc} ww)aBChecks whether the exact time the user asked for is free on whichever meeting provider this tenant has active -- and if not, real nearby alternatives instead of a generic list of whatever's chronologically first in the day. An unrecognized timezone string degrades to UTC rather than failing the call. c tdSr)rUr|srrz,execute_check_availability..#([)9:rNrUTCzUnrecognized timezone z for tenant rdz"; using UTC for the search window.ruCdate, hour_12, minute, and meridiem are required and must be valid.rminutesrrPc:tdzxsgSNrr^r)check_fnrT requested_endrequested_startsrrz,execute_check_availability..?s!HZ-)\]J^:^_ecerc3jK|]*}t|txr|jdk(,ywstartNrvrwrq)rsres rrz-execute_check_availability..@s-^Qz!T"HquuW~'HH^03okT)rhend)rr available requestedc xsgSrr)rcrT search_end search_startsrrz,execute_check_availability..Ls\:>D"rrhcBt|dz jS)Nrh)abs total_seconds)rjres rrz,execute_check_availability..Nsc1W:#?"N"N"PQr)rFrm)rrrn nearby_slots)rrrrqrrr<r=rtrrutcrLrgetattrrDgcal_check_availabilityteams_check_availabilityrnowr# isoformatmax_NEARBY_SEARCH_WINDOWrvrwsort_MAX_AVAILABILITY_SLOTS)r{r|rSrutz_namerJeffective_tz_namer{ exact_slotsnearbyrjrcrTrdrerqrrs ` @@@@@@rexecute_check_availabilityrs).(@(@:)<#<Hj%  nnZ(1EG g  .dB7O!^` `#i&;;M   6 6wG*26G*G&MeH ,,x|| $C#!OO44 egg ^R]^ ^"0A $*9*C*C*E(5(?(?(A!CD DsO.CCDL #88J??++DFFF `A:a#6155>aPWj\_N_a `F ` KKQKR ,, -F(9&,D !z!T/BEFEE'NaeeGn&>&>&@X\@Ae AEE%L$:$:$.`rZrNrr[r\rzThat time has already passed.r]r^rPc:tdzxsgSrarb)rcrTrmrhsrrz&execute_book_meeting..vsUC)A2F,FGM2rc3jK|]*}t|txr|jdk(,ywrgri)rrjrhs rrz'execute_book_meeting..ws-YZ4(DQUU7^u-DDYrkzDThat time is no longer available. Offer to check availability again.cSrr)rT create_fnrmrhr[r\srrz&execute_book_meeting..~s *eS-Nrz&Could not book that meeting right now.rlevent_id meeting_link)rrrrconfirmed_start)rqrrrrrrrr<r=rrwrLrxrDrr{rryrzr#gcal_create_eventteams_create_eventr|)r{r|rSrurrJr free_slots still_freebookingrcrTrrmrhr[r\s ` @@@@@@@rexecute_book_meetingrXsXXo.4";;=MHH^,299;L  !-`aa(-(@(@:)<#<Hj%  nnZ(1EG g  $D" -E }!^` ` eW= x||HLL))!-LMM )B' 'C*26G*G&MeH//MOOJYjYYJ !_a a&.1B%B!HZIOO,,NNPPG !-UVV J(?";;~6(#oo/ 11G#< ":x 8 \\OPsWA5H?G%!H" G(-BH H AH%H&AH($H HHHHcKtjjfdd{\}}|r|Sdjdr t j d|dk(rtnttjjfdd{}|sdddSd d iS7#t tf$rdY^wxYw7(w) z.Finds and cancels a previously booked meeting.c tdSr)rXrYsrrz(execute_cancel_meeting..rZrNr^rPc:jddS)Nr[r`) near_time)rq)r{ cancel_fnrTrsrrz(execute_cancel_meeting..s *dhh&CyYrruz6Could not find exactly one matching meeting to cancel.rrrl) rrrrqrrErIr<gcal_cancel_eventteams_cancel_event)r{r|rSru cancelledrrTrs`` @@@rexecute_cancel_meetingrs(-(@(@:)<#<Hj%  I xx"#  ..t4F/GHI&.1B%B!HZIoo..Y[[I !QS S d '#<:& I [s?&C B/C B1&9C C C 1CC CC ) r'r1r?rBrrGrOrQrrZr]cKtj|}|tjd|dddS|||d{S7w)zQRoute a model tool call to its executor. Returns a JSON-serializable result dict.Nz!Unknown tool requested by model: ruz unknown toolr)TOOL_EXECUTORSrqrtru)r/r{r|handlers r dispatch_toolrsM  &G 8?@!^<<s# ## #sAA AA )NN)F)c__doc__rrloggingrrrrzoneinforrrapp.core.configrapp.core.llm_clientr rapp.core.promptsr app.services.infra.databaser r r rrrapp.services.content.documentsrapp.services.messaging.emailrrr app.services.chat.tools_settingsrrrapp.services.infra.embeddingr#app.services.integrations.firestorer)app.services.integrations.google_calendarrrrryrrrapp.services.integrations.teamsrrzrrapp.services.catalog.productsr r!r"app.services.infra.quotasr#app.services.infra.redisr$r% getLogger__name__rtr$r TOOL_SCHEMASrrrrrrrrrrsetrrr rrr&r-r8rr~rwr@rLryrUrrrrrrrrrs  224 $789UUee7G  9D   8 $+ [! ((O%I  <-22!*2=!Q(0AWX(0A]^)1;T U&.?UV+3DY"Z9ARo0p ( $%6 7Q !"K'70 3j%h!)1B_ `'/@\](2  4,?!x@Z[&J  2 &!!)'\! !)'i  !)T$<)++ .`&-"! '$,(.60B'C*08V2D)E*0();+ *1 " " )M!'% (T# O!!))Q" !)'L )M  D(@.!!)'\ !)']! %I 3' *X(_D!!)(I!*(M !*(Y!)!%t (D!!)(])3!DFI%IJ M^"A2!!)(=!*(G !*'^ !)!%t (:!!)(M)!)'V& !)'M%E&NgS*7F IV$(!!)'X& !)(S) --  ] @"JM6` H #.#*22 -# - K%4%&*HD:0z&&5B"*d*$>&&2:Ez-1`2;>.<$0*44(, $r