rdesk CRM v7.0 Release Notes

Transcription

1 rdesk CRM v7.0 Release Notes September 30th, 2010 LPS Real Estate Group is proud to announce the release of rdesk CRM v7.0. These Release Notes highlight new or improved features of the product and the benefits that these features provide to LPS customers. Production release date: October 5th 2010 Note: release will occur during the night of October 4 th Release Highlights CRM Exchange Sync... 2 Agent Setup... 2 Initial Sync... 2 Initial Sync Methodology... 2 Automatic synchronization Conflict Resolution... 3 Synchronization Status... 3 Sync Notes:... 3 Technical Notes... 4 HTML Signature Block... 5 Tokens... 6 Operational guidelines and notes... 6 Quick / Activity / Action Plan Photo and Logo Controls... 7 View Activity as Web Page... Error! Bookmark not defined. Trackable Activities and Quick s.... Error! Bookmark not defined. Contact Screen Enhancements... 9 Key Changes... 9 Screen Shots Office Level Lead Routing Office Level Document Support Page 1

2 CRM Exchange Sync rdesk 7.0 introduces synchronization of contacts and calendars between rdesk and Microsoft Exchange Server 2007 SP2/SP3. The synchronization processing is automatic for agents who have the facility enabled and that have successfully performed an initial sync. Agent Setup Only available to agents that have the facility enabled by the cobrand admin. Agents can access the new Exchange Synchronization setting from within their personal profile. Agents enter their address and webmail login credentials and click save. Initial Sync Clicking the Sync button initiates the sync process; the process may take some time to complete. Initial Sync Methodology The Initial Sync routine performs a number of tasks as follows. 1) All contacts are first read from the Exchange Server. Each contact is then existence checked against the agents contact list in rdesk. A match on First Name, Last Name and Phone or address is required to consider the contact to be the same. rdesk then merges the data in the two records and create a link between them. The contact is updated in Exchange to include membership of the rdesk category. This signifies that this contact is synchronized with rdesk. Page 2

3 2) All remaining rdesk contacts (those that are not already linked per #1) are then pushed from rdesk to Exchange. A link between the two records is created and the Exchange contact gains membership to the rdesk category. 3) Exchange calendar items are read using a sync window of minus 30 days and plus 60 days. These events are added to the rdesk Calendar. 4) The rdesk event calendar is read using the same sync window and the events are pushed to Exchange using rdesk categories Automatic synchronization. Once the initial synchronization is complete, subsequent changes made in either rdesk or Exchange are synchronized automatically and are available in both places within minutes. Changes within rdesk are pushed to exchange almost instantly. These changes are then available to applications and devices that synchronize with Exchange. Exchange is polled on a regular basis for changes to contacts that belong to the rdesk category and to all calendar items, these changes are then applied to rdesk. Conflict Resolution In the event of a record being changed in both rdesk and Exchange almost simultaneously the conflict is handled by assuming that the last change is the most current and this change is applied to both rdesk and Exchange. Synchronization Status The status of the synchronization service are displayed in Settings tab of the Agents personal profile Sync Notes: - Contacts that are not members of the rdesk category are not synchronized, these are assumed to be non business contacts. - Contacts can be pushed to rdesk by adding contacts to the rdesk category. - If a contact is added to rdesk that already exists in Exchange unsynchronized (ie not a member of the rdesk category) there is no existence check to Exchange and the contact will be seen to be duplicated in Exchange. - If an agent changes their password they will disable the sync until they update their password in rdesk CRM. Page 3

4 Technical Notes - Exchange Server 2007 SP2(or SP3) is required, no prior versions are supported. - Exchange Server 2010 support is not yet available. - Exchange Autodiscover is highly recommended and is expected to be available at: o autodiscover.exchangeurl/autodiscover/autodiscover.xml or o EXCHANGEURL/autodiscover/autodiscover.xml Please consult your Exchange server administrator for details. - Prior to setup your account manager requires the following: o The EWS (Exchange Web Services) URL o The OWA (Outlook Web Access) URL o The Exchange authentication model o Provision of a test account (rdesktest@yourdomain) Key Benefit Agents have access to their rdesk address book and Calendar on every device that synchronizes with Microsoft Exchange Page 4

5 HTML Signature Block rdesk now supports HTML Signatures outgoing s and activities / action plans that utilize the signature block token will reference this block and display the HTML signature. A default HTML Signature can be set at the Cobrand Level for all HTML signature enabled agents. The default block is available in Cobrand Admin > Design Tab. The default signature block can be created using the RAD editor. A new system role titled Allow HTML Signature controls the availability for agents Agents who have the role enabled gain a RAD editor around their signature block in their profile. In addition to being able to create and edit their signature as HTML, they can also revert back to the company default. Page 5

6 Tokens The following signature block tokens are available via the RAD Editor Agent First Name Agent Last Name Agent Image Agent Logo Agent Phone Agent Phone 2 Agent Address Agent URL Equal Housing Logo Operational guidelines and notes Creating a Co-Brand level default signature does not replace any current or blank signature for agents. If the agent wishes to utilize the default signature, they can navigate to their personal profile to change their current signature. Page 6

7 Pressing the reset button will change the contents of the signature block to the Co-Brand default. The agent can choose to modify this should they wish before they save it adding any free-form personalization or utilizing additional tokens. Key Benefit HTML signatures on quick and activities. Quick / Activity / Action Plan Photo and Logo Controls rdesk 7.0 introduces additional controls over outgoing s with regards to the use of the Agent Photo and Logo. A new Cobrand level switch controls the use of the Logo and Photo on outgoing s Page 7

8 The three options available are: - Allow user to choose to display logo and photo. This is the current (pre 7.0) default. The agent controls the visibility of the photo and logo within each outgoing via a check box. - Always display logo and photo. This forces the photo and logo onto every outgoing and removes the choice from the agent. - Never display logo and photo. This turns off the facility and removes the choice from the agent. Key Benefit Control the look of outgoing s. Page 8

9 Contact Screen Enhancements As a part of the on-going usability and performance improvement program, we have made a number of changes to the contact screens to aid both usability and performance. Key Changes - The menu structure has changed slightly. o Removal of the dedicated and redundant Add option o Renaming the old View option to Contacts - New Search Tab to signify the entry point for Contact searches - New Search interface that automatically vertically re-sizes to fit the available screen height. - Faster Search facility through the use of new search technology - Removal of the old ABC search based on User Interface feedback - Addition of Action Plan assignment facility on the summary tab - Increased field sizes on the Details tab o Reduced whitespace to better utilize screen space o Better alignment and sizing of fields. Page 9

10 Screen Shots New Look Menu Options New Look Search (test data details blurred) Page 10

11 Action Plan Assignment Page 11

12 Enhanced Details Tab Layout, larger fields etc. Key Benefits cleaner user interface is easier to use; search is faster. Page 12

13 Office Level Lead Routing Office level lead routing rules can be maintained by the Office Lead Admin role. Agents with this role can only maintain the lead routing rules for the office to which they belong. The options outlined in red are now available le to the Office Lead Admin in addition to the ability to designate lead routing service regions. Page 13

14 Key Benefit Office Lead Administrators can now choose how office leads are routed and can maintain the rules. Office Level Document Support A new level for documents is now available for office level document storage in the WebDocs facility. The Office Roster Admin role is permitted to add documents at this level. Documents that are placed here are only available to agents within the office. Key Benefit Office documents are now private within an office. Page 14