Labsco
MCP SERVER

Salesforce Order Concierge

by gellasangameshgupta ↗

Answer a customer's "where is my order" and open the return, the case and the Slack alert behind it, all from the conversation.

Customer Support & Helpdesk
Summary
The whole return path, in one conversation instead of five tabs.

Checking the order, cutting the return, mailing the label, raising the case and telling the team are five screens in Salesforce and Slack. Here they are five calls an agent can make in order, on standard objects rather than a custom returns model.

What it is

A Node server over a Salesforce org, shaped around one job: the return desk. It reads order and shipping status, creates a standard Salesforce ReturnOrder, emails the label, opens or updates the support case, and posts a Slack alert.

What you get
  • Order status with shipping details and tracking information
  • Return orders created as standard Salesforce ReturnOrder records
  • Return shipping labels emailed to the customer
  • Support cases opened from a return, and existing cases updated with new priority or assignment
  • Formatted alerts posted to a Slack channel
Requirements

A Salesforce login: SF_LOGIN_URL, SF_USERNAME, SF_PASSWORD and SF_SECURITY_TOKEN in the client config, plus SLACK_WEBHOOK_URL if you want the alerts. Built with npm install and npm run build. Custom fields and flows ship as optional Salesforce metadata you can deploy with the sf CLI.

Setup effort

Build from source — clone the repository and build it, then point your client at the binary