• Lucas Bueno de Carvalho
  • NEWBIE
  • 0 Points
  • Member since 2018

  • Chatter
    Feed
  • 0
    Best Answers
  • 1
    Likes Received
  • 0
    Likes Given
  • 2
    Questions
  • 0
    Replies

Hello!

We are trying to find a solution to a issue about Omni Channel Routing.
Actually we are thinking about using skills-based routing, but this is only the first idea.
Well, we have some skills for our agents and all of the agents have all the skils, varying only on the skill level. So, we are in a situation like:

Senior Agents have the Active Clients Skill with skill level 10.
Junior Agents have the Active Clients Skill with skill Level 7.

When I create a PendingServiceRouting and we have a Active Clients Skill related to it, we expected the following result:
Omni channel first try to push the item to Senior Agent. With none Senior agent is available, Salesforce try to push it to Junior Agents. All this based on the skill level.
The problem is that Salesforce always route the work item based on the time it was created or by priority, never considering something like "the best agent first".

Can anybody help me with a solution or a idea?

 

We are doing this because today we have 3 kinds (the most qualified represents 5% of our clients, qualified 60% and non qualified 35%) of clients and all of our agents can give support to them. Otherwise, our most qualified client should be "helped" by our agent with best skill. This way of thinking can solve some problems, like:
- Seniors Agents will have as work items as the others.
- Qualified clients can have preference in waiting time.
- Qualified clients can have preference in best support.


Can someone give me a hand?



 

We are building some integration consuming Salesforce custom REST Service. When we build the call in JavaScript everything works pretty well using the following code:
 
var payloadConnection = {
	companyId : '1',
	serviceCode : 'SalesforceLogin',
	endpoint : '/services/oauth2/token',
	method : 'POST',
	dataType : 'text',
	headers : {
		"content-type" : "application/x-www-form-urlencoded",
		"cache-control" : "no-cache"
	},
	options : {
		"mediaType" : "application/x-www-form-urlencoded"
	},
	params : {
		grant_type : 'password',
		client_id : SALESFORCE_INTERFACE_CLIENT_ID + '',
		client_secret : SALESFORCE_INTERFACE_SECRET + '',
		username : USERNAME + '',
		password : PASS_SECRET + ''
	}
};

var clientService = fluigAPI.getAuthorizeClientService();
var vo = clientService.invoke(JSON.stringify(payloadConnection));
The problem is when we try to build the same call in AJAX format we are getting CORS erros. The code we are using is:
 
$.ajax({
	method : 'POST',
	dataType : 'json',
	url : integrationParameters.URL_CONNECTION,
	headers : {
		"content-type" : "application/x-www-form-urlencoded",
		"cache-control" : "no-cache"
	},
	data : {
		"grant_type" : "password",
		"client_id" : integrationParameters.SALESFORCEINTERFACE_CLIENT_ID,
		"client_secret" :  integrationParameters.SALESFORCEINTERFACE_SECRET,
		"username" : integrationParameters.USERNAME,
		"password" : PASS_SECRET
	},
	success : function(data) {
		// success
	},
	error : function(data, errorThrown, status) {
		// error
	}
});

Even Ip's and websites from we are making the calls were added to CORS, IP Ranges and Network Access. When we use the same code in POSTMAN it works well.

We are getting the following error:
Failed to load resource: the server responded with a status of 400 (Bad Request)

Failed to load https://customDomain.my.salesforce.com/services/oauth2/token: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'https://website.com.br:8081' is therefore not allowed access.

The address returned in errors is also present in our configurations ("https://website.com.br:8081").


Does anyone have an idea about what is happening?

Thanks in advice for your help,
Lucas Carvalho

 

Hello!

We are trying to find a solution to a issue about Omni Channel Routing.
Actually we are thinking about using skills-based routing, but this is only the first idea.
Well, we have some skills for our agents and all of the agents have all the skils, varying only on the skill level. So, we are in a situation like:

Senior Agents have the Active Clients Skill with skill level 10.
Junior Agents have the Active Clients Skill with skill Level 7.

When I create a PendingServiceRouting and we have a Active Clients Skill related to it, we expected the following result:
Omni channel first try to push the item to Senior Agent. With none Senior agent is available, Salesforce try to push it to Junior Agents. All this based on the skill level.
The problem is that Salesforce always route the work item based on the time it was created or by priority, never considering something like "the best agent first".

Can anybody help me with a solution or a idea?

 

We are doing this because today we have 3 kinds (the most qualified represents 5% of our clients, qualified 60% and non qualified 35%) of clients and all of our agents can give support to them. Otherwise, our most qualified client should be "helped" by our agent with best skill. This way of thinking can solve some problems, like:
- Seniors Agents will have as work items as the others.
- Qualified clients can have preference in waiting time.
- Qualified clients can have preference in best support.


Can someone give me a hand?