A “Contact us” web form turns into a ticket the moment it’s submitted. The reply goes back by email to the address the visitor left — the same way email tickets work.
Two ways to use forms. Link the ready-made hosted form, or keep your own form and have it POST to AB Support. Either way, each submission is one ticket.
Option 1 — the hosted form
In Settings → Web forms, click Open hosted form and share its link, or embed it on your site. Nothing to build.
The hosted form follows each visitor’s own browser language. To pin one language instead, add ?lang=ja to its address. English and Japanese are translated today; any other value shows English. The chat widget works the same way and explains the rule in full.
Option 2 — POST your own form
Send your form’s fields to the endpoint as JSON:
POST https://blz.actionbridge.io/api/support/chat/form/submit
{ "widgetKey": "wk_your_key", "name": "…", "email": "…", "subject": "…", "message": "…" }The widgetKey is the same one your chat widget uses — copy it from Settings.
Your own form is your own to translate. Posting straight to the endpoint skips our pages entirely, so the labels and buttons are yours. What we still handle is the reply: the AI answers in the language the visitor wrote in, from knowledge base articles written in that language.
Regenerating the widget key breaks your form as well as your chat widget. They share one key. If you regenerate it, update
widgetKey here and data-key in the chat snippet.Form replies are emailed — so the mailbox has to be connected. Because the answer goes to the submitter’s email address, your support mailbox must be set up first. A form on its own will collect tickets you can’t reply to.
Forms are one of five ways in — see how customers reach you.