Key Discussion Points
1. DiliChat Bug in Demo Environments
Issue: Julien reported issues with the Dili Chat AI summarization feature not functioning in his demo environment.
Reproduction: Jean-Baptiste confirmed the issue is reproducible and technical in nature.
Action: To be flagged as a bug and addressed by the technical team to ensure consistency across demo environments.
2. Proposal for Unified Demo Environments
Suggestion: Julien proposed region-specific standardized demo environments to avoid inconsistencies during client presentations.
Outcome: Jean-Baptiste acknowledged the value and recommended collaboration with Sales Enablement and Sales Ops to implement this.
3. AI and Excel Compatibility
Query: Sandrine asked if AI features can interpret Excel files for summaries/tables.
Response: AI should work with Excel documents, but testing and feedback are encouraged.
Limitation: Table creation directly within chat is not currently supported; future updates may enhance this.
4. Documentation Requests
Need: Sandrine requested details on maximum upload size and who can generate transcripts in Board Portal.
Action: Jean-Baptiste will retrieve this from the “ThisTime” documentation and confirmed improvements to FAQs are ongoing.
5. ELM Invoice Numbering
Maria’s Query: Clarification sought on automatic invoice numbering.
Answer: Internal system-generated numbers ensure uniqueness. Provider’s invoice numbers can be added in a separate field.
6. ELM Repository Column Reordering
Issue: Anouar raised a missing feature for reordering columns.
Response: Ombeline confirmed an update is planned to reintroduce column drag-and-drop in the next quarter.
7. Board Portal Activity Logs
Patrick’s Query: Whether user activity tracking can be disabled.
Answer: No. It’s core to governance. However, visibility can be restricted by role.
8. Offline Access Management
Clarification: Offline access can’t be remotely revoked or wiped post-access in native apps.
Suggestion: Patrick to confirm platform (e.g., iOS) for further technical verification.
9. CLM Translation Issues
Alberto’s Concern: Spanish CLM instances show untranslated or inaccurate labels.
Action: Ludwig offered to directly manage and push updates. Alberto to follow up with a summary or client names.
10. API Use Case Clarity
Alberto’s Suggestion: Need for clear guidance on which front-end features are available via API.
Response: Jean-Baptiste and Mohamed are working on Power Automate templates to document APIs and associated use cases.
11. Scheduled CLM Reports
Marin’s Query: Can CLM schedule regular exports without API?
Answer: Not currently. Recommended to use API with external schedulers for such functionality.
Actions & Follow-Ups
| Action Item | Owner | Status |
|---|---|---|
| Log and prioritize Dili Chat bug | Technical Team | ? Open |
| Share feedback on standardized demo envs with Sales Ops/Enablement | Jean-Baptiste | ? In progress |
| Test AI Excel file interpretation & table generation | Sandrine / Estelle | ? To be tested |
| Provide upload limits and transcript access rules | Jean-Baptiste | ? Done (via BizTime) |
| Reintroduce column reordering in ELM | Ombeline / Dev Team | ? Planned (Next Quarter) |
| Follow up on translation ticket list | Alberto → Ludwig | ? Pending summary |
| Improve API use case documentation (Power Automate) | Jean-Baptiste / Mohamed | ? In progress |
| Respond to CLM scheduled export feasibility | Mohamed / Marin | ? Clarified via API |
Notes
Meeting minutes will now be routinely recorded and shared via Freshdesk.
Product and CS teams encouraged to reference these to maintain knowledge continuity.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article