Project Settings
      Back to home
      1. Knowledge Base
      2. Project Settings

      Project Setup Guide

      Use the lists below to help you set up a new project.

      For convenience, the tasks are grouped into those that should be completed before your website/marketing launch and those that should be completed before your full project launch/contract writing. Note that these are general guidelines and your unique project may require additional steps or a different order.


      We’ve also made a guide for the most important information and how it should be formatted in order for Spark to import your inventory and contacts.


      Before Website/Marketing Launch


      • Team Settings
        • Define user role permissions
        • Add Team Members
        • Set up auto-assignment
      • Contact Settings
        • Add or customize contact ratings
        • Add or customize interactions to suit your sales process
        • Add standardized contact fields if your project will collect contact information that is not included by default within Spark
        • Add or customize registration sources
      • Email Settings
        • Register your domain to help improve email deliverability
        • Adjust your default email disclaimer, if desired
        • Add any email addresses campaigns will be sent from
        • If your team uses the BCC address to log email interactions, make sure they know the BCC address for the project
        • If your team uses the email sync feature, set interaction types for outgoing and incoming emails
      • Email Templates
      • Follow Up Schedules
        • If you would like a follow up schedule to be automatically applied to new registrants, create a follow up schedule so it can be chosen in the registration form settings
      • Questions
      • Registration Forms
        • Create a web registration form
          • If you will be linking to a Spark-hosted form or using iFrame, style your form in Carpenter
          • If you will be using the form code to make a custom form, create the basic form, then proceed to define the registration form settings
          • If you will be using the API to post contacts to Spark instead of or in addition to the registration form(s), be sure to create an API access token and configure its settings — if you are using Zapier as part of the API process, be sure to create your Zap(s)
        • Define the registration form settings to determine how incoming registrants should be handled, including which registration source and rating to apply, if registrants should be auto-assigned to team members, which auto-reply email to send and more
        • Get your form code from the Embed Options modal (form micromenu → Embed Options) or send it to your web developer so that it can be connected to your website



      Before Project Launch/Contract Writing


      • On-Site Registration Forms
        • If your team will be collecting walk-in or on-site registrants, create and style an on-site registration form to be displayed on a computer, tablet, or even on visitors' personal devices
        • Don't forget to apply the desired settings for your on-site registration form
      • Inventory Settings
        • Add or customize inventory statuses
        • Add standardized inventory fields if your project will collect inventory information that is not included by default within Spark
      • Parking and Storage settings (note: the availability of these settings depends on your subscription – if you have questions, contact us at support@spark.re)
        • Set and adjust parking stall type, number, price, cost and taxes in the Settings → Inventory → Parking Types tab
        • Set and adjust storage type, number, price, cost, size, and taxes in the Settings → Inventory → Storage Types tab
        • If included stalls and or/storage should be "no charge" for the purposes of revenue and reporting, go to the Settings → Contracts → General tab and use the checkbox in the Parking Stall Revenue section to select "pre-allocated stalls are no charge" and/or use the checkbox in the Storage Unit Revenue section to select "pre-allocated storage units are no charge".

      Inventory Imports


      Send your inventory list to Spark to import. Here are some tips on what to include and how data should be formatted for an inventory import:

       

      Column Notes
      Unit

      This column is mandatory and each unit needs to be unique. If your project has multiple buildings containing the same unit number, differentiate them in some fashion in this column (e.g. A-101 for building A and B-101 for building B) and then create a second column, Legal Unit, with the unit number as it should be displayed on your contract (using the above example, the unit in buildings A and B would both be 101). Spark will import the Legal Unit column as a standardized field.
      Status

      New inventory is imported with the Available status by default. If you would like all or some of the units to be imported with a different status, include a Status column. Be sure that the statuses listed in this column exactly match the statuses found in Settings → Inventory → Statuses.
      List Price

      This should be formatted as a number only, without dollar signs or other currency symbols.
      Floor/Level

      This column is essential for creating your stacking plan and data must be entered as whole numbers (decimals, such as 1.5, are not supported).
      Exposure

      If you would like your stacking plan to orient by exposure instead of numerically, this column is required. If you would like to note exposure for each unit but maintain a numerically-oriented stacking plan, be sure to tell us so Spark can import this column as a standardized field instead.

       

      Other commonly imported and useful fields include strata lot, area, unit type, and number of bedrooms, bathrooms, number of parking stalls and storage lockers.


      Contact Imports


      If you have a list of contacts to import, for example, if you are migrating from a different CRM, send the contact list to Spark. Here are some tips on what to include and how data should be formatted for a contact import:

       

      Column Notes
      Name

      Names should be provided in a first name column, a last name column, and, optionally, a legal name column. For example, you could have a contact with first name John (the name they go by), last name Smith, and legal name Jonathan Smith. If you have previously collected additional name fields, include columns for these as well and ask Spark to import them as standardized or additional fields.
      Email

      Each contact must have a unique email address - contacts cannot share an email address. If a contact does not have their own email address, they must have a phone number.
      Phone

      If a contact does not have an email address, they must have a phone number. Phone numbers do not need to be unique to a contact, however, and can be shared between multiple contacts.
      Agent

      Entries in this column must be either TRUE or FALSE. TRUE contacts will receive the agent tag within Spark.
      Legal

      Entries in this column must be either TRUE or FALSE. TRUE contacts will receive the legal tag within Spark.
      Rating

      By default, new entrants into your database will receive either the New or Agent rating. If you would like to specify different ratings (which should match those in Settings → Contacts → Ratings), include them in a Rating column.
      Registration Source

      If you have previously collected a registration source for the contacts to be imported, include them in a Registration Source column. 
      Marketing Source

      If you have previously collected a marketing source for the contacts to be imported, include them in a Marketing Source column. The marketing sources in this column should exactly match answers to your marketing source question in Spark.
      Project Questions

      If you have previously collected the answers to project questions for the contacts to be imported, include them in a column that is named to exactly match the existing project question. For example, if you have a project question, “What size home are you interested in?” use this as the column header. The answers in this column should exactly match answers to the applicable project question in Spark, unless the question allows registrants to enter their own answer.