| AK Preparedness | Provides access to customized emergency communication, training, and plans in app | HqO delivers the product specifications HqO configures the integration in the HqO app HqO permissions the integration to only be visible to users who are approved to view / use the integration | User can view safety plans in app User can view Emergency Response plans in app User can view training plans in app | - Customer has set up an account & workflows customized with AK Preparedness - Customer intro's HqO to AK Preparedness account team - AK Preparedness provides HqO with SSO link for HqO to integrate the SAML - Customer/ AK Preparedness provides HqO with a test account to test the integration - Customer provides list of users to permissions of users who should have access to respective integrations | - Customer has an account with AK Preparedness - Admin experience remains in AK Preparedness |
| Angus Resource Booking | Provides the ability to book resources via the Angus integration in app | HqO delivers the product specifications HqO configures the integration in the HqO app HqO permissions the integration to only be visible to users who are approved to view / use the integration | HqO acts as the IdP and initiates the log in to the partner's website. The third party partner owns the web experience and its functionality. | - Customer has set up an account & workflows customized with Angus - Customer intro's HqO to Angus account team - Angus provides HqO with SSO link for HqO to integrate the SAML - Customer/Angus provides HqO with a test account to test the integration - Customer provides list of users to permissions of users who should have access to respective integrations | - Customer has an account with Angus - Admin experience remains in Angus - Customer is respecting HqO & Angus functionality |
| Angus Visitor Registration | Provides the ability to invite visitor to the building via the Angus integration in app | HqO delivers the product specifications HqO configures the integration in the HqO app HqO permissions the integration to only be visible to users who are approved to view / use the integration | User can invite user through the app User can cancel invite through the app | - Customer has set up an account & workflows customized with Angus - Customer intro's HqO to Angus account team - Angus provides HqO with SSO link for HqO to integrate the SAML - Customer/Angus provides HqO with a test account to test the integration - Customer provides list of users to permissions of users who should have access to respective integrations | - Customer has an account with Angus - Admin experience remains in Angus - Customer is respecting HqO & Angus functionality |
| Angus Work Order | Angus provides building management tools and HqO currently integrates with: Resource booking, visitor management, and service requests. The integration leverages SAML and Angus webview. It does not impact the back end admin experience so property teams will still log into their Angus portals. Data cannot be managed from Angus today. | HqO delivers the product specifications HqO configures the integration in the HqO app HqO permissions the integration to only be visible to users who are approved to view / use the integration | User can raise a work order from predetermined fields User can view the work order status in app User can cancel work order | - Customer has set up an account & workflows customized with Angus - Customer intro's HqO to Angus account team - Angus provides HqO with SSO link for HqO to integration the SAML - Customer/Angus provides HqO with a test account to test the integration - Customer provides list of users to permissions of users who should have access to respective integrations | - Customer has an account with Angus - Admin experience remains in Angus - Customer is respecting HqO & Angus functionality |
| Azure / Azure AD (OIDC) SSO | Single Sign On (SSO) is a user authentication tool specifically for our sign up/sign in flow | HqO delivers the product specifications HqO configures the integration in the HqO app | App user is able to log into their HqO app or HqO web app instance using their existing company credentials, set up and managed through their company's IdP Admin user is able to log into HqO Administration using their existing company credentials, set up and managed through their company's IdP We are offering the choice to make SSO required or optional upon configuration If app is confirgured for SSO required then, App users are required to login via SSO If app is configured for SSO optional then, App users are given the choice to log in with either SSO or by creating their own HqO credentials | - Customer to share the email domains that will require SSO - Customer to confirm if they want SSO only or give their employees the option to sign up with email verification (current flow) - Customer to confirm they use Azure with OIDC - Customer to create an OIDC application, provide HqO with the required information for the application - Customer to provide HqO with a test user | - The domain they use applies to all users with that domain. SSO is not building specific. - We must have an IT contact to configure SSO. - We can support multiple domains. - We can support multiple IdPs |
| Bbot | User can order food from on-site retail/vendors who have onboarded through Bbot. User interface is in English Language only. Can operate in US, CA, UK, Ireland, France, Netherlands and Australia. | HqO delivers the product specifications HqO configures the integration in the HqO app HqO permissions the integration to only be visible to users who are approved to view / use the integration | English Language only. Available in US, CA, UK, Ireland, France, Netherlands and Australia. Users can view food options and address / location information for onboarded retail Users can use dropdown list to select any restaurants onboarded Users can view menus for food options Users can order food through the app (pickup & delivery options available) Users can view order cart Users can edit cart Users can view when order is accepted and/or ready Users can be provided promo code by retailer Users can purchase/pay through the app - connects to Apple Wallet or credit card | - Customer has onsite retail - Onsite retail is interested in setting up online orders - Customer is in a market with neighborhood retail available via partner. | - Admin experience remains in partner system - Bbot is a linkout, so customers will not be able to garner order-level analytics via HqO - Property team accepts that the Bbot UI will appear in English only |
| Best Spaces to Work Certification | Published quarterly, the list is based on real estate experience data from tenants and their employees gathered through HqO’s proprietary Intelligence products leveraging the world’s most powerful and trusted employee experience assessment framework. | HqO to publish Best Spaces to Work reports on quarterly and annual | User can access the public property page User can access the Best Spaces page to see their property Customer will receive a download of REX Assessment results | Complete a property evaluation with an HqO real estate experience (REX) expert | REX Score meets or exceeds benchmarks to be certified and promoted as a Best Space to Work. |
| bGrid | bGrid is a global sensor party that allows to track internal climate people and assets. | HqO delivers the product specifications Customer provides URL to HqO HqO configures the integration in the HqO app HqO permissions the integration to only be visible to users who are approved to view / use the integration | bGrid allows HqO to show in realtime if a meeting room is occupied bGrid allows HqO to show sensordata from a specific room bGrid allows HqO to control light, blinds, and climate in a specific room | - Customer has set up account with bGrid (all customization is set up through bGrid - Customer has access to bGrid URL to add to their HqO app | - Customer has account with bGrid - Admin experience in bGrid - All customization in bGrid |
| BluB0X Security | Users can access their respective buildings / amenities through the HqO app via their BlueB0x mobile credential | HqO delivers the product specifications HqO configures the integration in the HqO app HqO permissions the integration to only be visible to users who are approved to view / use the integration | User can request mobile credential through the app User can access authorized areas based on mobile credential via bluetooth | - Customer has mobile access / bluetooth readers enabled - Customer has an account set up with BluB0x - Customer provided portal information to HqO - Customer has paid BluB0x for the 3rd party integration fee - Customer provides list of users to permissions of users who should have access to respective integrations, as applicable | - Admin experience in BlueB0x - 3rd party integration fee required by BluB0x - Customer is using BluB0x with HID (not Blue ID product) |
| BraXos Liftoff | Allows users to call elevators to the floor chosen on their smartphone through the Destination Dispatch system installed in their building. Supported Providers: Kone, Siemens, TKE, Otis, Fujitec, Mitsubishi, MCE | HqO delivers the product specifications HqO configures the integration in the HqO app HqO permissions the integration to only be visible to users who are approved to view / use the integration | User can call an elevator User can set a maximum of 6 favorite floors User can set their home floor Users can view all floors Users can call an elevator from the favorites bar Users can call an elevator by manually typing in the floor number | - All beacon locations and uuids - Braxos configuration details - Braxos API access | - HqO does not 'scope' the floors to the floors that users have access to, all users will see all floors |
| Building Engines - PRISM Resource Booking | Users can reserve resources through the HqO app and send information to the Building Engines Classic app | HqO delivers the product specifications HqO configures the integration in the HqO app HqO permissions the integration to only be visible to users who are approved to view / use the integration | User can view bookable resources (names, picture, and occupancy size) User can view Location of resource User can view Description of resource User can view Opening Hours of resource User can select date to book resource User can select time to book resource User can confirm information prior to booking resource User can cancel resource booking | - Customer has set up an account & workflows customized with Building Engines (PRISM) - Customer has configured Building Engines (PRISM) based on HqO supported functionality - Customer intro's HqO to Building Engines (PRISM) account team - Customer/Building Engines (PRISM) provides HqO with customer IDs necessary to configure the integration - Customer/Building Engines (PRISM) provides HqO with a test account to test the integration - Customer provides list of users to permissions of users who should have access to respective integrations | |
| Building Engines - PRISM Service Requests | Users can raise work orders through the HqO app and send information to the Building Engines Prism app | HqO delivers the product specifications HqO configures the integration in the HqO app HqO permissions the integration to only be visible to users who are approved to view / use the integration | User can view previously input Service Requests User can put in "new" Service Request User can add a Description (open text box) User can add "Issue Type" (pick one - pulled from Building Engines instance) User can add "Location" (pick one - pulled from Building Engines instance) User can "Cancel" a request as needed User can in-app communicate (messaging) with Admin | - Customer has set up an account & workflows customized with Building Engines (Prism) - Customer has configured Building Engines (Prism) based on HqO-supported functionality - Customer intro's HqO to Building Engines (Prism) account team - Customer/Building Engines (Prism) provides HqO with customer IDs necessary to configure the integration - Customer/Building Engines (Prism) provides HqO with a test account to test the integration - Customer provides list of users to permissions of users who should have access to respective integrations | - Customer has an account with Building Engines (Prism) - Admin experience remains in Building Engines (Prism) - Customer is respecting HqO & Building Engines (Prism) functionality - Property Managers / Admin roles will not be able to use the Building Engines integration - only tenant users - Users who have profiles/accounts in multiple locations/account in Building Engines is not supported |
| Building Engines - PRISM Visitor Management | Users can invite visitors through the HqO app and send information to the Building Engines Prism app | HqO delivers the product specifications HqO configures the integration in the HqO app HqO permissions the integration to only be visible to users who are approved to view / use the integration | User can view upcoming Visitors User can add a new Visitor User can add First Name User can add Last Name User can add multiple invitees (group) User can add Date of Visit User can add Time of Visit User can add Suite of Visit User can add Visit Type (pick one - Guest or Vendor) User can add Check-in Instructions" (open text box) User can add "Reason for Visit" (open text box) User can add alternate host User can "Cancel" a Visit User can add phone number of Visitor" | - Customer has set up an account & workflows customized with Building Engines (Prism) - Customer has configured Building Engines (Prism) based on HqO supported functionality - Customer intro's HqO to Building Engines (Prism) account team - Customer/Building Engines (Prism) provides HqO with customer IDs necessary to configure the integration - Customer/Building Engines (Prism) provides HqO with a test account to test the integration - Customer provides list of users to permissions of users who should have access to respective integrations | - Customer has an account with Building Engines (Prism) - Admin experience remains in Building Engines (Prism) - Customer is respecting HqO & Building Engines (Prism) functionality - Property Managers / Admin roles will not be able to use the Building Engines integration - only tenant users - Users who have profiles/accounts in multiple locations/account in Building Engines is not supported |
| Building Engines Classic - Resource Booking | Users can reserve resources through the HqO app and send information to the Building Engines Classic app | HqO delivers the product specifications HqO configures the integration in the HqO app HqO permissions the integration to only be visible to users who are approved to view / use the integration | User can view bookable resources (names, picture, and occupancy size) User can view Location of resource User can view Description of resource User can view Opening Hours of resource User can select date to book resource User can select time to book resource User can confirm information prior to booking resource User can cancel resource booking | - Customer has set up an account & workflows customized with Building Engines (Classic) - Customer has configured Building Engines (Classic) based on HqO supported functionality - Customer intro's HqO to Building Engines (Classic) account team - Customer/Building Engines (Classic) provides HqO with customer IDs necessary to configure the integration - Customer/Building Engines (Classic) provides HqO with a test account to test the integration - Customer provides list of users to permissions of users who should have access to respective integrations | - Customer has an account with Building Engines (Classic) - Admin experience remains in Building Engines (Classic) - Customer is respecting HqO & Building Engines (Classic) functionality - Property Managers / Admin roles will not be able to use the Building Engines integration - only tenant users - Users who have profiles/accounts in multiple locations/account in Building Engines is not supported |
| Building Engines Classic - Visitor Management | Users can invite visitors through the HqO app and send information to the Building Engines Classic app | HqO delivers the product specifications HqO configures the integration in the HqO app HqO permissions the integration to only be visible to users who are approved to view / use the integration | User can view upcoming Visitors User can add a new Visitor User can add First Name User can add Last Name User can add Date of Visit User can add Time of Visit User can add Floor of Visit User can add Suite of Visit User can Cancel" a Visi" | - Customer has set up an account & workflows customized with Building Engines (Classic) - Customer has configured Building Engines (Classic)ebased on HqO supported functionality - Customer intro's HqO to Building Engines (Classic) account team - Customer/Building Engines (Classic) provides HqO with customer IDs necessary to configure the integration - Customer/Building Engines (Classic) provides HqO with a test account to test the integration - Customer provides list of users to permissions of users who should have access to respective integrations | - Customer has an account with Building Engines (Classic) - Admin experience remains in Building Engines (Classic) - Customer is respecting HqO & Building Engines (Classic) functionality - Property Managers / Admin roles will not be able to use the Building Engines integration - only tenant users - Users who have profiles/accounts in multiple locations/account in Building Engines is not supported |
| Building Engines Classic- Work Orders | Users can reserve resources through the HqO app and send information to the Building Engines Classic app | HqO delivers the product specifications HqO configures the integration in the HqO app HqO permissions the integration to only be visible to users who are approved to view / use the integration | User can view bookable resources (names, picture, and occupancy size) User can view Location of resource User can view Description of resource User can view Opening Hours of resource User can select date to book resource User can select time to book resource User can confirm information prior to booking resource User can cancel resource booking | - Customer has set up an account & workflows customized with Building Engines (Classic) - Customer has configured Building Engines (Classic) based on HqO supported functionality - Customer intro's HqO to Building Engines (Classic) account team - Customer/Building Engines (Classic) provides HqO with customer IDs necessary to configure the integration - Customer/Building Engines (Classic) provides HqO with a test account to test the integration - Customer provides list of users to permissions of users who should have access to respective integrations | - Customer has an account with Building Engines (Classic) - Admin experience remains in Building Engines (Classic) - Customer is respecting HqO & Building Engines (Classic) functionality - Property Managers / Admin roles will not be able to use the Building Engines integration - only tenant users - Users who have profiles/accounts in multiple locations/account in Building Engines is not supported |
| Citymapper | Allows users to view local transit information around the users building address and plan any trip | User can get directions using public transportation by entering a starting point and destination User can filter to nearby public transportation options User can search for public transportation lines User can search for places to get direction to the place | User can view local transit information (trains, buses, bikes, etc) User can get directions to any specific location | - Customer has local transit options available | - Local transit is available in the area. Implementation must select the city transit based on this list (https://citymapper.com/cities) - The language applies to all users and has to be set when setting up the URL by adding to the city url "?lang=fr". They only support the primary local short code. |
| Data Warehouse Feed | Feed of CSV files that contain the underlying HqO data for customers to use with their internal BI and data governance tools | HqO delivers app underlying data on spaces, users, content, utilities, events and bookings that a customer can use in internal BI tools or join to their proprietary data. The underlying data is modeled to make it possible to use the data in different ways. The Data Warehouse Feed data is delivered as is to all customers and HqO does not create one off exports | A recurring export of customer's underlying data to understand how their employees or tenants are using or engaging with the HqO suite of products. | - Customer will provide a destination for the data (SFTP, S3 bucket) - Customer will provide credentials for accessing storage location - Customer will confirm the required frequency of data transmission | - Customer can support/host SFTP server |
| Datawatch | Users can reserve resources through the HqO app and send information to the Datawatch app | HqO delivers the product specifications HqO configures the integration in the HqO app HqO permissions the integration to only be visible to users who are approved to view / use the integration | HqO acts as the IdP and initiates the log in to the partner's website. The third party partner owns the web experience and its functionality. | - Customer has set up an account & workflows customized with Datawatch - Customer intro's HqO to Datawatch account team - Datawatch provides HqO with SSO link for HqO to integrate the SAML - Customer/Datawatch provides HqO with a test account to test the integration - Customer provides list of users to permissions of users who should have access to respective integrations | - Customer has an account with Datawatch - Admin experience remains in Datawatch - Customer is respecting HqO & Datawatch functionality |
| Datawatch - Mobile Access (MAC) | Users can access their respective buildings / amenities through the HqO app via their Datawatch mobile credential | HqO delivers the product specifications HqO configures the integration in the HqO app HqO permissions the integration to only be visible to users who are approved to view / use the integration | User can request mobile credential through the app User can access authorized areas based on mobile credential via bluetooth | - Customer has mobile access / bluetooth readers enabled - Customer has an account set up with Datawatch - Customer intro's HqO to Datawatch account team - Customer has Mobile Credentials/IDs available - Customer provides list of users to permissions of users who should have access to respective integrations, as applicable | - Admin experience remains in Datawatch |
| Datawatch - Resource Booking | Users can reserve resources through the HqO app and send information to the Datawatch app | HqO delivers the product specifications HqO configures the integration in the HqO app HqO permissions the integration to only be visible to users who are approved to view / use the integration | HqO acts as the IdP and initiates the log in to the partner's website. The third party partner owns the web experience and its functionality. | - Customer has set up an account & workflows customized with Datawatch - Customer intro's HqO to Datawatch account team - Datawatch provides HqO with SSO link for HqO to integrate the SAML - Customer/Datawatch provides HqO with a test account to test the integration - Customer provides list of users to permissions of users who should have access to respective integrations | - Customer has an account with Datawatch - Admin experience remains in Datawatch - Customer is respecting HqO & Datawatch functionality |
| Datawatch - Visitor Registration | Users can invite visitors through the HqO app and send information to the Datawatch app | HqO delivers the product specifications HqO configures the integration in the HqO app HqO permissions the integration to only be visible to users who are approved to view / use the integration | User can invite user through the app User can cancel invite through the app Invitee provided an email with visit information Invitee provided a QR code to access the building | - Customer has set up an account & workflows customized with Datawatch - Customer intro's HqO to Datawatch account team - Datawatch provides HqO with SSO link to configure SAML integration - Customer/Datawatch provides HqO with a test account to test the integration - Customer provides list of users to permissions of users who should have access to respective integrations | - Customer has an account with Datawatch - Admin experience remains in Datawatch - Customer is respecting HqO & Datawatch functionality |
| Envoy - Visitor Management | This allows tenants to pre-register guests through the app. Guests receive a confirmation email and are able to sign in via an Envoy kiosk or through the access readers (if there is an access control integration between Envoy and the customers ACS) | HqO delivers the product specifications HqO configures the integration in the HqO app HqO permissions the integration to only be visible to users who are approved to view / use the integration | Users can invite user through the app Users can add a start & end date of visit Users can add a start & end time of visit Users can add phone number of visitor Users can add "visit reason" Users can view visit status Users can edit visit Users can cancel visit Invitee provided an email with visit information Invitee provided a QR code to access the building | - Customer has set up an account & workflows customized with Envoy - Customer has configured Envoy based on HqO supported functionality - Customer adds HqO to their Envoy account to configure the integration - Customer/Envoy provides HqO with customer IDs necessary to configure the integration - Customer/Envoy provides HqO with a test account to test the integration - Customer provides list of users to permissions of users who should have access to respective integrations | - Admin experience remains in Envoy - Customer has an account with Envoy - Admin experience remains in Envoy - Customer is respecting HqO & Envoy functionality - Envoy has several products but HqO only integrates with their visitor management solution. This allows tenants to pre-register guests through the app. Guests receive a confirmation email and are able to sign in via an Envoy kiosk or through the access |
| Essensys Flex | Provides the ability to book (paid) resources via the Essensys integration in app | HqO delivers the product specifications | User is able to view and book available Essensys resources in HqO app > booking will showup in Essensys User is able to view upcoming reservations (made in both Essensys & HqO app) User is able to cancel reservations (through both Essensys & HqO app) > booking will be cancelled in HqO & Essensys. Essensys booking rules (including pricing, credits and minimum booking duration, available booking window, cancellation policy, user booking access) are respected in HqO Payment process can be done through HqO/Stripe Connect | - Customer has set up an account with Essensys - Customer provides HqO with a test account to test the integration | - Custom features - Essensys features beyond HqO UX for resource booking |
| Forge Bluepoint | Users can invite visitors through the HqO app and send information to the Bluepoint app | HqO delivers the product specifications HqO configures the integration in the HqO app HqO permissions the integration to only be visible to users who are approved to view / use the integration | Users can invite user through the app Users can add a start & end date of visit Users can add a start & end time of visit Users can add phone number of visitor Users can cancel visit | - Customer has set up an account & workflows customized with Bluepoint - Customer has configured Bluepoint based on HqO supported functionality - Customer intro's HqO to Buepoint account team - Customer/Bluepoint provides HqO with customer IDs necessary to configure the integration - Customer/Bluepoint provides HqO with a test account to test the integration - Customer provides list of users to permissions of users who should have access to respective integrations | - Customer has an account with Bluepoint - Admin experience remains in Bluepoint - Customer is respecting HqO & Bluepont functionality |
| Google Maps | Allows users to view local transit information around the users building address and plan any trip | User can get directions using public transportation by entering a starting point and destination User can filter to nearby public transportation options User can search for public transportation lines User can search for places to get more information about the place or to get direction to the place User can link out to the Google Maps app | User can view local transit information (trains, buses, bikes, etc) User can get directions to any specific location | - Local transit is available in the area. Implementation must enter the building address in the url (https://www.google.com/maps/search/?api=1&38+Chauncy+ST%2C+Boston%2C+MA) - Language localization is supported | |
| Google SSO (OIDC) | Google SSO for OIDC | HqO delivers the product specifications HqO configures the integration in the HqO app | User is able to log into their HqO app or tenant web instance using their existing tenant company credentials, set up and managed through the tenant company?s IDP. We are offering the choice to make SSO required or optional upon configuration. This would make it so tenant employees would be required to use SSO to log in or to give them the choice between using SSO and creating their own HqO credentials. User is able to log into the HqO platform using their existing tenant company credentials, set up and managed through the tenant company?s IDP. Tenant operator is able to configure SSO within HqO Admin. | - Customer to share the email domains that will require SSO - Customer to confirm if they want SSO only or give their employees the option to sign up with email verification (current flow) - Customer creates a new application in Google - Customer shares issuer link, application ID, and client secret | |
| HID - Mobile Access | Users can access their respective buildings / amenities through the HqO app via their HID mobile credential | HqO delivers the product specifications HqO configures the integration in the HqO app HqO permissions the integration to only be visible to users who are approved to view / use the integration | User can request mobile credential through the app User can generate and consume an HID Origo invitation code(onboard) User can access authorized areas based on mobile credential via bluetooth Admin can view only Origo records in HqOS | - Customer has mobile access / bluetooth readers enabled - Customer has an account set up with HID - Customer has an Origo Portal - Cutomer invites HqO to Origo Portal - Customer has Mobile Credentials/IDs available - Customer provides list of users to permissions of users who should have access to respective integrations, if applicable | - Admin experience in HID |
| HqO Amenities | Amenities is a dedicated area in the app available through a utility button which displays all available amenities to an app user App users find this valuable to browse and discover the amenities that are available to them in the workplace Customers find this valuable to communicate the amenity offerings they provide | HqO delivers the product specifications | App user can tap on the Amenities utility button to view all available amenities App user can select a specific amenity and be taken to a details page Admins are able to create, edit and delete sections within Amenities section Admins are able to change order of sections with in Amenities section Admins are able to create, edit and delete Amenities Admins can create and edit Amenity name, details and imagery Admins can Preview how the content tile will look Admins can see in Analytics the most-viewed amenities | - Self-service functionality | |
| HqO Analytics | Our HqO Analytics dashboards provide admin users with a comprehensive view of user adoption and engagement of the platform. It allows them to view and track the number of users who have registered and are active, as well as the level of engagement with individual features. Additionally, admins can filter on specific buildings, companies (where applicable) or time frames to better understand app performance across different regions or user subsets. With the ability to analyze real-time data as well as historical trends, HqO Analytics provides admins with a comprehensive view of user adoption and engagement, helping them optimize their strategy and improve user experience. | Admins can view user activation, adoption and engagement statistics. Admin users can drill down to view engagement by building, company (where applicable) or time frame. Admin users can view activity trends by app or feature including utilities, content, feedback and space bookings. | Admins can view user activation, adoption and engagement statistics. | - Self-service - Customer logs into HqO Admin to see data | - Using integration / tech that is provided in the Analytics dashboard |
| HqO Audiences | Audiences allows Admins to target app content and push notifications to specific buildings, companies or individual users App users are able to see the content or receive the notifications if they are a member of the audience it is targeted to Customers find this valuable because they are able to provide a personalized experience to the users who are able to utilize functionality, programming, and other offerings communicated to app users through the app | HqO delivers the product specifications | App users are able to browse and discover content if they are a member of the Audience user group the content is targeting App users will receive push notifications if they are a member of the Audience user group the push notification is targeting Admins can target a piece of content to an Audience user group. The default Audience on content is the Building Audience, all users attached to the building can see all building content by default. Admins can target a push notification to an Audience user group. The default Audience on a push notification is the Building Audience, all users attached to the building will receive the notification if allowed by the app user. Audiences can be app users in a building, across multiple buildings, in a company, or a limited set of app users. Admins can manually create different types of audiences. Audience types include a building or multiple building(s), a company or multiple companies within a building, individual users | - Self service functionality | |
| HqO Capacity Manager | Office Capacity Manager allows Admin users to easily manage the number of employees that may come into the office on any given day. As employees request access to the building, they can provide additional information about their department, the reason for the request, and the priority of the request. The Capacity Manager will help ensure your company is maximizing your space to help facilitate a safer return for all of your employees. | HqO delivers the product specifications HqO configures the Capacity Manager in the HqO app | Users can submit in-office requests for any day of the upcoming week Users must agree to specified guidelines when submitting a request Admin users can customize terms that must be agreed to for a user to submit a request Admin users can adjust and track office capacity Admin users can enable contact tracing Admin users can manage all requests from a centralized dashboard Admin users can receive a capacity notification when requests exceed capacity restrictions | - Customer provides a list of tenant companies opting into Capacity Manager - Customer customizes questions/requirements to accept in-office terms - Customer determines admins to receive information collected through integration | - Can only be built at the company/tenant level - Can not view who the other users are that have secured a spot on a given day - only viewable at the admin level |
| HqO Content Creator | HqO offers an easy-to-use, purpose-built content creator so our customers can be empowered to create content quickly and easily. You can maximize your users' engagement with your properties' physical and digital offerings and improve their overall experience. The content creatior is flexible which allows customers to promote and highlight the property offerings and experiences in the way that resonates with your users to generate maximum engagement. Use a simple form with required information and then select from menu of options to tailor content and add additional fields like CTA buttons, RSVPs, location/host, directions, and custom text for any of these fields. Additionally, you can tailor the content with rich text, link to images or PDFs with media upload, target content to specific users with audiences and increase engagement using deeplinking push notifications. Content can be configured on the home page of the app and in an optional "Spotlight" tab which appears in the bottom navigation of the app. (See HqO Spotlight) | HqO delivers the product specifications HqO trains customer on Content Creator | App user can browse and discover content on the home screen that describes the information, programming, events, deals, food options, help or functions that are available to them If app user clicks into a content tile they see the details and may see a Call to Action (CTA) button that directs to the next step in the experience which may be more information through a website or media, another app experience, RSVP or claim a coupon or deal. App user may receive a push notification that communicates information or instructions about the experiences available to them and if clicked deeplinks the app user directly to the experience details Admins are able to create, edit and delete sections on the home screen Admins are able to change order of sections on the home sceen Admins are able to create, edit and delete content on the home screen Admins are able to select a piece of contact to promote in the app. The promoted content appears at the top of the home screen Admins can create and edit content with a title, subtitle, image, and description. Admin then can select a set of conditions on a piece of content Admins can write a description including rich text including bold, italics, underline, strikethrough, superscript, subscript Admins can write a description including bulleted list, numbered list, or emojis Admins can write a description that includes an External Link to a third party external web link/URL or web app Admins can write a description that includes a link to Uploaded media. Media can include a PDF, JPEG or PNG. This can be used for menus, memos, waivers, handbooks, marketing materials, other communications or images. Admins can add a Call to Action (CTA) button and customize the CTA button text and where it links to. After clicking the CTA button, app user can be navigated to an External URL, Screen available in the HqO app, Another app, or Uploaded media. If Admin selects and enters External URL, then the app user will be navigated to the to the third party external web link/URL or web app If Admin selects Screen in this app, then they can select other app features available to promote via content (surveys, who's in). The app user will be navigated to that screen. If Admin selects Another app and enters app link, then the app user will be navigated to the to the third party app If Admin selects Uploaded media and uploads a PDF, JPEG, or PNG, then the app user will be navigated to the uploaded media. This can be used to direct users to menus, memos, waivers, handbooks, marketing materials, other communications or images. Admin can add a Call to Action (CTA) button and customize the CTA button text and where it links to. After clicking the CTA button, app user can be navigated to an RSVP or Claim experience. Admins can limit number of RSVPs. Admin can limit number of claims and set limit of claims per individual app user Admins can add a Host (company or custom text) and let the app user know who is hosting the experience Admins can add a physical and/or virtual location and give additional directions to the app user to help them know how to find the experience Admins must select a standard category for data tracking Admins can Preview how the content tile will look on the home screen Admins can schedule the date/time the piece of content is publish in the app and the date/time it is archived in the app Admins can display the date/time information to the app user in content details, and/or show calendar icon on home screen tile Admins can limit the amount of time that the CTA button is active which can be used for deals, coupons, raffles, or other time bound experiences Admins can target a piece of content to an Audience user group. Audiences can be app users in a building, across multiple buildings, in a company, or a limited set of app users. Content can be sent to multiple Audience user groups Admins can send out a personalized push notification that deeplinks the app user to the experience Admins must select the home screen section the piece of content appears | - Self-service functionality - During initial build-out, customers can provide information, branding, content, and images to add to the app through the HqO admin experience | - If Admin selects External URL, then the app user will be navigated to the External web link/URL. HqO is not responsible for the experience of that third party as it may not be mobile friendly or responsive. HqO will work with you to test if needed. |
| HqO Directory | Directory is a listing of all companies classified as selected company type within a building. This directory can be accessed in both web and mobile apps, provided the Directory utility button is enabled for the building. | HqO delivers the product specifications HqO configures the Directory in the HqO app | User can see a list of all companies that are tagged with the selected company types User can see header image, logo, website link and description for each company Admins can edit company details that show in the directory by navigating to the company in the 'Communications' section Admins can amend the header image, logo, website link and description for each company Directories can be set up for one, all, or a selection of the below company types: Landlord, Tenant, Vendor, Developer | - HqO to provide Customer with file to capture key information around tenant companies - Customer provides company names and information to upload - Customer provides company details & logos | |
| HqO Floor Plans | Gives user the ability to view and book spaces (resources, e.g. desks/rooms) in the physical workspace through a digital floorplan. | HqO delivers the product specifications HqO configures the integration in the HqO app | User is able to view resources from different resource booking adapters (e.g. HqO native, Exchange, etc.) on the floorplan. User is able to view available resources for a specific date/time selection on the floorplan User is able to book resources through the floorplan view | - Customer provides floorplan (CAD, pdf, jpg, png). More specific information on requirements can be found here - Customer provides information of available resources in this template | |
| HqO Merchant Directory | User can see a list of merchants in or in the neighborhood | Admin can create merchants to display in the app. The merchant can have a name, a description, a header image, a logo and a link to a website or menu. Users can view a list of merchants Users can click to learn more about a merchant Users can click a CTA to open a website | Allows customers to create a directory of just merchants associated with the site. This can be any merchant that is onsite or nearby that the customer wants to highlight. | - Customer provides input on what merchants to include in the direc'tory | - Localization will depend on the capabilities of the URL destination and whether or not it supports a variable to set the user's language preference - We can't guarantee this will support deep linking into 3rd party apps on the user's device (e.g. deep linking to the Grubhub app). |
| HqO Onboarding | Every user that signs up to the HqO app has to go through the onboarding flow. This is either our standard flow as below, or SSO can be configured per tenant company. | HqO delivers the product specifications HqO configures the integration in the HqO app | User downloads the app and launches it for the first time User enters their email address - if this meets the conditions as set below, the user creates an account User creates a password User enters the verification code which is sent to their email address (domains can be whitelisted so users do not need to verify their account, however this is not recommended for security reasons) User chooses whether to allow app notifications User arrives at homepage and generally remains signed in This can be set up in 2 different ways; 1. Private email domains are attached to a tenant company, to allow users with this email domain to sign up to the app 2. The app is open for public sign up. Anybody with any email address is permitted to sign up for the app | - HqO provides Customer with form to compile information needed prior to launch - Customer provides list of approved companies & email domains | - Additional customization needed for non-corporate domain emails |
| HqO Push Notifications | Push notifications increase engagement with the app and inform app users of information and experiences available to them Admins have the ability to communicate to app users through push notifications | HqO Delivers the product specifications | App user actively chooses whether to allow push notifications as part of the sign up process If user has their permissions set to allow, they will receive scheduled push notifications to their device App users can turn off notifications for the app at any time Admins can schedule a push notification and write the header and body Admins can schedule a push notification to be sent ASAP or for a future date Admins can target push notifications to specific Audience user groups Users can use deeplinks to app content Admin users can view a list of pending and sent notifications Admin users can search notification lists Admin users can modify pending notifications | - Self-service functionality | - Push Notifications will be sent to users who enable Push notifications for HqO app on their device |
| HqO Resource Booking | Users can view, book and cancel available resources setup in Hqo admin. Resource settings and booking rules can be managed by admins in HqOs. | HqO delivers the product specifications | User is able to view and book available resources User is able to view upcoming reservations User is able to update, adjust and cancel reservations Admins can view, accept and reject resource booking requests Admins can set up new resources for booking Resources can be configured so they can be automatically booked, or so that reservation requests must be manually accepted or denied by an admin Resources can be free or paid for | - Customer provides information (hours of operation, description, etc) & photos of available resources - Customer determines if resources will be "free" or "charged" - If Customer chooses to charge, Customer will need to create a Stripe account to collect payment | - In the case of paid events, customer needs to have a Stripe account |
| HqO Service Booking | HqO's service booking enables users to view, book and pay for 1:1 appointments in-app. HqO's native service booking functionality is powered by TimeKit. | Users can view service providers Users can view a list of services Users can select a service and view availability Users can purchase a service using apple pay, debit card or credit card | Users can view service providers Users can view a list of services Users can select a service and view availability Users can purchase a service using apple pay, debit card or credit card | - Customer provides list of users to permissions of users who should have access to respective integrations - Customer provides information (date & time, cost, description, etc) around services desired to book | - Services available to book |
| HqO Service Requests | HqO's built-in service requests allows users to submit and monitor service requests (also known as issue reports and work orders). | HqO delivers the product specifications HqO configures the integration in the HqO app | User is able to create and submit a request User is able to select the issue type from a list, input the location, upload an image and add a free text description User is able to view status of pending requests and view past service requests User is notified when the status of their service request changes Admin is able to view, manage and update the status of service requests Admin can make a submitting a description and image either optional or required Users with the 'Landlord Operator' user role will be notified via email when a new service request has been submitted | - Customer provides list of users to permissions of users who should have access to respective integrations - Customer determines which users have admin privileges (landlord/property manager or tenant contacts) | - Admin cannot customize the list of services request types - User cannot communicate back and forth in app for service request |
| HqO Spotlight Tab | HqO Spotlight gives a dedicated space to highlight content of importance in a separate area of the app. This space can be used for any purpose. Examples of how customers have used Spotlight includes: 'Office Procedures' - content about safety protocols and important office information 'Events Calendar' - content about onsite and virtual events 'Member Benefits' - content about available deals and benefits 'Local Area Guide' - content about nearby retailers, cafes, gyms and facilities | HqO delivers the product specifications HqO configures the integration in the HqO app | App user can tap the icon next to the homescreen button to navigate to the spotlight tab App user can browse and discover content on the spotlight tab that describes the information, programming, events, deals, food options, help or functions that are available to them If app user clicks into a content tile they see the details and may see a Call to Action (CTA) button that directs to the next step in the experience which may be more information through a website or media, another app experience, RSVP or claim a coupon or deal. App user may receive a push notification that communicates information or instructions about the experiences available to them and if clicked deeplinks the app user directly to the experience details Admins are able to configure the icon and display name for the spotlight tab that the app user will see Admins are able to create, edit and delete sections on the home screen Admins are able to change order of sections on the home sceen Admins are able to create, edit and delete content on the home screen Admin is able to add, change and delete content in the spotlight tab Admins can create and edit content with a title, subtitle, image, and description. Admin then can select a set of conditions on a piece of content Admins can write a description including rich text including bold, italics, underline, strikethrough, superscript, subscript Admins can write a description including bulleted list, numbered list, or emojis Admins can write a description that includes an External Link to a third party external web link/URL or web app Admins can write a description that includes a link to Uploaded media. Media can include a PDF, JPEG or PNG. This can be used for menus, memos, waivers, handbooks, marketing materials, other communications or images. Admins can add a Call to Action (CTA) button and customize the CTA button text and where it links to. After clicking the CTA button, app user can be navigated to an External URL, Screen available in the HqO app, Another app, or Uploaded media. If Admin selects and enters External URL, then the app user will be navigated to the to the third party external web link/URL or web app If Admin selects Screen in this app, then... If Admin selects Another app and enters app link, then the app user will be navigated to the to the third party app If Admin selects Uploaded media and uploads a PDF, JPEG, or PNG, then the app user will be navigated to the uploaded media. This can be used to direct users to menus, memos, waivers, handbooks, marketing materials, other communications or images. Admin can add a Call to Action (CTA) button and customize the CTA button text and where it links to. After clicking the CTA button, app user can be navigated to an RSVP or Claim experience. Admins can limit number of RSVPs. Admin can limit number of claims and set limit of claims per individual app user Admins can add a Host (company or custom text) and let the app user know who is hosting the experience Admins can add a physical and/or virtual location and give additional directions to the app user to help them know how to find the experience Admins must select a standard category for data tracking Admins can Preview how the content tile will look on the home screen Admins can schedule the date/time the piece of content is publish in the app and the date/time it is archived in the app Admins can display the date/time information to the app user in content details, and/or show calendar icon on home screen tile Admins can limit the amount of time that the CTA button is active which can be used for deals, coupons, raffles, or other time bound experiences Admins can target a piece of content to an Audience user group. Audiences can be app users in a building, across multiple buildings, in a company, or a limited set of app users. Content can be sent to multiple Audience user groups Admins can send out a personalized push notification that deeplinks the app user to the experience Admins must select the home screen section the piece of content appears | - Self-service functionality - Customer determines which content should be highlighted in the spotlight tab in app - Customer determines what the "spotlight tab" should be called | |
| HqO SSO | Single Sign On (SSO) is a user authentication tool specifically for our sign up/sign in flow. | HqO delivers the product specifications HqO configures the integration in the HqO app | User is able to log into their HqO app or tenant web instance using their existing tenant company credentials, set up and managed through the tenant company?s IDP. -We are offering the choice to make SSO required or optional upon configuration. This would make it so tenant employees would be required to use SSO to log in or to give them the choice between using SSO and creating their own HqO credentials. -User is able to log into the HqO platform using their existing tenant company credentials, set up and managed through the tenant company?s IDP. -tenant operator is able to configure SSO within HqO Admin. | ||
| HqO Surveys | Understand your app users more than ever before by creating short custom surveys with open-ended or multiple choice questions Whether you are looking for app user input about events, amenities, or other workplace needs, our Survye builder will allow you to collect user feedback. HqO Surveys will give you insights in real-time. | HqO delivers the product specifications | App users can answer surveys and submit feedback Admins can create surveys with multiple choice and/or open feedback questions Admins can preview the survey Admins can publish surveys in app by linking through content, target to an audience, and engaging with notifications Admins can view responses by question Admins can download responses | - Self-service functionality | |
| HqO Tenant Web | Tenant web is a web-based version of the app. | HqO delivers the product specifications HqO configures the integration in the HqO app | Admin is able to amend all content shown in tenant web. Any changes made in Admin automatically pull through to both the app and the desktop version User can sign up for HqO app through desktop version | - Customer determines sub-account name (example: customer.hqo.co) - Customer provides desired experience of utility button customization | |
| HqO Utility Buttons | Utility Buttons allow users to quickly navigate to high value functionality within the app. Choose the button shape that works best for your brand and the number of capabilities available to your users. Select colors, icons, and titles for each of your utility buttons. | App users can navigate directly to different functionalites via a utility button. Functionalies available will be based on the customer's HqO contract. Admins can configure the display Title on the button Admins can select button icon from a standard list Admins may permission button to users based on app users' permissions Admins can enable utility buttons that link to the following functionalities based on the customer's HqO contract: Amenities Company Directory Merchant Directory Mobile Access Service Booking Resource Booking Visitor Registration Service Requests Who's In Third party external web link/URL or we app (if meets requirements) Third party external app (if meets requirements) SAML Integrations (if meets requirements) Ability to link from the HqO app to a functionality pre-installed on the device for text messaging, phone calls, or email. Admins can reorder utility buttons Admins can remove utility buttons | |||
| HqO Visitor Registration | Allows users to register the details of an upcoming visitor and log this with the front of house team. | HqO delivers the product specifications HqO configures the integration in the HqO app | User is able to register the details of a visitor due to attend the building Users enter their visitor's first name, last name, email (optional or required), date, start time (optional or required) and end time (can be optional or required) User can see all past and upcoming visitors Admin is able to view and manage upcoming and past visitors on any given day. They can view the visitor name, expected time, host name, host company and status (default - scheduled) Admin can update a visitor's status to scheduled, checked in, checked out, or canceled | - Customer determines who will manage Visitor Registration at the building (ex. security guard) - Customer designates who has access to Visitor Registration through the app - Customer provides list of users to permissions of users who should have access to respective integrations | Customer has an admin to monitor Visitor Registration / check-in |
| HqO White Label App | Customer branding of the app user's app store experience | HqO delivers the product specifications HqO configures the app section in the Apple & Google App Store | Customer can customize name of app in the app store Customer can customize logo of app in the app store Customer can customize developer name in the app store Customer can customize search filters in the app store Customer can customize app description in the app store | - Customer provides desired app logo - Customer provides desired app name - Customer provides desired app branding / colors - Customer provides desired app description - Customer creates an Apple Developer account & invites HqO to manage | - Customer has DUNS & Bradstreet - Customer has a legal entity |
| Impak Solutions Work Orders | For over 20 years, IMPAK Corporation has provided innovative solutions for individuals and businesses with modified atmosphere packaging needs. With a full range of sorbent and flexible packaging products, including Mylar films and bags, standard and embossed poly vacuum bags, stand up bags, mini pouches, desiccants, oxygen absorbers, and thousands of sealer products and accessories, IMPAK can address even the most complex packaging challenges. Other services include prototyping and custom product development, custom laminations, custom printing, adhesive labeling, product packaging, and machine assessment and repair. | ||||
| Kastle - Mobile Access | Users can access their respective buildings / amenities through the HqO app via their Kastle mobile credential | HqO delivers the product specifications HqO configures the integration in the HqO app HqO permissions the integration to only be visible to users who are approved to view / use the integration | User can request mobile credential through the app User can access authorized areas based on mobile credential via bluetooth | - Customer has mobile access / bluetooth readers enabled - Customer has an account set up with Kastle - Customer intro's HqO to Kastle account team - Cutomer to collect emails for all mobile access users prior to launch - Customer provides list of users to permissions of users who should have access to respective integrations, as applicable | - Admin experience in Kastle - Customer does not use PKOC readers (model readers: Nano & Quad) |
| Kastle - Visitor Registration | Visitor registration solution that allows a user to register a visitor coming to the building or suite/site. Kastle is a friendly partner who provides a mobile access solution. They also provide a very simple visitor registration tool that can connect directly to their mobile access solution. This provides a visitor an easy way to access a building or space without checking-in. In order to satisfy customer demand for this add-on functionality, we introduced a simple visitor registration integration powered by Kastle. | User can register a visitor via app. User can add name, location, and date + time information to the request. User's visitor will receive an invitation email. If applicable, that email will include a QR code the visitor can use to access the elevator/pass security gates etc by scanning the QR code. | -Customer uses Kastle as their access solution and want a simple visitor registration solution that is bundled with access. | ||
| LiveSafe | Provides access to customized emergency communication, training, and plans in app | HqO delivers the product specifications HqO configures the integration in the HqO app HqO permissions the integration to only be visible to users who are approved to view / use the integration | User can view safety plans in app User can view Emergency Response plans in app User can view training plans in app | - Customer set up account with LiveSafe (all customization will be completed with Livesafe) - Customer to intro HqO to Livesafe team - Customer/Livesafe to provide Org ID for HqO to configure in the HqO app - Customer to provide: -- Emergency Phone - provided by building contact. Typically the number used after hours as well for emergencies. -- Work Hours - provided by building contact -- Phone - The phone number provided by contact. This is the number that can be contacted during the Work Hours | - Admin experience in LiveSafe |
| MappedIn - Wayfinding | Users can use wayfinding to navigate their building | HqO delivers the product specifications Customer provides URL to map for HqO HqO configures the integration in the HqO app HqO permissions the integration to only be visible to users who are approved to view / use the integration | Users can view map of their space Users can find colleagues User can zoneshare their location to their specific floor User can access resource booking through map view User can access food ordering through map view | - Customer set up account with MappedIn/MapWize (all customization is in MappedIn) - Customer has access to floor/building map via a URL to provide to HqO | - Customer has a MappedIn/MapWize account - Admin experience in MappedIn/MapWize - Customer provides HqO the URL to add to the HqO app |
| Mazemap | Users can use wayfinding to navigate their building | HqO delivers the product specifications Customer provides URL to HqO HqO configures the integration in the HqO app HqO permissions the integration to only be visible to users who are approved to view / use the integration | Users can view map of their space Users can find colleagues User can zoneshare their location to their specific floor User can access resource booking through map view User can access food ordering through map view | - Customer set up account with Mazemap (all customization will be completed with Mazemap) - Customer has access to floor/building map through a URL to add to their HqO app | - Customer has account with Mazemap - Admin experience in Mazemap - All customization in Mazemap |
| Mindbody Class Booking | Users can book services. Can work with the membership solution | HqO integrates with Mindbody tier Accelerate 2.0 or higher HqO can show classes and class bookings in the user application User can see a calendar schedule of classes User can book a class through their contract User can join a waitlist | Users can view a calendar of available classes + services to book Users can book classes at onsite fitness centers Users can use promo codes to access onsite deals Users can add themselves to a waitlist for an upcoming class | - Customer has set up an account & workflows customized with Mindbody - Customer has configured Mindbody based on HqO-supported functionality - Customer intro's HqO to Mindbody account team - Customer/Mindbody provides HqO with customer IDs necessary to configure the integration - Customer/Mindbody provides HqO with a test account to test the integration - Customer provides list of users to permissions of users who should have access to respective integrations | - Customer has an account with Mindbody - Admin experience remains in Mindbody - Customer is respecting HqO & Mindbody functionality |
| Mindbody Memberships | Users can add memberships through the HqO app and send information to the Mindbody app. Can work with the class booking solution | HqO integrates with Mindbody tier Accelerate 2.0 or higher HqO can show membership options setup in Mindbody Users can see membership options User can purchase a membership User can agree to terms and conditions | Users can view available membership options Users can purchase membership to onsite fitness centers | - Customer has set up an account & workflows customized with Mindbody - Customer has configured Mindbody based on HqO supported functionality - Customer intro's HqO to Mindbody account team - Customer/Mindbody provides HqO with customer IDs necessary to configure the integration - Customer/Mindbody provides HqO with a test account to test the integration - Customer provides list of users to permissions of users who should have access to respective integrations | - The customer has an account with Mindbody - Admin experience remains in Mindbody Customer respects HqO & Mindbody functionality - Memberships must bill on the date of the purchase |
| Moffi | Users can reserve resources through the HqO app and send information to the Moffi app | HqO delivers the product specifications HqO configures the integration in the HqO app HqO permissions the integration to only be visible to users who are approved to view / use the integration | Users can view bookable rooms through the app Users can view details about the individual resources Users can book a resource Users can view their confirmed resource bookings Users can cancel their resource bookings | - Customer has created an account with Moffi - Customer provides list of users to permissions of users who should have access to respective integrations | - Admin experience remains in Moffi |
| Nexudus (Beta) | Users can book spaces, desk booking, & amenities through the HqO app via integration with Nexudus | Implementation team needs to establish feasible times to configure and launch because of the complex nature of flex. HqO delivers the product specifications HqO configures the integration in the HqO app HqO permissions the integration to only be visible to users who are approved to view / use the integration https://docs.google.com/spreadsheets/d/1fapk29xQfFqxoSso4QJzJ5lznCdi-agqxrYj5zuLuio/edit#gid=0 | Users can view bookable rooms through the app Users can sort resources by categories (ex. small conference room, desk, etc) Users can view details about the individual resources Users can book a resource Users can view their confirmed resource bookings Users can cancel their resource bookings | - Customer provides list of users to permissions who should have access to respective integrations | - Admin experience for flex provider remains in Nexudus |
| Nexudus Enterprise | Users can book spaces, desk booking, & amenities through the HqO app via integration with Nexudus | Implementation team needs to establish feasible times to configure and launch because of the complex nature of flex. HqO delivers the product specifications HqO configures the integration in the HqO app HqO permissions the integration to only be visible to users who are approved to view / use the integration | Customer can have invoicing via a configured member portal that allows users and the customers to pay after booking via monthly invoicing. User can make free bookings. User can pay ahead of time with direct debit. Customer can have resource booking rules and configurations including: *Advanced booking rules (Reject booking more than x hours before booking starts) *Late cancellations (Reject cancellations x hours before booking starts) *Late bookings (Reject booking less than x hours before booking starts) *Max duration (Cannot be longer than x time) and minimum duration (Cannot be shorter than x time) *No return policy (bookings for resources must be separated by x time gap) *Available times and days (limited schedule to open hours) *Edit image - self service *Have multiple booking windows in a single day *Have different booking windows each day of the week *Enable features to show in resource description *Edit description *Capacity Customer can have booking approval flow Customer can have advanced booking rules including: *Member and contacts: Different booking windows for different users *Members (tenants) having different rules than other users Customer can have advanced rate options including *Display on invoices as: different name displayed on customer invoices *Maximum price: Cap the price of bookings at X for bookings of this resource type. *Fixed Cost: The first X minutes have a fixed cost & The fixed cost for this period is X Customer can have company level bookings vs individuals. Customer can provide discounts to different groups of users. Customer can limit resources to user groups. Customer can have a configured member portal to add on products, edit bookings, and create a booking. Customer can have booking across multiple buildings. Customer can have custom questions for resources. Customer can have customized email communications. Customer can self service the admin dashboard to archive resources, hide resources from the app, and create flexible user roles. Customer can access room booking displays and ACS integrations via Nexudus and the third party provider. Customer can upload past bookings. | - Customer provides list of users to permissions who should have access to respective integrations | - Requires EPD scope based on specific customizations and setups. - Room booking displays via Nexudus and a third party provider, not HqO. |
| Nexudus Lite | Users can book spaces, desk booking, & amenities through the HqO app via integration with Nexudus in the HqO NX Network | Implementation team needs to establish feasible times to configure and launch because of the complex nature of flex. HqO delivers the product specifications HqO configures the integration in the HqO app HqO permissions the integration to only be visible to users who are approved to view / use the integration | Customer has access to Nexudus via the HqO NX Network. User can make free bookings. User can pay ahead of time with direct debit. Customer can have resource booking rules and configurations including: *Advanced booking rules (Reject booking more than x hours before booking starts) *Late cancellations (Reject cancellations x hours before booking starts) *Late bookings (Reject booking less than x hours before booking starts) *Max duration (Cannot be longer than x time) and minimum duration (Cannot be shorter than x time) *No return policy (bookings for resources must be separated by x time gap) *Available times and days (limited schedule to open hours) *Edit image - self service *Have multiple booking windows in a single day *Have different booking windows each day of the week *Enable features to show in resource description *Edit description *Capacity Customer can have booking approval flow Customer can have booking across multiple buildings. Customer can have customized email communications. Customer can self service the admin dashboard to archive resources, hide resources from the app, and create flexible user roles. Customer can access room booking displays via Nexudus and the third party provider. | - Customer provides list of users to permissions who should have access to respective integrations | - Room booking displays via Nexudus and a third party provider, not HqO. |
| Nexudus Standard | Users can book spaces, desk booking, & amenities through the HqO app via integration with Nexudus | Implementation team needs to establish feasible times to configure and launch because of the complex nature of flex. HqO delivers the product specifications HqO configures the integration in the HqO app HqO permissions the integration to only be visible to users who are approved to view / use the integration | Customer can have invoicing via a configured member portal that allows users and the customers to pay after booking via monthly invoicing. User can make free bookings. User can pay ahead of time with direct debit. Customer can have resource booking rules and configurations including: *Advanced booking rules (Reject booking more than x hours before booking starts) *Late cancellations (Reject cancellations x hours before booking starts) *Late bookings (Reject booking less than x hours before booking starts) *Max duration (Cannot be longer than x time) and minimum duration (Cannot be shorter than x time) *No return policy (bookings for resources must be separated by x time gap) *Available times and days (limited schedule to open hours) *Edit image - self service *Have multiple booking windows in a single day *Have different booking windows each day of the week *Enable features to show in resource description *Edit description *Capacity Customer can have booking approval flow Customer can have advanced rate options including *Display on invoices as: different name displayed on customer invoices *Maximum price: Cap the price of bookings at X for bookings of this resource type. *Fixed Cost: The first X minutes have a fixed cost & The fixed cost for this period is X Customer can have company level bookings vs individuals. Customer can provide discounts to different groups of users. Customer can limit resources to user groups. Customer can have booking across multiple buildings. Customer can have custom questions for resources. Customer can have customized email communications. Customer can self service the admin dashboard to archive resources, hide resources from the app, and create flexible user roles. Customer can access room booking displays and ACS integrations via Nexudus and the third party provider. Customer can upload past bookings. | - Customer provides list of users to permissions who should have access to respective integrations | - Room booking displays via Nexudus and a third party provider, not HqO. |
| Office 365 Resource Booking | Users can view, book and cancel available resources setup in Exchange in the HqO application. Two way sync of bookings. Exchange is source of through for the resources and their availability. | HqO delivers the product specifications | User is able to view and book available Exchange resources in HqO app > booking will showup in Exchange (calander of the user) User is able to view upcoming reservations (made in both Exchange & HqO app) User is able to cancel reservations (through both Exchange & HqO app) > booking will be cancelled in HqO & Exchange. | - Azure app setup | - Setup of Azure app |
| Okta (OIDC) SSO | Single Sign On (SSO) is a user authentication tool specifically for our sign up/sign in flow | HqO delivers the product specifications HqO configures the integration in the HqO app | App user is able to log into their HqO app or HqO web app instance using their existing company credentials, set up and managed through their company’s IdP Admin user is able to log into HqO Administration using their existing company credentials, set up and managed through their company’s IdP We are offering the choice to make SSO required or optional upon configuration If app is confirgured for SSO required then, App users are required to login via SSO If app is configured for SSO optional then, App users are given the choice to log in with either SSO or by creating their own HqO credentials | - Customer to share the email domains that will require SSO - Customer to confirm if they want SSO only or give their employees the option to sign up with email verification (current flow) - Customer to confirm they use Okta with OIDC or SAML (HqO's preference is SAML) - Customer to provide required information for their IdP and protocal | - The domain they use applies to all users with that domain. SSO is not app or building specific. - We must have an IT contact to configure SSO. - We can support multiple domains. - We can support multiple IdPs |
| Okta SCIM + SSO | The System for Cross-domain Identity Management (SCIM) specification is designed to make managing user identities in cloud-based applications and services easier. We have invested in a SCIM service for multiple IdPs as it is a scaleable enterprise solution for user creation and deactivation and gives our customers control over the data sent to us. Leverages customers' existing identity provider (IdP). Ensures user lists are always accurate as updates made to the users’ profile through IdP will be pushed to the HqO application. Reaches the right employees. As corporates' employees change, individual users' access is automatically updated to ensure the right users have access and can engage with the app. Improves user experience. User does not need to enter their name or create a password when signing up via SSO. Users will be associated with the right company & building(s). | If SCIM integration is enabled, then SSO is required If SSO & SCIM integration is enabled, then users in the customer's IdP will be created in the HqO platform (First name, Last name, Email) HqO app or web app user is automatically assigned to the company and the building(s) configured If a new user is added to the customer's IdP, then the user will be created in the HqO platform, (First name, Last name, Email) HqO app or web user is automatically assigned to the company and the building(s) configured If a user created by via SCIM integration and the user signs up for the HqO app then, the app user will have the following sign up flow experience: Enter work email > Choose Provider > IdP's Auth page > Accept HqO app Terms & Conditions > Select Primary Building (if user is assigned to more than one building) > Enable push notifcations > Congratulations! page > App Home screen If a user's name is updated in the IdP then, the customer's IdP will push the user's updated information to the HqO platform (First name, Last name) If a user is deactivated in the customer's IdP then, the customer's IdP will push that information to the HqO platform and the user will be deactivated in the HqO platform App user will be logged out of the HqO app within an hour. User updates in the IdP are received by HqO platform in real time If a user is created via SCIM integration, then they are created in the HqO platform and can be viewed in HqO Admin > Communications > Users. HqO Admin Users page will list the users and their status (Active, Pending, Deactivated). "Active" users have signed up for the app and accepted T&Cs "Pending" users were created via SCIM integration but user has not completed sign up for the app and has not accepted T&Cs "Deactivated" users are no longer provisioned for the HqO app. | |||
| OpenPath - Mobile Access | Users can access their respective buildings / amenities through the HqO app via their Openpath mobile credential | HqO delivers the product specifications HqO configures the integration in the HqO app HqO permissions the integration to only be visible to users who are approved to view / use the integration | User can request mobile credential through the app User can access authorized areas based on mobile credential via bluetooth | - Customer has mobile access / bluetooth readers enabled - Customer has an account set up with OpenPath - Customer to add HqO to their OpenPath portal - Customer collects emails of users prior to integration - Customer provides list of users to permissions of users who should have access to respective integrations | - Openpath visitor registration is out of scope - Openpath command portal is only available in English |
| Park Indigo - Link Out | Park Indigo provides Property Manager / Building teams the ability to collect payment for parking. Customers would work directly with Park Indigo to set up their parking/garage, rates, and availability. | HqO delivers the product specifications HqO configures the integration in the HqO app | User can see parking availability User can pay for parking | - Park Indigo can provide a link out for the building specific location - Customer should have a PoC to reach out to for their account | -Customer needs an existing Park Indigo account or must reach out to Park Indigo to set up an account |
| Ping Identity (OIDC) - SSO | The System for Cross-domain Identity Management (SCIM) specification is designed to make managing user identities in cloud-based applications and services easier. We have invested in a SCIM service for multiple IdPs as it is a scaleable enterprise solution for user creation and deactivation and gives our customers control over the data sent to us. Leverages customers' existing identity provider (IdP). Ensures user lists are always accurate as updates made to the users’ profile through IdP will be pushed to the HqO application. Reaches the right employees. As corporates' employees change, individual users' access is automatically updated to ensure the right users have access and can engage with the app. Improves user experience. User does not need to enter their name or create a password when signing up via SSO. Users will be associated with the right company & building(s). | HqO delivers the product specifications HqO configures the integration in the HqO app | If SCIM integration is enabled, then SSO is required If SSO & SCIM integration is enabled, then users in the customer's IdP will be created in the HqO platform (First name, Last name, Email) HqO app or web app user is automatically assigned to the company and the building(s) configured If a new user is added to the customer's IdP, then the user will be created in the HqO platform, (First name, Last name, Email) HqO app or web user is automatically assigned to the company and the building(s) configured If a user created by via SCIM integration and the user signs up for the HqO app then, the app user will have the following sign up flow experience: Enter work email > Choose Provider > IdP's Auth page > Accept HqO app Terms & Conditions > Select Primary Building (if user is assigned to more than one building) > Enable push notifcations > Congratulations! page > App Home screen If a user's name is updated in the IdP then, the customer's IdP will push the user's updated information to the HqO platform (First name, Last name) If a user is deactivated in the customer's IdP then, the customer's IdP will push that information to the HqO platform and the user will be deactivated in the HqO platform App user will be logged out of the HqO app within an hour. User updates in the IdP are received by HqO platform in real time If a user is created via SCIM integration, then they are created in the HqO platform and can be viewed in HqO Admin > Communications > Users. HqO Admin Users page will list the users and their status (Active, Pending, Deactivated). "Active" users have signed up for the app and accepted T&Cs "Pending" users were created via SCIM integration but user has not completed sign up for the app and has not accepted T&Cs "Deactivated" users are no longer provisioned for the HqO app. | - Customer to share the email domains that will require SSO - Customer to confirm if they want SSO only or give their employees the option to sign up with email verification (current flow) - Customer creates a new application in Ping - Customer shares issuer link, application ID, and client secret | |
| Planon (SamFM) | Users can raise work orders through the HqO app and send information to the Planon (SamFM) app | HqO delivers the product specifications HqO configures the integration in the HqO app HqO permissions the integration to only be visible to users who are approved to view / use the integration | Users can raise a work order from predetermined fields Users can determine their floor/location Users can add a free text description Users can view the work order status in app Users can cancel work order | - Customer has set up an account & workflows customized with Planon (SamFM) - Customer has configuredPlanon (SamFM) based on HqO supported functionality - Customer intro's HqO to Planon (SamFM)) account team - Customer/Planon (SamFM) provides HqO with customer IDs necessary to configure the integration - Customer provides list of users to permissions of users who should have access to respective integrations | - Customer has an account with Planon (SamFM) - Admin experience remains in Planon (SamFM) - Customer is respecting HqO & Planon (SamFM) functionality |
| Property Evaluation | The process in which HqO is conducting an on premise tour "evaluating" the property, taking photos and collecting REX assessments | Going on site for two hours, completing the property questionaire, taking photos and collecting rex assessments REX Intelligence scores will then be generated | Setting up the property to be able to support the REX assessments | HqO needs two hours on site to collect REX assesements from tenants. One of the hours the customer also needs to give us a resrouce to provide a tour of their property while HqO takes photos and fills out questionaire | In order to complete REX assessments, tenant employees must be in the building |
| Public “Property” page | Publicly available property page that is published on HqO's domain | HqO to create and publish property page HqO to cross channel promote page for calendar year | |||
| REX Assessment | The HqO REX Assessment is the mechnism used to gather employee and tenant sentiment of the workspace. The Assessment is based on the Leesman methodology and has been optimized for both mobile and desktop devices. | HqO to create buildings and upload user assignments HqO to distribute Assesment links via direct-to-user email OR HqO to create static link for customers to distribute to their user base | Users can receive and submit REX Assessments for their company and building. | ||
| REX Intelligence | HqO's REX Intelligence is a industry's first tool to analyze and understand the sentiment of tenants' and employees' experience in the workspace. Using the Leesman methodogy, HqO calculates a REX Score for each building and company using the data collected through the REX Assessment, which can be used to compare performance against relevant benchmarks. | HqO to create and invite users with Intelligence role | Users can view REX Scores, broken down by location and/or company. Users can view performance for individual components or questions. | ||
| Ritual - API Integration | Available in US and Canada currently User can order food from on-site retail/vendors and the surrounding neighborhood | Users can view local food & retail options and address / location information Users can use a search bar to filter local food & retail options Users can view menus for food & retail options Users can order food through the app (pickup & delivery options available) Users can view order cart Users can edit cart Users can link personal & work account through phone number verification User can view wait time for food order to be completed / available Users can be provided credits / rewards to certain retailers Users can purchase/pay through the app - connects to Apple Wallet or credit card | Advanced Food and Beverage solution that support online ordering, order ahead and online payments | - Customer has onsite retail - Onsite retail is interested in setting up online orders - Alternative/popular food ordering solutions identified if Ritual has no presence in the region | - On-site vendors/retail interested in setting up Ritual - Ritual may or may not have a presence in the region |
| ServiceNow Service Requests | Requirements Gathering Defining Scope of Work Delivering and testing integration | ServiceNow integration with the Service Request module | - Customer to provide details on their use of ServiceNow to confirm HqO can support how the customer is using ServiceNow | - Development is required to support ServiceNow | |
| SoloInsight Inc. (Cloudgate) | Users can invite visitors through the HqO app and send information to the Cloudgate / Soloinsight app | HqO delivers the product specifications HqO configures the integration in the HqO app HqO permissions the integration to only be visible to users who are approved to view / use the integration | Users can invite user through the app Users can add a start & end date of visit Users can add a start & end time of visit Users can add floor & suite location of visit Users can add phone number of visitor Users can add "visit reason" Users can view visit status Users can edit visit Users can cancel visit Users can add VIP visitor (bypass) Users can add escort option Users can add alternative hosts Invitee provided an email with visit information Invitee provided a QR code to access the building | - Customer has set up an account & workflows customized with Cloudgate/Soloinsight - Customer has configured Cloudgate/Soloinsight based on HqO supported functionality - Customer intro's HqO to Cloudgate/Soloinsight account team - Customer/Cloudgate provides HqO with customer IDs - Customer provides list of users to permissions of users who should have access to respective integrations | - Customer has an account with Clodugate/Soloinsight - Admin experience remains in Cloudgate/Soloinsight - Customer is respecting HqO & Cloudgate functionality |
| STid | Users can access their respective buildings / amenities through the HqO app via their STid mobile credential | HqO delivers the product specifications HqO configures the integration in the HqO app HqO permissions the integration to only be visible to users who are approved to view / use the integration | User can request mobile credential through the app User can access authorized areas based on mobile credential via bluetooth | - Customer has mobile access / bluetooth readers enabled - Customer has an account set up with STid - Customer passes over STid portal information - Customer has Mobile Credentials available - Customer collects mobile access user emails prior to launch - Customer provides list of users to permissions of users who should have access to respective integrations | - Admin experience in STiD |
| Stripe Connect | Stripe is a global payment provider and allows easy credit card and iDeal payments | HqO delivers the product specifications HqO configures the integration in the HqO app HqO permissions the integration to only be visible to users who are approved to view / use the integration | Stripe allows HqO to supports global payments for resource booking and service booking in app Stripe Connect allows HqO to distribute funds to customer and partner financial / banking institutions | - Customer sets up Stripe account through HqO's Stripe Onboarding (cannot use previously created Stripe account) - Customer needs bank information | - Need to add banking information for payment to be transferred - Supports HqO Service Booking and HqO Resource Booking - Customer sets up Stripe account through HqO's Stripe Onboarding (cannot use previously created Stripe account) |
| Swiftconnect | SwiftConnects software platform enables for both tenants and visitors seamless flexible access by automating the provisioning of access credentials across different buildings and office spaces. SwiftConnect was founded in 2020 and based in Stamford, Connecticut. | HqO delivers the product specifications HqO configures the integration in the HqO app HqO permissions the integration to only be visible to users who are approved to view / use the integration | User can request mobile credential through the app User can access authorized areas based on mobile credential via NFC | - Customer has HID readers that have been approved by Apple(Signo e.g.) - Customer has configured Swiftconnect based on HqO supported functionality - Customer has configured HID based on HqO supported functionality - Customer provides list of users to permissions of users who should have access to respective integrations | - Customer has an account with Swiftconnect - Customer has HID Origo account set up - Customer has signed SwiftConnect and Apple agreements |
| TransitScreenGo | Allows users to view local transit information around the users building address | HqO delivers the product specifications HqO configures the integration in the HqO app | User can view local transit information (trains, buses, ubers/lyfts, bikes, etc) User can "favorite" their most commonly used transportation options User can view the weather in app | - Customer has local transit options available - HqO works with ActionFigure to customize view | - Local transit is available in the area - Geolocated to the building, not the users device |
| Valet Manager - Parking | Users can book a parking space via the app. | HqO delivers the product specifications HqO configures the integration in the HqO app HqO permissions the integration to only be visible to users who are approved to view / use the integration | Users can book a parking spot for the morning or afternoon or the entire day Users can't book a parking spot if the number of spots available has been fully booked for the requested time slot Users can see a list of their upcoming parking reservations | - Customer has set up an account & workflows customized with Valet Manager - Customer intro's HqO to Valet Manager account team - Valet Manager provides HqO with SSO link for HqO to integrate the SAML - Customer/Valet Manager provides HqO with a test account to test the integration - Customer provides list of users to permissions of users who should have access to respective integrations | - Valet Manager available in the area - Customer has an account with Valet Manager - Admin experience remains in Valet Manager |
| Who's In | A tool to support employees' decision on when they are going to the office by knowing when the people that matter to them are also going to the office | HqO delivers the product specifications HqO configures the integration in the HqO app HqO permissions the integration to only be visible to users who are approved to view / use the integration | Users can see which colleagues are coming to the office Users can search and add employees to their close colleagues and see their registrations Users can register to an office day Users can register on the same days as their colleagues Users can add a private registration Admins can view total registrations per day for the past and upcoming days/ weeks and quickly access a list of registered employees Admins can easily sort days by most and least total registrations to uncover trends Admins can filter data by desired timeframes, days of the week, and employee name Admins can export data as CSV file for the selected dates/filters |
Reading Time: 53 minutes