Consultant Guide to Verity

Consultant Guide to Verity

Everything AMs/Consultants need to know to scope and deliver Verity projects

CONTENTS

• Section 1: Introduction to Verity
• Section 2: What to consider when scoping
• Section 3: What to consider in development phase
• Section 4: What to consider right before and during deployment
• Section 5: Additional resources

Section 1: Introduction to Verity

Why Verity:

Verity transforms how we approach role plays by removing the limitations of traditional live practice. In the past, sessions required significant preparation. We had to train coaches ahead of session launches, dedicate extra development time creating materials for both roles within a role play, and ensure the client could get enough coaches to be onsite to support scoring and participation. 

With Verity, participants can engage in role plays as many times as they want, receive consistent scoring across participants, and scale practice across larger groups with fewer resources involved. This makes the experience not only more efficient and accessible, but also more modern and impactful as learners can focus on improving their skills without the barriers of time, availability, or inconsistency.

AI is here to stay, and our clients are increasingly asking how it can be part of their learning experiences. Verity offers a powerful way to integrate AI into programs in a way that feels practical, scalable, and impactful. If you’re exploring how to bring Verity into your next proposal, use this guide as a roadmap to understand the key considerations at each step.

Ways clients want to use verity

Verity can be used in a text-to-text or a voice-to-voice format. Depending on your client need, and session logistics, one option might make more sense than another. See below for common examples of how a client might want to use the platform.  

1. Single event use: Use only during live session. This is only really used when the bots are embedded into a simulation and the content is very specific to the SIM which makes it difficult to use outside of this context. Project examples:
   1. Thermo Fisher Power of Connections 2024 (NAM)
   2. Coca-Cola Freestyle Experience 2025 (NAM)
   3. JLL 2025 (EUR/ NAM)
2. Continued practice after events: Usually first experienced at live session then individual continued use afterwards. It is strongly recommended that you use the product like this as it allows the client to measure the impact of the training and for us to prove the value of our work. Project examples:
   1. Kaiser Permanente 2025 (AMER) 
   2. BJs 2025 (AMER)
   3. Mediatek (MOW)
3. Self-paced: Users complete a training journey online whereby they learn a concept and then immediately put new skills into practice in a roleplay with a bot. This is often integrated with Momenta. Project examples:

1. BMS 2025 (AMER)
2. Mubadala 2025 (EUR)
3. Boston Scientific 2025 (AMER)

4. Self service: Customers have the option to build and deploy their own bots using our self-service SaaS product. This is much more affordable if they plan to build >5 bots and is great for building closer relationships with customers. It’s still early but we are optimistic that this we can sign multi-year contracts here as the product gets more valuable the more bots they build and data they collect. They also get access to our library of standard bots included in their license. Project examples:
   1. Philip Morris International (EUR)
   2. Parker (EUR)

*Note: A full list of all client projects can be found here

What clients want to see from the platform

1. Single event use: Incorporated into a program where participants can practice (in teams or individually) and debrief as a group to further drive learning. Allows the opportunity for those who did well to share their strategy or for facilitators and leaders to chime in and draw out key learning points tied to the session objectives. This option allows facilitators to see how well people understood the training and the common misunderstandings across the group in real-time.
2. Continued practice after events: The first role play would happen during a live event (in teams or individually) and usage would continue at an individual level afterwards as part of a go-do. Participants can continue to practice with the bot(s), allowing managers to check in on how scores improve overtime. This allows clients to measure the impact of their training. Sellers can practice with voice-to-voice or text-to-text format, helping them gain confidence in their ability show up for their clients.  
3. Self-paced usage: These bots are typically used to practice content that people have learned on Momenta or their LMS, so they can immediately put new skills into practice. Clients want to see how often the bot(s) were used, what the average scores were across participants, areas for improvement, and improvements over time.
4. Self service:  Clients are looking for an affordable way to scale up bot usage across the organization. They get access to our standard bots, and over time they build their own bots which are tailored to their organizational needs. Over time, this collection becomes a reusable asset that grows with the organization providing a way for people to practice all of the most difficult conversations that employees face (think of a library of bots, each tailored to a different need or different team within a single organization). The product becomes more valuable as they build more bots and collect data around performance and usage, making it difficult to remove or replace (similar to an LMS). Bots can also be integrated into customers LMS upon request.

Section 2: What to consider when scoping

When incorporating Verity into a proposal, it’s important to have a solid grasp of the key areas outlined below. 

Clearly identify what the client is hoping to achieve from the AI role plays and ensure those needs align with what Verity can deliver. Consider:

