Cubu Docs
Technical Guide
Technical Guide
  • Welcome to Cubu's Technical Guide!
  • White Papers
    • Data Protection
    • Sign On and Authentication
  • Advanced Configuration
    • Configuring Video Meetings
      • ⚒️Using Microsoft Teams for Video Meetings
      • ⚒️Using Zoom for Online Meetings
    • Calendar Integration
      • ⚒️Configuring Microsoft Office 365 Calendar Integration
      • ⚒️Configuring Google Workspace Calendar Integration
    • Configuring Single Sign On (SSO)
      • ⚒️Configuring SSO with Azure AD
      • ⚒️Configuring SSO with Okta
      • ⚒️Configuring SSO with Auth0
    • Configuring Chatbots
      • Configure Chatbot using WhatsApp
  • Webhooks
    • Webhooks Configuration
    • Developing Webhooks
      • Dev Tools
      • HMAC Validation (ASP.NET Core)
    • Webhooks Reference
      • Organization Webhooks
        • 🪝Webhook: Send SMS
      • Data Table Webhooks
        • 🪝Webhook: Query
        • 🪝Webhook: Find
        • 🪝Webhook: Fetch
      • Service Webhooks
        • 🪝After Book Appointment
        • 🪝After Check In
        • 🪝After Close
        • 🪝Before Book Appointment
        • 🪝Before Check In
        • 🪝Before Queue-Up
        • 🪝Before Resolve
        • 🪝After Queue-up
        • 🪝After Resolve
        • 🪝After Start Work
      • Kiosk Webhooks
        • 🪝Before Query Appointments
  • Server to Server (S2S) API
    • Server to Server (S2S) API
Powered by GitBook
On this page
  • Overview
  • API
  • URL
  • Request Body
  • Response Body
  1. Webhooks
  2. Webhooks Reference
  3. Service Webhooks

After Resolve

Overview

This webhook is called after an agent has resolved the case.

DEC 2024 B Release

API

URL

[base-url]/service/actions/afterResolve

Request Body

The webhook receives the following input:

  • caseId: The case ID to be created.

  • parentCaseId: The parent case ID (when applicable).

  • referenceDate: The case’s reference date.

  • unitId: The ID of the service’s parent unit.

  • serviceId: The service used for creating the case.

  • serviceCategoryId: Service category ID.

  • serviceTypeId: Service type ID.

  • status: The case’s target status (Pending/Waiting).

  • channel: Communication channel (Face-to-face, Video, etc.).

  • language: The preferred communication language.

  • ticket: The ticket number

    • prefix

    • number

    • suffix

  • fields: A Dictionary of fieldTypeId + fieldValue pairs.

  • tagIds: An array of tag IDs (for future use).

  • customerRecordId: The ID of the customer record linked to the case.

  • useCustomerContactInfo (bool): Indicates whether the linked customer record's contact information (phone number and email) is used as this case's contact information.

  • contactPhoneNumber: The case's contact phone number

  • contactEmail: The case's contact email

  • triggeredByUserId: The ID of the user who triggered this action (when applicable). The value is null when a Kiosk or the S2S API triggers the operation.

  • triggeredByUserEmail: The email address of the user who triggered this action (when applicable).

  • lockedByUserId: When an active case is resolved, this field contains the user's ID to the user processing the case. This field is null if a case is resolved while waiting or pending.

  • appointment

    • date: The appointment date

    • cuIndex: The calendar index (“Capacity Unit Index”)

    • start: The appointment start time, represented as the number of minutes past midnight.

    • timeLocal: The appointment’s date and time in the service’s time zone.

    • timeUtc: The appointment’s date and time in the UTC zone.

    • timeZoneId: The appointment’s service time zone.

    • duration: The appointment duration (in minutes).

    • preventSelfCheckIn: A boolean value indicating whether the customer can check in to this appointment using the kiosk.

Response Body

This webhook does not return data.

PreviousAfter Queue-upNextAfter Start Work

Last updated 5 months ago

🪝