Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

API: This page summarizes currently exposed APIs for integration with virtual queues. I believe the most interesting one is the webhooks mechanism as it exposes most of the events from the system to a third party.

Common integration ideas and integrations that were done in the past:

...

This document outlines common integration strategies using our platform's capabilities, particularly focusing on webhooks and APIs. These integrations enable seamless connections with customer relationship management systems, customized booking interfaces, and mobile applications, enhancing both operational efficiency and user experience.

CRM Integration Using Webhooks

  • Purpose: Our service sends information about tickets and bookings via webhooks to another web service that , which then maps integrates this information data into CRM customer activities.

  • Benefits: This allows you to capture the capturing detailed information about customer visits or customer feedback in your system and associate associating it with your existing CRM customer profiles. In general, data flowing Data received from webhooks can be captured and used for anything: Webhooks integration

 

  • Building own booking UI using our APIs in order to, for example, include a payment gateway in the flow – we have exposed APIs that let you build your own customer-facing booking flow using our APIs that will seamlessly integrate with walk-in queue and still gain all the benefits of using Grid Platform; Analytics, Queue manager, Digital Signage.

 

  • Mobile app integration through embedding our booking UI inside the app – embed web-based booking UI in the app

 

  • Mobile app integration using native UI, but our APIs – build your own UI for the customer journey, but use our APIs
     

  • Mobile app notification integration – create a position/booking and associate with push notification identifier. Using the webhooks mechanism you can then capture information about ticket/booking status updates utilized extensively for various purposes.

Building a Custom Booking UI

  • Purpose: Utilize our exposed APIs to create a custom booking interface for customers, potentially including a payment gateway.

  • Benefits: This approach allows organizations to maintain all benefits of the Grid Platform, including analytics, queue management, and digital signage, while offering a tailored booking experience.

Mobile App Integration

  • Web-based UI Embedding: Embed our web-based booking UI directly into a mobile app.

  • Native UI with APIs: Develop a custom UI for the customer journey using our APIs, providing a native app experience.

  • Notification Integration: Create positions/bookings associated with push notification identifiers. Use webhooks to capture status updates on tickets or bookings and send native mobile app notifications instead of default traditional SMS or email notifications
     BONUS: we .

Custom Domain/URL Branding

  • We can set a custom domain/base URL for booking and ticket pages to further brand the service further and make sure , ensuring customers feel comfortable and maintain brand consistency by staying within the a familiar domain name

 

...

  • .

These integration ideas demonstrate the versatility of our platform, offering multiple pathways to enhance customer interaction and backend processes through smart, scalable solutions.