Have Claude build a ticket view
In short: A ticket view is an extra tab next to the ticket that shows data from a connected system, for example the customer’s file, an overview of appointments or an order history. You do not build such a view in aishaa itself: you design it together with Claude through the aishaa MCP connection. Claude writes the view, you look at it through a preview link, and Claude only publishes it once you approve. After that, you manage the view in the View library.
Where to find this
The design work happens in Claude, not in aishaa. First connect aishaa to Claude as a connector; see Connect aishaa to Claude or ChatGPT (MCP). Then ask Claude for a ticket view in plain language.
The result appears in aishaa under Organisation > View library. On the detail page of a view there, you see the chip Edited through MCP: for a new version, you ask Claude again.
Who: from the Organisation admin role upwards. The view applies to the organisation Claude creates it for. If you have access to several organisations, mention in your request which organisation it is for.
You need at least one integration that supplies the data the view should show. See Set up an integration.
What a ticket view is for
A ticket view answers one question: what does a colleague need to see about this customer while handling the ticket. The view does not retrieve the data itself; it shows what aishaa has already retrieved for the ticket from your connected systems.
- A ticket view consists of data boxes: one box per type of data (for example a file, a schedule or an order history) that aishaa fills with what was found for this customer.
- The view decides how that data looks: which fields are at the top, what you need to see at a glance and what can be left out.
- A ticket view can also contain buttons: for an extra request, for example retrieving a document, or for a plugin action. See To do.
- By default, the tab only appears on tickets for which there is data. Claude can also make the view so that the tab is always there.
An open ticket with a ticket view as its own tab next to the conversation, with the title of the view as the tab title.
How it works, step by step
You do not carry out these steps yourself; Claude does. They are listed here so you know what happens and what to look out for.
- Claude reads the contract first. There is a fixed writing guide for ticket views: what a view is allowed to do, which data it receives and what it must comply with. Claude reads it before writing anything.
- Claude checks which data is available. For each connected plugin, Claude retrieves which types of records there are, which data can be retrieved, what it looks like and which actions exist, including the plugin’s sample responses. No customer data is used for this.
- You say what you want to see. Describe in plain language what should be on the tab and what you use it for. The more specific you are, the less back and forth.
- Claude saves a draft. The draft appears in the view library straight away with the chip Draft. Nothing changes yet in what your team sees.
- You get a preview link. Claude gives you a link to a preview page of the view. That page opens without signing in, is valid for one week and only shows sample data, no customer data. So you can also open it in a browser in which you are not signed in to aishaa. You also get a link to the view’s detail page in aishaa.
- You review the view in different states and screen widths. Ask Claude to show the view with complete data, with partial data, without data, while the data is still being retrieved and after retrieving has failed. Also ask for desktop, tablet and mobile. That way you know the view also works when a customer is slightly different from the example. If an example does not tell you enough, Claude can show the view with the data recorded for a real ticket; mention the ticket number.
- Adjust until it is right. Say what needs to change. Claude writes a new version of the draft and gives you a new preview link.
- Publish. Claude only publishes the view once you approve. It then becomes the current version and appears as a tab on your organisation’s tickets for which there is data.
Which role you need
You need at least the Organisation admin role. With a lower role, the view functions in the connection are not available.
One exception: if another organisation in the same account uses the version you want to replace, that is an account decision. Publishing then only works with the Account admin role. Claude tells you if this is the case.
What you do yourself in the view library afterwards
Designing and adjusting happens through Claude; you manage the view in aishaa, under Organisation > View library:
- switch the view on or off as a tab, with Show as ticket tab and Deactivate, and as an Account admin for all organisations in the account;
- Change name and description, without affecting the design;
- Archive view and Restore from archive;
- Delete draft if you no longer want a draft;
- view the Version history and go back to an earlier version with Restore this version;
- lock the view once it has been checked and is right, so that nobody changes it any more.
See View library.
Good to know
- aishaa does not create ticket views by itself. Every ticket view of your organisation was either supplied by aishaa or created through the Claude connection on your own account.
- Requesting the available data sources does not touch any customer data: Claude receives the descriptions and the sample responses of the plugins. Only if you ask for it yourself does Claude look at the data of one ticket.
- The preview link belongs to exactly that version of the view. If Claude saves a new version, it gets a new link; an old link therefore never shows a different version from the one it was made for.
- Publishing never happens by itself. Claude only publishes after you have said it is right.
- A ticket view only shows data that aishaa has retrieved for the ticket. If Customer records for the integration is set to Off, the view stays empty. See Plugin settings: customer data, catalogues and actions.
- Every publication is a new version. Earlier versions are kept in the Version history on the detail page in the view library.
- Once a view is locked, nobody can change it, not even aishaa or the assistant, until an Account admin unlocks it in the app.