+1!!!! Great base for a demo as well.. Isabelle. __________________________________________________
Isabelle Mauny On Jul 22, 2014, at 4:30 AM, Shevan Goonetilleke <[email protected]> wrote: > Having all these connectors integrated together would form a good test for > the connectors that were previously developed and tested as standalone > connectors. Once developed and tested we should probably publish them as 4 > separate scenarios like - > 1. ZOHO CRM for campaign and lead management > 2. ZOHO CRM for order management > etc > > These can also eventually form separate recipes on the iPaaS. > > Any other thoughts? > > > > > On Fri, Jul 18, 2014 at 3:38 PM, Rasika Hettige <[email protected]> wrote: > 1. Overview > ZohoCRM is on-demand Customer Relationship Management (CRM) software as a > Service (SaaS) solution that delivers complete CRM functionality at a > fraction of the price of other offerings. With ZohoCRM you can manage all > your Sales, Marketing, Customer Support & Service, Inventory Management and > Email within a single business system. Hence it is not only an application or > tool but it is a way of doing business. > 2. Benefits of ZohoCRM > ZohoCRM has its own calendar through which meetings could be scheduled and > events could be managed. This facilitates easy follow up with clients and > leads. > > It is also a collaboration tool which has its own messaging and chatting > components through which the business opportunity is enhanced. > > ZohoCRM could also be easily integrated with external APIs such as Quickbooks > for financial and inventory management, Campaign monitor for lead management > and etc. > > Great value for money; It provides greater software applications for > businesses at reasonable and affordable prices. Therefore it increases > revenue at a lower cost. > 3. Zoho CRM Business Scenario > > In describing the business scenario of ZohoCRM, it can be divided into > sections such as Initiate Marketing, Process Sales, Manage Orders and Support > as shown below: > > 3.1 Initiate Marketing > > Step 1: Either campaigns and/or Leads can be created as the starting point of > ZohoCRM. > 1a. Create Campaigns > Create campaigns in Zoho CRM and create them as draft campaigns in Campaign > Monitor API. Email these campaigns to subscribers in Campaign Monitor API. > Post details of events related to the campaigns in the campaign owner’s > Facebook wall. > > Advantages of integrating with Campaign Monitor API > Campaign Monitor is an email marketing service, which can be used to publish > campaigns to bring more business to the company. > Advantages of integrating with Facebook API > Facebook can be used as a marketing tool where you can post your campaign > details on your wall and get interested individuals as leads in ZohoCRM. > > 1b. Create Lead > Create leads directly in Zoho CRM. > Lead creation can be done by retrieving the clicker’s details (who clicks on > the link) from the Campaign Monitor API. > Creating leads by retrieving information from the Twitter API (by searching > tweet contents or hash tags). > Leads can also be created by retrieving the caller’s contact details from the > CallRail API. > Associate leads with products which are either goods or services that can be > sold or purchased by the organization. > > Advantages of integrating with Twitter API > Twitter is an online social networking and microblogging service that could > be used to increase marketing and identifying leads in ZohoCRM by searching > tweet contents/ hash tags. > Advantages of integrating with Campaign Monitor API > Campaign Monitor can be used to aquire new subscribers(leads) in ZohoCRM. > Advantages of integrating with CallRail API > CallRail API is call tracking tool which can be used to capture caller > details as leads in ZohoCRM to initiate marketing. > > Step 2: Convert Lead > Convert the qualified leads to an Account (organizations) and Contact > (individuals), optionally a Potential (opportunity). > The contacts in ZohoCRM can be created as customers in Quickbooks for > accounting purposes. > If the lead is unqualified then the status is updated as Junk Lead. > 3.2 Process Sales > > Step 3: > Initiate sales process by creating Quotes. > Create quotes as estimates in Quickbooks for accounting purposes. > Step 4: > Once the order is won, it can be converted to a sales order and it could be > created in Quickbooks for accounting purposes. > If the order is lost, update the Potential/Quote as Closed-Lost in ZohoCRM as > well as update the estimates in Quickbooks. > Step 5: > Create invoices for the sales orders in ZohoCRM. > Create invoices in Quickbooks for accounting purposes. > > Advantages of integrating with Quickbooks API > As an accounting API, QuickBooks helps to record book-keeping functionalities > by mapping relevant financial details such as customers, invoices, sales > orders in ZohoCRM. > > 3.3 Manage Orders > > Step 6: > Create Vendors by retrieving vendors from Quickbooks. > Create Products by retrieving Items from Quickbooks. > Create Purchase Orders using the Vendors and Products in ZohoCRM and create > them in Quickbooks for accounting purposes. > Associate purchase orders with relevant contacts in ZohoCRM. > > Advantages of integrating with Quickbooks API > QuickBooks helps to record inventory management details such as items, > vendors and purchase orders in ZohoCRM. > > > 3.4 Support > > Step 7: > Create cases for feedback received for products in Zoho CRM. > Track these cases as issues in JIRA and follow them up. The issue comments in > JIRA can be updated in Zoho CRM. > > Advantages of integrating with JIRA API > Cases in ZohoCRM are used to track feedback received for products. JIRA API > can be used as a product tracking tool to discuss any product related issues > and track them until a solution is provided. This can be used in the support > phase of the ZohoCRM by mapping the solutions to cases. > > Thanks & Regards > Rasika > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > > > > -- > Shevan Goonetilleke > Director of Engineering > WSO2, Inc. > lean.enterprise.middleware > m: +94777340680 > w: http://wso2.com > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
