Hi Mark,

To be clear, Pocket does have all of this functionality, it's simply not present in the "Add a contact" workflow - it's present on the contact itself in various areas (most of which you'll find in the related tab). The statement I was making simply related to reasons to not overload the "Create" workflow which is deliberately limited to 4 fields.

In relation to adding the property if it doesn't already exist - I assumed this was available but apparently it's something that's missing from this particular auto complete.

Happy to take this as a suggestion for two things:
1. When adding a related property via Contact Record > Related > Properties - if the record does not exist allow the user the option to add it (similar to the way related contacts works ).
2. When adding a new relationship give the user a tick box to "Set this property as the owner's address" or something similar - if you tick this that would populate the address field on the contact record.

Hi Alex,
Thanks for your reply. I am assuming that you mean that a related property means that the property already exists in the system? What about if it doesn’t? It really should be able to be added at the time of contact entry whether it does or doesn’t exist already. I also saw another support request about this, but wanted mine to cover both new and existing properties. I also saw another request later about the address being in the correct fields, rather than just all in one and needing separating later. Sellers and potential landlords are the most valuable contacts in a database, hence the level of importance you’ve enquired about. If there’s one or three more steps in getting the detail in there, it pushes the whole process back and data is lost. In relation to your comments about adding buyer match data, it actually makes perfect sense to have that. The Renet app had match data, add a Property, and an appraisal, bulk sms etc, so I thought pocket would have at least all of this info. Zenu uses a responsive site that looks and acts like an app, with full functionality of the database in. It has a workflow that covers all of the functionality we are speaking about here. With the claim that Pocket is the best real estate CRM app available, all of this functionality is at least required. If i’m totally missing something and there’s an easy way to add properties, attach them as being owned, identify if they are home address or investment, add appraisal,add trail, add match data to a contact etc in the app, then please just send through what i need to type in the help menu and ill take a look. Hope this helps. Feel free to call with any other questions. Cheers MK

Hi Alex, I’m assuming that you’re referring to a related property as one that already exists in the system, is this correct? I’m talking primarily about adding a property that doesn’t already exist there and then, in the one entry. If it already exists in the system, then marrying the two up makes sense too. I saw a similar suggestion by another user also, but I wanted to make it clear at what point we want to enter, so made a new suggestion. There were also comments and a request about having seperate fields for address, rather than one field for street number, street name, suburb Etc

You can add a property to an owner via related > properties once the contact has been added.

Putting more and more in the add workflow tends to be a bit dangerous. Do we also present creation of match profiles as part of the add workflow, extra notes, feedback for the last property etc they attended, relationships to other contacts in the system. When you try to optimize too much you often end up at a worse solution.

I am curious to see how many votes you get here and why a contact's residence which can be entered immediately after addition of the contact (which from watching the behaviour and interaction of users almost never seems to be asked for or added while in the field) is any more justified for prioritization to the addition workflow than anything else.