• Type of role play(s) they want to create
• Scale of audience
• Do they want ongoing practice (individuals of the org will need access to Verity)
• Data: Below are some examples of data points a client might want to see. Please check what is most important for them:
  1. Performance scores: Tracking how participants perform across role plays, with consistency in scoring criteria.
  2. Progress over time: Showing individual or group improvement across multiple practice sessions.
  3. Usage insights: Number of attempts, time spent practicing, and which scenarios are most used.
  4. Comparisons and benchmarks: Highlighting differences across teams/ individuals, regions, or roles to identify strengths and development areas.
  5. Understanding gaps: Identifying areas for improvement across the entire org, team and individual level

If you’re not sure about Verity’s capabilities, reach out to Bowen (Head of Verity team) to check what’s possible. This helps avoid overpromising and ensures the client sees the direct value Verity brings to their program.

1. Demos

• You can find all material related to demos here.
• This list of people have been trained to run demos across our regions. They can demo the bot conversation, reporting, self service and can answer any basic FAQs and security questions. Please find someone locally for standard demos and first intro calls.
• Bowen can also join for demos for large deals, late stage or complicated deals where more detailed questions are expected.

1. Follow-up material

• All follow-up material including pitch decks, links to our standard bots, screenshots of our reporting and security FAQs can be found here.

1. Proposals

• You can find examples of successful proposals here. 

1. Pricing & budget

Depending on the client’s need, cost will vary. You can find the pricing sheet here. There will be an internal charge against the project according to these prices. However, consultants have authority to offer a discount to clients if needed. In some cases, consultants have offered the bots for free to get them excited to upsell a bigger deal later.

It’s key that you are clear with both the client and the Verity development team on the timeline. Timeline should account for:

1. Consulting development work to define the moment and fill in briefing form for Verity team
2. Bot/ scorecard development and review with the client
3. Build of bot(s)
4. Internal team testing AND large-scale testing when needed
5. Client testing before session launches

The verity team typically needs 2 weeks for steps 2 and 3. Please allow extra time for the other steps as needed.

Because Verity uses AI, it’s likely that it will need to be reviewed by customers AI council and we will need to complete a security questionnaire. To avoid delays to your project, it is strongly recommended that you start the security review in parallel to the contracting. Below are some documents you can share to get the process started. Clients also typically want us to fill out a security questionnaire in their format, please send them to Bowen and he will fill them out within a few days. So far, we have never lost a project due to data security or compliance. It can be time consuming but it has always worked out.

• One pager FAQs you can share with your buyer
• 3-pager you can send to the clients IT team
• All detailed resources available in our legal box folder

1. Data privacy and employee unions

Some clients may be concerned that the data and reporting will be used by companies to inform hiring, firing or promotion decisions. So far, this has only come up in <5% of projects but seems to be more a more common concern under the EU AI Act and among companies with strong employee unions. As standard, we always make it clear to employees that these role plays are only for training purposes and will never be used for hiring, firing or promotion decisions. In addition, we can take the following steps we can take to reduce the risk to employees. You can choose to implement one or all of them:

1. We can turn off the scoring so that employees only receive feedback on each item but do not get an overall score (out of 100).
2. Use password protected links which employees use to access the tool without logging in. This makes it impossible to tie the results back to individual users.
3. We can only show aggregate reporting for groups >10 so no results can be tied back to individual users.

Please note that by implementing these options you will lose some reporting functionality. However, even if you decide to implement all of the above you will still be able to get aggregate an aggregate report for groups >10 which will allow you to understand how well people have understood the training and if there were any topics which you would need to revisit.

Because Verity leverages AI and requires system access, some clients may have additional contracting requirements. This could include creating a separate SOW specific to the platform or requesting that the Verity email address be whitelisted by their IT security teams. These steps can take extra time to process, so it’s important to flag them early in scoping. Getting ahead of contracting needs ensures we avoid last-minute delays in the days leading up to a session launch and keeps the program timeline on track

• LOA template
• Examples of successful SOWs here

Section 3: What to consider in development phase

Once the SOW has been signed, the focus shifts to development. This stage is focused around co-creation with the client so we can ensure Verity is set up for success and ready for a seamless client experience. Key areas to pay attention to include:

1. Process for building bots and resourcing 

   1. Let Bowen know that the project has been signed so we can start planning resources
   2. Complete this New Verity Project Request Form outlining the scope of the project and share it with Bowen. You need to do this for every project no matter what (see note below).
   3. Verity team will setup the client account and configure it with the right features you need for the project 
   4. Verity team will work with PRO team to allocate internally to support the project and allocate a bot builder. This might be someone from Verity (i.e. Richard Lombos) or one of the bot builders that have been trained in the local offices. See full list of bot builders here.
   5. A project slack channel is created where we can keep track of all communication related to the project

Please note: It’s critical that you let the Verity team know about the project so that we can correctly setup and configure the account. DO NOT USE:

