# Help Desk Support / ITSM  Automation via External Chat Browser

### 1.Use Case Overview

#### <mark style="background-color:yellow;">Objective:</mark>&#x20;

Enable IT support teams to automatically respond to IT-related issues (e.g., “Printer not working”) using the Soika AI Agent. The agent can collect user credentials, search knowledge bases, and escalate by raising a support ticket and assigning a technician based on the severity — all automated using natural language instructions.

#### <mark style="background-color:yellow;">Primary Actors:</mark>

* End User (Employee/Staff reporting an issue)
* Knowledge Base (PDFs, Confluence pages, internal documentation)
* Base row Database (Technician Directory + Ticket Management)

#### <mark style="background-color:yellow;">Target Platforms:</mark>

* WhatsApp
* Email
* External Web Chat Dashboard
* Internal IT Knowledge Base
* Base row (Database for Ticket & Technician info)

#### <mark style="background-color:yellow;">Business Value Proposition</mark>

The Soika AI HelpDesk agent helps organizations reduce IT support load by resolving common issues like “Printer not working,” “VPN not connecting,” or “Outlook not syncing” using predefined solutions. It minimizes response time, triages effectively, and ensures escalations are handled swiftly by qualified technicians.

#### Benefits:

* &#x20;80% faster query resolution
* Knowledge base leveraged automatically
* Auto-ticket creation with technician assignment
* Reduced support costs and manual triage
* Support via natural language (Email, WhatsApp)

### 2. Flow Summary

User gives prompt: *"* Create a General Agent which is a Customer Support Assistant integrated. Your role is to receive incoming queries by internal chat and manage them systematically using Base Row DB and Emails.”

* Soika creates an AI Agent tailored to Heldesk.
* AI Agent connects to Email Tool and Base Row DB tools via Authorization from Default tools.
* Tools request OAuth authorization (user grants access).

·         User Prompt to the Agent: “Hi, my printer is not working.”

System Response:\
→ AI Agent: “Please confirm your email and password for verification.”\
→ User provides credentials.\
→ Agent searches internal KB for known solutions.\
→ If not resolved: Agent checks Base row DB to find an available technician.\
→ AI Agent raises a support ticket (with severity = Medium or High).\
→ AI informs user: “Your case has been assigned to our technician \[Name]. You will be contacted in the next 30 minutes.”

### 3. Step-by-step process

### A. AI Agent Creation

<table data-header-hidden><thead><tr><th width="112">SL.NO</th><th width="705">STEPS TO BE FOLLOWED</th></tr></thead><tbody><tr><td><p> </p><p><br> Step 1</p><p></p></td><td>User opens Soika Mockingjay platform with Login ID and Password</td></tr><tr><td><p> </p><p>Step 2</p><p> </p></td><td><p>Ask Soika to Create an AI Agent based on the use case with Natural Language Prompt </p><p><strong>Example</strong> : Create a General Agent which is a Help Desk Support Assistant integrated. Your role is to receive incoming queries by internal chat and manage them systematically using Base Row DB and Emails.</p></td></tr><tr><td><p> </p><p>Step 3</p><p> </p></td><td><p> The Agent is created in the left panel : Help Desk  Support Assistance</p><p>Choose your LLM Model from the Agent in <strong>Edit AI-> AI Model-> llama3.3</strong></p></td></tr><tr><td>Step 4</td><td><p>Once Agent is created, you can upload your knowledge Base, by Clicking on</p><p>Edit AI--> Instructions  -> Knowledge Base ->Add Knowledge Base</p></td></tr><tr><td>Step 5</td><td>Once added, Enable it with the help of  toggle icon. Upload any Knowledge base based on your organization needs (E.g. IT_Support_Levels_with_Queries_and_Solutions.xlsx)</td></tr></tbody></table>

<figure><img src="/files/E4Yib9Qk0aKIjjQGjeA4" alt=""><figcaption><p>Soika created the Help Desk Support Assistance Agent</p></figcaption></figure>

<figure><img src="/files/ySrk3g02HtuCbyywziCz" alt=""><figcaption><p>Click on +Add Knowledge</p></figcaption></figure>

