Quick recap

The team reviewed several new mobile app features including reputation management, workflow management, and custom menu capabilities, with discussions around user interface improvements and functionality enhancements. They addressed concerns about white-label app notifications and app updates, while also exploring upcoming AI integration capabilities and data privacy considerations. The conversation ended with plans for weekly town halls and discussions about improving user control over AI features and workflow automation.

Mobile Reputation Management App Prototype

Nikhil presented a new mobile application feature for reputation management, showcasing a prototype with a streamlined interface for reviewing and responding to customer feedback. The app includes tabs for reviews, requests, and metrics, with features such as sentiment analysis, review disputes, and photo attachments for review requests. Dan suggested adding a quick-access option for sending review requests from the contact screen, which Nikhil agreed to implement. Haydar inquired about the availability of other review sources beyond Google, to which Nikil confirmed a phased approach starting with Google, followed by Meta and other platforms.

Mobile Workflow Management Feature Review

Nikhil presented a new mobile workflow management feature, which will allow users to view, publish, pause, and manage workflows directly from their mobile devices. Lior and Dan provided feedback, suggesting that the delete button should be removed due to potential misuse, and that users should be able to remove contacts from workflows more easily. They also discussed the need for folder locking and better organization of workflow actions within the contact tab. Nikhil acknowledged these points and agreed to review the current workflow management system and improve the user experience.

White-label App Customization Discussion

The team discussed the white-label mobile app's custom menu feature, with Lior inquiring about its use cases and data handling capabilities. Urvash explained that custom modules could be built using Highlevel's APIs, and while URL parameters for sub-accounts were not immediately confirmed as supported, Urvash promised to investigate further. Charles raised concerns about inconsistent naming conventions between the web and mobile interfaces, particularly regarding workflows and tags, which Nikhil acknowledged and committed to addressing. The team also briefly discussed upcoming new pricing details, which Urvash teased would be announced at a future "Level Up" event in October.

Mobile App Features Discussion

The team discussed several mobile app features and capabilities. Nikhil confirmed that processing fees for mobile app invoicing would be available in September. Dea raised questions about managing membership and communities in the mobile app, which Urvash and Nikhil agreed to investigate further. Charles explained that white-labeling would be necessary to prevent users from seeing other communities in the Go Collab app. Lior requested the ability to add custom buttons with links at the contact level and for custom objects, similar to the existing account-level custom menu link feature.

Mobile App Feature Enhancements Discussion

Nikhil discussed upcoming features for the mobile app, including bulk actions for contacts via SMS, email, WhatsApp, and calls, allowing users to manage calls from multiple locations with contextual actions. He addressed user feedback on improving access to opportunities from conversations and enhancing the customer profile entry point. Dan suggested a faster way to access opportunities and a menu option for quick actions, while Jeff highlighted the need for better filtering of missed calls and messages. Nikhil acknowledged these suggestions and committed to reviewing and implementing improvements.

White-label App Notification Challenges

The team discussed issues with the white-label app, particularly regarding notifications and app updates. Joel reported problems with receiving notifications, while Todd mentioned that the notification count remained unchanged. Urvash explained that they are working on improving communication about app updates and addressing build failure issues. Charles suggested using IFTTT for notifications, and Dan proposed adding a customizable icon for missed notifications. The team also discussed the possibility of holding town halls specifically for the white-label app to address concerns and improve communication.

Mobile App AI Integration Plans

The team discussed upcoming changes to the mobile app, including the addition of bulk text messaging and AI capabilities. Ryan announced that he will host weekly town halls between now and Level Up to collect feedback and update the team on public updates. Urvash presented plans for integrating AI into the app, including a business card scanner feature and potential for more advanced AI functions. Tiyana expressed interest in using the app's AI capabilities for an AI receptionist feature, and Urvash invited her to schedule a call to discuss this further. The team also discussed the potential for a 300 MB additional download for AI functionality, with concerns about user acceptance and security.

Mobile App AI Privacy Strategy

The team discussed the development of a mobile app with AI capabilities, focusing on user experience and data privacy. They agreed that an on-device model would be preferable, allowing users to choose whether to download additional software for enhanced features, while ensuring data remains private. Ryan emphasized the importance of clear communication about the app's benefits and privacy features, while Lior highlighted the need to give users control over AI integration. The team also touched on the potential for voice dictation and workflow automation within the app.

Quick recap

Mayank presented recent platform releases and upcoming features including new payment options, reporting capabilities, and service enhancements. The team discussed various booking and calendar features, with Swadha confirming timelines for group bookings, custom statuses, and calendar view improvements while addressing concerns about the booking page's default view and client portal access. Several user experience improvements were discussed, including calendar compactness, add-on functionality, and consent checkboxes, with Ryan announcing the next town hall would focus on the mobile app and reminding attendees about Level Up ticket availability.

