Sugar CRM Generic Web Launcher usage

Sugar CRM Generic Web Launcher usage

SugarCRM & Web Launcher

So let's say that you have your own SugarCRM implementation.  You would like to open a contact or opportunity by the incoming Caller ID if it matches something already in your Sugar database.

 

The search string for this type of search would be like:

http://crm.fonality.com/index.php?module=Home&action=UnifiedSearch&query_string=%%caller_number%%

 

In the string above, crm.fonality.com should be changed to YOUR COMPANY'S SUGAR URL.

 

Now let's take a moment to discuss the pitfalls here:

  1. The phone number stored in Sugar must match exactly the Caller ID information sent by your phone company.

    1. If you have a phone number like 310-861-4300 (with dashes), but the phone company sends3108614300 - the number won't match.

  2. Sugar may find more than one match, and return a list of possible results instead of an exact contact or opportunity.  This may or may not be what you want - but it's important to be aware of the possibility.

 

You could, instead of the above URL, send the call to a CGI that formats the number for you as you have information stored in Sugar.  So you could write a simple CGI that runs a PERL script to perform some simple formatting on the phone number so that it will match your Sugar input.

Looking for labels? They can now be found in the details panel on the floating action bar.

Related content