Match My Email is the culmination of 10 years of doing one thing well, email integration for Salesforce

In the early days of UNIX, way back when before the Internet, cloud computing and Instagram, the visionaries that invented UNIX at Bell Labs, Ken Thompson and Dennis Ritchie, published a philosophy of software development. At the time, their ideas were revolutionary and represented a paradigm shift about how software should be written1.

Rule #1 of the UNIX creed is “Make each program do one thing well”2.

Back in 2009, when the development team at Match My Email was formed, it was instructed to follow the UNIX philosophy and focus on one thing: email integration for Salesforce. All of the other companies working on email integration, including Salesforce, took a different approach. They spread their development resources over a number of integration points – calendar, contacts, tasks and email. As a result, ten years later, Match My Email is acknowledged as the very best email integration app for Salesforce, whereas the other companies offer email integration tools that lack features, flexibility and the ability to work with a full range of email systems.

The developers at Match My Email were given five design goals.

  1. Automate the Salesforce email syncing process
  2. Capture email activity metadata for analytics
  3. Work with standard and custom Salesforce configurations
  4. Enable remote user activation and management
  5. Connect to as many email systems as possible

These design goals were driven by a set of use cases that the Salesforce community was demanding.

  1. Users don’t like to do data entry; they want an automated tool that syncs emails for them in background, from any device or computer and in real time.
  2. Users want the email data in Salesforce to be well organized and easy to read
  3. Users want to know that every email is captured in Salesforce in every relevant record automatically, no email is missing
  4. Users want to see the emails that their colleagues have sent or received from customers in shared SFDC records
  5. Users hate duplicate emails in Salesforce so make sure duplicates don’t happen
  6. Users hate attachment clutter, e.g., signature logos and social media icons filling up Salesforce records, so remove them
  7. Users expect emails to associate with standard and custom SFDC records
  8. User want emails to sync to the right Opportunity even if multiple Opportunities are open for the same customer
  9. Users need a tool to easily create new Salesforce records from email data
  10. Users don’t want to be involved in the app setup
  11. Users want to know that privacy controls are in place so their emails are shared with the right people
  12. Sales managers want email activity data so they can create reports that track user productivity and response times

Ten years later, the Match My Email development team can declare victory. By concentrating their efforts on one goal, email integration for Salesforce, they have built the most advanced, easy to use program on the market. The excellence of their creation is being recognized by more and more Salesforce users who try Match My Email and then find they can’t imagine working in Salesforce without it.

If you would like to experience the joy of truly automated email integration for Salesforce, sign up for a free trial account on the Match My Email web site at https://www.matchmyemail.com/install-salesforce-email-integration/.

 

Footnotes
1. Philosophy of Unix by Malcolm McIlroy, Bell System Technical Journal
  1. Make each program do one thing well. To do a new job, build afresh rather than complicate old programs by adding new “features”.
  2. Expect the output of every program to become the input to another, as yet unknown, program. Don’t clutter output with extraneous information. Avoid stringently columnar or binary input formats. Don’t insist on interactive input.
  3. Design and build software, even operating systems, to be tried early, ideally within weeks. Don’t hesitate to throw away the clumsy parts and rebuild them.
  4. Use tools in preference to unskilled help to lighten a programming task, even if you have to detour to build the tools and expect to throw some of them out after you’ve finished using them.
2. Peter H. Salus, A Quarter-Century of Unix (1994)