2019 archive

Agenda Review marketing site — launch status Review import status Marketing Application Data cleaning status import Data validation checks look like: confirm email addresses are valid. presence fname, lname. presence of client name. presence of property ID and address. (ADDRESS,CITY,STATE,ZIPCODE). Data conflict checks look like: Same client name, but different first name, last name, or email address. A different client name, for an already existing email address. »

Agenda Review new CMS for siegelcallahan.com Review content needs — delivery Monday? Review portal imports »

Agenda Import data review and groups Import algorithm confirmation Import data review and groups Import algorithm Read the email address. If it doesn’t exist in the portal yet, then create a client record, and add the first name, last name too. If it already exists in the portal, then: If the first name, last name is different than what’s on record, ??? Read the property address. »

Agenda Application Review last week’s import discussion Admin migration 80% complete: ready for demo 1st week Dec Import 10% complete UX remaining (see last week below) Marketing Tennesse Resolution Partners Happy Thanksgiving! No meetings next week Application Last Week’s Conclusions Use the Group Name to bind clients under a single client name, for import and property record association. The group represents referrals Groups Vallikalam, O’Hara are examples of this. »

Agenda In final QA on staging In progress Planned Import: CSV file requirements Import: CSV validation criteria Import: confirmation report draft Import: workflow in final QA on staging email deliverability email to client, if scheduled payment declines Email when payment plan setup email to client when RAVA confirmed authorized agency copy on RAVA confirmation popup for RAVA confirmation In progress Administration merge Need copy: “Send email to client, when they confirm the RAVA copy. »

Agenda Review Payments features in progress Review RAVA Portal features in progress Finalize needed copy or assign Payments Update email from billing@prptax.com to eric@prptax.com Email deliverability In progress: implement DCIM records, avoids “via” from sending service, authenticates mail; In progress: Google bounces emails, claims no From In progress: Client email when payment plan is setup Need copy, probably variation on https://www.figma.com/file/BRg0Cs73NIHPQMIeFBADtGhZ/Payment-Plans-Master?node-id=7%3A2697 In review: email to client when payment declines Variation on https://www. »

Agenda Email deliverability Review RAVA Portal features in progress Features complete, pending copy Started admin migration Payments Email deliverability Completed: implemented DCIM records (four days of support with GoDaddy) Testing: Google bounces some emails, claims no from address In progress: Client email when payment plan is setup Feature complete, copy drafted In review: email to client when payment declines Feature complete, copy drafted »

Agenda Import: CSV file requirements Import: CSV validation criteria Import: confirmation report draft Import: workflow Nashville: review drip campaign prototype Nashville: review page content review Import CSV format expectations Per last week: yes, we can unify clients.csv and properties.csv to a single .csv Recall the “ignore anything we won’t use” current approach We’ll need to exclude client address information, use properties address information only We’ll expect exact client name duplication when a client name has additional properties CSV validation criteria client name, first name, last name, primary contact email exists primary contact email is formatted as an email address address, city, state, zip exists consider: Client_Name and CLIENT match? »

Agenda Review recurring charge failure notifications September 25 meeting recap Demo: client-property records Recurring charge failure notifications Portal notification of decline what is the current practice? Do you reach out to client, or retry immediately? Stripe notifications Error logging captured Current Payment Plan Index Improved Payment Plan Index Sept 25 meeting recap Challenges When we associate Clients to Properties, we want an unambigious link between a client and a property record. »

Agenda Credit card validation on payment plan creation Multiple payments bug Ongoing related records work Discuss Nashville marketing Credit card validation on payment plan creation Eric reports that case “Adam Bihon” — credit card number was given to him wrong. He was able to setup a plan, but it later failed to charge, b/c card number was wrong. We validate credit card numbers on payment plan creation. »