FRIDAY, OCTOBER 9

Good morning, Rakesh ☀

A clearer view of your support, with a little help from AI.

Total tickets

248

↗ 12.4%vs. last week

AI assisted

186

75%of all tickets

First response

4m 12s

↓ 28%faster this week

Needs approval

1

Your action

Support at a glance

AI assistedTeam only

Ticket volume · last 7 days · illustrative data

WORKFLOWS ARE RUNNING

Your support team,
with more room to breathe.

AI reads the request, finds the right context, and prepares the next step.

EmailSQL & NoSQLAPIs

Tickets that need a look

Ticket	Status	Next step

Recent activity

Live demo

Ticket inbox

Every conversation, its context, and a clear next step.

Try “Simulate intake” on a ticket

All conversationsNewest first

AI workflows

Turn incoming requests into the right actions.

Incoming support request

Active

1. Receive a requestEmail, customer portal, or a custom form

3. Check access & routing rulesWorkspace, requester identity, tool permissions

Read contextApproved MCP lookupSQL · NoSQL · API

Request approvalRefund or restricted changeApprove → execute & resolve

Hand offUnclear or missing detailsNo tool execution

4. Prepare reply & update ticketShow evidence, tool results, and action history

5. Send, follow up & resolveAutomatic resolution where complete · SLA · replies

One MCP layer routes approved tools to the correct customer connection.

Classification & tool routing

When the request is about

Use this approved toolThe connector executes a prepared query or API action.

Minimum classification confidenceIllustrative threshold. Validate it with real support requests.

Approve critical actionsRefunds and restricted changes pause for a personRequired

Auto-resolve routine requestsOnly a verified answer that completes the request

Escalate unanswered ticketsNotify team lead after the SLA deadlineEnabled

Low confidence, failed identity checks, missing identifiers, or tool failures send the ticket to a person.

Configured routes

Workspace: Acme

Connections

Give your agents the context they need, through one MCP layer.

How a lookup travels

Ticket intentApproved toolMCP hubCustomer connectorScoped result

Form builder

A support process that fits each customer’s work.

CUSTOMER PORTAL

Start from a template

Form title

Description

Route submissions to

Submissions create tickets and scoped records in the product’s managed data store. Customers can also connect their existing systems.

Live form previewCustomer view

Acme Support

Request a service

This prototype stores sample submissions only in memory. Refreshing resets them. A production version stores form definitions, submissions, and ticket links per customer.

Customers & setup

The same product, configured for different businesses.

Customer workspaces

Platform owner view

Customer	Deployment	Inbound email	Configuration

Platform management is restricted to the owner. Customer agents see only their own workspace.

Deployment & commercial model

Choose how the current customer runs the product.

Hosted on your servers

Customer workspace, forms, tickets, and connectors. Upfront setup plus ongoing hosting and usage costs.

Installed on the customer’s server

One product package, including the MCP connector hub. Upfront licence; customer manages infrastructure and AI usage.

Sell the full product

Transfer the agreed product assets and rights to a buyer. Include deployment instructions, code, and handover.

A customer’s setup checklist

Workspace & teamCustomer identity, agents, approvers, roles

Support mailboxRead inbound mail; configure sending separately

Forms & workflowFields, queues, SLA rules, approvals

Connections & AI toolsPrepared queries, API actions, data permissions

Activity log

See what the agent read, who approved, and what happened next.

Production audit events should include workspace, actor, tool, record scope, approvals, and execution outcome. Secrets are never shown here.

Acme Logistics · recent events

Traceable actions