Kustomer Implementation Steps

The following is a guide to implementing the Kustomer integration into Corso. The Corso x Kustomer integration embeds returns, warranties, and shipping protection claims directly into your Kustomer workspace, letting support teams create, manage, and resolve claims without leaving the CRM. This streamlines workflows, reduces platform switching, and ensures faster, more accurate customer support.

1) Install the Corso App in Kustomer

In Kustomer, install the “Corso” app.

2) Create a Kustomer API key

In Kustomer, go to Settings → Security → API Keys.

Create a new API key for Corso with the following permissions (you can copy and paste these values directly from the integration within the Corso admin):

org.admin.apps
org.permission.customer.read
org.permission.kobject
org.permission.klass

Set the key to never expire.

Copy the API key value.

3) Connect Kustomer to Corso

Return to Corso Admin → Settings → Integrations → Kustomer.

Enable the integration and open the integration settings.

Paste the Kustomer API key and Save.

4) Configure Corso App Settings in Kustomer

Finalize the integration by setting the Corso App config settings in Kustomer:

In Corso Admin Kustomer Integration settings (at the bottom), you’ll find the following ‘Corso App Settings’ to copy:

• Config Identifier
• Store Identifier
• Config Token

In Kustomer → Apps → Corso → Settings, paste those values into the same settings:

• Config Identifier
• Store Identifier
• Config Token

Save.

Back in Corso Admin Kustomer integration, you can optionally run a historical data sync to backfill historical data.

5) Verify

In Kustomer, search for “Corso” to confirm the app renders.

Verify that your customer has Shopify orders showing up in the Corso Customers panel on the right-hand side (this can take a few minutes after implementing the integration).

Open a customer timeline and confirm Corso cards load. You should see Corso claims show up as timeline entries and should be able to view, edit, and finalize claims.

6) User access alignment

Each Kustomer agent who needs to view Corso data must exist as a user in Corso with the same email address.

Invite any missing users in Corso Admin so emails match exactly.

---

Notes

After the steps above, Corso surfaces claims, registrations, and customer views directly in Kustomer.

If the app UI does not load, recheck the API key permissions and that Config ID, Store ID, and Config Token match the values shown in Corso Admin.