Platform Updates and Future Features

Mayank presented recent releases and upcoming features for the platform. Recent releases included bank services going live, new features for services like hiding payment amounts and configuring time formats, and enhancements to reporting and workflow triggers for services. Upcoming features include support for PayPal, gift cards, and client portal integration, as well as new notification channels and snapshot support for services.

Service Features and Booking Updates

Mayank presented upcoming features including tax and tip configurations for services, new reporting widgets for revenue tracking, and a rental booking system supporting various use cases. Swadha confirmed that group bookings for services would be available in Q4 (around December), and discussed plans for custom statuses in Q1 and calendar view improvements. AJ raised several questions about booking features and calendar functionality, which Swadha addressed by confirming timelines and planned improvements for Q1 and beyond.

GHL Payment and Service Display

The team discussed payment options and gift cards in GHL. Swadha confirmed that gift cards could be created in GHL and redeemed across various checkouts, though CSV export functionality for gift cards needs verification. Tiyana and others raised concerns about the booking page's default view, noting that it currently shows all services in a list or grid format, which can be overwhelming for clients, especially in the beauty industry with many services. The team agreed that the default view should be category-based, allowing users to drill down to specific services, and Swadha noted this feedback for future updates.

Booking and Forms Feature Updates

The team discussed several features related to booking and forms. Swadha explained that while global forms are currently available, custom forms for individual services will be introduced in the next 3-4 weeks as part of the Level Up release. Tiyana raised concerns about users needing to choose services from a comprehensive menu, and Swadha confirmed this functionality would be supported. The team also discussed the client portal, which will allow customers to manage existing appointments and book new ones, with plans to integrate service packages in Q4. Lior inquired about embedding options, and Swadha clarified that embed codes with fixed or dynamic height would be available, with native integration planned for Q4. Todd asked about service locations and credit card processing, and Swadha confirmed that both features would be supported, with card information being saved for future charges.

User Experience Improvements Discussion

The team discussed several user experience improvements. Todd suggested making the calendar view more compact to improve visibility on smaller monitors, and Swadha confirmed this was on the roadmap for the current quarter. Joshua raised concerns about add-on sorting and grouping functionality, which Swadha explained were planned for Q4. Charles highlighted issues with client portal access, specifically the difficulty of generating and sharing magic links, and requested a zero-barrier entry system, which Swadha agreed to discuss with the client portal team by Monday. Zach suggested allowing multiple consent checkboxes without custom forms, particularly in light of carrier regulations, which Swadha noted for future consideration.

Event Calendar and Town Hall Updates

The team discussed event calendar functionality, with Simone raising a concern about calendar conflicts when scheduling events. Swadha confirmed that group bookings for fitness studios, gyms, and education institutions are planned for Q1 or Q2 next year, and the team acknowledged Simone's feedback about calendar conflict checking. Ryan announced that the next town hall would focus on the high-level mobile app, with weekly general town halls resuming on Mondays, and reminded attendees about Level Up ticket availability with a QR code and coupon system.

Quick recap

The meeting focused on upcoming feature updates and releases, including pipeline redesigns, rich text formatting capabilities, and new company workflows. The team discussed various improvements to contact and company management functionality, including custom fields, duplicate detection, and association features, while addressing several user feedback concerns about data entry and system usability. The session concluded with discussions about contact management system updates, including customizable widgets, improved navigation, and future development plans for opportunities and custom objects.

Pipeline Redesign and Feature Updates

Pallavi presented updates on several upcoming features and releases. She discussed a major redesign of the pipelines page, including a new option to choose the stage for moving opportunities when deleting a stage. A new feature allowing rich text formatting in tasks and notes was announced, along with an improved export experience that will be more reliable and efficient. Pallavi also previewed upcoming company workflows, which will include two new triggers, though these are still in testing.

New Features for Company Management

Pallavi presented updates on several new features for companies and custom objects. She explained upcoming workflow triggers, actions, and form services that will allow users to create, update, and associate company and contact records. Pallavi also discussed dashboard and reporting capabilities, as well as a new import feature for bulk data transfer. Additionally, she introduced a task association feature that will enable users to link tasks to multiple object records across different entities.

Pipeline Updates and Task Improvements

