AscendixRE CRM is built on top of Salesforce CRM, so to access AscendixRE after you’ve started a trial or become a customer you can use https://login.salesforce.com/ and sign-in with the credentials either we’ve provided at signup or your admin has provided.
Tip: Save the website as a ‘favorite’ and click on ‘remember me’ when you login so you don’t need to re-type it every time
For the best mobile experience, use the Salesforce mobile app.
The Salesforce mobile app is available for iOS® and Android™ phones and tablets. You can download the iOS app from the App Store®, or the Android app from Google Play™.
The Property is the central core of AscendixRE. All other records are connected to the property by virtue of their relationship to it: Leases represent the Company that is a tenant and the abstract info of the lease agreement. Inquiries & Preferences are the desired terms of that space. Perhaps brokers or prospective buyers/tenants are inquiring about space that’s listed – or investors/companies have buying/leasing criteria. Deals are your “pipeline” – Tenant & Buyer Reps work on site selection, Landlord Rep have spaces they need to fill with tenants, etc.. Accounts & Contacts – don’t necessarily need to be tied to a Property, but can be: Example: Property Owner, Finance, Asset Manager, Marketing, Property Manager, etc.
2. Scan Search & Filter: Access the Property record, and find all related Inquiries, Availabilities, Deals & Leases to that Property.
Example: You can “view all” Leases in Merit Tower, or use filters to refine the views such as those expiring this year or filter Deals by a specific Stage. These filters are temporary (clear when you log out) and are personal.
When users access Ascendix, the default view for any Object will be “Recently Viewed” – which might show no data, because that user will not have recently viewed anything. There are other views a user can select, and pin as a favorite. See below:
Can I default my view to something other than “Recently Viewed”?
This is the #1 top question we get.
Yes! This is up to each user and what their default list is per tab.
For example, you set your Accounts default to “All Accounts” and your Contacts default to “My Contacts”.
Here is how to set a default view:
Select the view you want to see (i.e. My Contacts)
Think of an inquiry as an unqualified lead. You can capture Contact and Company info, and once qualified, they can be converted to full-fledged Contacts and accounts.
For Listing Brokers:
An inquiry would be a buyer rep or tenant rep broker reaching out to you on behalf of the listing, inquiring about the space. It could also be an end-user inquiring directly. The inquiry form allows you to link the interest to the Listing, so you have a grouping of all inquiring parties since you’ve won the Listing. It’s a good lead pipeline and a way to report to your seller or landlord on ‘foot traffic’.
For Buyer Reps/Tenant Reps:
The inquiry form also has an area where you can jot down investment or leasing preference. Price min and max, space requirements, Property type requirements, required move in or purchase date.
You convert an inquiry when you think it is appropriate.
*Note that any customized fields you add to the inquiry, will not be captured when you convert the records.
Property is the building itself. Its physical characteristics, location, total space, # of floors, etc.
The Listing is the agreement you win to sell or lease that building.
As a Listing Broker you would create both records, but track all of your outbound marketing/selling efforts and inbound inquiries against the listing. Again this helps you for reporting purposes and ensures everything is tied to one common record.
There is an exception here. If you are a Land Broker, and you are on an AscendixRE Land trial, we have co-mingled the Property and Listing tabs, so that you are managing all of your listings, within the Property record itself.
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
The cookie is set by CloudFare. The cookie is used to identify individual clients behind a shared IP address d apply security settings on a per-client basis. It doesnot correspond to any user ID in the web application and does not store any personally identifiable information.
This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary".
This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Non Necessary".
This cookie is native to PHP applications. The cookie is used to store and identify a users' unique session ID for the purpose of managing user session on the website. The cookie is a session cookies and is deleted when all the browser windows are closed.
Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc.
This cookie is installed by Google Analytics. The cookie is used to calculate visitor, session, camapign data and keep track of site usage for the site's analytics report. The cookies store information anonymously and assigns a randoly generated number to identify unique visitors.
This is a pattern type cookie set by Google Analytics, where the pattern element on the name contains the unique identity number of the account or website it relates to. It appears to be a variation of the _gat cookie which is used to limit the amount of data recorded by Google on high traffic volume websites.
This cookie is installed by Google Analytics. The cookie is used to store information of how visitors use a website and helps in creating an analytics report of how the wbsite is doing. The data collected including the number visitors, the source where they have come from, and the pages viisted in an anonymous form.
A unique indentifier for the web browser
This cookie is set by Youtube and registers a unique ID for tracking users based on their geographical location
This cookies is set by Youtube and is used to track the views of embedded videos.
Advertisement cookies are used to provide visitors with relevant ads and marketing campaigns. These cookies track visitors across websites and collect information to provide customized ads.
Used by Google DoubleClick and stores information about how the user uses the website and any other advertisement before visiting the website. This is used to present users with ads that are relevant to them according to the user profile.
This cookie is used to a profile based on user's interest and display personalized ads to the users.
This cookie is set by Youtube. Used to track the information of the embedded YouTube videos on a website.