Quakker ‐ Configuring endpoint for SMS in Salesforce - clorce/QuakkerPub GitHub Wiki
1. Before reading this guide 3
2. Configuring endpoint for SMS in Salesforce 3
a. Salesforce domain registration 3
4. Adding PLATFORM3S to remote site settings 6
-
Before reading this guide {#before-reading-this-guide}
The Quakker application is designed to handle telephone calls within the Salesforce system. It allows for receiving incoming calls and making outbound calls within Salesforce. Additionally, all conversations made through this application are recorded as activities and associated with a specific contact or account.
The solution is based on the Salesforce ecosystem. Therefore, for any difficulties related to basic functionalities, assistance can be found on www.trailhead.com (tutorials and instructions) or www.help.salesforce.com (technical documentation).
This instruction is the next step in expanding the Quakker application with the ability to send and receive text messages directly on Salesforce.
-
Configuring endpoint for SMS in Salesforce {#configuring-endpoint-for-sms-in-salesforce}
-
Salesforce domain registration {#salesforce-domain-registration}
-
Go to Setup -> Sites -> Register My Salesforce Site Domain
Check the checkbox next to the Salesforce Sites Terms of Use and click the button -> Register My Salesforce Site Domain.
After refreshing Sites click 'New' and fill in the data :
- Site Label: InboundSMS,
- Site Name: InboundSMS,
- Active Site Home Page: AnswersHome,
- Clickjack Protection Level: Don't allow framing by any page (Most protection).
Only checkboxes that you need are: Enable Content Sniffing Protection, Enable Browser Cross Site Scripting Protection and Referrer URL Protection (Screenshot).
After saving, we click 'Activate'.
-
Assign permissions {#assign-permissions}
- After site creation is finished click the 'Public Access Settings’ button and then ‘View users’ button, click the name of the user ‘InboundSMS Site Guest User’ and for the ‘Permission Set Assignment’ section click ‘Edit Assignment’ button.
- Assign ‘Quakker Inbound Text Messages Permissions’ permission set to the user and click ‘Save’.
-
Adding PLATFORM3S to remote site settings {#adding-platform3s-to-remote-site-settings}
Go to Setup -> Remote Site Settings -> New Remote Site
Complete the data and save.
- Remote Site Name: individual
- Remote Site URL: individual
-
First Login {#first-login}
After logging into Quakker for the first time as Quakker Admin, we go into settings and 'Text Messages Settings'. Complete the data and save.
The data is written to Custom Metadata Types (ccTextMessagesProviderSettings__mdt).
- Provider Name: individual
- Webservice Endpoint: individual
- API Username: individual
- API Password: individual
- Decryption Key: individual
- Agent Number: individual
Everyone can see the Sender Number field and it is simply a ccAgentPhone a user* field, it should be completed with a country code such as 48 xxx-xxx-xxx.
Contact {#contact}
If you want to contact us, write to [email protected]
and we will try to answer all your questions.