Skip to content

Docs: Add Customer Service Collaboration Use Case #19

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Docs: Add Customer Service Collaboration Use Case #19

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
25 changes: 24 additions & 1 deletion use_case.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -141,7 +141,30 @@ <h2>Use Cases</h2>

<section id="customer-service-collaboration">
<h3>Customer Service Collaboration</h3>
<p class="ednote">TODO: This section needs further development and refinement.</p>

<p><strong>Scenario Overview:</strong> A customer's flight with "ServiceAir" is delayed, and they wish to reschedule.</p>

<p><strong>Step 1 - Requirements Gathering:</strong> The customer's Personal Agent gathers the necessary information, including details of the existing reservation and the parameters for the rescheduled flight (e.g., desired time windows, acceptable layovers, cabin class).</p>

<p><strong>Step 2 - Authentication and Flight Lookup:</strong> The Personal Agent discovers the official ServiceAir Agent and uses the customer's identity credentials to authenticate. The Personal Agent provides the current booking details, which the ServiceAir Agent validates, confirming the reservation.</p>

<p><strong>Step 3 - Rescheduling Collaboration:</strong> The Personal Agent requests to reschedule the flight, providing the parameters gathered in Step 1. The ServiceAir Agent searches for available options and presents a structured list of potential flights to the Personal Agent. The Personal Agent can then either:
<ul>
<li>Autonomously select the best option based on the customer's pre-configured preferences (e.g., "lowest price" or "shortest travel time") and proceed to booking.</li>
<li>Present the curated options to the customer for a final decision (i.e., human-in-the-loop).</li>
</ul>
</p>

<p><strong>Step 4 - Rebooking Transaction:</strong> Once an option is selected (either autonomously or by the human-in-the-loop), the Personal Agent confirms the choice with the ServiceAir Agent. The ServiceAir Agent then initiates and completes the rebooking transaction, handling any associated payments or credits. The Personal Agent receives a final confirmation and reports the outcome to the customer.</p>

<p><strong>Collaboration Value:</strong> In this process, the Personal Agent acts as the customer's digital representative, and the ServiceAir Agent acts as the company's representative. This agent-to-agent collaboration, enabled by standardized protocols, creates significant efficiencies for both parties. The customer avoids hold times and complex web interfaces, while the company automates a high-volume service interaction, reducing operational costs and freeing up human agents for more complex issues.</p>

<p><strong>Requirements:</strong> <a href="#agent-identity-authentication">Agent Identity
Authentication</a>, <a href="#agent-discovery">Agent Discovery</a>, <a
href="#agent-interaction">Agent Information Interaction</a>, <a href="#agent-transactions">Agent
Transactions</a>, <a href="#privacy-protection">Privacy Protection</a>, <a
href="#identity-interoperability">Identity Interoperability</a></p>

</section>

<section id="hotel-booking">
Expand Down