Error: Compile Error: Invalid field CallerId__c for SObject TwilioConfig__c at line 19 column 59

[paulbfischer]

I receive a compile error when trying to manually create this class in a development org. I set the API version to 29.0, because our org is not using version 30.0 yet. I was not able to create the Visualforce pages because I believe a few items in the page are dependent on this APEX class.

When I open this class in the Developer Console and try to save there is a 'problem' that says 'TwilioClientController' line 2 Invalid type: TwilioCapability.

I followed the previous steps including successfully installing the Twilio library (From Pull Request 33 on Twilio-Salesforce github).

I installed the Twilio library in both production and sandbox. I updated the link from login.salesforce.com to test.salesforce.com and left the remaining extension was able to successfully install Twilio library in development sandbox.

[choppen5]

Ok - when you successfully install Twilio-Salesforce were you able to follow setps 2-5 from here? https://github.com/choppen5/TwilioSalesforceClick2Dial#non-package-install

I think we may have an issue, you have to do step 5 first, creating the CallerId field in custom setting first. If you can confirm, I'll update it.

[paulbfischer]

I can confirm this solved the issue.

A few other notes for others trying to accomplished this. I created the CallerID field first. I then created the class and Visualforce pages manually in a developer org by pasting the code in. I then put the class, the 2 Visualforce pages, and the Custom Setting in a change set, and pushed it to production.

I completed the deployment, created a site, tweaked the custom settings. You then need to import the call center definition file. I was unable to copy and paste this into a notepad doc and save as XML. Instead I downloaded the ZIP from Github and selected the XML file directly.

Then update your site info in Twilio. I'll try to write a more comprehensive step-by-step to make this even more obvious. Thanks Charles! We're really excited about Twilio!

On to adding directing inbound calls to the browser, and being able to answer that call! If anyone has any softphones/CTI pre-built hit me up at paulfischer312 (at) gmail [.] com.

[choppen5]

Great to hear Paul. I've updated the instructions to change the order. In theory, if a user goes through the "non package install", then the could go through all the other steps. If you have any updates, do a pull request with updates..

About inbound routing, we actually have a pull request to this repo contributed by c6a130a - that does some basic inbound routing.

Another option is this repo - https://github.com/choppen5/client-acd - this provides inbound routing and some other features inside of Salesforce.

[paulbfischer]

Cool, thanks Charles! That last repo with a Heroku site looks nice! Any idea on what 40 users taking inbound calls w/ low - med. (2 hours per day each max) talk time with cost on the Heroku side?

I've heard bad things about using Twilio with Salesforce sites for inbound. I'm going to play with the first pull request to see if I can use it with our existing code pack. If so, we will buy 40 Twilio numbers and ramp things up (then possibly improve inbound with Heroku).

Thanks again!