Integrate Five9 with Krisp as a call source

Who can use this feature?

Plan: Call Center AI
Managed from: Admin Portal
User type: Admin

Summary:

  • Direct server-side integration that sends Five9 call events to Krisp through a Five9 Event Subscription
  • No Five9 credentials are shared with Krisp: Krisp gives you a webhook URL, header name, and secret
  • Available for email-based teams, set up once per team
  • Krisp side: Integrations >>> Call source >>> Five9 >>> Connect team
  • Five9 side: Admin Console >>> Event Subscriptions
  • One call source per team, the secret is visible only once.

The Five9 integration lets Krisp receive call events directly from your Five9 domain, without relying on the Krisp Bridge browser extension. You set it up once per team: generate webhook details in the Krisp Admin Portal, then create an Event Subscription in Five9 that sends call events to Krisp.

The Five9 integration is currently in Beta.

Before you begin

Make sure you have:

  • Admin access to the Krisp Admin Portal (Org Admin or Team Admin)
  • An email-based Krisp team to connect
  • The Event Subscriptions add-on enabled for your Five9 domain. If you don't have it, contact your Five9 representative
  • A Five9 admin user with the eventssubscript permissions to view, create, and start event subscriptions.

  Important

Krisp receives call events from one source per team. If the team currently uses Krisp Bridge or another CCaaS integration, Krisp asks you to confirm the switch when you connect Five9. The previous source stays active until Krisp receives the first event from Five9, so there's no gap in call events during setup.

If Krisp Bridge is enforced for the team through a policy, confirming the switch also removes the team from that policy.

Step 1: Generate webhook details in the Krisp Admin Portal

  1. In the Krisp Admin Portal, go to Integrations >>> Call source.
  2. On the Five9 card, click Connect team.
  3. From the Team dropdown, select the Krisp team to connect, then click Generate webhook details.
  4. Copy the Webhook URL, Header name, and Secret. You'll paste them into Five9 in the next step.

The team can't be changed after the connection is created. To connect a different team, disconnect the integration and start again.

  Important

The secret is shown only once. Copy it before leaving the page. If you lose it, you can regenerate it later from the integration settings.

Keep the Krisp page open while you work in Five9. It shows a short version of the setup steps, and Open Five9 in new tab opens Five9 for you.

Step 2: Create an Event Subscription in Five9

For full details on event subscriptions, see the Five9 guide: Creating an Event Subscription.

  1. Sign in to the Five9 Admin Console and open Event Subscriptions, then create a new subscription.
  2. Enter a Name, for example "Krisp".
  3. Under Delivery Method, select HTTPS and POST, then paste the Webhook URL from Krisp.
  4. Under Header Attributes, add a header:

    • Key: the Header name from Krisp (X-Krisp-Webhook-Secret)
    • Value: the Secret from Krisp.
  5. Under Configure Event Groups, select the InteractionEvent group. Don't add any filters.
  6. Select the following events:
    • Offered
    • Accepted
    • PutOnHold
    • RetrievedFromHold
    • AgentEnded
    • Rejected
    • Ended.
  7. Keep all fields selected.
  8. Click Create, then click Start to activate the subscription.

  Hint

A new subscription doesn't send events until it's started. If the Krisp status stays on waiting, check that the subscription is active in Five9.

Step 3: Finish the setup in Krisp

  1. Go back to the Connect Five9 page in the Krisp Admin Portal.
  2. Click I have finished setting up. The secret is masked from this point on.

The integration status shows Waiting for the first Five9 event until Five9 sends its first call event. Once Krisp receives it, the status changes to Connected, along with the last time Krisp received an event from Five9.

Manage the integration

After setup, you can see which users with app access are mapped to Five9 and which are not.

Regenerate the secret

If the secret is lost or exposed, regenerate it from the integration settings. After you confirm, the old secret stops working right away and the new one is shown once for copying. Update the header value in your Five9 subscription with the new secret, otherwise Krisp stops receiving events.

Deactivate or disconnect

Action What happens
Deactivate Krisp stops receiving events. Webhook details and user mappings are kept, so you can turn the integration back on without repeating the setup.
Disconnect The webhook URL, header, secret, and all user mappings are deleted. To connect again, start from Step 1.

After disconnecting, stop or delete the Event Subscription in Five9 as well, so Five9 no longer tries to deliver events to Krisp.

Have more questions? Submit a request

Was this article helpful?
0 out of 0 found this helpful