Project Description

The main goal for a client was to cut down manual data entry from Zoho CRM to QuickBooks. For that reason, we developed an automated solution that allows to automatically sync Zoho CRM Invoices with QuickBooks. The basic flow is set to where once Invoice reaches a certain status – we send data into QuickBooks.

For both systems to communicate we had to set the middleman database to store items that are getting synced. Such database is having its own user-friendly interface that allows a user to see the status of the connector.

Here is a list of data points that can be synced:

• Accounts & Contacts
• Products & Items
• Quotes
• Invoices
• Purchase Orders
• Sales Orders
• And more…

For this particular project, we used 4 data categories. Products, Accounts, and Invoices with line items. Each of these categories has its own section within the report page.  Basically, the Quickbooks database mirrors Zoho. Upon initial sync, the system checks if there any changes made in Zoho to any of data points. If something does not match it will insert/update missing info.

Once data transfer completed, a user is able to see what is synced, what not as well as sync errors if any. There are additional buttons were set to re-upload newer version of the invoice in case of revision.

Before setting up the connector, we’ve set certain validation rules to prevent sending invalid data and to meet QuickBooks field standards.

In Quickbooks production file client had to add a small (.qbc) file: File -> Update Web Services -> Add new.

Since now Zoho has exact same data as in QuickBooks – your revenue data will be 100% accurate. Now its time to build all sorts of reports and dashboards for the leadership team. Saved time on manual copy paste can be used for something more important.

Project Description

SalesForce customer portal allows customers to check their service details, review documents and update their information directly into CRM. All updates are real-time no matter where you do the change. Each user has its own login and password. There are times when the same contact is present in multiple accounts in SalesForce. Such users have access to multiple accounts within one customer portal profile. Admin has full control over access to the portal. There are all sorts of reports that are available to track customer interaction. For instance, a number of logins, registration date, last login time, login count, etc.

How it works

SalesForce Customer’s portal is a standalone application that works bi-directionally with CRM. By leveraging apex triggers we are able to push information into portal’s database. In other words, updated information immediately displayed within the account.

We used a bootstrap template to produce user interface. Therefore, we can ensure that the page is user-friendly no matter what device is used. On the other end, any update from portal goes straight into SalesForce via a custom made connector.

A user also has different contact tools within the portal which will appear as cases in Salesforce. To ensure data quality, we’ve set some validation rules on both ends.

Results & Big Wins

A client was able to save time on a phone that was used to spend on sending reports and other PDFs. Customers are now having quick access to their documents and account information. They are also able to interact with customer service within the portal. All conversations are now in one place. This allows to run reports and have a better vision over the customer service department. The sales team can add this feature to the company’s portfolio when getting new customers. The solution itself is way cheaper than SalesForce Communities.

Project Description

The main goal for a client was to cut down manual data entry from Salesforce to QuickBooks. For that reason, we developed an automated solution that allows to automatically sync salesforce opportunities with QuickBooks. The basic flow is set to where once Salesforce Opportunity reaches a certain stage – we send data into QuickBooks.

For both systems to communicate we had to set the middleman database to store items that are getting synced. Such database is having its own user-friendly interface that allows a user to see the status of the connector.

There are 3 main data categories to be synced. Products, Accounts, and Opportunities with line items. Each of these categories has its own section within the report page.  Basically, the Quickbooks database mirrors SalesForce. Upon initial sync, the system checks if there any changes made in SF to any of data points. If something does not match it will insert/update missing info.

Once data transfer completed, a user is able to see what is synced, what not as well as sync errors if any. There are additional buttons were set to re-upload newer version of the invoice in case of revision.

Before setting up the connector, we’ve set certain validation rules to prevent sending invalid data and to meet QuickBooks field standards.

In Quickbooks production file client had to add a small (.qbc) file: File -> Update Web Services -> Add new.

Since now Salesforce has exact same data as in QuickBooks – your revenue data will be 100% accurate. Now its time to build all sorts of reports and dashboards for the leadership team. Saved time on copy paste can be repurposed to something else.

Project Description

SalesForce ecosystem has a relatively low entry level, which means lots of things can be set by non-certified users. As the company grows, more and more processes are added. It may become an even bigger problem if multiple users are making changes to the back end. On average it takes about two years to clog the CRM. Like stated above, Salesforce is very user-friendly but it is still a database.

Our client had an ongoing issue with data in their Salesforce org. They were having lots of unnecessary fields, validation rules and annoying email notifications for every cause.

For that reason, we came up with checklist & action items:

Audit Existing Fields (Standard & Custom Objects)

• Field Usage Report: We’ve built a report to display field usage per object. By seeing usage percentage – department heads were able to quickly identify what can be deleted.
• Lookup Fields: We had to ensure that objects are related correctly. Sometimes native relations are replaced with custom lookups. Ex: There is a standard lookup field on Order to Opportunity that is replaced by custom lookup field.
• Field Types: Sometimes a field that supposed to be a currency is a number type. Or number field is actually a text field type. We’ve resolved all the above.
• Page Layouts: After determining fields that are needed, everything else is removed from page layouts. After a certain time, unused fields are erased.