Welcome to the Loopio Dictionary! The language of Loopio falls into 5 core areas: the Loopio platform, Library organization, the Projects workspace, content Reviews, and Admin functions.
Tips for using the Loopio Dictionary:
- Dictionary terms in purple link to another page with more information. Links will open in a new tab so you don't lose your place.
- Looking for a specific term on this page? Use CTRL-F or ⌘-F to search for what you need!
Click on an option below to learn more about each.
A cloud-based sales response platform for RFPs, Security Questionnaires, Proposals and DDQs. Loopio was founded in Toronto, Canada in 2014 and serves over 1000 customers worldwide.
A comprehensive guide to platform functions with step-by-step how-to articles. Be sure to bookmark support.loopio.com for on-demand access.
An annual customer conference for response professionals. Attendees can grow their skills, attend roundtables, and connect with other experts in the community.
An initiative by the Engineering, Product, and Design teams at Loopio to connect directly with platform users for feedback on feature development and updates. Users can opt-in under their Account Details.
A dedicated team of platform experts available to Loopio users. Our Support Team can be contacted by email (firstname.lastname@example.org), by phone (+1 844-456-6746, ext. 1), or within the platform under the Help menu.
A Slack-hosted community for professionals who respond to complex sales and marketing documents. Members around the world connect to offer insights, ask platform questions, and share best practices.
A one-stop hub for Loopio mastery. Loopio users can take interactive e-learning modules, get Loopio Certified, and view an assortment of best practice resources.
The central knowledge and content repository of Loopio. A Library is a collection of a business’ current winning descriptions and responses that can be used as a ‘single source of truth’. To avoid creating a messy and enlarged content repository, avoid having duplicate entries.
A visible message to provide your team with additional context about how a Library Entry should be used, or any steps required before using it. Alerts are limited to 250 characters.
Variations of a Question, such as synonyms, phrasing, or industry terms. Adding Alternate Questions to Entries helps aid the search process, giving more keywords to match with.
The body of a Library Entry that typically responds to a specific Question, but can also represent collected information. Answers can contain text, links, tables, images, and attachments.
Files that are associated with a specific Answer. Examples include PDFs, Images, and PowerPoint decks. When an Answer is used in a Project, the Attachment will be included with the export in a .zip file.
The next level down of content categorization in Loopio. If Stacks are the rooms in a Library, think of Categories as the filing cabinets within your rooms, further dividing up the content by topic. In your Company Information Stack, some example Categories might include Overview, HR, and Legal.
Library reference notes, added to specific Entries, to provide context or source details. Comments are internal-facing only, and do not appear when an Answer is used in a Project.
Short-form binary answers, typically used for Questions beginning with “Do you/Can you/Have you ___?”. The default options are Yes, No, and N/A; additional options can be added under Site Settings.
The individual building blocks of a Library, also known as Q&A Pairs, Content, Answers, Records, Responses. Library Entries populate your Stacks, Categories, and Subcategories.
Every variation that an Entry has gone through from its initial date of creation. The Entry History tracks when Alternate Questions are added, the location is changed, and Answers are updated.
A visual indicator of an Entry’s trustworthiness based on how recently it has been Reviewed. When an Entry is created and/or Reviewed, the score is 100%. As an Entry sits in the Library without Review, its score drops as time passes.
The language of an Entry. Current options include English, Danish, Dutch, Finnish, French, German, Hungarian, Italian, Norwegian, Portuguese, Russian, and Spanish. **Subscription-based
A dynamic text placeholder for values that change over time. Library Merge Variables typically come in the form of a metric (e.g. number of customers) or piece of information (e.g. customer service hours, list of 3rd party vendors) and can be embedded in multiple Library Entries.
This creates a one-to-one link between two Library Entries. Examples include linking English to French library entries, or short vs long versions of an Entry. **Subscription-based
The initial prompt/header/keywords/search terms for an Entry. Questions can be an Entry title or a full question, identifying the content of the Answer to follow.
The highest level of content categorization in Loopio. Examples include Company Information, Sales Content, Information Security. Stacks are, metaphorically, the individual rooms within a Library, each holding specific areas of content. Content Access is controlled at the Stack level via User/Role Permissions. **Subscription-based
The lowest level of content categorization in Loopio. Think of Subcategories as the dedicated folders within the filing cabinets. Subcategories are highly specific in topic and are an optional tier in your Library. In your HR Category, some example Subcategories might include Hiring, Staffing, and Background Checks.
Used as metafilters added to Library Entries that can cross the Library structure to differentiate between Answer variations. Examples include Product-specific or Region-specific Tags.
Stand-alone workspaces used to build individual client-facing documents. Project content can be populated by Magic, found directly within the Library, or be supplied by a company’s Subject Matter Experts on-demand.
A limited-access role, Assignees can view and answer all Questions assigned directly to them, or any in Sections with Open Collaboration enabled. Assignees can communicate with other Project Participants using Comments.
Collaborators hold mid-level Project permissions. Once invited to a Project, they have a read-only view of all Questions and can leave Comments on any of them.
Comments on Project Entries enable direct communication between Project Participants. Be sure to @mention your intended recipient to direct both a message and notification their way.
Extracting the completed Project into a downloadable file. Available formats are Word, Excel, and HTML. If a Source Document is used, then the Project Export can use its format for structure.
Completed Projects can be extracted into a Word document company branding format using Export Themes. Export Themes can be configured by Administrators.
The process of bringing a Source Document and its Sections, Subsections, and Questions into a Project.
Loopio’s “first pass” question-answering automation, which populates any unassigned, unanswered Project Entries with content from your Library.
When multiple respondents are needed for a group of Questions, instead of direct assignments the Admin can turn on Open Collaboration for specific Sections in a Project. This allows any Project Participants to provide an answer to any Question in that Section.
Project Administrators can share the tasks and permissions of a Project Owner, performing high-level tasks such as Importing Questions, running Magic, selecting Question Assignees.
A Question/Answer pair within a Project. Project Entries are nested within Sections and (optionally) Subsections. Project Entries can have multiple response fields, such as Answer Sets as well as multiple free-text Answer fields for compound Questions.
A dynamic placeholder of text that will change per Project (e.g. Client Name). Project Merge Variables can be added to Loopio by Administrators.
Individual tasks required for a Project’s completion. Milestones can be added within the Project’s Timeline, and even beyond the Due Date. Milestones can also be assigned to specific owners, with the option for reminder notifications.
The table of contents for a Project, built from its Sections and Subsections. Found on the left side panel of a Project, a Project Outline can come directly from a Source Document, or be created ad-hoc by the Project Owner.
When launched, a Project has an Owner that is responsible for overseeing its progress from start to completion. Project Ownership can be changed, but only one user can be the Owner at a time.
A Loopio User who has been added to a specific Project to complete Project work. This can include: answering and reviewing Project Entries, importing content from RFP documents, exporting completed Project documents, and managing other Project Participants.
Used for tracking/reporting purposes. Once created, a Project is in an Active state. Projects can be Stopped if they need to be archived while incomplete, Complete when finished, and Won or Lost when the outcome is determined.
Reusable Project Outline formats, such as Proactive Proposal or Statement of Work templates. Project Templates can be created by Administrators and used to launch Projects.
The total time allowed for completion, as outlined by the Start and Due Dates. Days remaining are visible and total time for Completion can be reported once the Project is Complete. Found next to the Project Outline in the side panel.
A Reviewer can make further revisions to the answer, or communicate additional instructions via Comments to the Assignee or any other Project Participants. All answers provided by Assignees then pass through to the designated Reviewer.
Loopio’s practice for keeping your Library up-to-date and complete. At the end of a Project, all new or updated Project Entries are isolated and can be populated back into your Library. This ensures the accuracy of Entries and the continued growth of the Library as a whole.
High-level content groupings for Project Entries by topic, as identified by the Source Document or response instructions. Sections can be used to assign Questions in bulk or to run Magic results for individual Sections at a time for greater accuracy of results.
A Word, Excel, or PDF-based document issued by a client/prospect that you can Import to a Project, either as a reference or to import its Questions.
Mid-level content groupings, sitting within Sections. Subsections can also be used for bulk Question assignments, and for grouping multi-part questions along with their instructions.
Proactive content checks for Library Entry accuracy and validation. Reviews keep the Freshness Score high, as well as user confidence in the Library itself.
The owner of a Review Cycle, or the first Reviewer in a sequence. **Subscription-based
Proactive, recurring, assigned, and scheduled content reviews. A Review Cycle can be set for custom intervals on Categories, Subcategories, or on individual Library Entries.
The recipient and assignee for specific content Reviews.
The intervals in which the Review Cycle will trigger.
When a Project is complete, its responses can be used to: update Library Entries that were used and modified; add Alternate Questions to existing Entries and; add new Entries to the Library for future use. Reviews from Projects are essential in maintaining a healthy Library and improving Magic hit rates.
One-off Reviews on individual Library Entries, assigned to a specific Reviewer.
Review Start Date
The first occurrence of a Review Cycle, and the calendar date for future Review Cycles.
Time to Complete
The time allotted to the Reviewer before the Review becomes overdue.
Administrators have access to the Admin page and its site settings/user management options. Changes made here are reflected across all user accounts.
Loopio can generate text-only extracts of a Library’s content for download and storage offline. Once the Backups function is activated, the password-protected extracts are produced monthly, or can be generated on an ad-hoc basis.
The look and feel of content in the Library and in some Exports. Content Style settings allow for customization of Library Entries
Admins can add additional fields to the Project creation page, such as Customer Vertical, Deal Size, and Prospect Location.
Loopio can connect to other platforms through purpose-built integrations (such as with Slack and Seismic) or custom-built through the API. The Integrations page allows Admins to manage site integrations and behavior.
Both a Role and a specialized license type, Library Users have read-only access to the Library. Viewing permissions can be customized at the Stack level for Library Users. **Subscription-based
A key benefit of Loopio's integrations with Slack or Teams is that end users can receive notifications directly in their Slack or Teams instance. Admins can customize the notification methods for users receiving assignments and reminders from Loopio.
A development option allows for custom-built integrations with other platforms and services.
The option to formalize the Project Milestones required for a business’ response process. A Project Plan Template can be added to a launched Project to make sure no key steps are missed.
Permission sets for groups of Users. Customized Library access and platform functionality can be created by Role and extended to groups of Users or individuals.
A pass-through and authentication process governed by a customer’s IdP (identity provider). SSO allows users to log into Loopio securely without the use of a password. **Subscription-based
Global site updates for all users that include revising the Freshness score scale and adding additional Answer Set Option for cases outside of the default Yes, No and N/A (ex. Partial, 3rd Party, On Roadmap).
This License type can give a user access to all platform functions (in the form of an Administrator account), or be customized to create unique Roles.
Customized groupings of users by their areas of focus, used to assign Project Questions to groups when several different SMEs could respond. **Subscription-based
Holders of active Loopio accounts.