Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Wow, you really can't track an email for a contact that is not on a list? How annoying is that! That makes the low end version of SalesforceIQ with one list almost impossible to use. Unless you have a field on your list for Type of Contact maybe. Hopefully I'm missing something. 
    • Even as a a micro business, I still have all sorts of different people I want to track - clients, leads, suppliers, co-partners working on the same project, clients' suppliers, clients' app vendors, and I want to track emails against them.
    • It does not appear in the lower end version plan, but even as a micro business, I don't think I can get away with using the lower end version plan. 
  • You can't add additional contacts fields, but you can add additional Accounts fields - weird, weird, weird. Especially if you use a contact-first model for your lists. 
  • Whist the starter plan includes 1 list, it seems you can not use the chrome extension to add people to the list. This makes the chrome extension kinda useless then. 

Missing bits

  • It's ALL about emails - no web to lead, no website tracking - I gather that's where the Hubspot integration comes in. 
  • Outlook! If you don't use Gmail, you can't use SalesforceIQ for Calendar integration from the looks of it. Weird. 
  • No Campaigns. Well, I guess you could use different lists in the high end version of SalesforceIQ to function like Campaigns, and with the integration with Mailchimp you have some email marketing, but Campaigns are more than that. 
  • Whilst Zapier is good, and I can see it will be GREAT for updating the Stream when things happen in your OTHER APPS, Zapier is not ideal for some purposes, and it is not "enterprise level", set and forget software. See my blog post on integrations.  
  • I can't associate emails ABOUT the client WITH the client. Eg, I email support from Company X about Client Y. I would like to record that email against my "Project" list. 
    • I could probably add a field to the Account, but that then de-normalises the data model - I can only have one related contact to an account rather than multiple. 
  • Beware of using Email Aliases, and probably stick with Gmail for emailing. 

...