WFM + Dixa

Dialpad WFM's Dixa integration seamlessly pulls historical data from Dixa to provide valuable insights within your Dialpad WFM dashboard.

Forecast demand, create schedules, and track performance by integrating your Dixa voice, chat, or messaging ticket data into Dialpad – the exclusive WFM for Dixa.

Connecting Dialpad and Dixa is a 2-step process. First, you’ll need to create a Dixa API key, and then you’ll need to connect Dialpad WFM to Dixa.

Let’s dive into the details.

Who can use this

Dialpad WFM is available to all Dialpad users.

Contact your Customer Success Manager to discuss adding Dialpad WFM to your plan.

Create Dixa API key

An API key, which a Dixa admin can generate, is required to connect Dialpad WFM to your Dixa account.

To generate a Dixa API key, go to your Dixa Settings.

1. Navigate to Manage

2. Select Integrations

3. Choose API Tokens as a card, the select Configure API tokens

4. Select Add API token

5. Name the API token

   1. We recommend naming it Dialpad WFM.

6. Choose Dixa API as the API version, then select Add API token

7. Copy the token and make a note of it
   

Connect Dialpad WFM to Dixa

Now that you have your Dixa API token, its time to connect Dialpad WFM to Dixa.

To connect Dixa, go to your Dialpad WFM Settings.

1. Navigate to Integrations

2. Select Customer service

3. Select Connect to Dixa
   

4. Enter your Dixa API key

5. Select Save

That’s it! Your Dixa account will be connected and ready for forecasting.

Frequently asked questions

What ticket data does Dialpad retrieve?

Dialpad can only see your ticket volumes, not ticket content. Content is redacted when we collect your data.

Which agent actions are tracked in Dixa?

Dialpad WFM tracks agent’s interactions with tickets in Dixa to create comprehensive activity timelines and performance metrics.

These interactions are categorized as follows:

• Status Changes

  • Tracks when an agent changes the status of a ticket assigned to them (e.g., OPEN to CLOSED)

  • Records when tickets are reassigned, including the first time it’s assigned

    • The interaction will be labeled with the ticket's status at reassignment (e.g., OPEN)

    • The interaction will be attributed to the new assignee, not the agent who did the reassigning

    • Status changes to unassigned tickets are not tracked

• Comments

  • Captures when an agent sends messages or responses to customers

  • Captures when an agent adds an internal note

  • The interaction will be attributed to the author, not necessarily the ticket assignee

Dialpad WFM uses generic ticket status categories to fit with multiple integrations. The equivalent mapping for Dixa is as follows: