Put the Support Form Deflector on your support form in about ten minutes.

​
Before you start

  • A knowledge base with content indexed. It must not be an internal knowledge base.
  • An owner or admin role in the workspace.
  • A way to add a <script> tag to the page that holds the form.

​
Set up

1

Create the deflector

Go to Integrations → Support form deflectors and click Add deflector. Enter a name, pick the knowledge base, and pick a Public client key. To make one, click Create public key (New public key when the knowledge base already has keys). Click Create and set up.
2

Point it at the form

Inspect your support form in the browser and find two selectors:
FieldWhat to enterExample
Form selectorThe <form> element#new_request
Question fieldThe field where the reader describes the problem#request_description
Enter both on the Form wiring tab and click Save changes. A selector can be CSS, a name or an id. For fields inside an iframe or a shadow root, see Crossing DOM boundaries.
3

Rename the submit button

A button that says “Submit ticket” but opens an answer makes readers think the ticket was filed. On the Copy tab:
  • Set Submit button text while armed to something like Next step.
  • Set Notice shown before generating to a short line, such as “We’ll check for an answer first. If we can’t help, your ticket goes straight to our team.”
The button text needs a Submit element or Submit button selector (Form wiring tab, under Advanced). The save is refused without one.
4

Paste the snippet

Copy the Embed snippet from the Setup tab into the page with the form:
<script
  async
  src="https://widget.kelu.dev/kelu-widget.js"
  data-knowledge-base-id="YOUR_KNOWLEDGE_BASE_ID"
  data-client-key="kl_pk_..."
  data-deflector-id="YOUR_DEFLECTOR_ID"
></script>
This also starts the Ask AI widget, with its button in the page corner. To keep only the deflector, add data-launcher-button-hidden="true" and data-modal-open-on-command-k="false".
5

Test it

Add data-debug-mode="true" to the script tag. Open the page and submit a real question of at least 25 characters. localhost, 127.0.0.1 and ::1 always pass the deflector’s Allowed domains, so you can test locally. The public client key’s own allowed origins still apply, with no exception for localhost: if the key lists any origins, your local address must be one of them.Read the browser console:
You seeWhat it means
deflector: attachedThe form and question field were found
No attached lineA selector matched nothing within 10 seconds
question below the 25-character floorThe question was too short. Type a longer one
no deflectionIt ran, but no answer was confident enough to show
could not load configuration 403The page’s domain isn’t in Allowed domains or in the public key’s own Allowed origins, the knowledge base is internal, or the deflector is disabled
The ticket files with no pauseSet Intercept on to Click event (Form wiring, Advanced)
Remove data-debug-mode when you are done.
6

Go live

On the Setup tab, add your site under Allowed domains, one per line, with the scheme (https://support.example.com). https://*.example.com covers one level of subdomains. Empty allows any site.Leave Confidence threshold at 55% until the Activity tab shows a week of data.
If your public client key has its own Allowed origins, the support page’s domain must be listed there too.

​
Next

Behaviour

Every setting, attribute and default.

Zendesk support form

Step-by-step for Zendesk Guide.