• Internal BTS accounts for client projects (e.g. demo account): The account is setup for demos and a lot of the reports are static and won’t work for projects. It’s not setup to scale for large events and it’s illegal to mix and match different client data in the same account.
• Existing client accounts without checking with us first: If we have already done a project for a client in the past, we may be able to reuse it. However, please check with us first and we routinely delete old client accounts and you could lose the data half-way through or your event may be disrupted. 

1. Timeline

Make sure timelines are clearly communicated between the Verity team and the client. Build in buffer time for development, internal reviews, and client approvals to avoid last-minute crunches. Please see timeline in scoping section above.

Collaborate closely with the client to co-create the scorecard and bot personalities. This ensures the role play scenarios feel authentic, relevant, and aligned to the client’s learning objectives while maintaining Verity’s consistency in scoring.

Allocate sufficient time for thorough testing, both internally and with client stakeholders. Testing should cover technical functionality, scoring accuracy, and the overall participant experience. We typically go through 2-5 interactions of feedback and testing with the client before its perfect.

Establish regular check-ins with both the client and the Verity team. Transparent communication helps flag risks early and ensures both sides stay aligned as the program moves toward launch.

There are 3 steps to change languages in Verity:

• Change bot language: The bots speak 52 languages. You can quickly toggle between languages in the bot builder. See video below to see how.
• Change scorecard language: If the scorecards were written in english (all standard bots are), you will need to change the language. See video below to see how.
• Change product interface: We can also change the language of the product interface (buttons etc.) on the user side only. We cannot change the interface language for admins. To do so, please reach out to the Verity team. Please note: we can currently only have one language per account so any changes that are made will be seen by everyone in the account. 

Watch this video to see how to change the bot and scorecard language as an admin using the the self-service (4 mins): https://www.loom.com/share/65b8085093ec41c19329e756b1728bcc  

There are a few different ways that participants can access Verity. Please allow 1 additional week in your timeline if you plan to use SSO or integrations with internal platforms. Integration with external platforms will take longer and needs to be agreed with the Verity team.

1. Integrating with internal tools
   • Verity bots can be integrated into Momenta, Pulse, ISOMER, Ibider via an iFrame. Once the bots are integrated, participants will be able to role play with them directly within the system (i.e. Momenta) rather than having to switch between tools to do the role play in Verity.
   • However, only the participants experience is integrated. Administrators will still need to login into Verity to see the aggregate data and reporting. So far this has not been an issue as only a few people have needed the admin access.
   • If you would like to setup an integration, please let the Verity team know in advance so we can plan this head of time.
   • Integrating with external tools
   • LMS and CRM integrations are available upon request for $10-15k. We recommend only doing this for large projects.

See this guide with the details on how to setup SSO. Feel free to share with your clients IT team: https://wonderway.notion.site/OIDC-Setup-Guide-2654549f0bcb80c9be62f7b41cf4c34a?source=copy_link     

We have three different user roles with different levels of access in Verity. We can setup the reporting lines when we add the users to the system either manually or via a bulk upload.  The roles can be changed anytime in the users section of the product. The different roles are:

1. Learners/Members:  Can only see their own reports and data and the bots they have been assigned to
2. Team leads:  Can only see data and reports for people in their team, can assign bots to their team members
3. Admins: Can see all reports and data, can assign bots to people, can build bots (if using self-service

1. Technical checks

Please check through these ahead of time so everything runs smoothly on launch day:

• Using Verity at events
• Minimum device & network requirements
• Domains to whitelist 
• Trouble shooting – what to check if the bots can’t hear you speak

Section 4: What to consider right before and during deployment:

The final stretch is all about ensuring everything runs smoothly during the live session. Preparation and support in these moments are critical to delivering a seamless participant experience. Key considerations include:

Run a full test on the day of the session to confirm that all links, logins, and bots are functioning as expected. This helps catch last-minute issues before participants log in. Please double run through the technical checks listed above.

Verify that the Wi-Fi at the session location is stable and strong enough to support all participants. Also, double-check devices and browsers are compatible and ready to go. It is strongly recommended to use Google Chrome browser. 

Align with the Verity team to have a support contact available and online during deployment. Their presence provides an added layer of assurance in case troubleshooting is needed quickly. Suggested to send calendar invites to your Verity contact for exact time Verity is expected to run. 

During the session, keep an eye on participant progress and surface-level issues and report these back to your Verity contact. Having facilitators or leaders ready to step in if questions arise helps keep the session flowing without interruptions.

Section 5: Additional resources

All resources for Verity can be found in this folder. 

Public links to our standard bots which you can share with clients can be found here.

Good luck on your next bot project, we’re looking forward to working with you and supporting along the way! If you have any questions, please don’t hesitate to reach out to any bot expert in your region.