Sanaf AI
Start free
Customer Support

Gleap, worked by an AI employee

Not another app for your team to learn, and not a set of rules for you to build. You hire an AI employee, you give it access to your Gleap account, and you ask it for things in Slack or Teams the way you would ask anyone else on the team. There is nothing to map and nothing to maintain.

  • Customer Support
  • Connects with a key
  • 29 ready-made tools
  • Asked in Slack or Teams
At work

An illustration of how the conversation reads, not a transcript from a client account.

What Gleap is

Gleap is an all-in-one customer feedback tool for apps and websites, enabling direct communication with users to build better software by discovering their everyday pain points.

You paste in a key from your own Gleap account. It is kept encrypted, and you can withdraw it from inside Gleap whenever you like.

How a run works

One message in, the work done in Gleap.

  1. 01

    You ask

    You message your AI employee in the chat your team already has open, in one sentence, in your own words.

  2. 02

    It works out the step

    It decides what the job needs in Gleap. You do not pick anything from a menu or wire anything together.

  3. 03

    It does the work

    Signed in to your own Gleap account, inside the access you granted it, doing the thing you asked for.

  4. 04

    It reports back

    It tells you what it did, in the same thread. If it could not do something, it says so rather than guessing.

29 tools it already has

What it can do in Gleap

These are the ready-made tools your AI employee already has in Gleap. It is not limited to them, but it never has to be taught these.

  • Archive a TicketTool to archive a ticket. Use after confirming the ticket ID and that the ticket is resolved. Call when moving tickets to history.
  • Create a CollectionTool to create a help center collection. Use when adding a new organizational grouping in your Help Center.
  • Create a new chat messageTool to create a new chat message. Use when sending a message in an active chat session.
  • Create a new teamTool to create a new team. Use when you have team details ready and want to assign tickets among members.
  • Create a new ticketTool to create a new ticket. Use when you have ticket details ready to open a support ticket.
  • Delete a User from a ProjectTool to remove a user from a project. Use when you need to revoke a user's access by their ID.
  • Get a ChecklistTool to retrieve a specific engagement checklist by its ID. Use after obtaining a valid checklistId.
  • Get a CollectionTool to retrieve a help center collection by ID. Use when you need to fetch specific collection details by its ID.
  • Get a ticketTool to retrieve a specific ticket by its ID. Use after confirming the ticket ID. Returns full ticket details.
  • Get all articlesTool to retrieve all articles in a help center collection. Use when you have a helpcenterCollectionId and want to list its articles.
  • Get all chat messagesTool to retrieve all chat messages. Use when you need to list full conversation history.
  • Get All CollectionsTool to retrieve all help center collections. Use when you need to list all collections for the authenticated project.
  • Get All Invitations for a ProjectTool to retrieve all invitations for a project. Use when you need to list every pending or accepted invitation within the current project context.
  • Get all sessionsTool to retrieve all sessions for the current project. Use after project context is confirmed. Fetches all user sessions for analysis or reporting.
  • Get All TeamsTool to retrieve all teams. Use when you need a list of all teams for the authenticated project.
  • Get All TicketsTool to retrieve all tickets. Use when you need to list all tickets for the authenticated project.
  • Get All Users for a ProjectTool to retrieve all users for a project. Use when you need to list every user associated with the current project.
  • Get current userTool to retrieve the currently authenticated user's details. Use when you need the user's profile and settings.
  • Get Help Center SourcesTool to retrieve available help center sources. Use when you need to list all help center sources for a project.
  • Get notification ticketTool to retrieve a notification ticket using its share token. Use when you have a share token and need to fetch ticket details.
  • Get session checklistsTool to retrieve checklists for a given session. Use after confirming a valid sessionId. Returns all checklists associated with the specified session.
  • Identify or update userTool to identify or update user information. Use when you need to sync server-side user profile after authentication.
  • Link a TicketTool to link a ticket. Use when you need to connect two existing tickets after confirming both IDs exist. Example: Link a duplicate issue ticket to its original.
  • Search for TicketsTool to search for tickets. Use when needing to find tickets based on search criteria.
  • Track eventsTool to track server-side customer events. Use when you have collected a batch of events and want to send them to Gleap via the /admin/track endpoint.
  • Unarchive a TicketTool to unarchive a ticket. Use when you need to restore a previously archived ticket after validation.
  • Unlink a TicketTool to unlink a ticket. Use after confirming both tickets are linked to remove their association.
  • Update a User for a ProjectTool to update a user’s role in a project. Use when you need to change a user's permissions.
  • Update Chat MessageTool to update a chat message. Use when you need to modify the content of an existing chat message after obtaining its ID.
Access, and who is in charge of it

You stay the boss of your Gleap account.

Nothing connects until you approve it. You grant access one app at a time, you can take it back the same way, and everything your AI employee does in there is written down where you can see it.

How we handle your data
  • It signs in to your own Gleap account. You are not moving anything into ours.
  • You grant access one app at a time, and you can take it back the same way.
  • Everything it does in Gleap is written down, with what it did and when.
  • Anything you tell it to check with you first, it checks with you first.
Other apps in the same corner of the business

It works in Gleap and the rest of your software in the same job

A real job rarely stays in one place. Reading a message in one app, checking a record in another and writing the result in a third is one request to your AI employee, not three.

See every app

Questions people ask about Gleap

Can an AI employee really work inside Gleap?
Yes. It signs in to your own Gleap account and works in it the way a new hire would, from the chat your team already has open. Nobody installs anything, and nobody learns a new screen.
Do I have to move anything out of Gleap?
No. Nothing moves and nothing is replaced. Your records stay in Gleap, your team carries on in the same screens they used yesterday, and your AI employee works alongside them in there.
How does it get into my Gleap account?
You paste in a key from your own Gleap account. It is kept encrypted, and you can withdraw it from inside Gleap whenever you like. You approve it before anything connects, and you can take the access back the same way you gave it.
What can it actually do in Gleap?
It has 29 ready-made tools in Gleap today, among them Archive a Ticket, Create a Collection and Create a new chat message. The full list is on this page. It is not limited to those, but it never has to be taught them.
Can it use Gleap and the rest of my software in the same job?
Yes, and that is usually the point. Reading a message in one app, checking a record in Gleap and writing the result somewhere else is one request to your AI employee, not three separate ones you stitch together.
Who decides what it is allowed to do in Gleap?
You do. You grant access one app at a time and can withdraw it at any time, anything you ask it to check with you first it checks with you first, and everything it does in Gleap is written down with what it did and when.