Alana White

My feedback

  1. 6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Feature Requests » Reporting  ·  Flag idea as inappropriate…  ·  Admin →

    Hi Neri (and others who have voted on this request),

    Thanks for your suggestion.

    Would you mind clarifying: when you say on a per agent basis, do you mean per listing agent or per agent running the open home?

    An error occurred while saving the comment
    Alana White commented  · 

    I see this was posted back in 2015. I still can't seem to pull a report or find any filter to be able to be able to provide a home open list to an agent (for the home opens they have). Not sure how everyone is currently doing this (presumably manually putting together a list each week of what home opens they have. Just adding the Agent Attending onto the Public Report would do the trick (as I can see the Open Times have now been added to the Public Report, but just not the Agent Attending)

  2. 6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Feature Requests » Reporting  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Alana White commented  · 

    Hi Alex, just with this one, the date it has been created in REX or the date of the Listing Authority was signed will never be the date it hits the market, as it's entered and then prepared over the course of however long before it hits the market as a general practice I'm sure with most users, so unfortunately the current way DOM is calculated is unable to be used for anything and is confusing in it's current format as it's not correct (and negatively effected by taking an early date than it did actually hit the market). I'm aware of other CRM's (and the one have a field that would pull in published date of "Date First Advertised" which could be over written in the rare instance that you wanted to pre-date the published date as the First Published Date. Be great if this could be looked at if it's not too much to fix up to DOM stats pull correctly. Wouldn't matter if a listing was rested etc, days on market still only populated from First Published Date.

    An error occurred while saving the comment
    Alana White commented  · 

    Yes please, would love to be able to use the Days on Market in REX rather than having to use third party portals for this info.

  3. 1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Feature Requests » Reporting  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Alana White commented  · 

    This would be a great enhancement, as a one stop activity report for each agent rather than having to pull various reports to be able to report on activity

  4. 3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Feature Requests » Other  ·  Flag idea as inappropriate…  ·  Admin →
    Alana White shared this idea  · 
  5. 71 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    11 comments  ·  Feature Requests » Tracks / Templates  ·  Flag idea as inappropriate…  ·  Admin →

    It looks like there’s 2 requirement requests going on here:

    1. Triggering addition of tracks based on an event.
    2. Having reminders that are attached to floating dates (e.g. unconditional date, settlement date etc). E.g. 3 days before unconditional.

    Would be good to get some more info on both of these items.

    1. Regarding triggering addition of tracks based on events:

    • Presumably you want support for this in multiple modules. If so, is it all modules or just some?
    • For each module, what are the events that you think should be supported for triggering track addition?
    • Is this an automatic process or is the user prompted to add the track when the event occurs.
    • If the desire is for the track addition it to be automatic, how do we deal with questions like which contact should a track be attached to in a listing or property that includes multiple contacts…
    An error occurred while saving the comment
    Alana White commented  · 

    We have used all of this functionality in our previous CRM, so can advise how it use to work there if that's of any help (and put the comments in UPPERCASE so it's easier to see)

    1. Regarding triggering addition of tracks based on events:

    Presumably you want support for this in multiple modules. If so, is it all modules or just some?
    For each module, what are the events that you think should be supported for triggering track addition?

    WE HAD IT IN THE LISTING MODULE, SO ESSENTIALLY THERE WERE SEVERAL DEFINED EVENTS (LISTING STATUS EVENTS) THAT WERE PREDETERMINED TO AUTOMATICALLY ADD A TRACK , SO FOR EXAMPLE TRACKS WOULD BE ADDED AUTOMATICALLY WITHIN THE LISTING STATUS EVENTS AS FOLLOWS:

    NEW LISTING CREATED,
    CONTRACT ENTERED (UNDER OFFER),
    ON MARKET (UNDER OFFER BUT STILL ADVERTISED FOR SALE)
    FINANCE APPROVAL RECEIVED (UNCONDITIONAL),
    SALE NOT PROCEEDING,
    SETTLEMENT,
    WITHDRAWN.

    ANY UPDATE TO A STATUS WITHIN THESE LISTING STATUS EVENTS WOULD THEN CANCEL OUT A PREVIOUS TRACK (COMPLETED TASKS WOULD REMAIN BUT OUSTANDING ONES WOULD BE REMOVED, AND THEN NEW TRACK FOR THE NEW STATUS WOULD AUTOMATICALLY BE ADDED

    THERE WERE OTHER TRACKS THAT COULD BE MANUALLY ADDED OR LINKED TO BE ADDED IN CONJUNCTION WITH ANY OF THE ABOVE (I.E. AUTHORITY EXPIRING TO BE LINKED TO NEW LISTING CREATED - HOWEVER AS IT'S NOT PART OF THE DEFINED EVENTS FOR LISTING STATUS EVENTS, THIS TRACK WOULD NOT REMOVED WHEN A LISTING STATUS WAS UPDATED)

    THESE EVENTS TRACKS WOULD BE TRIGGERED AT THE TIME OF EVENT, AS OPPOSED TO TRIGGERED BASED UPON A DATE FIELD (SUCH AS FLOATING DATES I THINK YOU ARE REFERRING TO BELOW)

    Is this an automatic process or is the user prompted to add the track when the event occurs.
    If the desire is for the track addition it to be automatic, how do we deal with questions like which contact should a track be attached to in a listing or property that includes multiple contacts or in a contact that includes multiple listing /properties? WE HAD AN AUTOMATIC PROCESS, AND THE TRACK WAS ALWAYS ATTACHED TO THE LISTING RECORD, WHICH COULD PULL THE ATTACHED CONTACTS, INCLUDING THE OWNERS, THE BUYERS, THE SETTLEMENT AGENTS/SOLICITORS SO THAT THE ASSOCIATED LETTERS/EMAILS ALREADY HAD THE MERGE FIELDS COMPLETED AND READY TO JUST HIT SEND WHEN THEY CAME UP (NO NEED TO FIND/ATTACH WHO IT WAS TO GO TO EACH TIME) - AS THEY WERE ALL ATTACHED TO THE LISTING RECORD. WE HAVE SETUP OUR REX CONTACTS WITH ONE CONTACT RECORD FOR THE OWNER EVEN IF THERE ARE TWO PEOPLE SO AT LEAST THE AUTOMATION OF THE OWNER MERGE FIELDS WORK, BUT WE ARE STILL HAVING TO DO IT QUITE MANUAL FOR CONTRACT/BUYERS/SETTLEMENT AGENTS, FOR THE SAME REASON THAT THEY ARE NOT LINKED TO THE LISTING RECORD THE SAME WAY THAT THE OWNER IS, SO IT'S DIFFICULT TO GENERATE CORRESPONDENCE AUTOMATICALLY. THE MAIN LIMITATION AT THE MOMENT WITH THE OWNER HAVING TWO CONTACTS IN ONE RECORD IS THAT YOU CAN'T CHOOSE TO EMAIL JUST ONE OF THE CONTACTS, BUT OTHER THAN THAT THE MERGE FIELD SIDE OF AUTOMATION FOR EMAILS/LETTERS WORKS WELL. HAVING THE BUYERS AND SETTLEMENT AGENTS LINKED TO THE LISTING FOR THE PURPOSE OF USING THE MERGE FIELDS FOR GENERATION OF CORRESPONDENCE WITHIN THE LISTING STATUS EVENTS WILL MAKE IT MUCH LESS MANUAL

    If the process is manual and the event occurs via API or in some way other than the user interacting with the track what do we do? N/A IN OUR SCENARIO SO NOT SURE
    How are these tracks cancelled? TRACKS CANCELLED IF ANOTHER STATUS UPDATE WITHIN THE SAME LINKED TRACKS (I.E. LISTING STATUS TRACKS) WAS RECEIVED AND NEW TRACK ATTACHED

    2. Regarding floating date reminders:

    Presumably you want support for this in multiple modules. If so, is it all modules or just some?
    For each module, what are the date fields that you think should be supported for a reminder to be tied against.
    LISTING MODULE DATE SENSITIVE EVENTS SUCH AS:

    * LISTING AUTHORITY EXPIRY DATE
    * DEPOSIT DUE DATE
    * SETTLEMENT DATE
    * FINANCE DUE DATE

    What happens to these reminders when they exist but the date does not (e.g. a reminder that is tied to an active contract unconditional date but there is no active contract on the property).
    Would be great to get more input on this either here in the comments section or in rexperts.
    AS THE REMINDERS ARE TIED TO THE DATE ENTERED INTO THOSE FIELDS, THEY ARE NOT APPLIED/TRIGGERED IF THERE IS NO DATE IN THE FIELD

    WE DID NOT HAVE ANY AUTOMATIC TRACKS FOR PROPERTY MODULE, BUT IT WOULD BE AWESOME TO HAVE AUTOMATIC TRACKS WHEN A OAB IS ENTERED (OR AT LEAST A FLICK UP TO ASK IF YOU WANT TO ADD IT) AND COMPLETED APPRAISALS.

    An error occurred while saving the comment
    Alana White commented  · 

    This is a great suggestion and would really help make REX more automation friendly

    Alana White supported this idea  · 
  6. 5 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Feature Requests » Reporting  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Alana White commented  · 

    This would be great, would save so much time running the report once with a page break per agent as opposed to having to run the same report multiple times over and over.

  7. 10 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Feature Requests » Reminders  ·  Flag idea as inappropriate…  ·  Admin →
    Alana White shared this idea  · 
  8. 19 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Feature Requests » Other  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Alana White commented  · 

    Was just about to log this one myself as we are new users to REX and it's a lot of extra clicks for an admin person to enter a Contact on behalf of everyone - this would save all admin people entering contacts so much time so has my vote!

    Alana White supported this idea  · 

Feedback and Knowledge Base