Glossary of Terms by Object

Review this Glossary of Terms but note that only Account, Contact, Notes, Files and Task objects are native to Salesforce.

All other objects in improveit 360's managed package are Custom managed objects in the Salesforce Lightning ecosystem. See also: Object Relationship Diagram

Below this Article you will find a downloadable Excel file with the entire Object and Field Schema as of June 2025. 

Note: As a Salesforce OEM Partner, improveit 360 cannot use the following native Salesforce objects: Leads, Opportunities and Cases. 

Account - The Account record is usually synonymous with the term "lead" or "customer." Account is the primary object in Salesforce and improveit 360. An Account represents an individual customer account, an organization or a partner your business works with. improveit 360 utilizes two (2) Account record types: Vendor or Customer. Each Account can have multiple Contact records and multiple Address records associated with it. Note: Account "Type" can be used to provide more information about the relationship between your company and the Account.

• A Vendor record type is used for Material Suppliers or Financial Lenders.
• Customer record type is used for Residential customers or Commercial customers and allows you to track multiple property locations. 

Address - Address records are related to the Account and an Address is required when creating a Sales Appointment, Sale and Project. The Address contains the physical location of the property including Latitude and Longitude and (if applicable) Territory designation. Street Address and Zip Code are required fields. 

Commission - Each record stores commission information for a staff record (typically a Sales Rep or Foreman) related to a specific Sale or Project. Note: Commissions can be related to a Sale, and can also be related to a Project, but does not have a Master-detail relationship to either object.

Commission Adjustment - These records are used to store adjustments or payments made to Commission records. Commission Adjustments usually represent when you pay out the Commission to a Rep, or when you need to claw-back Commission from a Rep. Can be a Type of Payment or Credit. Note: There are no out-of-the-box automations related to Commission Adjustments or when Commissions are paid to a Rep. 

Contact - Each Contact can be related to an Account and the record is used to track contact information specific to one person. For example, if the Account is a residence labeled "Robert Shaw Household", we might have two Contact records, one for Robert with his phone number and email address, and a second Contact record for his wife Suzanne with her phone number and email address. However, if the Account is a commercial partner, the Contact might be an investor or realtor and they may have multiple related Address records for multiple properties they are currently renovating to put on the market. 

eLead - This stands for "electronic lead" and is a custom object used to store lead data sent into the system from a variety of lead providers. eLeads can be received through an integration using a URL endpoint or an email endpoint. eLeads can receive data from providers like HomeAdvisor or your company’s website allowing your team to see lead data and schedule leads faster. eLeads can be automatically converted to an Account, Contact, Sales Opportunity, and even a Sales Appointment (if appointment information is provided). Unconverted eLeads are marked accordingly and can be viewed in a List View and converted separately.

Files - These records can be system Files, that may be used as a template (like an HTML document, or an uploaded image) but Files might also be PDF documents, Word docs, or Excel files attached to specific records like Sales Appointments, Quotes or Sales. Use the File Manager tool to see all Files related to one Account. Note: In-App Guidance screen shots are also stored in Files. 

Inbound Text - These records store all inbound texts received whether the customer is replying to an Outbound text from the system or not. Required fields are: To Number, Status and From Number.

Lead Source - The primary marketing effort that a specific lead should be attributed to. Examples of Lead Sources are: 2017 Home and Garden Show, Home Depot Store #351, Spring 2023 Postcard Mailer, etc. Source and Source Type within each Lead Source are used to track the broader categories of marketing effort that the lead should be attributed to. Note: Source Type is a global Picklist Value Set. For example: the Source Type might be "Retail" while the Source is "Home Depot", and the individual Lead Source is "Home Depot store #562." 

Lead Source Cost - Each Lead Source Cost record stores the amount of spending for a specific marketing effort. Be sure to track Lead Source Cost data in order to use critical marketing reports and calculate Return on Investment. Amount is required and this object is a child of the Lead Source object. 

Loan - Each record stores Loan details specific to one customer's Sale. The Loan record can utilize a Loan Option (as a Template) but it is not required. Loan is a child of the Sale object and contains Borrower and Co-Borrower details. 

Loan Options - These records store the Finance option data related to each Lender Account your company works with. If a Lender offers multiple financing options, you will create multiple Loan Option records for each type of financing offered by each of your Lenders. For example: "6 Months same as Cash" might be one Loan Option offered. Lender is required and is a lookup to Account records with a Type value of Lender. 

Notes - This record type is native to Salesforce and allows your team to create rich text records related to any primary object type in the system. 

Outbound Texts - An Outbound Text record is created for every text message sent from improveit 360's texting feature. Whether sent as an automated message using a triggered Flow or sent manually by typing directly into the texting component, an Outbound Text record is saved. Required Fields include To Number and Status. Outbound texts can originate from Sales Appointments, Sales Opportunities, Sale, Payment, Project, and Project Activities as well as the texting component on the Account page.

Payment - This record stores the payment or discount data related to a Sale and/or Project. Amount and Type are required, as well as Sale. 

Product - This record is used to store a database of Products you sell and their specific details, such as SKU, unit of measure, cost, etc. Product Category is required. Products are required on Quote Items and Sale Items.

Project - The Project record stores production data such as Product Category, Project Manager, Status and overall Start Date. A Project will contain several steps (Project Activities) required to complete the project. Apply a Project Template to Projects in order to create a quick repeatable production process and keep your teams organized. 

