The CongressIQ Field App mobile experience is a fast, intuitive app experience for sponsor representatives and booth staff to capture and qualify interactions at congresses and trade shows.
As part of the CongressIQ solution, it is used alongside the premium-paid Universal lead capture module as well as the premium-paid Appointments modules.
It is a new and specially designed user interface that can be enabled on mobile app for sponsor representatives and booth staff.
Configuration steps to enable the CongressIQ Field App mobile experience on your event
1 - Enable the CongressIQ Field App mobile experience. This is available to SpotMe Support only.
- Enable the Field App dashboard and widgets.
- Enable the redesigned app menu (optional) to align with the Field App new look and feel.
2 - Configure the Universal lead capture module in Backstage.
Using the Field app mobile experience for capturing leads requires the exact same Backstage configuration steps that are explained in the How to use the Universal lead capture module, so make sure you continue to refer to the content in this article.
There are some additional Backstage configuration steps that will be needed that are exclusively available when using the Field App mobile experience, and that are explained in this article. In particular:
- Using pre and/or post capture pages (using the new capture page builder).
- Choosing whether the post-capture or qualification page can be skipped by reps or not.
- Enabling (if needed) the new Quick scanning.
- Allowing reps to review the automatic field mapping when optical scanning.
- Allowing reps to mark leads as out of scope during identity resolution.
- Adjusting any UI labels or translations if needed
Keep in mind that the Field App will by default always work when offline. Therefore when the Field App is enabled, the optional Offline mode setting is removed for the Universal lead capture module.
Please also note that, when using optical scanning in the Field App, the automatic AI-powered field mapping available in the Universal lead capture module is enabled by default, therefore this setting is also removed.
3 - Configure the Appointments module in Backstage.
Using the Field App mobile experience to manage meetings requires the exact same Backstage configuration steps that are explained in the How to use the Universal lead capture module, so make sure you continue to refer to the content in this article.
Enabling the CongressIQ Field App mobile experience
Available to SpotMe Support only. The steps are described here for reference only. Please contact your Account Manager to enable this.
The CongressIQ Field App mobile experience needs to be enabled via the Workspace settings > Admin and Support > CongressIQ Field App mobile experience by the SpotMe Support team:
Enabling the CongressIQ Field App mobile experience will enable a dedicated user interface that is only visible to app users that are selected as Sponsor representatives in the workspace in Backstage.
Here the support team can choose what to enable:
- Enable the CongressIQ Field App mobile.
- Enable the Field App dashboard.
- Choose the widgets that will be displayed in the dashboard (leads, meetings, sessions, booth).
- Choose to add a widget that links to the configured Home screen.
- Choose whether or not to use a newly “redesigned app menu”.
Field App dashboard overview
When enabled, the CongressIQ Field App mobile experience can begin by displaying an optional and fully configurable Field App dashboard:
The Field App dashboard, when enabled, will replace the “standard” configured mobile app home screen, with a specially designed dashboard that will only be visible to sponsor representatives.
The configured home screen remains visible to all “non representative” app users per usual. Representatives can access the Field App functionalities via the dashboard or via the configured app menu. The configured app navigation bar remains visible.
Note: When the dashboard is enabled, a “Home link” widget can be added to allow representatives to visit the configured home field at any time.
When the dashboard is disabled, representatives will see the same configured home screen as the standard attendee app users. They can access functionalities via the configured home screen and app menu. The configured app navigation bar remains visible.
When the dashboard is enabled, Support can select the widgets you want to make visible to representatives:
- Leads widget: works hand in hand with Universal lead capture module
- Meetings widget: works hand in hand with the Appointments module
- Sessions widget: works hand in hand with the Agenda module
- Booth widget: works with sensors installed in the booth. Currently not available
- Home link: adds a button located at the bottom of the dashboard to allow representatives to easily access the configured home screen
You can see below how each of these widgets look when enabled in the dashboard in the Field App:
|
Leads widget
|
Meetings widget
|
Booth widget
|
Home link visible at bottom of screen:
Full lead capture flow
See below the steps that can typically make up a complete lead capture using the Field App.
Note: It is worth noting many of the steps are optional, as they are included depending on the lead capture configuration. Also, a "quick scan" mode can also be enabled at the sponsor level, which will remove some of the below steps.
Step 1: Dashboard |
Step 2: Pre-capture page |
Step 3: Capture |
Step 4: Interaction saved |
Step 5: Identity matching |
Step 6: Post-capture page |
Step 7: Qualification page |
Lead list w/ fully qualified lead |
Lead list w/ incomplete lead |
Configuration steps in the Universal lead capture module
In addition to the Backstage configuration steps described in the How to use the Universal lead capture module, Backstage users can also perform the following actions:
- Choose whether or not to use pre and post capture pages.
- Build or adjust default or custom pre and post-capture pages.
- Select the pre and post capture pages for the sponsors.
- Enable (if needed) lead capture page skipping.
- Enable (if needed) Quick scanning.
- Enable (if needed) ability for reps to perform field mapping review step for optical scanning.
- Enable (if needed) ability for reps to mark captured leads as "out of scope" during identity resolution.
What are pre-capture, post-capture, and lead qualification pages?
Pre and post capture pages are optional steps that can be added to the lead capture process.
Backstage users can choose to enable a pre-capture page, a post-capture page, both together, or none at all.
Default pre and post-capture pages can be used for all sponsors, or custom pages can be created and selected for each individual sponsor.
When enabled, the pre and post-capture steps will take place respectively before and after capturing a lead, and always before qualifying the lead. To see where exactly the pre and post capture steps take place in the flow, please refer to the Full lead capture flow.
To complete the pre and post-capture pages, the representative can if needed hand the device to the lead in order for them to complete them, included (if needed) providing a signature:
|
Pre-capture page example |
|
- The pre-capture page can be used before capturing and before identity matching.
- The post-capture page can be used after capturing and after identity matching, but before lead qualification.
Note: The post-capture page and the lead qualification steps can be configured in a way that reps can skip the step if needed. The pre-capture step however cannot be skipped if it is configured as part of the capture flow. Pre and post-capture pages can also be included in the capture flow when Quick scanning is enabled.
The lead qualification page is the page that will be used to truly capture the lead's information. It will include all the questions that the sponsor representative wants to ask of the lead:
Lead qualification page example
Managing the default and custom lead capture pages via the settings
Workspaces contain default pre and post, and qualification capture pages. These default pages are managed via the Lead capture > Settings section in Backstage:
Here, users can select the default pages for the lead pre-capture, post-capture, or the qualification pages.
These pages can also be edited here by clicking on Edit. Or new custom pages can be created by clicking on Create.
Selecting the default or custom pages at the sponsor level
The capture pages that are managed at the Lead capture > Settings level can then be selected at the sponsor level.
For each individual sponsor you can choose what specific pages to use:
Here, users can use the drop downs as follows for the Lead pre-capturing page, the Lead post-capturing page, and the Lead qualification page:
- Dropdown is left blank: Uses the default page configured in the Lead capture > Settings.
- A page is selected: Uses the specifically selected page (default page or a custom created page).
- Do not use: This means that no page will be used, and therefore for the selected page there will be no step added to the capture flow (pre-capturing, or post-capturing, or lead qualification).
How to create or edit the pre/post-capture, or lead qualification pages
Editing the capture page title and subtitle
Backstage users can use the Create or Edit buttons in the Sponsor page or the Lead capture > Settings page, in order to edit a selected page or create a new one.
Creating a new page will open the below window where the user can enter the name, title and subtitle for the page:
- Name: Name of the page seen only in Backstage, in the page selector dropdown menus.
- Displayed title: Main title visible on the actual page in the app.
- Displayed subtitle: Subtitle visible on the actual page in the app.
To note, the Subtitle field is optional, and is especially not needed when creating or editing lead qualification pages, as the page displays the name of the lead instead, below the title (see below to the right):
Pre-capture page |
Post capture page |
Lead qualification page title only (lead name as subtitle): |
Adding or editing the fields in the capture pages
To edit or create the page itself, Backstage users will use the page editor. At the top the editor the user can see and edit the current page's title and subtitle.
To facilitate configuration, the page editor is split into three panels:
- On the left are the functional components (or field types) that can be dropped into the center panel to be configured.
- On the right is where the fields are configured and content is added
- In the center is where the page is built according to the fields added and how they are configured.
Note: Each component or field in the page that requires a response can be made required, or not.
Each component or field that asks for a response also has a value key field that is used to assign a lead profile metadata field name that will be linked to this input. The field will display the attendee's stored value and save any changes they make back to their profile (e.g. position, company).
The available components that can be used in the page are as follows:
Header
Add a header to the page with a title and a subtitle. This is only visual and is not used to collect any input:
Paragraph
Add a paragraph to the page and use the formatting options, including links to external content that will open on the device browser, or internal content in that app. This is only visual and is not used to collect any input:
Text input
Add a text input field, to collect an open text response. This includes a label name for the component, a description, a default value that will appear until a response is provided, a placeholder text that will be added to the page result if no answer is provided.
A dictate option can also be enabled to allow users to dictate their response instead of typing it.
Radio button
Add a radio button field, to allow users to select one response. This includes a label name for the field, a description, as well as the different options to choose from using the radio buttons.
Users can also include a “Other” option to be selected, if needed, that can allow users to then enter a free text response.
Check box
Add a check box field, to allow users to select one or more responses. This includes a label name for the field, a description, as well as the different options to choose from using the check boxes.
Users can also include a “Other” option to be selected, if needed, that can allow users to then enter a free text response.
Dropdown
Add a dropdown field, to allow users to select a single response. This includes a label name for the field, a description, as well as the different options to choose from using the dropdown.
Users can also include a “Other” option to be selected, if needed, that can allow users to then enter a free text response.
Signature
Add a signature component to collect a lead’s signature. This includes a label name for the field and a description.
Consent
Add a consent field, to allow users to provide their consent.
This includes a label name for the field, a description, as well as the different options that users can select from using checkboxes.
Options here can be made mandatory, meaning that a user must select them in order to proceed.
Allowing the reps to skip pages during the lead capture flow
A Allow skipping this step during capture option is available to allow representatives to skip the post capturing page and/or the lead qualification page when needed. Skipping is never available for the pre capture page:
Important: If a pre-capture page is configured for the lead capture process, it is always mandatory and cannot be skipped by the representative
If skipping is enabled, a Skip button will be available for reps to select at the top of the post-capture or lead qualification page in the app, therefore making the step optional:
Example of post-capture page
with Skip button enabled
If skipping is disabled, any of these steps, once configured, will be mandatory (non-skippable) steps in the lead capture process. The Skip button will not be available.
How to use Quick scanning
Quick scanning is a lead capture mode that is tailored for reps that need to capture leads at a fast pace, without stopping to qualify each one. It can be used with all lead capture methods (optical scan, QR code/barcode scanning, and manual entry).
With Quick scanning enabled, the device capture method (device camera or manual entry screen) stays active so the rep can continuously scan badges or enter lead details, in rapid succession, one badge after another.
Identity resolution runs in the background and incomplete matches can be addressed at a later time, after the rush:
|
Step 1: User scans badge (or performs manual entry) |
Step 2: Capture takes place (approx. 2 seconds) |
Pre and post-capture pages can be included in the Quick scan flow (if configured), but everything else is skipped:
|
Step 1: Pre capture (if configured) |
Step 2: User scans badge (or manual entry) |
Step 3: Capture takes place |
Step 4: Post capture (if configured) |
Quick scanning can be enabled in Backstage, on a per sponsor basis, via the Lead capturing > Quick scan toggle:
Once Quick scanning is enabled for a sponsor, it is applied to all the representatives for that sponsor.
Please note that representatives will be able to use only the Quick scan method once it is enabled.
The Quick scan toggle will need to be disabled at the sponsor level in order to give the representatives for that sponsor the standard lead capture approach.
Allow reps to review the automatic field mapping when optical scanning
Keep in mind that, when using optical scanning in the Field App, the automatic AI-powered field mapping available in the Universal lead capture module is enabled by default. The setting is therefore removed from the Universal lead capture module.
When capturing leads using optical scanning, there is a setting in Backstage that can be enabled in order to allow reps to be able to check and if needed edit the automatic field mapping that is performed when capturing the contents of a badge.
|
Step 1: Optical scan |
Step 2: Interaction saved |
Step 3: Mapped fields shown |
|
|
Step 4: Edit and view missing fields |
Step 5: Rep completes missing fields |
If you are using identity resolution the identity resolution step will take place as soon as the optical scan is performed, before the rep has reviewed/confirmed that the mapping is accurate.
If the rep makes changes to the mapping that impact the identity resolution stage, then the new results are added to the previously generated results so the rep can choose the correct match.
To enable the review of mapping results as part of the optical scanning capture flow, Backstage users need to enable the Show mapping results via the Lead capture > Settings:
Allow reps to mark leads as "out of scope" during identity resolution
As part of the identity resolution process, in addition to selecting the right match for the lead based on returned results, or selecting "No match" if none of the matches are correct, you can also allow reps to mark a captured lead as "out of scope", so that the captured lead does not get resolved.
This is a quick and efficient way to allow representatives to keep their lists of captured leads relevant on the spot, and to ensure that future look-ups are efficient and do not return out of scope results.
When marking a lead as "out of scope", the representative must choose between three available reasons to clarify why the captured lead was out of scope:
- Not a HCP.
- Outside geographical area.
- Industry.
These options currently cannot be edited.
Making a captured lead as "out of scope" can be performed during the identity resolution, or from the captured leads list:
|
Rep selects "Out of scope" during resolution |
Rep selects "Out of scope" |
Rep adds why lead is |
To enable this functionality in Backstage, go to the Lead capture > Settings > Complete profile with custom integration section:
Here you can enable the Allow flagging lead as out of scope toggle.
Accessing and editing the Field App dashboard translation keys
The translation keys for the Field App and in particular the dashboard are all available In the Translation editor in the workspace.
In the search bar, type representatives.dashboard.general. This will display all the translations that pertain to the Field App, where you can adjust the English label and add translations if needed:
Below are some examples of the main translation keys that can be accessed and edited:
Text located in the header at the top of the dashboard:
Day {0} of {1}
This is when the event is live, located above the greeting message.
representatives.dashboard.general.day_of_total_days
Hey, {0}
This is the greeting message.
representatives.dashboard.general.greeting
Event status:
This is the current event status.
representatives.dashboard.general.upcoming
representatives.dashboard.general.live
representatives.dashboard.general.past
Date {0} to {1}
This is for event start and end dates.
representatives.dashboard.general.start_to_end
Lead statuses:
leads.status.complete
leads.more_details_needed
reads.status.retrieving
Last refresh date and time:
At bottom of dashboard after scrolling down:
“Last refresh”:
sync.last_update
“at”:
representatives.dashboard.general.date_at
Enabling the redesigned app menu
As part of the settings that can be enabled by SpotMe Support when activating the Field App mobile experience, a redesigned app menu can be enabled.
This is strictly a design change that is applied to the configured app menu, so that it aligns with the look and feel of the Field App.
For reference, please see below the comparison between the app menu with and without enabling the redesigned app menu:
|
Without redesigned app menu |
With redesigned app menu |
Recommendations for users testing the app
When performing all the configuration steps, Backstage users will need to access the app in order to test that everything is working as it should.
To do so, they will need to:
- Access the app as a “standard” app user, to experience the app the way a standard event attendee would, to verify that everything is working for the main audience.
- Access the app as an app user that is selected as a sponsor representative, so they can experience the Field App on mobile, and check that everything is working as it should there.
Comments
0 comments
Please sign in to leave a comment.