All postsAI support

Let your support AI do things for customers with webhook actions

Many support questions need something done: check an order, start a backup, resend a key. An AI that can only answer passes those to a person. Actions let FiveBot call your own HTTPS endpoint for them, in the Hollo website chat and in Discord tickets, and reply with what your server sent back.

An example from FiveDock

FiveDock, a backup and hosting tool for FiveM servers, runs FiveBot as the chat on its site. A signed-in user writes "back up my server". The AI already knows which servers that user has, because FiveDock passes them in when the chat opens, and asks which one if there's more than one. It then shows a card with the server name and a Run button. One press, FiveDock's endpoint starts the backup, and the chat says it's running.

The same works for "is my server online?" or "restore Kowalski's inventory from yesterday".

Defining an action

Under Settings, AI, Actions you can add up to 10. Each one has:

  • a name and a sentence saying when to use it;
  • the HTTPS address FiveBot calls;
  • up to five typed fields, such as a server name or a number of hours, which the AI fills in from the conversation;
  • Run without asking, for safe reads like a status check;
  • an on/off switch.

Send test fires a sample call and shows the status code and how long it took. The page also shows the last 10 calls.

Who can trigger one

Actions run only for people FiveBot can identify: a website visitor your site signed when the chat opened, or the person who opened a Discord ticket. Anonymous visitors and email get answers from your knowledge base and nothing more.

The AI checks the fields against the types you set. If a value is missing, it asks one short question and names the choices. Unless the action runs without asking, the customer gets a card in the chat, or buttons in Discord, with Run and Cancel.

What your endpoint receives

A POST with the action, its fields, the user and the ticket, signed with your workspace's signing secret:

FiveBot-Signature: t=<unix time>,v1=<HMAC-SHA256 of t.body>

The settings page has a Node snippet that checks the signature. FiveBot resolves the address first and refuses private and local networks, doesn't follow redirects, waits 10 seconds at most and reads up to 16 KB of the reply. The reply is treated as data, so text inside it can't give the AI new instructions.

Cost

Each call costs one AI credit on top of the answer and shows up as Actions in the credit log. Every call is logged with its result.

Questions people ask

Which plan do I need?

Pro or Network. Prices are on fivebot.ai/pricing.

Can a customer trick the AI into acting for someone else?

FiveBot takes the user from the signature your site created or from the Discord account that opened the ticket, and your endpoint gets that identity with every call. Details that look like an attempt to give the AI instructions are dropped.

How does my site sign a visitor?

Your backend signs the visitor with the Hollo identity secret and passes the result to FiveBot.identify. More about Hollo.

How is this different from assistant actions?

Assistant actions are for you and your staff and fire events or commands on your FiveM server. Webhook actions are for your customers and call any HTTPS endpoint you run. Assistant actions.

Keep reading

Your staff has answered that one forty times today.

Setup takes about ten minutes, and there's no cap on tickets.