BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//PYVOBJECT//NONSGML Version 1//EN
BEGIN:VTIMEZONE
TZID:America/Chicago
BEGIN:STANDARD
DTSTART:20001029T020000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10;UNTIL=20061029T070000Z
TZNAME:CST
TZOFFSETFROM:-0500
TZOFFSETTO:-0600
END:STANDARD
BEGIN:STANDARD
DTSTART:20071104T020000
RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=11
TZNAME:CST
TZOFFSETFROM:-0500
TZOFFSETTO:-0600
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20000402T020000
RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=4;UNTIL=20060402T080000Z
TZNAME:CDT
TZOFFSETFROM:-0600
TZOFFSETTO:-0500
END:DAYLIGHT
BEGIN:DAYLIGHT
DTSTART:20070311T020000
RRULE:FREQ=YEARLY;BYDAY=2SU;BYMONTH=3
TZNAME:CDT
TZOFFSETFROM:-0600
TZOFFSETTO:-0500
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:20260730T013257Z - 13669@eupp202
DTSTART;TZID=America/Chicago:20260819T110000
DTEND;TZID=America/Chicago:20260819T114500
CREATED:20260730T013257Z
DESCRIPTION:<a href="https://nalios.com/event/4-ai-workflows-for-your-odoo-
 141">4 AI workflows for your Odoo</a>\nYour Odoo already holds the answers
 . What eats the week is everything that happens before you reach them: rea
 ding back through an email thread before a call\, checking whether a reord
 er point still makes sense\, noticing that a delivered order was never pai
 d. On Wednesday\, August 19\, Nalios US walks through four AI workflows th
 at remove that layer\, live in Odoo. 01Where the time actually goes Ask a 
 sales rep\, a buyer or a controller what slows them down\, and almost none
  of them will say "the software." They will describe the work that sits in
  front of the software. Before a client call\, someone reads eleven emails
  to remember where the conversation stopped. Before a purchase order\, som
 eone opens six months of history and forms an opinion. Before an invoice g
 ets chased\, someone has to notice it was never paid. None of that is judg
 ment. It is retrieval\, cross-checking and manual entry\, and it is where 
 the hours disappear. That is the layer AI is genuinely good at removing to
 day. Not the decision. The preparation of the decision. 02The four workflo
 ws we will demo live Four use cases\, shown in a real Odoo environment. No
  slideware\, no mockups. 1 · From email thread to CRM opportunity A full 
 prospect correspondence gets summarized and pushed onto the opportunity\, 
 so the context lives in the CRM instead of in one person's inbox. The work
 flow then proposes next activities based on what was actually said in the 
 last exchange\, rather than on a generic follow-up cadence. 2 · Reorder r
 ules that keep up with reality Reorder points tend to be set once\, then q
 uietly drift out of step with demand. Here\, order volume history is read 
 to propose adjustments\, and anomalies are flagged for a human look: a sud
 den spike worth questioning\, a reference nobody has ordered in eight mont
 hs\, a rule that would trigger a purchase you do not need. 3 · Delivered\
 , but never paid Two situations [...]
DTSTAMP:20260730T013257Z
LOCATION:Online webinar
SUMMARY:4 AI workflows for your Odoo
X-ALT-DESC;FMTTYPE=text/html:<a href="https://nalios.com/event/4-ai-workflo
 ws-for-your-odoo-141">4 AI workflows for your Odoo</a>\nYour Odoo already 
 holds the answers. What eats the week is everything that happens before yo
 u reach them: reading back through an email thread before a call\, checkin
 g whether a reorder point still makes sense\, noticing that a delivered or
 der was never paid. On Wednesday\, August 19\, Nalios US walks through fou
 r AI workflows that remove that layer\, live in Odoo. 01Where the time act
 ually goes Ask a sales rep\, a buyer or a controller what slows them down\
 , and almost none of them will say "the software." They will describe the 
 work that sits in front of the software. Before a client call\, someone re
 ads eleven emails to remember where the conversation stopped. Before a pur
 chase order\, someone opens six months of history and forms an opinion. Be
 fore an invoice gets chased\, someone has to notice it was never paid. Non
 e of that is judgment. It is retrieval\, cross-checking and manual entry\,
  and it is where the hours disappear. That is the layer AI is genuinely go
 od at removing today. Not the decision. The preparation of the decision. 0
 2The four workflows we will demo live Four use cases\, shown in a real Odo
 o environment. No slideware\, no mockups. 1 · From email thread to CRM op
 portunity A full prospect correspondence gets summarized and pushed onto t
 he opportunity\, so the context lives in the CRM instead of in one person'
 s inbox. The workflow then proposes next activities based on what was actu
 ally said in the last exchange\, rather than on a generic follow-up cadenc
 e. 2 · Reorder rules that keep up with reality Reorder points tend to be 
 set once\, then quietly drift out of step with demand. Here\, order volume
  history is read to propose adjustments\, and anomalies are flagged for a 
 human look: a sudden spike worth questioning\, a reference nobody has orde
 red in eight months\, a rule that would trigger a purchase you do not need
 . 3 · Delivered\, but never paid Two situations [...]
END:VEVENT
END:VCALENDAR