October 2024 LeadManaging Product Updates

 

Highlight Feature

This release introduces key improvements to enhance the visibility and management of high-priority leads for PMCs with Nurturing enabled. These updates streamline workflows for leasing agents, ensuring that “hot” leads with immediate urgency are prioritized and managed efficiently.

  • Hot leads flagged by Vivian with immediate urgency now remain on the To-Do’s page until the associated event is updated by a leasing agent. This ensures that agents can focus on high-priority leads and address them in a timely manner.
  • Leasing agents are now required to perform a quick event update to remove a lead from the To-Do’s tab. Once the update is completed, the lead will automatically be moved to the “Has Been Processed” section.
  • Other hot leads that do not require immediate action are handled automatically by Vivian and will not appear on the To-Do’s tab.

Customer Benefit: These updates aim to improve the efficiency of leasing agents in managing high-priority leads, ensuring that no critical interactions are overlooked. In upcoming releases, there will be further enhancements to the To-Do’s page to make lead priority more visible within the UI, so stay tuned!

 

Improvements

We’ve introduced a new functionality allowing users to bulk update events in the new Guest Card, enhancing efficiency when managing multiple events. This feature enables users to update several events at once while maintaining flexibility in adjusting key event details, all within a single action.
Users can now select multiple events in the Event History table of the Guest Card and update them simultaneously. This feature allows quick and streamlined management of leads and events.

 

Customer Benefit: This feature saves time and effort by allowing users to manage multiple events in the new Guest Card more efficiently, without needing to update each event individually. The bulk update process ensures flexibility while maintaining the integrity of event data.

 

 

The “Contact Stage” dropdown has been added to the new guest card under the “Status” label in the Prospect Profile section, allowing users to update the contact’s current status seamlessly. The contact’s current status is reflected beside the Prospect’s name on the guest card.

Customer Benefit: Users can now manage contact statuses directly within the new guest card while preserving the familiar dropdown functionality, enhancing the guest card’s usability and alignment with the legacy version.

 

 

 

The “Event” column has been added to the Recent Events section in the Lead History in the new guest card. This column provides users with a quick reference to identify the type of interaction (e.g., Email, Call, SMS) that has occurred, enhancing the clarity and usability of the Recent Events list.

 

Customer Benefit: This update improves the user experience by providing immediate visibility into the nature of interactions, streamlining the process of tracking and managing lead communications.

 

 

For PMCs with Nurturing enabled, Calls answered by Vivian are now accurately reflected as “Call Answered by Virtual Agent” in the new guest card. This update aligns the new guest card with the correct status display, ensuring that users have clear and consistent information about call interactions.

Customer Benefit: This update improves the clarity and accuracy of call history, allowing leasing agents to quickly identify interactions handled by Vivian. This, in turn, streamlines lead management and enhances the efficiency of tracking communication efforts.

 

 

The new release introduces new front-end controls for PMCs using Nurturing Voice. These updates provide more flexibility and clearer visibility into the configurations at the building and route levels.

 

Key Updates:


1. New “Off” Value for VV Flow: A new value, “Off,” has been added to the “Vista Voice Flow” dropdown in the Add/Edit Route modal. This option allows you to easily indicate when VV is disabled for a specific route.

 

2. Routes Table: A new column has been added to show if Vista Voice is part of the route and will answer calls. This provides a quick reference for which routes are VV-enabled.

 

3. Phone Numbers Table: A new column is now available to display if VV is associated with a route and will answer calls. This enhances visibility into phone number management. 

 

Customer Benefit: These changes improve the user experience by making VV configurations more transparent and easier to manage directly within the interface.

 

 

Vivian’s emails to prospects are now enhanced with property-specific information for all PMCs with nurturing enabled. This update ensures that the emails are personalized and branded to represent the property, enhancing the communication experience for prospects

Key Updates:

1. Vivian generates the first part of the email, including the greeting with the prospect’s name and the main body of the message.

2. Before the email is sent, additional property-specific details are appended to the bottom of Vivian’s message:

     1. Prospect Name: Correctly displays the prospect’s name in the greeting.

     2. Building Name: Pulled from the building’s configuration settings.

     3. Media Source-specific Tracking Number: Displays the tracking number and labels whether the interaction was a call or SMS, providing context for the inquiry.

     4. Building Address: Includes the full building address, city, province/state, and postal/zip code.

     5. Building Logo: Shows the building’s logo, or defaults to the PMC’s logo if a building logo is unavailable, for a branded visual touch.

 

3. The current email structure and branding details are fixed and not customizable by customers at this time.

4. These updates apply to all Vivian outbound emails and replies, ensuring a cohesive communication experience across all interactions.

 

Customer Benefit: These enhancements provide a consistent and branded email experience, helping prospects identify the property and fostering a stronger connection with potential tenants.

 

 

For PMCs with Smart Surveys enabled, the system now processes responses from Smart Survey SMS sent to agents after a tour (post-tour survey):

  • If an agent responds with “Yes” to the question “Were you able to tour with the prospect?”, the appointment status will automatically update to “Toured
    • A note will be added to the appointment: “Appointment result updated to ‘Toured’ from Smart Surveys.”
  • If an agent responds with “No Show” (Option 2) to the question “Why were you unable to give a tour?”, the appointment status will automatically update to “No Show”.
    • A note will be added to the appointment: “Appointment result updated to ‘No Show’ from Smart Surveys.”

All other information within the appointment record will remain unaffected, with only the appointment result and notes being updated.

 

Customer Benefit: This automation reduces manual effort for agents, ensuring appointments are accurately reflected in the system without additional input. It also improves transparency with detailed note tracking in the Notes History.

 

Fixes

  • We have resolved an issue where a prospect’s last name was displayed as “NULL” on the guest card when they submitted a booking inquiry via the website’s booking link with the “Last Name” field left blank. This fix now prevents “NULL” values from appearing when the last name is not provided.
  • We have resolved a bug where the number of leased leads did not match between Site Performance and Building Notes. This fix ensures that the leased leads count is now consistent across both sections.
  • We have resolved an issue where changes made to the Allow SMS setting were not consistently saved. Users can now enable or disable Allow SMS, and changes will persist after clicking Save Changes.
  • We have resolved an issue where users were unable to manually merge guest cards that contained common information. This fix ensures that users can now manually merge guest cards without impacting the existing automatic merge logic.

 

 

 

 

 

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request