| Steps                                                                                                                                        | Instructions                                                                                                                                                                                                                                                                 |
| -------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| <p>Step 6 : Create two Tables (Table I & Table II in Base Row DB )</p><p> <strong>Click on the Link :  (<https://baserow.io/>)</strong> </p> | <p>Example: -</p><p><strong>Table I</strong>: Contains a database with Technician Details Based on the severity Label(Ref. below image).</p><p><strong>Table II:</strong> Agent will be resolved for creation of ticket based on the QUERIES, SEVERITY(Ref. below image)</p> |

<figure><img src="/files/ShxKqykp0Zx9tO2btQtB" alt=""><figcaption><p>Step 6: Table I</p></figcaption></figure>

<figure><img src="/files/UEPkJZ4ROlo0R0iBqJaQ" alt=""><figcaption><p>Step 6: Table II</p></figcaption></figure>

### **B. Tool Integration (Email + Base row DB)**

| <p> </p><p>Step 7</p><p> </p> | <p> </p><p>Connect the AI Agent with the Default Tools under the Edit AI -->Tools-->default Tools Section -->  Email  Tools and Base Row DB</p> |
| ----------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- |
| <p> </p><p>Step 8</p><p> </p> | <p> </p><p>Once Authorized, Enabled the tools with the help of Tools-> Tools Manager - Default -Toggle the button</p><p> </p>                   |
| <p> </p><p>Step 9</p><p> </p> | <p> </p><p>Once connected with the tools, Provide System Instructions from Edit AI-> System Instructions</p><p> </p>                            |

**Tools Authorized**

Email: <https://developers.google.com/workspace/gmail/imap/imap-smtp>

<https://myaccount.google.com/apppasswords>

&#x20;

**Base row DB**: [Grid - ITSM | Baserow](https://baserow.io/database/246844/table/609727/1140824)

**API URL**: <https://api.baserow.io>

<figure><img src="/files/QwoEv8ZaMeKhMiCB1ncY" alt=""><figcaption><p>Step 7 :Email Tool Authorization</p></figcaption></figure>

<figure><img src="/files/kzaJSaU0FqB0ItcfkDwI" alt=""><figcaption><p>Step 7 : Base  Row DB Authorization</p></figcaption></figure>

<figure><img src="/files/FCeD9Ty6iJPvVeWjjLW3" alt=""><figcaption><p>Step 8 :Enable the functionalities of Base row DB and Email</p></figcaption></figure>

### Accessing the External Chat Browser

Step I : Click on Edit AI-> General -> Change Visibility to Public -> Preview

<figure><img src="/files/w2b5LUItQMfkrsFAzCyB" alt=""><figcaption><p>Click on Preview</p></figcaption></figure>

Step II : Interact with the Agent via Speech or Text

<figure><img src="/files/qb5FlFtmAW3s3w9Zo1oZ" alt=""><figcaption><p>Use the microphone Icon for Voice  communication</p></figcaption></figure>

Step III : Agent accessing the Knowledge base for your query

<figure><img src="/files/zC7E7XMDq27mcB2XhQkL" alt=""><figcaption></figcaption></figure>

Step IV : Automatic ticket Generation  Example : Ticket- 123456, if your query is not resolved.

Tools used : Base Row DB to get the Customer support executive details.

<figure><img src="/files/HGHdAa0MEbgZj5ipaecD" alt=""><figcaption><p>Tools used by Agent for Automatic Ticket Creation</p></figcaption></figure>

### **Example of system instructions you can provide**

&#x20;You are an AI-Powered ITSM Support Assistant integrated into an internal chat system. Your role is to manage incoming queries systematically using Base Row DB and Emails. Follow the steps below to handle support queries efficiently. Ensure that the output does not contain any XML tags.

&#x20;

**Step 1: Receive and Interpret Query**

\- Upon receiving a message such as “I have an issue with the system and need help ASAP,” analyze the text to extract the core issue.

\- Ask the customer for their email ID and phone number.

\- Check the IT Support Knowledge Base (IT\_Support\_Levels\_with\_Queries\_and\_Solutions.xlsx) for known issues and resolutions.

\- Provide an initial resolution based on the knowledge base. For example, suggest actions like checking router status, restarting the PC, verifying credentials, or resetting the adapter.

&#x20;

**Step 2: Redirect to Base Row DB**

\- If the user is unsatisfied with the solution from the knowledge base, redirect them to the BASE ROW DB Table with Table ID (609727).

\- Use the table fields: Severity Level, Contact Person, and Contact Details.

&#x20;

**Step 3: Escalation Handling**

\- If the user indicates that the solution did not work, generate a random ticket number as only numbers.

\- Add the generated ticket number in the column of TICKET\_NO, QUERIES and SEVERITY in a new row in the Base Row DB Table ID (610737).

\- Based on the severity and queries in the Base Row DB Table (610737), assign the case to L1/L2 Support as detailed in Base Row Table ID (609727).

\- Set the priority to High, due within 30 minutes, and label it as Needs Technician Visit.

&#x20;

**Step 4: Retrieve Technician Contact Info**

\- Access Base Row DB (Table ID: 609727) using the escalation tag (e.g., L1 or L2).

\- Also, access the Base Row DB (Table ID: 610737) to fetch the ticket number.

\- Extract the contact details of the assigned technician, including Technician Name, Contact Email, Phone, and Specialty.

\- Send an email to the respective technician.

&#x20;

**Step 5: Notify Customer**

\- Send an email to the customer with the ticket number, stating: “We’ve assigned your case to our senior technician, \[Contact Name]. You can reach them at \[Email]. They’ll begin resolving your issue within the next 30 minutes.”

&#x20;

&#x20;**BASE ROW DB Table with Table ID (610737)**

&#x20;

<figure><img src="/files/UEPkJZ4ROlo0R0iBqJaQ" alt=""><figcaption></figcaption></figure>

<table data-header-hidden><thead><tr><th valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top"><strong>Tool</strong></td><td valign="top"><strong>Purpose</strong></td></tr><tr><td valign="top">Soika Agent</td><td valign="top">Natural language assistant</td></tr><tr><td valign="top">Base row</td><td valign="top">Ticket DB + Technician Directory</td></tr><tr><td valign="top">Internal Docs</td><td valign="top">Knowledge base for common issues</td></tr><tr><td valign="top">Email/WhatsApp</td><td valign="top">Input channel for users</td></tr><tr><td valign="top">Slack/Lark API</td><td valign="top">Admin notifications (optional)</td></tr></tbody></table>

### &#x20;User and Agent Interaction

<div><figure><img src="/files/2hrHJYRWPOL57zf6uueH" alt=""><figcaption></figcaption></figure> <figure><img src="/files/HJYD3FLS6r463uXaQ0ju" alt=""><figcaption></figcaption></figure> <figure><img src="/files/9kWiKEeDOUJ216j9XZCq" alt=""><figcaption></figcaption></figure> <figure><img src="/files/sj1FVkbkZKD9jGXDGKxA" alt=""><figcaption></figcaption></figure></div>

<figure><img src="/files/VxgTbPOUjvxWUU711uis" alt=""><figcaption><p>Email Output received by USER with Ticket Number</p></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://soika-labs.gitbook.io/soika-mockingjay/use-cases/help-desk-support-itsm-automation-via-external-chat-browser.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