Project Activity - These records store your individual production steps needed to complete each Project. These can be either a Task or an Appointment and are typically assigned to specific users. Project Activities represent the individual task to "Order" materials for the Jones window project or "Install" the Edwards roofing project. Project Activities with the Type of Appointment will appear on the Staff Calendar and are used to track Start, End and Completed dates for a particular step within the Project. Project Activity Name is required. Note: automations can be created to send emails or text messages from this type of record.

Project Costs - This object stores job cost records associated with the Project. This can include Types such as Commission, Material, Labor, Permits and other costs. Type and Amount are required, and Project Cost is a child of the Project object. 

Project Templates - The Project Template records store a pre-defined set of production steps (Tasks and/or Appointments) that need to be completed for a given project of a specific type (typically based on Product Category). Example: The steps may be different between a Window installation versus a Roofing installation. Two templates can be created to define the steps needed in those two production processes. Project Template Name is required.

Project Template Activities - Used to define production processes, these records are a child of the Project Template and are individual templated steps which can be applied onto a specific Project. These could also be called Production Steps. Step Dependency can be used to ensure your teams are not trying to work a step in the Project before a preceding step in the Template has been completed. Project Template Activity Name and Step are required. 

Quote - Custom object that stores the Quote/Estimate information. Although typically attached to the Sales Appointment that stores an estimate, the Quote record can also be created directly from the Account in improveit360, without needing a Sales Appointment. It is comprised of Quote Items, which make up an itemized price for the Account. Quotes which are related to the Sales Appointment, when marked as Run and the status detail is Sold, the selected Quote and Quote Items will import to a Sale record. 

Quote Items - These records are the individual estimated line items (products) on a given Quote/estimate. These Quote Items are specific to one Quote and the Contact/Account. 

Quote Template - This object stores a template of pre-defined Products quoted when estimating a specific type of work. You might have a "Half Bath" Quote Template versus a "Tub/Shower" Quote Template. These are used by Sales Reps when creating Quotes for your Bathroom Products. A Quote Template can be applied to a Quote in order to populate pre-defined Quote Items. Note: Reps can make changes and add additional Quote Items to a single Quote without impacting the Template. 

Quote Template Items - This object is a child of the Quote Template and contains the individual pre-defined line items (products) for the given Quote Template. Quote Template and Product are required.

Sale - Represents the contractual agreement between your company and the Account. The Sale record stores the Sold On date, Approval date, Balance Due, and much more. The Sale is also related to which Sale Opportunity(s) was/were Sold and the Sales Appointment which was ran and resulted as Sold. A Sale record indicates the related Account has signed a contract and agreed to hire your company to install their project. Status is a required field. Payment is a child object of the Sale. Sale utilizes two Record Types, one for standard Sale and one for Canceled Sale. 

Sale Item - These records store individual line items (Products) sold to the customer and include the Quantity, Unit Price, Description, etc. The detailed Sale Items can be displayed on an Invoice document generated from the system. Sale Items are a child of the Sale. 

Sales Appointment - Record which stores the appointment information including date, start time, duration, Sales Rep and product category of interest. The Sales Appointment represents a scheduled time with an Account for the assigned sales rep to attempt to sell your company’s goods or services. Appointments will display on the Staff Calendar based on Staff Capabilities. Account, Address, and Type are required fields on the Sales Appointment record. 

Sales Opportunity - an Account can and should have multiple Sales Opportunity records throughout the life of their relationship with your business. The Sales Opportunity represents the unique Lead Inquiry record and contains the Date the lead was taken, what they're interested in, as well as the Lead Source and Source Type data of where that lead heard about your company. Each Product Interest/Category should have its own Sales Opportunity. Sales Opportunities are not tasks, but rather future chances at selling products or services to current or past leads. Tasks are generated on a Sales Opportunity as a reminder for your staff to call, text, or email the Contact in an attempt to set them for a Sales Appointment. Lead Source, Interested In and Taken On is required.

Staff - Custom object that stores your staff information. Staff are people who may access your improveit 360 system (Users) or they may simply be someone you wish to email and assign to a project. A staff that does not also have a user record could be a sub-contractor. You can still send emails to Staff members, even if they are not Users in improveit 360. Staff Name and Start Date is required.

Source/ Source Type - Source is a field on the Lead Source object which represents a broader category of Marketing. Source Type is a global picklist which represents the broadest category of marketing that can be reported on. For example: the Source Type might be "Retail" while the Source is "Home Depot" and the individual Lead Source is "Home Depot store #562." 

Tasks - These records are native to Salesforce and can be related to any primary object type in the system. Tasks are used as reminders to Set an Appointment, or call the customer to Rehash their Quote, or Order Materials, or call a customer for quality assurance follow-up after an Install. 

Territories - These records are used to identify geographic parameters and divide your Address database based on Territory data. Territories can be auto assigned to Address records out-of-the-box. If you plan to auto-assign Territory to Account, Lead Source or Staff, a Flow automation would be needed to populate the Territory based on the record's related Address record(s). See also: Territory Field Weighting 

Time Blocks - This record is related to Sales Appointments and Project Activities and allows users to assign an Appointment or Project Activity to a block of time, rather than a specific Rep. The Dispatcher tool can later be used to assign any unassigned Appointments. Time Block utilizes record type and is used to dictate if the Time Block considers Staff Availability or Capacity for its scheduling method.