test branding

Participants commented on the tool's naming and branding.

A participant raised whether the tool could produce live generated minutes during the session.

Live minute generation was demonstrated successfully during the session; item resolved.

Live transcript generation from the assistant was demonstrated and confirmed to be working during the session.

Repeated confirmation that live transcript generation continued working successfully throughout the session.

Session concluded with the assistant recording turned off.

A participant mentioned that a restaurant sources sushi grades imported directly from Japan.

Decision made to get sushi for dinner, to be recorded as an insight.

A participant mentioned privacy-related dining places in Nashville.

A need to troubleshoot cloud access to HubSpot was raised.

Cloud access issue clarified as users not having access to HubSpot.

A participant noted that 26 percent of support inquiries related to financial how-to topics, including budget entry, allocation, and currency exchange rate changes.

Users were reported to be asking what the term EAC means and where to find EAC in the platform.

Discussion included how to create a budget and how to enter a budget as recurring user questions.

Suggestion made to review support session URLs to observe user interactions directly.

A question was raised regarding EAC calculation methodology on projects, noting it currently sums committed and uncommitted values, resulting in zero variance versus project budget.

A preference was expressed for EAC to instead reflect a forecast of the project.

EAC was described as estimated cost to complete plus committed costs, referred to as estimate at completion.

A question was raised about documenting a budget line expected to be underspent with no contract in place, to reflect this in the forecast.

A manual workaround for adjusting allocated funds was mentioned but described as not clear enough.

A workaround was suggested involving transferring funds between budget line items using an uncommitted column adjustment for change orders.

A suggestion was made that the platform could provide inline guidance showing users how to perform an action before they attempt it.

Additional support inquiries noted regarding analytical cost codes visibility and how to change provider currency, including changing exchange rate between rupees and USD.

All identified support ticket themes were confirmed to have been converted into recorded insights.

A suggestion was made to produce periodic (e.g. weekly) summary reports aggregating support inquiry themes.

It was noted that three users asked how to manually allocate funds despite prompts guiding them.

No decision reached on implementing weekly summary reporting; carried to next meeting.

A previous weekly summary report on support chats was discontinued after approximately three months due to low readership.

The discontinued report was described as lengthy, broken up by module, listing key topics and specific examples.

Seven percent of support tickets related to undo actions, such as deleting duplicates, reverting contracts, or contrasting draft versus final application forms.

Clarification sought on whether ticket theme statistics covered the last week or a four-week period; confirmed as four weeks.

Additional ticket theme statistics noted: approximately 10 percent of tickets related to project setup.

A question was raised about the meaning of actual versus forecast values in reporting.

Support inquiries noted regarding editing retention percentage on an executed contract or invoice.

Issue raised where retention was mistakenly marked as paid and required reverting the invoice to draft to correct.

Question raised on how to change contract retention percentage without affecting invoices already issued.

Attempt to set contract retention to zero percent found no such option on the edit screen.

Issue reported where a user is unable to release retention as expected.

Support inquiries noted regarding structuring a budget where acquisition and construction costs are normally split, and whether the platform can display it that way.

Approximately 15 percent of tickets related to schedule topics, including task creation.

Noted that multiple users raising the same confusion may still result in only a single support ticket, so ticket counts understate the issue.

Suggestion made to change data imports to an AI-based approach accepting files in any format.

Noted that a large share of the reviewed tickets originated from a small number of accounts, many being basic getting-started questions.