The team discussed several updates and feedback on the pipeline stages, forms, and task associations. Charles raised concerns about the intuitive language used for including reports and suggested improvements for task assignment to both companies and contacts. Pallavi confirmed that a rich text editor would be available soon and addressed issues related to company and contact data entry, promising to ensure seamless transitions and future upgrades. Dea inquired about the differentiation between business names and company names, and Pallavi confirmed plans to differentiate these in forms and workflows. The team also discussed the need for better search functionalities when associating tasks with companies and contacts, with Charles suggesting a more intuitive interface to reduce errors.

Bug Fixes and Feature Requests

Dea reported a bug where workflow notes add extra spaces after sentences, which Pallavi agreed to investigate and potentially fix. Sam raised two pipeline-related issues: the need for a form icon in opportunities created from forms, and the requirement to simplify the contact deletion process, both of which Pallavi noted for future consideration. Chris inquired about the possibility of adding rich text to workflow tasks and notes, which Pallavi said would be added as soon as possible, likely during the Labs phase. Steve raised concerns about the export feature's email delivery, which Pallavi explained was due to architectural limitations, and they agreed to schedule a follow-up call to discuss the issue further.

Company-Centric CRM Development Updates

Pallavi explained that while the company-contacts association feature won't be ready this quarter, it's targeted for Q4, with workarounds available in the meantime. Glenn raised concerns about the current contact-centric architecture and emphasized the importance of company-centric data entry, to which Pallavi responded that a more customizable contact addition system and company field support are being developed, with company-centric CRM functionality planned for Q4. Tamara inquired about pipeline cloning, which Pallavi confirmed is on the roadmap for Q3 or Q4.

CRM Custom Objects Feature Updates

Pallavi discussed several upcoming features for custom objects and contacts in their CRM system. She outlined plans for custom object opportunity associations, new workflows for both custom objects and companies, and the ability to mark custom object fields as unique. Pallavi also announced the development of templates to simplify the creation of custom objects and improve user experience. The team will release these features in smaller increments over the next few months, rather than in one major update.

Contact Feature UX Overhaul Plans

Pallavi discussed upcoming UX overhauls for the contacts feature, including a new sidebar for the add contact modal with customizable fields and an updated list view with advanced filters. She presented a prototype for the contact detail page, featuring a cleaner design, customizable widgets, and improved navigation. Pallavi also announced plans to introduce auto-save functionality, new field types, and a duplicate contact identification feature, all of which will be available through Labs for testing before wider release.

Opportunity Features and Custom Objects

Pallavi discussed upcoming features for opportunities, including pipeline permissions and color tags on opportunity cards. She mentioned that smart lists for opportunities would be pushed to the next quarter. Lior inquired about associating opportunities with custom objects, and Pallavi explained that this feature would be available manually in the current quarter, with workflow support likely in Q3 or early Q4. They also discussed the development of opportunity-based workflows and the flexibility of object-centric CRM functionality.

CRM Custom Fields and Duplicates

Lior requested improvements to custom fields in the CRM, specifically the ability to see how many contacts have data in each field to facilitate easier cleanup. Pallavi noted this feature would be challenging to implement in the first version but promised to add it to the roadmap for future development. Glenn highlighted issues with duplicate company entries due to incorrect or slightly different business names and suggested implementing a string search feature to prevent duplicates. Pallavi explained that company names would be enabled as a dropdown in all relevant areas, allowing users to quickly find and update existing company entries.

Duplicate Detection and Usability Concerns

Pallavi explained that the current focus is on building duplicate detection for contacts and companies, with the first version rolling out for contacts only, followed by companies. Glenn expressed frustration about the lack of basic usability features, such as phone extension capture for companies with PBX systems, and emphasized the importance of user experience in software adoption. Charles raised concerns about the lack of social profile linking functionality on the contact page, which Pallavi noted for future consideration but did not commit to including in the current design.

CRM Contact Management System Issues

Charles and Pallavi discussed issues with contact management in their CRM system. Charles highlighted a problem with changing primary email addresses, which can disrupt client portal access. Pallavi agreed to add warnings and notification features to address this. They also discussed the need for more flexible lookup fields, similar to Salesforce's implementation, to improve system functionality. While Pallavi suggested future improvements to make the system more B2B-friendly, Charles emphasized that the current approach would not fully achieve this goal.

Contact Management System Updates

The team discussed several updates and improvements to the contact management system. Pallavi confirmed that the overview section would be customizable, allowing users to move widgets and view opportunities. Dan raised concerns about AI summary options and TikTok contact creation, which Pallavi agreed to investigate further. Haydar reported an issue with number formatting in contacts, which Pallavi assured was already being addressed by the development team. Breakaway requested the ability to add primary and secondary phone numbers with customizable labels, which Pallavi noted for future consideration. The conversation ended with a reminder of an upcoming town hall focused on calendars.