ContactMonkey for Business

Transcription

1 ContactMonkey for Business Business is about communication. We all want to make it easy for our leads, opportunities and clients to communicate with us, right? Who knows when that next big deal will be awarded and you want to ensure you can be quickly called or ed with the good news! Also, what happens when you move? You probably send out an with your new details, correct? Do you think people add those new details to their address books? Do you, when you get those s? Probably not! Who wants to take all that time to manually add this new info!? So why use ContactMonkey? 1) You want your contact info at your customers' fingertips making it easy for them to communicate with you; 2) You want to be the first point of contact for your clients; 3) You want your info to be accurately stored in your customers' address books and synced to their Blackberrys and iphones; 4) You want to make it easy for your customers to update your contact info when you move; 5) You want to track who has been downloading your contact info; 6) While your competitors' contact info is lying on their desk in a pile of business cards! 7) You want to make it simple to manage all Exchange signatures. Active Directory Integration The Active Directory Integration component provides a secure real- time solution for mirroring user s contact details from an internal Active Directory domain up to the ContactMonkey Contact Cloud service. The ContactMonkey for Business service comprises of 3 parts: Active Directory Extender (ADE) [OPTIONAL] Active Directory Integration (ADI) DNS Integration and Branded Cloud The ContactMonkey for Business service supports a range of mail servers that can provide access to Active Directory merge fields for signature/disclaimer templates, including Microsoft Exchange and Lotus Notes. Active Directory Extender (optional) The internal Active Directory Schema (User object class) is extended using the ADE in order to support a new optional attribute named contactmonkeyurl. This attribute will be used to track each user s unique ContactMonkey identifier which provides the contact details for the user on the ContactMonkey Contact Cloud service. Using the ADE is a onetime operation and would only require repeating during Active Directory migrations. NOTE: This part is optional; if you do not wish to extend your Active Directory you may choose an existing attribute to hold the ContactMonkey identifier.

2 Active Directory Integration The main ADI component is installed as a Service that runs locally within the internal LAN, the component is configured to your internal domain details and a ContactMonkey API Key will be received. Your API key is used to ensure all users using the service are locked to your companies branded cloud on ContactMonkey. The ADI component is currently limited by user group within the local AD, the domain administrator is free to define their own group for limiting users of the service, alternatively, we provide a default group ContactMonkey User Group which you will need to create within the Users container. When the ADI service is started the component creates a new local database which will be used to keep track of any user changes between the local AD and the ContactMonkey Contact Cloud service, and then it starts its main process which is outlined below. 1) The ADI service polls the local AD for the members of the named group as specified in the configuration. A comparison is then completed against the ADI database to acquire the status of each user (ADDED / REMOVED / UPDATED) and takes the appropriate action via the secured web services in the cloud. 2) The ADI service then executes a long running LDAP search on the users; this is an asynchronous request that gives real- time feed back to the ADI service to notify of any changes. The LDAP query runs for a period of 24hrs, during which time any changes to the watched users / group will be pushed to the web services in the cloud. 3) After the LDAP request has completed (24hrs), a new poll of the group is performed and the cycle begins again from step 1. The sub set of fields that are mirrored to the ContactMonkey Cloud are; First name Initial Surname Internal External SMTP Telephone Mobile Fax Street Locality State/County Postal code Country WWW Homepage Job title Company name Further fields maybe used; please contact us to work out your requirements. All communication between the ADI service and the ContactMonkey Contact Cloud is executed over HTTPS, and at NO point does the ContactMonkey Contact Cloud create an inbound connection to your internal LAN.

3 DNS Integration and Branded Cloud In order to provide a seamless switch it is necessary for your DNS Administrator to create a new A record pointing to the ContactMonkey Contact Cloud service, we suggest you name this contacts.yourcompanyname.com. The purpose of the DNS pointer is to provide you with a branded website for which you will need a company logo that can be ed to us directly. Once this process is completed you will be able to login and manage your company user contacts by accessing All users of the system will then have a card that can be accessed directly (e.g. Please note the unique identifier (in this case MarkWestwood ) corresponds with the contactmonkeyurl attribute or optional attribute. It is this field that you would then use to build an Exchange template signature using the Active Directory merge fields of most 3 rd party disclaimer/signature applications. An example signature may look something like the following: Mark Westwood Acme Limited, 100 Acme Drive, Kent, W12 6BD, England Telephone: +44 (0) Mobile: +44 (0) Fax: +44 (0) mark@acme.com Add me to your address book - it's easy! When the user sends out an and the receiver clicks on the link provided they will then be presented with options to download your contact details in one of the supported formats: Outlook, Outlooks Express, Lotus Notes, Goldmine CRM, Act by Sage, Mac Address Book, Mac Outlook, Entourage Gmail, Yahoo, Windows Live, Salesforce.com iphone, BlackBerry, Android 2.2+,WindowsPhone After downloading the contact details the visitor has the oppportunity to register for updates, whenever an update to your contact details occur the visitor will be notified so that they may again download your most recent details. Figure 1 provides a high level diagram of the complete solution. Requirements In order to install the Active Directory Integration service you will need an Active Directory domain server or member server with the following: Microsoft.NET 4.0 Access to Microsoft Windows 2003 / Windows 2008 Access and write permissions to the Active Directory

4 To take advantage of the Active Directory merge fields within signatures / disclaimers you will need to be running either a mail server that supports direct integration with Active Directory or a 3 rd party application for that purpose (see below). Microsoft Exchange 2010 now supports this feature directly. Signature / Disclaimer Templates A number of software providers support Active Directory merge fields for the purpose of signatures and disclaimers. Exclaimer - Policy Patrol - Code Two - Gfi MapiLab

5 Figure 1: Logical flow of communication ContactMonkey for Business User ( recipient) Notification service User ( recipient) Contact request ContactMonkey Contact Cloud contacts.yourcompanyname.com HTTPS Company Firewall HTTPS Member Server.NET 4.0 ADI Service Active Directory Group Poll LDAP Search Requests Active Directory 2003 / 2008