One rule is not always enough.

Start with the information. Not the logos.

We start from what support needs to know to help the customer, and then look at how that information can be retrieved.

CRM

Customer view, contact details or contracts needed for the chosen ticket type.

ERP

Order status, invoices or other agreed information that otherwise has to be looked up manually.

Existing helpdesk

Channels and ticket history included in the rollout. You do not have to assume everything will be replaced.

Examples of systems we connect to.

These systems are examples, not finished standard connections. We go through your technical prerequisites and build the connection as part of the rollout.

CRM

HubSpot · Salesforce · Dynamics

ERP

Business Central · Fortnox · Visma · Monitor · SAP · Jeeves

E-commerce

Shopify · WooCommerce · Magento

Payments

Stripe · Klarna · Fortnox

Logistics

PostNord · DHL · Bring · nShift

Knowledge sources

Google Drive · Notion · Confluence · SharePoint · Your website

Reading is not the same as changing.

Retrieving order status and changing an order require different permissions. A read connection does not automatically mean Supportifier can perform actions in the system. That is specified separately.

This is what we go through together.

Bring the names of the systems and an example of a question that requires someone to leave the inbox to find the answer.

Access and identity

What information is needed? How is the customer identified, and who may see the information?

Technical prerequisites

Is there a suitable API or other permitted access? How are errors and stale information handled?

Scope and responsibility

What should the connection do, how is it followed up and what is included in rollout and maintenance?